Fact-checked by Grok 2 weeks ago

Comtrade

COMTRADE (Common format for Transient Data Exchange) is an international standard that defines a file format for exchanging transient data from power systems. Developed by the IEEE Power System Relaying Committee and adopted by IEC, it is specified in IEEE/IEC standard C37.111. The format enables the storage and interchange of oscillography, status, and other data related to power system disturbances for analysis, testing, simulation, and archival purposes.^[1] The standard includes configuration (.cfg), data (.dat), header (.hdr), and information (.inf) files, supporting both analog and digital channels with precise time tagging to facilitate cross-vendor compatibility in protective relaying and fault analysis. It covers transient events in electrical power systems, encompassing over 99% of global utility practices through widespread adoption.^[2] Originally published in 1991, COMTRADE has evolved through revisions in 1999 and 2013 to address advancements in data handling and synchronization requirements.^[3]

Overview

Definition and Purpose

COMTRADE, which stands for Common Format for Transient Data Exchange, is a standardized file format developed for the interchange of transient data in electrical power systems.^[2] It provides a vendor-independent method for storing and exchanging oscillography and digital status data captured during power system disturbances, such as faults, transients, or other short-duration events.^[4] This format ensures that data from protective relays, digital fault recorders, and other monitoring devices can be shared seamlessly across different systems and organizations.^[5] The primary purpose of COMTRADE is to facilitate interoperability among equipment from various manufacturers, allowing engineers to analyze transient events without compatibility issues arising from proprietary formats.^[6] By standardizing the representation of waveform and event data, it supports consistent evaluation of power system reliability and performance, enabling utilities and researchers to identify causes of disturbances and improve grid stability.^[7] For instance, during a fault, COMTRADE captures detailed records that aid in post-event analysis and simulation validation.^[8] Transient data in this context refers to high-resolution waveform captures of voltage and current, along with binary states representing logical events like breaker operations or relay triggers, all occurring over brief time intervals typically lasting milliseconds to seconds.^[9] This structured approach promotes efficient data exchange for applications in power quality monitoring and system testing, ultimately contributing to enhanced operational safety and efficiency in electric grids.

Scope and Standardization

The COMTRADE format is primarily governed by the IEEE Std C37.111, a standard developed by the IEEE Power System Relaying and Control (PSRC) Committee within the IEEE Power and Energy Society.^[1] This standard establishes a common framework for exchanging transient data files in power systems, ensuring interoperability among devices and analysis tools.^[10] An equivalent international standard, IEC 60255-24, has been harmonized with IEEE C37.111 to facilitate global adoption and consistency in transient data handling. This alignment allows for seamless use across international borders, particularly in regions adhering to IEC guidelines for electrical relays and protection equipment.^[1] The scope of COMTRADE is limited to short-duration transient data from power systems, such as high-resolution captures of voltage, current, and binary events during faults or disturbances, typically spanning up to a few seconds to focus on dynamic phenomena.^[10] It does not encompass steady-state monitoring or long-term power quality assessments, which are addressed by formats like PQDIF under IEEE Std 1159.3.^[11] The standard explicitly applies to files stored on physical media or offline exchange, excluding real-time data transfer protocols.^[1] COMTRADE has seen widespread adoption in substation environments, where it is employed by protective relays, digital fault recorders, and monitoring equipment to capture and share event data for post-incident analysis.^[12] This usage supports critical functions like relay testing and system validation without requiring proprietary formats.^[13]

Technical Specifications

File Structure

The COMTRADE file structure is designed to facilitate the modular exchange of transient data, typically organized into a set of four core files sharing a common base name but distinguished by extensions: .CFG, .DAT, .HDR, and .INF.^[3] The .CFG file serves as the mandatory configuration file, providing essential metadata in ASCII text format to define the overall structure and parameters for interpreting the data.^[4] It includes details such as the station name (e.g., "SMARTSTATION"), recording device identifier (e.g., "IED123"), revision year of the standard compliance (e.g., 2013), total number of analog and digital channels, line frequency, sampling rates per channel group, start and trigger dates/times, and channel-specific information like identifiers, phases, units, primary and secondary scaling factors, and minimum/maximum values.^[14] This file ensures interoperability by specifying how the recorded data aligns with power system conventions, without containing the actual measurements.^[15] The .DAT file is the mandatory data file that holds the core transient content, capturing time-synchronized analog waveforms (e.g., voltage and current samples) and binary digital status points (e.g., relay contacts or breaker states).^[4] It can be formatted in ASCII text or binary modes, as declared in the .CFG, and stores sequential samples from pre-trigger to post-trigger periods, directly reliant on the .CFG for channel ordering, scaling, and timing interpretation.^[3] The .HDR file, optional and in ASCII text, offers a human-readable summary of the .CFG contents, often including descriptive notes on the event such as fault type, system conditions, or recording triggers to aid quick reference without parsing the configuration.^[14] Similarly, the .INF file, also optional and ASCII-based, accommodates supplementary information like revision history, manufacturer-specific notes, or additional context, structured into public (interoperable) and private (proprietary) sections for flexibility across vendors.^[15] Introduced in the 2013 revision, the .CFF variant provides a compact single-file alternative, consolidating the .CFG, .INF, .HDR, and .DAT components into one self-contained file with extension .CFF.^[14] Sections within the .CFF are delimited by clear markers (e.g., "--- file type: CFG ---"), preserving the logical separation and relationships of the multi-file format while simplifying storage and transmission—reducing the file count from four to one without altering the underlying organization.^[3] All files in the structure, whether multi-file or .CFF, adhere to the .CFG-defined metadata for consistency, with encoding options (ASCII or binary) specified therein to support diverse applications in power system analysis.^[4]

Data Encoding and Formats

The COMTRADE standard, as defined in IEEE Std C37.111, specifies multiple encoding formats for the data file (.DAT) to represent transient recordings efficiently and accurately. The ASCII format uses plain text with comma-separated values, making it human-readable and suitable for direct inspection, though it produces larger files due to the overhead of textual representation. In contrast, the 16-bit binary format employs two-byte two's complement integers for compact storage of analog samples, ranging from -32768 to 32767, which balances file size and precision for typical power system applications. The 32-bit binary format extends this to four-byte integers for enhanced dynamic range, while the IEEE 754 32-bit floating-point format (introduced in the 2013 revision) allows for high-precision representation of fractional values without loss of significant digits, particularly useful for simulations or high-fidelity measurements.^[16] Analog channels capture time-synchronized samples of continuous waveforms, such as voltage or current signals from protective relays, with each sample encoded according to the selected format to preserve waveform integrity. Digital channels, on the other hand, store binary states (0 or 1) for discrete events like relay operations or circuit breaker trips, often packed into words for efficiency in binary modes. These channels are defined in the configuration file (.CFG), ensuring that the data reflects the physical phenomena with appropriate synchronization across all recordings.^[4]^[16] Sampling in COMTRADE files supports both uniform rates, where fixed intervals apply throughout a record, and non-uniform rates for variable-speed captures, as specified in the .CFG file's sample rate table. Time stamps are recorded in UTC, providing resolution down to microseconds to align samples precisely with real-world events and facilitate multi-device correlation. For instance, the first line of the .DAT file in ASCII mode includes the absolute time of the initial sample, followed by relative intervals.^[4]^[16] Raw values in the .DAT file are scaled to physical units using conversion factors outlined in the .CFG file, following the equation actual_value = (raw_value × A) + B, where A is the primary scaling factor and B is the offset. This allows encoded integers or floats to map directly to engineering units like volts or amperes, with factors tailored per channel to account for transducer characteristics.^[4]^[16] The standard imposes certain limitations on data representation, for example, typical recorders support 16 to 128 analog channels in early versions like IEEE Std C37.111-1999, to maintain compatibility with legacy systems, and it does not include mechanisms for data compression, prioritizing straightforward interchange over size optimization. These constraints ensure broad interoperability but may require segmentation for recordings with extensive channel counts in modern applications.^[2]

Evolution of the Standard

Initial Development (1991)

The COMTRADE standard originated with the publication of IEEE C37.111-1991 by the IEEE Power System Relaying Committee (PSRC), aimed at establishing a common format for exchanging transient data from protective relays to resolve interoperability issues among diverse recording devices.^[17]^[7] This standard addressed the growing challenges in the power industry during the late 1980s and early 1990s, when the proliferation of microprocessor-based digital protective relays generated increasing volumes of transient data that could not be easily shared across different vendors' systems or utilities.^[18]^[15] Prior to this, engineers relied on ad-hoc methods for data transfer, such as proprietary formats or manual conversions, which hindered efficient analysis of faults and relay performance.^[15] The development was driven by the PSRC's recognition of the need for a standardized approach to facilitate evaluation of relay operations using digital fault recorder outputs.^[3] The initial specification introduced a simple file structure consisting of ASCII-based configuration (.CFG) and data (.DAT) files, along with an optional information (.INF) file for auxiliary details.^[15]^[19] Key features included support for multiple analog and digital channels—typically up to 16–64 analog channels for voltages and currents, and a comparable number of digital status inputs—allowing representation of transient waveforms and binary events like relay trips.^[19] Basic metadata in the .CFG file captured essential parameters such as sampling rates (often in the range of 1 kHz or higher, up to several kHz depending on the recorder), line frequency, channel assignments, and scaling factors to ensure accurate reconstruction of events.^[19]^[20] This design prioritized human readability and portability across early computing environments, with data stored in a tabular ASCII format where each row represented a time step and columns corresponded to channel values.^[19] Early adoption of the 1991 standard occurred primarily among North American utilities and relay manufacturers, where it was used for post-event fault analysis following disturbances and blackouts.^[9] By mid-1991, beta versions of supporting software were distributed to over 50 utilities and vendors, enabling initial interoperability in analyzing transient data from digital relays and fault recorders.^[9] This facilitated quicker diagnostics of protection system behavior during events, reducing the time required for manual data formatting.^[3] However, limitations emerged soon after implementation, particularly with the ASCII-only data encoding, which resulted in large file sizes due to the verbose representation of numerous time-sampled values in text format.^[19]^[20] The absence of binary support exacerbated storage and transfer inefficiencies on the hardware of the era, such as floppy diskettes, often necessitating multiple files for longer recordings.^[19] Additionally, constraints on channel counts and fixed sampling structures proved restrictive for evolving recorder capabilities, prompting calls for revisions in subsequent years.^[3]

Major Revisions (1999 and 2013)

The 1999 revision of the COMTRADE standard, designated IEEE C37.111-1999, introduced significant enhancements to address limitations in file handling and data representation from the prior version. A key update was the specification of a 16-bit binary format for the .DAT file, which stored samples as integer counts to reduce file sizes and eliminate the need for user-supplied conversion programs previously required for binary data. This change targeted the inefficiency of ASCII-based .DAT files, which often resulted in bloated storage for large datasets typical in power system transients. Additionally, an optional .INF file was added to accommodate supplementary public or private information not covered in the core files, enhancing flexibility for users. The .CFG file saw improvements, including new fields for instrument transformer scaling ratios (primary, secondary, and primary-secondary), a floating-point line frequency entry, expanded status channel details (up to five fields), and support for variable sampling rates in event-triggered modes, which facilitated better fault location analysis through precise scaling and timing data.^[21]^[22] The 1999 standard was reaffirmed in September 2004 by the IEEE Power System Relaying Committee Working Group H5d, incorporating only minor clarifications without substantive changes to the core specifications. This reaffirmation ensured continued relevance amid evolving power system needs while maintaining backward compatibility.^[14] The 2013 update, IEEE C37.111-2013 (also adopted as IEC 60255-24 Edition 2.0), built on these foundations by accommodating higher-resolution data from modern intelligent electronic devices (IEDs) and phasor measurement units (PMUs). It introduced 32-bit binary (Binary32) and 32-bit floating-point (Float32, per IEEE 754-2008) formats for the .DAT file, enabling precise representation of analog values beyond the 16-bit integer limits. Time tagging was enhanced with support for fractional seconds up to 1 ns resolution, time zone offsets via a new Time Code field (e.g., "-5h30" for UTC), Local Code for timezone identification, Time Quality Indicator (e.g., hexadecimal 'B' for maximum error), and Leap Second Indicator for adjustments. A new .CFF single-file format was defined, consolidating .CFG, .INF, .HDR, and .DAT sections into one UTF-8 or binary file for simplified exchange, with filenames extended to 64 characters per IEEE C37.232-2007. Metadata in the .CFG was expanded for synchrophasor support, including critical fields like channel ID (ch_id) and skew, alongside an informative Annex H outlining a synchrophasor schema developed by a 2008 PSRC task force. These updates addressed the demands of smart grid applications requiring universal time synchronization, as highlighted by the 2003 Northeast Blackout, and removed 1990s-era computational restrictions for broader interoperability.^[3]^[14] Since the 2013 revision, no full new standard has been issued, though a 2021 PSRC Working Group H35 technical report titled "COMTRADE: Next Generation" proposed upgrades including data compression techniques and XML-based structures for configuration and metadata to improve efficiency and integration with standards like IEC 61850 and CIM; these recommendations remain unadopted pending further IEEE/IEC dual-logo development.^[23]

Applications

Disturbance Recording in Power Systems

Disturbance recording in power systems utilizes the COMTRADE format to capture transient events generated by intelligent electronic devices (IEDs), such as protective relays, which continuously monitor electrical parameters in substations. These devices trigger recordings upon detecting anomalies, including overcurrents, voltage sags, or frequency deviations, often using thresholds based on magnitude, rate-of-change, or harmonic content.^[24] For instance, a relay may initiate capture when current exceeds a preset level indicative of a fault, ensuring the system logs the event automatically without manual intervention.^[25] The data captured typically includes pre- and post-fault waveforms, spanning short windows of 0.5 to 2 seconds to encompass the transient period, sampled at rates like 64 to 128 samples per cycle for high-resolution fidelity.^[24] Analog channels record voltage and current signals, while binary signals document discrete states, such as breaker trip commands or protection operation flags, providing a timestamped sequence of events with resolutions down to 0.5 milliseconds.^[26] This combination allows for a complete snapshot of the disturbance, from initiation to clearance. Integration with supervisory control and data acquisition (SCADA) systems or dedicated digital fault recorders (DFRs) facilitates automatic archiving of these records during events like short circuits or switching transients. IEDs transmit the data via Ethernet or serial links to a central DFR, which stores and time-synchronizes files from multiple locations for comprehensive event reconstruction.^[26] In transmission networks, for example, COMTRADE recordings from line faults enable engineers to retrieve and correlate data swiftly, supporting root-cause analysis to maintain grid stability and prevent cascading failures like blackouts.^[24] Benefits of this approach include rapid identification of fault origins, such as excessive energy in transformers during internal short circuits, by examining waveform signatures and binary timelines, which accelerates restoration efforts and enhances overall system reliability.^[25] The standardized COMTRADE format ensures interoperability across vendor equipment, minimizing data loss during transfer to archival systems.^[10]

Analysis and Testing

COMTRADE files enable detailed fault analysis in power systems by allowing engineers to review captured waveforms and determine event causes. For instance, voltage and current data from these files support impedance calculations to assess distance relay operations during faults, revealing whether protection settings were appropriate for fault location and type.^[27] Harmonic content analysis from the waveforms identifies disturbances like capacitor switching or non-linear loads contributing to faults.^[28] In relay performance testing, COMTRADE data simulates real events in laboratory settings to validate protection schemes. Engineers replay waveforms into test sets connected to relays, verifying trip decisions, timing, and coordination under replicated conditions, which is essential during commissioning of new equipment.^[29] This approach ensures relays respond correctly to transients without requiring full system tests, though limitations such as insufficient predisturbance data or timing mismatches can affect replay accuracy.^[29] For system-wide studies, COMTRADE integration facilitates blackout investigations and regulatory compliance. During the 2003 Northeast blackout analysis, synchronized COMTRADE data from multiple substations helped reconstruct event sequences and identify cascading failures.^[30] Under NERC standards like PRC-002-5, utilities report COMTRADE files for disturbance monitoring, ensuring time-tagged data supports event analysis and reliability assessments.^[31] Advanced applications include event correlation across sites and machine learning for anomaly detection. COMTRADE data from protective relays and fault recorders can be integrated into power quality databases, correlating transients from multiple locations to trace propagation in interconnected grids.^[32] Machine learning models, such as convolutional neural networks, process COMTRADE waveforms converted to images, achieving high accuracy in classifying fault types and locations for proactive anomaly detection.^[33] Challenges arise in handling large COMTRADE datasets from high-speed sampling in modern grids, where rates exceeding 10 kHz generate voluminous files that strain analysis tools.^[34] Synchronization issues across devices and data conversion errors further complicate processing, necessitating robust software for efficient interpretation.^[29]

Implementation

Software Tools

Software tools for handling COMTRADE files are diverse, ranging from simple viewers for visualization to advanced analyzers for in-depth power system diagnostics. These tools enable engineers to parse, display, and interpret transient data captured during electrical disturbances, supporting tasks like waveform plotting, data extraction, and fault analysis. Most tools adhere to the IEEE C37.111-1999 and 2013 standards, with varying degrees of support for binary and ASCII formats.^[35]^[36] Viewers provide basic functionality for loading and displaying COMTRADE files, often including waveform plotting and simple export options. Free tools such as openComtradeViewer, an open-source multi-platform application, allow users to visualize oscillograph records and extract data on Windows and Linux systems.^[37] Similarly, MATLAB's COMTRADE reader toolbox decodes files, applies scaling and offsets to analog signals, and supports plotting for educational and analytical purposes.^[38] Elspec's PQSCADA Sapphire offers a free viewer that transforms COMTRADE data into high-quality graphics without requiring installation.^[39] Analyzers extend beyond visualization to include advanced features like phasor analysis, fault location, and automated reporting. Commercial software such as SEL's SynchroWAVe Event enables time-aligned viewing of multiple COMTRADE files, relay event diagnosis, and oscillography plotting for protective relay behavior assessment.^[40] Omicron's TransPlay software supports playback of COMTRADE transients, injection into relay testing setups, and processing for waveform analysis in protection testing workflows.^[41] Open-source options facilitate custom scripting and integration into larger data pipelines. Python libraries like the comtrade module on PyPI allow parsing of COMTRADE files in Python 3, enabling automated data extraction and analysis scripts.^[42] The pycomtrade library provides similar functionality for reading files, supporting both ASCII and binary formats for research and development applications.^[43] Common features across these tools include import and export to formats like CSV for interoperability, zoomable visualizations for detailed inspection, and basic event classification based on timestamped triggers.^[35]^[41] Compatibility is generally strong up to the 2013 revision, including support for extended channel counts and frequency-domain data, though adoption of emerging features like the optional Channel Frequency File (.CFF) remains limited in many implementations.^[36]^[14]

Hardware and Integration

COMTRADE files are embedded within intelligent electronic devices (IEDs) from major vendors such as Siemens, GE Vernova, and ABB, where protective relays automatically generate these files upon detecting disturbances or triggers like faults. For instance, Siemens SIPROTEC 5 relays support both the 1999 and 2013 versions of the COMTRADE standard, enabling the capture of transient data directly from analog and digital inputs during power system events. Similarly, GE Multilin G30 generator protection relays incorporate COMTRADE 2013 for waveform capture, facilitating postmortem analysis of generator faults. ABB Relion series, including the REF615 feeder protection relay, produce COMTRADE-formatted disturbance records accessible via Ethernet interfaces. These implementations ensure that IEDs serve as primary data sources, recording voltage, current, and binary status changes in a standardized format for subsequent exchange. Integration of COMTRADE into broader power system architectures typically involves exporting files from IEDs to central servers or analysis platforms using Ethernet-based protocols. Relays often transmit COMTRADE files via FTP or SFTP over Ethernet networks, allowing automated retrieval by substation automation systems without manual intervention. This method supports compatibility with synchrophasor systems, such as phasor data units (PDUs) compliant with IEEE C37.118, where COMTRADE records can complement high-resolution time-series data for synchronized event reconstruction. In substation environments, IEDs generate and store files locally before pushing them to networked repositories, enabling real-time or near-real-time data flow in distributed control setups. Storage in hardware devices relies on onboard flash memory within relays to temporarily hold COMTRADE files until transfer, with capacities typically measured in cycles of waveform data to accommodate multiple events. For example, protective relays allocate non-volatile flash for retaining records of pre- and post-fault data, ensuring persistence across power cycles. The COMTRADE format itself lacks built-in compression, so efficient exchange depends on underlying network protocols like TCP/IP for secure and reliable transmission to external systems. This approach minimizes onboard processing demands while prioritizing data integrity during high-volume disturbance scenarios. Key challenges in hardware integration include maintaining timestamp synchronization across multiple IEDs to ensure coherent multi-device event analysis. Accurate time-stamping, often derived from IRIG-B or PTP sources, is essential for aligning COMTRADE records from disparate relays; discrepancies can arise from unsynchronized clocks, leading to errors in replay or correlation. Backward compatibility in mixed-version environments poses another issue, as legacy 1999-format files must interoperate with 2013 implementations, requiring adapters or converters to handle differences in XML schemas and data structures. Looking ahead, COMTRADE integration is increasingly aligned with IEC 61850 standards for substation automation, promoting seamless data exchange through services like file retrieval from logical nodes. This convergence enables IEDs to report disturbances directly via GOOSE or MMS protocols, reducing latency and enhancing interoperability in smart grid architectures. Such trends support automated fault location and predictive maintenance by embedding COMTRADE generation within process bus communications.

References

[1]
UN Comtrade Database - the United Nations
The United Nations Comtrade database aggregates detailed global annual and monthly trade statistics by product and trading partner for use by governments, ...Trade DataDatabasesUN Comtrade AnalyticsAPISurvey
[2]
International statistics United Nations (UN): Comtrade database
This database covers the external trade of all states. Data is presented by several international classifications ( BEC , SITC , HS ).<|control11|><|separator|>
[3]
C37.111-1999 - IEEE Standard Common Format for Transient Data ...
COMTRADE defines a common format for exchanging fault, test, and simulation data for power systems, stored on physical media, not for network transfer.
[4]
COMTRADE File Format - NI
### COMTRADE File Structure Summary
[5]
Integration of COMTRADE Data Into a PQ Monitoring System ... - EPRI
Dec 12, 2005 · The Standard mostly defines a common format for the exchange of electrical power system transient data files on voltage and current waveforms.<|control11|><|separator|>
[6]
[PDF] NIST Framework and Roadmap for Smart Grid Interoperability ...
The critical role of standards for the Smart Grid is spelled out in EISA and in the June 2011. NSTC report, which advocates the development and adoption of ...
[7]
COMTRADE: The Next Generation | PAC World
COMTRADE is a standard file format for power system data. The next generation uses XML, following the same structure with XML-specific additions.
[8]
IEEE C37.111-1999 - IEEE Standards Association
IEEE C37.111-1999 defines a common format for data files and exchange medium for fault, test, or simulation data for electrical power systems.
[9]
[PDF] COMTRADE: a new standard for common format for transient data ...
COMTRADE is a new IEEE standard for a common format to exchange transient data from power systems, including voltage, current, and logical events.
[10]
IEEE/IEC C37.111-2013
IEEE/IEC C37.111-2013 defines a format for transient data exchange (COMTRADE) in power systems, for files stored on physical media, not networks.
[11]
C37.111-2013 - IEEE/IEC Measuring relays and protection ...
Apr 30, 2013 · Scope: This International Standard defines a format for files containing transient waveform and event data collected from power systems or power ...
[12]
[PDF] Report on a Common Data Format for IED Sampled Data
Jan 18, 2008 · This section describes how to map power system waveform and event data stored in the IEEE Std 1159.3-2002 PQDIF to the IEEE Std C37.111-1999 ...<|control11|><|separator|>
[13]
Basics of Power System Post Fault Analysis using COMTRADE file
Apr 16, 2021 · COMTRADE files are typically generated by Intelligent Electronic Devices (IEDs), such as an electronic protective relay, in electrical ...
[14]
COMTRADE-based fault information system for TNB substations
This work aims to help the TNB protection engineer to have a faster solution in parameter extraction from protective relay recorded from substations in COMTRADE ...
[15]
[PDF] Summary Changes in 2013 IEEE/IEC Dual Logo COMTRADE ...
The 2013 COMTRADE standard removed restrictions from 1990s computing and satisfied the need for universal time information in files.
[16]
[PDF] Summary of Changes in 2013 COMTRADE Standard:
Apr 30, 2013 · The 2013 COMTRADE standard added new time fields, time code, local code, time quality indicator, leap second indicator, single file format, and ...
[17]
[PDF] Conformance Errors in COMTRADE Records - Softstuf.com
The 2013 revision defines an optional single file format (CFF) which combines the four files (INF,. HDR, CFG, DAT) into one. The CFF file is separated into four ...
[18]
[PDF] COMTRADE recorder - EMTP
Jul 12, 2022 · This device records the EMTP control signal waveforms included into its bundle into COMTRADE files following the standards IEEE C37. 111-1999 ...
[19]
IEEE C37.111-1991 - IEEE Standards Association
IEEE C37.111-1991 defines a common format for data files and exchange medium for fault, test, or simulation data in power systems.
[20]
[PDF] Centralized Substation Protection and Control - PSRC - IEEE PES
The present era with microprocessor based relays started in the beginning of the 1980s, where microprocessor performed the logics, but the filtering was analog.
[21]
IEEE Standard Common Format for Transient Data Exchange ...
COMTRADE defines a common format for storing and exchanging digital records of transient events in power systems, including fault, test, and simulation data.
[22]
c37 111-1991 | PDF - Scribd
Typical recorders monitor 16-64 analog channels and a comparable number of event (contact status) inputs. Sampling rates, anslog-to-digital converter ...
[23]
Ieee STD c37 | PDF | File Format - Scribd
Rating 5.0 (2) The state of a status input is represented by a number Ò1Ó or Ò0Ó in the data Þle. The data Þles may be in either ASCII or binary formatÑa Þeld in the ...<|control11|><|separator|>
[24]
[PDF] WinXFM - Advanced Power Concepts
Jun 28, 2020 · DAT files can be either ASCI or BINARY format. In Standards 1991 and 1999 Binary format each sample was stored as a 16 bit integer. The 2013 ...
[25]
[PDF] power system relaying and control committee - PSRC - IEEE PES
Sep 23, 2021 · The Chair noted that once the PAR was approved and the revision WG formed, the PES TR90/PSRC report on possible upgrades to COMTRADE will be an ...
[26]
[PDF] Considerations for Use Of Disturbance Recorders - PSRC - IEEE PES
Dec 27, 2006 · For example, protective relays monitor current(s) and voltage(s) to make decisions based on the settings to clear faults on the power system by ...
[27]
[PDF] Standard Data Formats for Disturbance Analysis | TRUC
records collected from power systems. It addressed the fact that protection relays and other IEDs store in their memory historical event data. The main ...
[28]
[PDF] DDFR™ - GE Vernova
The GE Multilin DDFR™ is a Power System Fault Recorder that collects, archives and manages Disturbance and Fault information that is recorded by microprocessor ...
[29]
https://selinc.com/api/download/119832/
[30]
https://ieeexplore.ieee.org/document/6672932
[31]
[PDF] Understanding the Limitations of Replaying Relay-Created ...
COMTRADE files created using hardware-based frequency tracking can have different time intervals between when consecutive raw measured samples are recorded. B.
[32]
https://www.epri.com/research/products/1010185
[33]
[PDF] NERC, PRC-002 Compliance Statement - Arbiter Systems
However it is done, compliance with this NERC requirement implies that event records. (COMTRADE files, for instance) should be time-tagged using UTC time, not ...
[34]
Integration of COMTRADE Data Into a PQ Monitoring System Database
### Summary of Integration and Correlation of COMTRADE Data for Power Quality Monitoring
[35]
Deep-Learning Based Fault Events Analysis in Power Systems - MDPI
The format of the COMTRADE file is an IEEE standard (i.e., IEEE C37.111-2013) and refers to the recorded and stored transient power system disturbances (e.g., ...<|control11|><|separator|>
[36]
Ensembled methodology for the comtrade analysis regarding ...
This research proposes a methodology for automated COMTRADE analysis using ensembled algorithms for fault analysis in medium voltage circuits, specifically for ...
[37]
Data Analysis - COMTRADE Viewer - Softstuf.com
The Universal Viewer is an advanced version of the COMTRADE Viewer. It includes drivers for reading proprietary formats from various IED producers. It includes ...
[38]
COMTRADE Chart - Redis Assistant
The software provides a variety of analysis tools, no programming required, to explore data immediately: fast Fourier transform, curve fitting, correlation ...Missing: viewers libraries
[39]
ldemattos/openComtradeViewer: An open/free multi ... - GitHub
An open/free multi platform IEEE COMTRADE oscillograph records visualizer and data extractor. It's have been successfully tested in GNU/Linux, Microsoft Windows ...Missing: viewers analyzers
[40]
COMTRADE reader - File Exchange - MATLAB Central - MathWorks
Decodes a COMTRADE file, used throughout the power industry, applying the scaling and offsets to analogue signals.
[41]
Free COMTRADE Viewer - Elspec LTD
Oct 31, 2022 · PQSCADA Sapphire is a free COMTRADE viewer developed by Elspec. It reads COMTRADE files and transform them into high quality graphics.Missing: libraries | Show results with:libraries
[42]
SEL-5601-2 Synchrowave Event Software
COMTRADE Viewer—View COMTRADE reports from a variety of sources together in Synchrowave Event for complete COMTRADE file analysis.
[43]
TransPlay - OMICRON
TransPlay allows the loading and playback of transient files containing voltage and current analog transient waveforms. COMTRADE files can be automatically ...Missing: structure | Show results with:structure
[44]
comtrade - PyPI
Python Comtrade is a module for Python 3 designed to read Common Format for Transient Data Exchange (COMTRADE) files.
[45]
miguelmoreto/pycomtrade - GitHub
pyComtrade is a python module that provides you a transparent way for reading and writing oscillographic files in Comtrade format - miguelmoreto/pycomtrade.