Fault test and analysis method for relay protection information management substation of transformer substation

Abstract

The invention relates to the field of power system fault diagnosis, and discloses a transformer substation relay protection information management substation fault test and analysis method, which comprises the following steps that a, a tester is communicated with a transformer substation relay protection information management substation, and the tester has the capability of being compatible with a communication protocol of the relay protection information management substation; b, acquiring related data from the information protection substation by using a tester; c, the collected data are analyzed and processed, and potential fault causes are found out; and d, adopting an efficient fault diagnosis algorithm to quickly locate the fault reason in the operation of the signal protection substation. Through compatibility with various communication protocols of the information protection substation, loading and analysis of dynamic protocols are supported, data frames of different protocols can be automatically identified and analyzed, and efficient and stable communication between devices is ensured. The multi-protocol compatibility improves the adaptability and expansibility of the equipment, and communication of multi-type relay protection equipment and fault detection and management under multiple scenes are realized.

Description

Technical Field

[0001] The invention relates to the field of power system fault diagnosis, and in particular to a fault testing and analysis method for a transformer substation relay protection information management substation. Background Art

[0002] With the continuous advancement of power system automation, substation relay protection information management substation plays a key role in substation operation. The substation communicates data with various protection devices to obtain key parameters such as telemetry, telesignaling, and set values ​​in real time, and performs protection and control on power grid equipment. Various types of protection devices in substations are often connected to the protection and information system through communication protocols such as IEC 60870-5-103, IEC 60870-5-101 / 104, and manufacturer-defined protocols to achieve information exchange. However, due to the wide variety of protection device protocols and the use of customized communication protocols by devices from different manufacturers, system integration, data compatibility, and fault diagnosis have been greatly challenged.

[0003] First, the existing relay protection information management substation system is often not compatible with multiple communication protocols. In particular, when facing the manufacturer's customized protocol, the system needs to be customized, which increases the difficulty of integration and maintenance. At the same time, the differences between different protocols make system expansion and equipment upgrade difficult, which seriously limits the flexibility of the system. The present invention supports IEC 60870-5-103, IEC 60870-5-101 / 104 and manufacturer's customized protocol, has multi-protocol compatibility and dynamic protocol loading functions, can adapt to the various communication needs of different devices and manufacturers, and fundamentally solves the complexity of multi-protocol integration.

[0004] Secondly, most traditional systems can only collect basic data such as telemetry and telesignaling, but cannot effectively collect fixed values, action information and fault information. The incompleteness of such data collection makes it difficult to obtain comprehensive fault background information when a device fails, affecting the accurate analysis of the cause of the fault. To address this problem, the present invention provides a comprehensive data collection and analysis function, which can collect all key data including telemetry, telesignaling, fixed values, action information and fault information, and perform accurate analysis and feature extraction, which helps to comprehensively and quickly discover potential fault causes;

[0005] Finally, the existing relay protection information management substation system usually uses a simple threshold judgment method to detect faults and lacks an intelligent fault diagnosis algorithm, resulting in slow fault detection response and low accuracy, especially poor performance when dealing with complex fault modes. The present invention adopts an efficient fault diagnosis algorithm, which can perform anomaly detection and fault mode matching based on the collected data, quickly and accurately locate the cause of the fault, greatly improving the speed and accuracy of fault diagnosis, and providing effective protection for the safe operation of the substation. Summary of the invention

[0006] In view of the deficiencies of the prior art, the present invention provides a fault testing and analysis method for a substation relay protection information management substation, which solves the problem of incompatibility with multiple communication protocols.

[0007] To achieve the above objectives, the present invention is implemented through the following technical solutions: A fault testing and analysis method for a substation relay protection information management substation, comprising the following steps:

[0008] a. Communicate with the substation relay protection information management substation through the tester, and the tester has the ability to be compatible with the communication protocol of the substation;

[0009] b. Collect relevant data from the Baoxin substation using a tester;

[0010] c. Analyze and process the collected data to find out the potential causes of failures;

[0011] d. Use efficient fault diagnosis algorithms to quickly locate the cause of faults in the operation of the trustworthy substation. Preferably, in step a, the tester supports IEC 60870-5-103, IEC60870-5-101 / 104 and other vendor-defined protocols, including protocol stack library, physical interface support, protocol parsing module, protocol compatibility layer and dynamic protocol loading;

[0012] The protocol stack library is used to parse and encapsulate communication messages, including decoding of data frames, identification of message headers and tails, and extraction of data fields;

[0013] The physical interface supports adapting to different connection requirements;

[0014] The protocol parsing module includes:

[0015] Message frame structure analysis, which is used to analyze specific message frames, including start flag, address, function code, data area, and check code;

[0016] Data type mapping, which is used to convert binary data into specific types for analysis;

[0017] The protocol compatibility layer includes:

[0018] Protocol Driver Protocol Driver, including but not limited to starting or stopping the communication link with the device, handling communication timeout and packet loss;

[0019] The protocol mapping rules are used to define specific fields and types in the data frame through the configuration file or UI interface.

[0020] The dynamic protocol loading makes the tester architecture modular and supports the loading and upgrading of dynamic protocols.

[0021] Preferably, in step a, the tester has multiple interfaces, including an Ethernet interface, an RS-485 interface and an RS-232 interface, for physically connecting to different types of relay protection information management substation equipment.

[0022] Preferably, in step b, the relevant data includes telemetry data, telesignaling data, constant value data, action information and fault information.

[0023] Preferably, in step c, the tester has multi-level data analysis capabilities and can perform basic data analysis, historical data comparison and contextual correlation analysis on telemetry data, telesignaling data, constant value data, action information and fault information.

[0024] Preferably, in step c, the user interface of the tester has a concise and intuitive visualization function, which can graphically display the trend of the collected data, abnormal points, and the diagnosed fault type and cause;

[0025] The user interface of the tester has a simple and intuitive visualization function, which can graphically display the trends, abnormal points, and diagnosed fault types and causes of the collected data, and the user can zoom in, zoom out, and pan the data charts displayed in the graphical manner to deeply view the detailed data of each time period;

[0026] The user interface has simple navigation and operation functions, and the user can quickly complete equipment selection, start and stop fault diagnosis, data browsing and report generation operations by clicking or dragging elements in the interface.

[0027] Preferably, in step c, the analysis comprises the following steps:

[0028] (1) Data classification: First, the collected raw data is classified by type, and each type of data is represented using a specific structure or format;

[0029] (2) Data decoding: Decode the collected data according to the communication protocol used to extract the value and status information;

[0030] (3) Timestamp synchronization: Timestamp all data to ensure that data from different devices or different types can be compared on the same timeline;

[0031] The formats in (1) include but are not limited to JSON and XML, and (2) further includes parsing the address, function code, data field and check code in the data frame.

[0032] Preferably, in step c, the processing comprises the following steps:

[0033] S1. Data preprocessing: data denoising, abnormal data processing and data formatting;

[0034] S2. Feature extraction:

[0035] Extract the average value, maximum value, minimum value and fluctuation range from the telemetry data;

[0036] Remote signaling data extracts time series information of equipment status changes and identifies key status change points;

[0037] The state change points include but are not limited to circuit breaker tripping and switch action;

[0038] S3. Data anomaly detection: Use the analysis results to determine whether the data is abnormal, and mark or further analyze the abnormal data;

[0039] Whether the data is abnormal is identified by the following formula:

[0040]

[0041] Among them, x is the data value, μ is the mean value, σ is the standard deviation, and z is the threshold standard. When |z|>z threshold , then mark the data as abnormal;

[0042] S4. Historical data comparison and trend analysis: Compare the currently collected data with historical data to determine the abnormality or trend of equipment operation;

[0043] S5. Fault pattern matching and report generation: Match it with the predefined fault pattern library to quickly determine the possible fault type, generate a fault diagnosis report, and display the analysis results to the user.

[0044] Preferably, the efficient fault diagnosis algorithm formula is:

[0045]

[0046] Among them, fault is the matched fault type or mode number, j is the index number of the fault mode, and different modes are selected from the fault mode library. i is the index number of the feature, from 1 to n, representing all the extracted features, and x i is the characteristic value currently collected, such as current and voltage, μ i is the average value of the corresponding feature i in the historical data, used as a reference for standardization, σ i is the standard deviation of feature i, indicating the fluctuation range of the feature value, and is the fault mode M j The value corresponding to feature i in represents the feature value in a specific fault mode. is the modulus of the current feature vector after normalization, indicating the comprehensive normalization result of all features. is the failure mode vector M j The modulus represents the characteristic intensity of the failure mode.

[0047] Preferably, the efficient fault diagnosis algorithm includes the following stages:

[0048] (A) Feature extraction: x in the formula i Indicates the real-time data collected from the Baoxin substation, such as current, voltage and other characteristics;

[0049] (B) Anomaly detection: By i After standardization, the formula automatically detects abnormal feature values;

[0050] (C) Fault mode matching: The formula compares the real-time data with the historical fault mode library by calculating the cosine similarity and selects the most likely fault mode;

[0051] (D) Fault location: The final output fault corresponds to the most similar fault mode, which helps to quickly locate the problem.

[0052] The present invention provides a fault testing and analysis method for a substation relay protection information management substation. It has the following beneficial effects:

[0053] 1. The present invention is compatible with a variety of communication protocols of security substations and supports dynamic protocol loading and parsing. Through multi-protocol compatibility and parsing functions, it can automatically identify and parse data frames under different protocols, making communication between devices more efficient and stable, eliminating the limitations of traditional single-protocol devices in complex application scenarios. This multi-protocol compatibility greatly improves the adaptability and scalability of the device, thereby enabling communication with various types of relay protection equipment and achieving fault detection and management in multiple scenarios.

[0054] 2. The present invention collects various data types from the security substation and cooperates with efficient fault diagnosis algorithms to quickly locate the cause of the fault, and uses intelligent technologies such as feature extraction and pattern matching for diagnosis, which greatly improves the accuracy and speed of diagnosis, enabling it to handle more complex fault modes, especially the ability to dynamically expand the fault mode library, ensuring the continued effectiveness of the system when upgrading or processing new equipment in the future.

[0055] 3. The present invention has a simple and intuitive user interface that supports graphical display of data trends, anomalies and fault diagnosis results. Users can quickly understand the operating status of the equipment through visualization tools. The interface supports free scaling and operation, allowing users to easily analyze historical data and real-time fault information. At the same time, the modular design of the system and the dynamic protocol loading function ensure future expansion capabilities, so that new protocols, new equipment support, and diagnostic algorithms for new fault modes can be quickly added according to user needs, providing broad space for future system updates or the introduction of new technologies, greatly enhancing the ease of use and scalability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 is a flow chart of the method steps of the present invention;

[0057] Figure 2 It is a schematic diagram of the detection process of the present invention. DETAILED DESCRIPTION

[0058] The following will be combined with the drawings in the specification of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0059] Embodiment 1:

[0060] Please see attached Figure 1 The embodiment of the present invention provides a substation relay protection information management substation fault testing and analysis method, comprising the following steps:

[0061] a. Communicate with the substation relay protection information management substation through the tester, and the tester has the ability to be compatible with the communication protocol of the substation;

[0062] b. Collect relevant data from the Baoxin substation using a tester;

[0063] c. Analyze and process the collected data to find out the potential causes of failures;

[0064] d. Use efficient fault diagnosis algorithms to quickly locate the causes of faults in the operation of the Baoxin substation;

[0065] In step a, the tester supports IEC 60870-5-103, IEC 60870-5-101 / 104 and other vendor-defined protocols, including protocol stack library, physical interface support, protocol parsing module, protocol compatibility layer and dynamic protocol loading;

[0066] The protocol stack library is used to parse and encapsulate communication messages, including decoding of data frames, identification of message headers and tails, and extraction of data fields;

[0067] Physical interface support adapts to different connection requirements;

[0068] The protocol parsing module includes:

[0069] Message frame structure analysis, which is used to analyze specific message frames, including start flag, address, function code, data area, and check code;

[0070] Data type mapping, which is used to convert binary data into specific types for analysis;

[0071] The protocol compatibility layer includes:

[0072] Protocol Driver Protocol Driver, including but not limited to starting or stopping the communication link with the device, handling communication timeout and packet loss;

[0073] The protocol mapping rules are used to define specific fields and types in the data frame through the configuration file or UI interface.

[0074] Dynamic protocol loading makes the tester architecture modular and supports dynamic protocol loading and upgrading;

[0075] In step a, the tester has multiple interfaces, including Ethernet interface, RS-485 interface and RS-232 interface, for physical connection with different types of relay protection information management substation equipment;

[0076] In step b, the relevant data includes telemetry data, telesignaling data, fixed value data, action information and fault information;

[0077] In step c, the tester has multi-level data analysis capabilities, and can perform basic data analysis, historical data comparison, and contextual correlation analysis on telemetry data, telesignaling data, fixed value data, action information, and fault information;

[0078] In step c, the user interface of the tester has a simple and intuitive visualization function, which can graphically display the trends, abnormal points, and diagnosed fault types and causes of the collected data;

[0079] The tester's user interface has a simple and intuitive visualization function, which can graphically display the trends, abnormal points, and diagnosed fault types and causes of the collected data. Users can also zoom in, zoom out, and pan the data charts displayed in the graphical mode to deeply view the detailed data of each time period;

[0080] The user interface has simple navigation and operation functions. Users can quickly complete equipment selection, start and stop fault diagnosis, browse data and generate reports by clicking or dragging elements in the interface;

[0081] In step c, the parsing includes the following steps:

[0082] (1) Data classification: First, the collected raw data is classified by type, and each type of data is represented using a specific structure or format;

[0083] (2) Data decoding: Decode the collected data according to the communication protocol used to extract the value and status information;

[0084] (3) Timestamp synchronization: Timestamp all data to ensure that data from different devices or different types can be compared on the same timeline;

[0085] (1) The format includes but is not limited to JSON and XML, (2) further includes parsing the address, function code, data field and checksum in the data frame;

[0086] In step c, the processing includes the following steps:

[0087] S1. Data preprocessing: data denoising, abnormal data processing and data formatting;

[0088] S2. Feature extraction:

[0089] Extract the average value, maximum value, minimum value and fluctuation range from the telemetry data;

[0090] Remote signaling data extracts time series information of equipment status changes and identifies key status change points;

[0091] Status change points include but are not limited to circuit breaker tripping and switch actuation;

[0092] S3. Data anomaly detection: Use the analysis results to determine whether the data is abnormal, and mark or further analyze the abnormal data;

[0093] Whether the data is abnormal can be identified by the following formula:

[0094]

[0095] Among them, x is the data value, μ is the mean value, σ is the standard deviation, and z is the threshold standard. When |z|>z threshold , then mark the data as abnormal;

[0096] S4. Historical data comparison and trend analysis: Compare the currently collected data with historical data to determine the abnormality or trend of equipment operation;

[0097] S5, Fault pattern matching and report generation: Match it with the predefined fault pattern library, quickly determine the possible fault type, generate a fault diagnosis report, and display the analysis results to the user;

[0098] The formula of efficient fault diagnosis algorithm is:

[0099]

[0100] Among them, fault is the matched fault type or mode number, j is the index number of the fault mode, and different modes are selected from the fault mode library. i is the index number of the feature, from 1 to n, representing all the extracted features, and x i is the characteristic value currently collected, such as current and voltage, μ i is the average value of the corresponding feature i in the historical data, used as a reference for standardization, σ i is the standard deviation of feature i, indicating the fluctuation range of the feature value, and is the fault mode M j The value corresponding to feature i in represents the feature value in a specific fault mode. is the modulus of the current feature vector after normalization, indicating the comprehensive normalization result of all features. is the failure mode vector M j The mode of represents the characteristic intensity of the failure mode;

[0101] An efficient fault diagnosis algorithm consists of the following stages:

[0102] (A) Feature extraction: x in the formula i Indicates the real-time data collected from the Baoxin substation, such as current, voltage and other characteristics;

[0103] (B) Anomaly detection: By i After standardization, the formula automatically detects abnormal feature values;

[0104] (C) Fault mode matching: The formula compares the real-time data with the historical fault mode library by calculating the cosine similarity and selects the most likely fault mode;

[0105] (D) Fault location: The final output fault corresponds to the most similar fault mode, which helps to quickly locate the problem.

[0106] Embodiment 2: Relay protection information management method supported by a single protocol

[0107] step:

[0108] Single protocol communication support: The tester only supports IEC 60870-5-101 protocol and is not compatible with other protocols. All substation devices must support this protocol to communicate;

[0109] Data collection: The tester can only collect the telemetry data and telesignaling data of the equipment, but cannot collect fixed value data or action information;

[0110] Data processing: The tester performs basic analysis on the collected telemetry data, but does not support historical data comparison or have a complex anomaly detection mechanism;

[0111] Fault report generation: The tester can only generate simple fault reports, including the basic status of telemetry and telesignaling data, without detailed fault cause analysis;

[0112] Summarize:

[0113] Since this embodiment only supports a single protocol, its functions are very limited, its device compatibility is poor, it cannot process more complex fault information, and it cannot generate a complete fault diagnosis report. Therefore, this solution has great functional limitations in practical applications and is not as good as the multi-protocol compatibility and comprehensive data collection capabilities of the first embodiment.

[0114] Embodiment 3: Relay protection information management method for manual data collection and analysis

[0115] step:

[0116] Manual data collection: The tester does not have automatic data collection function. Users need to manually input the device's telemetry data and status information into the system;

[0117] Data analysis: Since data entry is completely dependent on manual operation, the tester only supports the display of simple numerical data and cannot perform real-time dynamic analysis;

[0118] No fault diagnosis algorithm: The tester does not have automatic fault detection and diagnosis capabilities, and users must manually analyze data to find potential fault causes;

[0119] No report generation: The system cannot automatically generate a fault diagnosis report. Users need to summarize and record the cause of the fault themselves.

[0120] Summarize:

[0121] This embodiment emphasizes manual data collection and processing, and lacks automated data collection and diagnosis functions. In contrast, the substantial improvement of the first embodiment is reflected in automated data collection and intelligent fault diagnosis, which not only reduces the manpower burden, but also improves the efficiency and accuracy of detection.

[0122] Embodiment 4: Relay protection information management method without scalability

[0123] step:

[0124] Fixed communication protocol support: The tester only supports the fixed IEC 60870-5-103 protocol, and does not have the ability to support other manufacturers' protocols, and cannot dynamically load or expand the protocol;

[0125] Basic data collection: The tester only supports basic telemetry and telesignaling data collection of the equipment and cannot be expanded to other data types according to different requirements;

[0126] Fixed fault diagnosis mode: The tester uses only a simple threshold judgment algorithm and does not support complex fault diagnosis algorithms or future algorithm updates;

[0127] No UI extension: The tester’s UI is fixed and cannot be customized according to user needs, nor can it be extended with new visualization features.

[0128] Summarize:

[0129] This embodiment emphasizes the non-scalability of the tester and faces many limitations in actual use. In contrast, the first embodiment provides good scalability, supports dynamic updates and upgrades of protocols, fault diagnosis algorithms and user interfaces, and adapts to different devices and future expansion requirements.

[0130] Example 5: Relay protection information management method without data visualization

[0131] step:

[0132] Data collection: The tester can automatically collect telemetry and telesignaling data, but there is no visual interface. The data is only presented in text format and cannot be displayed graphically.

[0133] Data analysis: The analysis results are only presented in a numerical list, and users need to read text information to understand the device operating status;

[0134] Simple fault diagnosis: Faults are detected by judging whether the value exceeds the threshold. Users must manually compare multiple data to find the potential cause of the fault;

[0135] No visual reports: The system cannot generate charts or trend graphs. Users can only view simple text reports and cannot perform detailed data analysis.

[0136] Summarize:

[0137] The limitation of this embodiment is that it lacks data visualization function, and it is difficult for users to quickly understand the operating status and fault causes of the equipment through text data. However, the user interface of the first embodiment is not only simple and easy to use, but also provides a detailed graphical display, which greatly facilitates the user's fault analysis work.

[0138] Summary:

[0139] Embodiment 1 has communication protocol compatibility, data collection and analysis, efficient fault diagnosis algorithm, simple and easy-to-use user interface, and good scalability, and is a highly automated, intelligent, and highly compatible system; Embodiment 2 only supports a single protocol, has poor device compatibility, lacks flexibility, and its functions are far inferior to those of Embodiment 2; Embodiment 3 relies entirely on manual operation, lacks automation and intelligence, and has a heavy workload for users and low efficiency, which is far inferior to the automation advantage of Embodiment 1; Embodiment 4 has no scalability, fixed functions, and cannot support future new protocols and algorithm expansions, while Embodiment 1 has good scalability and supports future development; Embodiment 5 has no data visualization, and the user interface functions are simple, making it difficult for users to quickly analyze the device status, while Embodiment 1 provides powerful visualization support, which greatly improves the user experience.

[0140] Through the comparison of these embodiments, Example 1 has more comprehensive technical advantages, covering the compatibility of communication protocols, automation of data acquisition and processing, intelligent fault diagnosis, ease of use of the user interface and scalability of the system, demonstrating its superior performance in fault diagnosis of relay protection information management substations.

[0141] Test experiment:

[0142] Test Experiment Design:

[0143] Test environment and equipment:

[0144] Device 1 (supporting IEC 60870-5-103): a relay protection device that outputs telemetry, telesignaling, setting information, and supports IEC 60870-5-103 protocol;

[0145] Device 2 (supporting IEC 60870-5-101): another relay protection device, supporting IEC 60870-5-101 protocol;

[0146] Device 3 (supports manufacturer-defined protocols): relay protection device using manufacturer-defined protocols, used to test protocol compatibility and extensibility;

[0147] Tester: A tester connected to the above three devices, used to simulate Examples 1 to 5.

[0148] Test steps:

[0149] Device connection: Connect the tester to three devices through the Ethernet interface, RS-485 interface, and RS-232 interface respectively to check the tester's multi-protocol communication support and interface compatibility;

[0150] Data collection: Each embodiment needs to collect the telemetry, telesignaling, set value, action information and fault information of the equipment, and test the success rate, speed and integrity of the collection;

[0151] Fault injection: artificially create common relay protection faults (such as short circuit, overcurrent, etc.) in the device to test the fault detection and response capabilities of each embodiment;

[0152] Data analysis and visualization: Use the user interface of each embodiment to observe whether the data can be intuitively displayed and generate a fault diagnosis report, focusing on testing its visualization function;

[0153] Extensibility test: Try to load new protocols or devices to test the extensibility of each implementation example;

[0154] Fault handling and diagnostic report generation: Evaluate each implementation example on the speed of fault handling and the degree of automation of report generation.

[0155] Testing process:

[0156] Test experiment 1. Communication protocol compatibility test

[0157] Objective: To test whether the tester can communicate normally with devices with different protocols, and the stability and success rate of data transmission.

[0158] process:

[0159] Connect the tester to device 1 (IEC 60870-5-103), device 2 (IEC 60870-5-101) and device 3 (manufacturer-defined protocol) respectively;

[0160] Start the protocol parsing module of the tester to check whether each implementation example can communicate normally with different devices and check the correctness of message parsing;

[0161] Data Records:

[0162] Communication success rate (number of successful connections out of 10);

[0163] Protocol parsing time (the time for each message parsing, in milliseconds).

[0164]

[0165] analyze:

[0166] Example 1 performed best in the protocol compatibility test and was able to stably support all protocol devices. Examples 2, 3, 4, and 5 performed poorly, especially Example 2 and Example 4 could only support a single protocol, limiting the adaptability of the device.

[0167] Test experiment 2. Data collection and processing test

[0168] Objective: To test the acquisition capability, acquisition speed, and data analysis accuracy of each embodiment.

[0169] process:

[0170] Collect complete data packets including telemetry, telesignaling, setting, action information and fault information from each device;

[0171] Check the speed and completeness of data collection and whether it can be correctly parsed.

[0172] Data Records:

[0173] Data collection success rate (number of successful collections out of 100);

[0174] Average data collection time (the time for each data collection, in milliseconds);

[0175] Data completeness (percentage, whether all categories of data are fully collected).

[0176]

[0177] analyze:

[0178] Embodiment 1 performs best in terms of acquisition speed, success rate and data integrity, and can comprehensively acquire all data of the equipment and process them in a timely manner. Embodiments 2 and 3 have longer acquisition times and lower data integrity, especially the lack of acquisition of constant value and fault information.

[0179] Test experiment 3. Fault diagnosis efficiency test

[0180] Objective: To evaluate the response speed and accuracy of each implementation in fault detection.

[0181] process:

[0182] Different types of faults (such as short circuit, overcurrent, etc.) were simulated in Device 1 and Device 2 respectively, and the fault response speed and accuracy of each embodiment were observed;

[0183] Check whether a detailed fault report is generated and record the generation time.

[0184] Data Records:

[0185] Fault response time (milliseconds, the time from fault occurrence to detection);

[0186] Fault diagnosis accuracy (percentage, proportion of faults correctly detected);

[0187] Report generation time in milliseconds.

[0188]

[0189] analyze:

[0190] The fault diagnosis speed and accuracy of Example 1 are much higher than those of other examples, and it can quickly locate the fault and generate a detailed report. Examples 3 and 4 have slow fault response speeds, poor diagnostic accuracy, and long report generation times, which affect the efficiency of fault handling.

[0191] Test experiment 4. User interface usability test

[0192] Objective: Test the convenience and visual display capabilities of the user interface.

[0193] process:

[0194] Check the device's operating data through the user interface to see if data trends and abnormalities can be displayed intuitively.

[0195] Test whether users can quickly operate the interface and generate reports.

[0196] Data Records:

[0197] Data visualization effect score (1-5 points, 5 points is the best);

[0198] User operation complexity score (1-5 points, 1 point is the simplest);

[0199] Average operation time (seconds).

[0200]

[0201] analyze:

[0202] Embodiment 1 has the best visualization function and is easy to operate, and the user can quickly generate a fault report. Embodiment 4 has an interface design that is not intuitive enough, and the user operation is complicated and time-consuming, which affects the efficiency of use.

[0203] Test experiment 5. Scalability test

[0204] Objective: To test the extensibility of each implementation in terms of protocols, interfaces, and algorithms.

[0205] process:

[0206] Try to add new protocol support and fault diagnosis algorithms to the tester to observe the flexibility of expansion;

[0207] Try connecting the tester with a new device to test whether it can be quickly adapted.

[0208] Data Records:

[0209] Extension protocol support time (seconds);

[0210] New device adaptation success rate (percentage).

[0211]

[0212] analyze:

[0213] Embodiment 1 has the best expansion capability and can quickly load new protocols and adapt to new devices. Other embodiments have poor expansion performance, especially embodiments 3 and 4 have limited adaptability.

[0214] Summary:

[0215] Example 1 performed well in all test items, and has multi-protocol compatibility, complete data acquisition and processing capabilities, fast fault diagnosis, excellent user interface usability and strong scalability, and can provide users with comprehensive relay protection information management and fault analysis functions; Example 2 performed well under a single protocol, but lacked scalability and fault diagnosis capabilities, and was suitable for simple application scenarios; Example 3 has low overall efficiency due to manual data collection and poor fault diagnosis capabilities, and is difficult to adapt to complex application scenarios; Example 4 has fixed functions and interfaces that limit the scalability and adaptability of the system, and the user experience is poor; Example 5 performs relatively general in fault diagnosis and interface operation, but its scalability is still insufficient; Through testing, the comprehensive capabilities of Example 1 are significantly better than other embodiments, demonstrating its strong advantages as a relay protection information management substation fault testing and analysis method.

[0216] Comparative experiment 1: Communication protocol compatibility experiment

[0217] Purpose:

[0218] The compatibility and communication success rate of different device protocols are tested, and the compatibility and efficiency of the prior art and the present invention when processing multi-protocol devices are compared.

[0219] Experimental equipment:

[0220] The solution of the present invention: the tester supports IEC 60870-5-103, IEC 60870-5-101 / 104, and manufacturer-defined protocols, and has dynamic protocol loading and multi-protocol parsing functions.

[0221] Existing technical solution: The tester only supports a single protocol (IEC 60870-5-103) and does not have multi-protocol compatibility and dynamic protocol loading functions.

[0222] Experimental steps:

[0223] Device connection:

[0224] Three devices are connected: device 1 supports IEC 60870-5-103, device 2 supports IEC 60870-5-101, and device 3 uses a manufacturer-defined protocol, and communication connections are established with the devices on the testers of the present invention and the prior art, respectively.

[0225] Protocol identification and parsing:

[0226] The solution of the present invention: the tester automatically identifies the protocol type, loads the corresponding protocol stack, and performs message parsing.

[0227] Existing technical solution: Since only IEC 60870-5-103 is supported, the protocols of device 2 and device 3 cannot be correctly identified and parsed.

[0228] Test data record:

[0229] Measures communication success rate, data transmission stability (packet loss rate), resolution time and protocol compatibility.

[0230] Experimental results:

[0231]

[0232] analyze:

[0233] The solution of the present invention: supports dynamic loading and identification of multiple protocols, can communicate with multiple devices, has a short parsing time, a packet loss rate of 0, and exhibits extremely high compatibility and stability;

[0234] Existing technical solution: only supports a single protocol, device 2 and device 3 cannot communicate, and there are serious compatibility issues.

[0235] Comparative experiment 2: Data collection and analysis experiment

[0236] Purpose:

[0237] Test different solutions in terms of collection capability, parsing speed and data integrity when collecting various data types of equipment (such as telemetry, telesignaling, set values, action information, fault information).

[0238] Experimental equipment:

[0239] The solution of the present invention: supports the collection and analysis of multiple data types, including telemetry, telesignaling, set value, action information, and fault information;

[0240] Existing technical solutions: only support the collection of telemetry and telesignaling data, and cannot process constant value and fault information.

[0241] Experimental steps:

[0242] Device connection:

[0243] Connect the tester to device 1 (IEC 60870-5-103) and device 2 (IEC 60870-5-101) respectively and start data acquisition.

[0244] Data collection and processing:

[0245] The solution of the present invention: collects all relevant data of the equipment (telemetry, telesignaling, set value, action information, fault information), and performs data analysis;

[0246] Existing technical solutions: only collect telemetry and telesignaling data, and are unable to analyze constant values, action information, and fault information.

[0247] Test data record:

[0248] Measure data acquisition success rate, resolution time, data integrity, and acquisition speed.

[0249] Experimental results:

[0250]

[0251] analyze:

[0252] The solution of the present invention: can collect and process various data types (such as fixed values ​​and fault information), has fast parsing speed and 100% data integrity;

[0253] Existing technical solutions: only support basic data types, lack the ability to parse set values ​​and fault information, have poor data integrity, and cannot meet usage requirements in complex scenarios.

[0254] Comparative experiment 3: Fault diagnosis algorithm and scalability experiment

[0255] Purpose:

[0256] Test the differences between the two solutions in terms of fault diagnosis response time, accuracy, and fault mode expansion capability.

[0257] Experimental equipment:

[0258] The solution of the present invention: adopts an efficient fault diagnosis algorithm, supports feature extraction, anomaly detection, fault pattern matching, and has the ability to dynamically update the fault pattern library;

[0259] Existing technical solution: adopts a simple threshold detection algorithm and cannot expand new fault diagnosis modes.

[0260] Experimental steps:

[0261] Device connection and fault injection:

[0262] Connect the tester to device 1 and artificially inject faults (such as short circuit, overcurrent, circuit breaker malfunction, etc.) into the device to observe the fault diagnosis capability of the tester.

[0263] Troubleshooting process:

[0264] The solution of the present invention: automatically extracts data features, performs anomaly detection, matches patterns in the fault pattern library, and quickly locates the cause of the fault;

[0265] Existing technical solutions: using fixed thresholds to determine whether data is abnormal, which cannot match complex failure modes.

[0266] Failure mode scalability testing:

[0267] Try adding new failure modes to the system and observe the system's response time and ability to scale.

[0268] Test data record:

[0269] Measure fault response time, fault diagnosis accuracy, and fault mode library expansion time.

[0270] Experimental results:

[0271]

[0272] analyze:

[0273] The solution of the present invention has fast fault response speed, high diagnostic accuracy, supports dynamic expansion of fault mode library, and has good scalability;

[0274] Existing technical solutions: only support basic threshold detection, slow response time, poor fault diagnosis accuracy, lack of failure mode expansion capabilities, and difficult to adapt to future equipment update needs.

[0275] Comprehensive experimental conclusion:

[0276] Through three comparative experiments, the present invention supports dynamic loading and parsing of multiple protocols and can communicate seamlessly with a variety of devices, while the existing technology only supports a single protocol and cannot handle complex scenarios; the present invention can collect and process complete data of the equipment, including constants, action information and fault information, and the data integrity and parsing speed are far superior to the existing technology; the present invention adopts an efficient fault diagnosis algorithm with fast response speed and high accuracy, and supports dynamic expansion of the fault mode library, while the existing technical solutions are insufficient in diagnostic capabilities and scalability; these test results show that the present invention has higher flexibility, accuracy and scalability in practical applications, and can significantly improve the efficiency of fault testing and analysis of the relay protection information management substation.

[0277] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A fault testing and analysis method for a substation relay protection information management substation, characterized in that: The following steps are involved: a. Communicate with the substation relay protection information management substation through the tester, and the tester has the ability to be compatible with the communication protocol of the substation; b. Collect relevant data from the Baoxin substation using a tester; c. Analyze and process the collected data to find out the potential causes of failures; d. Use efficient fault diagnosis algorithms to quickly locate the causes of faults in the operation of the Baoxin substation.

2. A fault testing and analysis method for a substation relay protection information management substation according to claim 1, characterized in that: In step a, the tester supports IEC 60870-5-103, IEC 60870-5-101 / 104 and other vendor-defined protocols, including a protocol stack library, physical interface support, protocol parsing module, protocol compatibility layer and dynamic protocol loading; The protocol stack library is used to parse and encapsulate communication messages, including decoding of data frames, identification of message headers and tails, and extraction of data fields; The physical interface supports adapting to different connection requirements; The protocol parsing module includes: Message frame structure analysis, which is used to analyze specific message frames, including start flag, address, function code, data area, and check code; Data type mapping, which is used to convert binary data into specific types for analysis; The protocol compatibility layer includes: Protocol Driver Protocol Driver, including but not limited to starting or stopping the communication link with the device, handling communication timeout and packet loss; The protocol mapping rules are used to define specific fields and types in the data frame through the configuration file or UI interface. The dynamic protocol loading makes the tester architecture modular and supports the loading and upgrading of dynamic protocols.

3. A fault testing and analysis method for a substation relay protection information management substation according to claim 1, characterized in that: In the step a, the tester has multiple interfaces, including an Ethernet interface, an RS-485 interface and an RS-232 interface, for physically connecting to different types of relay protection information management substation equipment.

4. A fault testing and analysis method for a substation relay protection information management substation according to claim 1, characterized in that: In step b, the relevant data includes telemetry data, telesignaling data, constant value data, action information and fault information.

5. A fault testing and analysis method for a substation relay protection information management substation according to claim 1, characterized in that: In step c, the tester has multi-level data analysis capabilities and can perform basic data analysis, historical data comparison and contextual correlation analysis on telemetry data, telesignaling data, constant value data, action information and fault information.

6. A fault testing and analysis method for a substation relay protection information management substation according to claim 1, characterized in that: In step c, the user interface of the tester has a simple and intuitive visualization function, which can graphically display the trend of the collected data, abnormal points, and the diagnosed fault type and cause; The user interface of the tester has a simple and intuitive visualization function, which can graphically display the trends, abnormal points, and diagnosed fault types and causes of the collected data, and the user can zoom in, zoom out, and pan the data charts displayed in the graphical manner to deeply view the detailed data of each time period; The user interface has simple navigation and operation functions, and the user can quickly complete equipment selection, start and stop fault diagnosis, data browsing and report generation operations by clicking or dragging elements in the interface.

7. A fault testing and analysis method for a substation relay protection information management substation according to claim 1, characterized in that: In step c, the analysis includes the following steps: (1) Data classification: First, the collected raw data is classified by type, and each type of data is represented using a specific structure or format; (2) Data decoding: Decode the collected data according to the communication protocol used to extract the value and status information; (3) Timestamp synchronization: Timestamp all data to ensure that data from different devices or different types can be compared on the same timeline; The formats in (1) include but are not limited to JSON and XML, and (2) further includes parsing the address, function code, data field and check code in the data frame.

8. A fault testing and analysis method for a substation relay protection information management substation according to claim 1, characterized in that: In step c, the processing includes the following steps: S1. Data preprocessing: data denoising, abnormal data processing and data formatting; S2. Feature extraction: Extract the average value, maximum value, minimum value and fluctuation range from the telemetry data; Remote signaling data extracts time series information of equipment status changes and identifies key status change points; The state change points include but are not limited to circuit breaker tripping and switch action; S3. Data anomaly detection: Use the analysis results to determine whether the data is abnormal, and mark or further analyze the abnormal data; Whether the data is abnormal is identified by the following formula: Among them, x is the data value, μ is the mean value, σ is the standard deviation, and z is the threshold standard. When |z|>z threshold , then mark the data as abnormal; S4. Historical data comparison and trend analysis: Compare the currently collected data with historical data to determine the abnormality or trend of equipment operation; S5. Fault pattern matching and report generation: Match it with the predefined fault pattern library to quickly determine the possible fault type, generate a fault diagnosis report, and display the analysis results to the user.

9. A fault testing and analysis method for a substation relay protection information management substation according to claim 1, characterized in that: The efficient fault diagnosis algorithm formula is: Among them, fault is the matched fault type or mode number, j is the index number of the fault mode, and different modes are selected from the fault mode library. i is the index number of the feature, from 1 to n, representing all the extracted features, and x i is the characteristic value currently collected, such as current and voltage, μ i is the average value of the corresponding feature i in the historical data, used as a reference for standardization, σ i is the standard deviation of feature i, indicating the fluctuation range of the feature value, and is the fault mode M j The value corresponding to feature i in represents the feature value in a specific fault mode. is the modulus of the current feature vector after normalization, indicating the comprehensive normalization result of all features. is the failure mode vector M j The modulus represents the characteristic intensity of the failure mode.

10. A fault testing and analysis method for a substation relay protection information management substation according to claim 1, characterized in that: The efficient fault diagnosis algorithm includes the following stages: (A) Feature extraction: x in the formula i Indicates the real-time data collected from the Baoxin substation, such as current, voltage and other characteristics; (B) Anomaly detection: By i After standardization, the formula automatically detects abnormal feature values; (C) Fault mode matching: The formula compares the real-time data with the historical fault mode library by calculating the cosine similarity and selects the most likely fault mode; (D) Fault location: The final output fault corresponds to the most similar fault mode, which helps to quickly locate the problem.

Images