A Digital Fault Recorder (DFR) is a specialized Intelligent Electronic Device (IED) installed in substations to capture high-fidelity, time-synchronized waveform data during electrical anomalies. Unlike simple event loggers, a DFR continuously samples analog inputs at high rates—typically 96 to 256 samples per cycle—and uses configurable triggers such as undervoltage, overcurrent, or rate-of-change-of-frequency to permanently store pre-fault, fault, and post-fault data segments.
Glossary
Digital Fault Recorder (DFR)

What is a Digital Fault Recorder (DFR)?
A Digital Fault Recorder (DFR) is a dedicated data acquisition device that continuously monitors and records high-resolution voltage and current waveforms, triggering permanent storage during power system disturbances for post-fault analysis and COMTRADE file generation.
The primary output of a DFR is a COMTRADE (IEEE C37.111) file, a standardized format containing both the raw waveform samples and configuration metadata. Protection engineers use these files with analysis software to perform fault location, validate protection relay operation, and assess CT saturation behavior. Modern DFRs support IEC 61850 sampled values and GOOSE messaging, integrating directly into digital substation architectures for centralized disturbance monitoring.
Key Characteristics of a DFR
A Digital Fault Recorder is defined by its ability to capture high-fidelity, time-synchronized waveform data during power system disturbances. These characteristics distinguish it from simple sequence-of-event recorders or SCADA alarms.
High-Resolution Waveform Sampling
DFRs sample analog voltage and current inputs at rates typically between 1 kHz and 15 kHz (for 50/60 Hz systems), providing granular detail of transient phenomena. This high sampling rate captures harmonic content and high-frequency traveling waves that slower SCADA scans miss.
- Sampling Rate: 96–256 samples per cycle is standard.
- Bit Depth: 16-bit or 24-bit analog-to-digital converters ensure dynamic range.
- Anti-Aliasing: Hardware filters prevent distortion above the Nyquist frequency.
Continuous Circular Buffer Recording
The DFR writes continuously to a circular memory buffer, overwriting old data. When a trigger condition is met, the buffer freezes, capturing a configurable window of pre-fault, fault, and post-fault data.
- Pre-fault Duration: Typically 100 ms to 5 cycles.
- Total Record Length: Often 1–10 seconds, configurable per channel.
- Storage: Data is saved to non-volatile memory to survive station power loss.
Multi-Channel Analog and Digital Inputs
A single DFR unit monitors multiple signals simultaneously, providing a correlated view of the event. This includes phase voltages, currents, and binary status signals from protection relays and circuit breakers.
- Analog Channels: Typically 8, 16, or 32 inputs for CT and VT secondaries.
- Digital Channels: 16–64 opto-isolated inputs for trip signals, breaker status (52a/52b), and communication flags.
- Cross-Triggering: A trigger on any single channel captures all channels synchronously.
Sophisticated Triggering Logic
DFRs use complex, programmable triggers beyond simple magnitude thresholds. Triggers can be set for rate-of-change, harmonic content, or sequence components to detect subtle faults.
- Over/Under Threshold: Magnitude triggers on RMS or instantaneous values.
- Rate-of-Change (dv/dt, di/dt): Detects fast transients.
- Symmetrical Components: Triggers on negative-sequence or zero-sequence overcurrent.
- External Trigger: Accepts a binary input from an external protection relay.
Precise Time Synchronization
Accurate time-stamping is critical for correlating events across a wide-area network. DFRs use an internal GPS receiver or an external IRIG-B signal to synchronize their internal clocks.
- Accuracy: Typically ±1 microsecond to UTC.
- IRIG-B: Industry-standard unmodulated or modulated time code.
- IEEE 1588 (PTP): Increasingly used in digital substations for sub-microsecond synchronization over Ethernet.
COMTRADE File Generation
The DFR stores disturbance records in the IEEE C37.111 (COMTRADE) standard format. This ensures interoperability with any vendor's analysis software.
- .CFG File: Configuration file describing channel scaling and sampling rate.
- .DAT File: Data file containing the actual sample values in binary or ASCII.
- .HDR File: Optional header file with free-form text about the event.
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 answers to the most common technical questions about Digital Fault Recorders, their operation, and their role in modern grid protection.
A Digital Fault Recorder (DFR) is a dedicated data acquisition device that continuously samples high-resolution voltage and current waveforms from instrument transformers, storing a circular buffer of data and triggering permanent recording when a disturbance violates user-defined thresholds. It works by monitoring power system quantities at sampling rates typically between 4 kHz and 15 kHz, enabling the capture of high-frequency transients that slower SCADA systems miss. When a trigger event occurs—such as an undervoltage, overcurrent, or rate-of-change-of-frequency excursion—the DFR timestamps the event using a GPS-synchronized clock, saves the pre-fault, fault, and post-fault data to non-volatile memory, and generates a COMTRADE (IEEE C37.111) file for analysis. Modern DFRs also perform continuous synchrophasor streaming and can trigger cross-triggers across multiple substations via IEC 61850 GOOSE messaging, providing a wide-area view of cascading disturbances.
Related Terms
Digital Fault Recorders are the primary data source for a suite of analytical and protective technologies. These related concepts define how raw waveform data is captured, communicated, and utilized to automate grid recovery.
Fault Detection, Isolation, and Recovery (FDIR)
The automated control loop that consumes DFR data to restore service. FDIR systems use fault passage indicators and IED status to:
- Detect the fault's presence and type
- Isolate the smallest possible network segment
- Recover healthy sections via alternative feeders DFR recordings validate that FDIR logic operated correctly, providing the ground truth for protection coordination audits.
Traveling Wave Fault Location
A high-precision method that captures the high-frequency electromagnetic transients generated at the fault inception. By timestamping the arrival of these traveling waves at line terminals, the fault position is calculated to within a single tower span.
- Requires sampling rates of 1 MHz or higher
- Immune to fault resistance and line loading
- DFRs with high-speed sampling modules are the primary capture devices for this technique.
IEC 61850 GOOSE Messaging
The peer-to-peer communication protocol that enables bay-to-bay interoperability in digital substations. Generic Object Oriented Substation Event (GOOSE) messages replace hard-wired binary signals.
- Published by IEDs on a multicast basis
- Latency requirements as low as 3 ms for tripping applications
- DFRs subscribe to GOOSE messages to record the exact sequence of protection commands alongside analog waveforms, providing a complete event timeline.
Protection Coordination Study
The engineering analysis that ensures selectivity—the device closest to a fault trips first. Engineers use DFR recordings to:
- Validate that actual fault currents match the study assumptions
- Verify IDMT curve timing in real-world conditions
- Identify miscoordinations caused by distributed generation infeed DFR data closes the loop between theoretical time-current coordination and actual field performance.
Wavelet Transform Fault Detection
A signal processing technique that decomposes DFR waveforms into time-frequency components. Unlike Fourier analysis, wavelets capture transient singularities with high temporal resolution.
- Detects high-impedance faults invisible to fundamental frequency relays
- Identifies incipient cable defects from partial discharge signatures
- Serves as a feature extractor for deep learning fault diagnosis models trained on DFR archives.

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