Protection measurement and control device engineering adaptation and batch debugging method based on universal platform
By generating an engineering database through data acquisition and standardized processing, and automatically generating configuration files for parallel download and automated testing, the problem of low efficiency and poor reliability of protection and control devices in substation projects has been solved, achieving efficient and reliable engineering adaptation and batch debugging.
Patent Information
- Application Number
- CN202511361572.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-23
- Publication Date
- 2025-12-09
AI Technical Summary
In existing technologies, protection and control devices based on general platforms suffer from low efficiency, poor reliability, and insufficient standardization in substation engineering implementation. This is especially true in ultra-large-scale substations or complete substation renovation projects, where a large amount of manual operation is required and configuration errors or debugging oversights are prone to occur, leading to safety hazards and low efficiency.
The system employs data acquisition and standardized processing to generate an engineering database, automatically generates configuration files through difference analysis, downloads them in parallel, and performs automated testing to achieve batch debugging and verification, thereby generating standardized engineering deliverables.
It greatly improves engineering efficiency, significantly enhances accuracy and reliability, achieves a high degree of standardization and traceability, reduces human error, shortens the project cycle, and improves the reliability of substation commissioning.
Smart Images
Figure CN121098720A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of power system measurement and control technology, and particularly relates to an engineering adaptation and batch debugging method for protection and control devices based on a general platform. Background Technology
[0002] With the deepening of smart grid construction, the scale of substation automation systems is constantly expanding, placing higher demands on the reliability of protection and control devices and the efficiency of engineering implementation. To reduce costs and improve interoperability, developing protection and control devices based on general-purpose hardware and software platforms has become the mainstream trend in the industry. However, in specific engineering applications, general-purpose platform devices still require a large amount of on-site adaptation and debugging work based on the substation's primary wiring, operating rules, and protection settings. This constitutes the "last mile" bottleneck for technology implementation.
[0003] Currently, traditional engineering implementation methods heavily rely on engineers' manual experience. The configuration process is largely manual, requiring engineers to consult numerous design drawings, setting sheets, and signal lists, setting, verifying, and downloading parameters one by one using specialized configuration tools. The commissioning phase necessitates manual operation of testing instruments, applying analog quantities one by one, and observing device behavior and waveform recordings to determine correctness. This method has significant drawbacks: first, it is extremely inefficient, especially for ultra-large-scale substations or complete substation upgrade projects, requiring a large investment of manpower and time for repetitive work; second, it is prone to configuration errors or commissioning oversights due to human negligence or fatigue, creating potential safety hazards; and third, project deliverables (such as commissioning reports) have low standardization, making digital management and traceability difficult. Summary of the Invention
[0004] The technical problem to be solved by the present invention is to provide an engineering adaptation and batch debugging method for protection and control devices based on a general platform, so as to solve the problems of low efficiency, poor reliability and insufficient standardization in the existing technology.
[0005] Technical solution of the present invention:
[0006] A method for engineering adaptation and batch commissioning of protection and control devices based on a general platform, comprising:
[0007] Step 1: Collect template files of general protection and control devices, system configuration files of the target substation, real-time data of on-site commissioning equipment, and engineering-specific parameter tables, and perform parsing, extraction, and correlation mapping to generate a standardized engineering database;
[0008] Step 2: Based on the engineering database, generate configuration files for general protection and control devices through difference analysis and matching of engineering requirements;
[0009] Step 3: Deploy the generated configuration files to each target device in batches using a parallel download method, and verify the download results.
[0010] Step 4: Execute the predefined test case sequence, apply test signals to the target device, collect response data, and automatically determine the test results based on preset criteria;
[0011] Step 5: Summarize the configuration files, debugging results, and verification reports to generate the final project deliverables and archive them.
[0012] The method for collecting template files for general protection and control devices includes: exporting a capability description file from the general device platform, which defines all logical nodes (LN), data objects (DO), configurable protection function blocks, input / output signals, and communication parameters supported by the device; the system configuration file for the target substation is from the final version of the SCD file from the design institute, which includes the primary wiring of the entire substation, the instantiation configuration of all IEDs, communication configuration, and, most importantly, the primary system relationships of the substation; the project-specific parameter table includes a protection setting list, a soft pressure plate activation / deactivation list, a signal point table, and a control logic diagram; the project-specific parameter table; and real-time data from the field commissioning equipment, including actual operating data of the device collected by the commissioning interface gateway during the commissioning phase.
[0013] The method for generating a standardized engineering database includes: extracting logical nodes, data objects, communication parameters, and primary system association information by parsing system configuration files and template files; reading engineering-specific parameter tables to obtain protection settings, soft pressure plate activation / deactivation status, and signal point table information; and associating the parameters in the engineering-specific parameter tables with the information extracted from the system configuration files and template files through keyword matching and predefined mapping rules to construct the standardized engineering database.
[0014] The methods for parsing, extracting, and associating mappings include: using an XML parser and a file reader to convert semi-structured and unstructured data into a unified, standardized data model within the system; automatically associating data based on keyword matching and predefined mapping rules, including descriptor specifications and naming conventions; and manually confirming and mapping entries that cannot be automatically associated.
[0015] The method for generating the configuration file includes: comparing the engineering configuration items defined in the engineering database with the device function items defined in the template file one by one to identify the compatible items and the differences; for the compatible items, filling the setpoint parameters into the corresponding data object of the configuration template; and compiling the control logic description into the logic equations that the device can execute to generate the final configuration file.
[0016] The method for compiling control logic descriptions into logic equations includes: converting control logic diagrams or natural language descriptions in the engineering database into executable logic equations or program code within the device; and generating the device's CID file according to the GSEControl and DataSet configurations defined in the SCD file for the communication and mapping section.
[0017] The parallel download and verification methods include: using multi-threading technology to establish concurrent connections with each target device to perform parallel download of configuration files; and calculating the checksum of the configuration file downloaded to the device and comparing it with the checksum of the local configuration file. If they match, the verification passes.
[0018] The check code is verified using a cyclic redundancy check code or by comparing the content line by line.
[0019] The method for automatically determining test results based on preset criteria includes: real-time acquisition of the action signal, action time, and action value of the target device; and, based on the preset expected action value I_expected and expected action time T_expected in the test case, determining whether the acquired actual action value I_actual satisfies I_actual ≈ I_expected, and whether the actual action time T_actual satisfies T_actual < T_expected + Δt, where Δt is the allowable error threshold, thereby determining the test result.
[0020] The beneficial effects of this invention are:
[0021] This invention greatly improves engineering efficiency: by automatically collecting, standardizing, and associating multi-source data, it replaces the tedious manual review and entry work; through parallel downloading and automated testing, it enables batch processing of multiple devices simultaneously, freeing engineers from repetitive labor, shortening the engineering cycle, and improving efficiency by several times or even dozens of times.
[0022] This invention significantly improves accuracy and reliability: fully automated processing avoids human error; the post-download verification mechanism ensures the integrity and correctness of the configuration file; and the automatic execution of test criteria eliminates the subjectivity and oversight of manual judgment, greatly reducing safety risks caused by configuration or debugging errors and improving the reliability of substation commissioning.
[0023] This invention achieves a high degree of standardization and traceability: the entire process is system-driven, forcibly following predefined rules and standards, ensuring consistency in output results across different projects and personnel. All operation logs, configuration files, test data, and reports are automatically generated and electronically archived, forming a complete, accurate, and traceable digital delivery chain, providing a solid data foundation for subsequent operation and maintenance.
[0024] This invention possesses excellent versatility and scalability: its core lies in processing logic and procedures, rather than relying on specific device models. Its data parsing engine, logic compiler, and other modules can expand their application scope by adapting to different manufacturers' device templates (ICDs) and project file formats (SCDs), making it suitable for various protection and control devices based on general platforms, with broad prospects for widespread application.
[0025] In summary, this invention forms a complete closed loop from engineering design data to operable devices and then to archived commissioning reports. It emphasizes data standardization, automated processing (analysis, generation, download, and testing), and batch processing of operations. The data in each link originates from the output of the previous link, and the logic is closely related, ultimately significantly improving the implementation efficiency, accuracy, and standardization level of protection and control devices in substation projects.
[0026] It solves the problems of low efficiency, poor reliability and insufficient standardization in existing technologies. Attached Figure Description
[0027] Figure 1 This is a schematic diagram of the process of the present invention. Detailed Implementation
[0028] A method for engineering adaptation and batch commissioning of protection and control devices based on a general platform, comprising:
[0029] Step 1: Data Acquisition and Standardization: Collect template files of general protection and control devices, system configuration files of the target substation, and engineering-specific parameter tables. Analyze, extract, and map these multi-source data to generate a standardized engineering database.
[0030] By parsing system configuration files and template files, logical nodes, data objects, communication parameters, and primary system relationship information are extracted.
[0031] Read the specific parameter table of the project to obtain the protection settings, soft pressure plate activation / deactivation status and signal point table information;
[0032] By using keyword matching and predefined mapping rules, parameters in the engineering-specific parameter table are associated with information extracted from the system configuration file and the template file to construct the standardized engineering database, in which each device instance is associated with its configuration items and function items.
[0033] Step 1 specifically includes:
[0034] Step 1.1: Collect data information:
[0035] ①: General Device Basic Template Library (ICD / CID File): Export the capability description file (such as an ICD file conforming to the IEC 61850 standard) from the general device platform. This file defines all logical nodes (LNs), data objects (DOs), configurable protection function blocks, input / output signals, communication parameters, etc. supported by the device. This is the device's "capability list".
[0036] ②: Substation SCD file (system configuration description of the entire station): The final version of the SCD file from the design institute contains the primary wiring of the entire station, the instantiation configuration of all IEDs, the communication configuration, and the most important substation primary system relationship (such as which protection device is responsible for protecting which circuit breaker and which bus section).
[0037] ③: Engineering-specific parameter table (Excel / CSV / XML): A list of specific engineering parameters provided by the designer, including: protection setting list (such as overcurrent stage I current and time); soft pressure plate activation / deactivation list; signal point table (such as signal names and address mappings that need to be sent to the monitoring system); control logic diagram (or simplified logic condition description).
[0038] ④: Real-time data of on-site commissioning equipment (via commissioning interface): During the commissioning phase, the actual operating data of the device is collected by the commissioning interface gateway, such as analog sample values (Ia, Ib, Ic, Ua, Ub, Uc), switch status, protection element action signals, etc.
[0039] Step 1.2, Data Processing Logic and Principles:
[0040] Data parsing and extraction:
[0041] The system's built-in parsing engine parses SCD files, ICD files, and external parameter tables respectively.
[0042] Specifically, an XML parser (for SCD / ICD) and a file reader (for Excel / CSV) are used to convert semi-structured and unstructured data into a unified standardized data model (such as an object-oriented IED device model, signal point table model, setpoint model, etc.) within the system.
[0043] Data association and mapping:
[0044] Associate data from different sources. For example, associate the "101 circuit breaker trip" signal in the parameter table with the corresponding IED logic device, logic node, and data object in the SCD file.
[0045] Specifically, automatic association is performed based on keyword matching and predefined mapping rules (such as signal descriptor specifications and naming conventions). For entries that cannot be automatically associated, the system provides an interface for engineers to manually confirm and map them. This step bridges the gap between engineering requirements and device capabilities.
[0046] Step 1.3, Data Results: Generate a standardized, internally unified engineering database in which each device instance is associated with all the configuration items it must implement (from SCD and parameter tables) and all the functional items it can implement (from ICD).
[0047] Step 2, Intelligent Configuration Generation: Based on the engineering database, the matching degree between the device capabilities and engineering requirements is identified through difference analysis, and a configuration file suitable for general protection and control devices is automatically generated.
[0048] The engineering configuration items defined in the engineering database are compared one by one with the device function items defined in the template file to identify compatible items and differences.
[0049] For adaptable items, the setpoint parameters are filled into the corresponding data object of the configuration template; and the control logic description is compiled into a logic equation that the device can execute, generating the final configuration file.
[0050] The process of compiling the control logic description into a logic equation is as follows: the trip condition Output described by natural language or logic diagram is compiled into a logic function Output = Func_AND(Func_AND(Protection_OC1_Start, CB_Position_Close), Prot_SoftPlate_En), where Protection_OC1_Start is the overcurrent protection element action signal, CB_Position_Close is the circuit breaker position signal, Prot_SoftPlate_En is the soft plate status signal, and Func_AND is a logic AND function.
[0051] This is the system's "brain," responsible for calculating how to adapt general-purpose devices to specific projects.
[0052] Step 2.1: Input data information: the standardized engineering database generated in the previous stage.
[0053] Step 2.2, Data Processing Logic and Principles:
[0054] Gap Analysis
[0055] The system automatically compares the "Capability List" (ICD) of a single device with the "Task List" of that device in the project (configuration items from the SCD and parameter table).
[0056] Specifically, the system iterates through all configuration items assigned to the device in the engineering database and checks whether the corresponding functional module or signal point exists in the ICD. If it exists, it is marked as "compatible"; if it does not exist (for example, the project requires low-frequency load shedding function, but this general-purpose device has not purchased this function), it is marked as "difference item" and a report is generated, prompting the engineer to change the device model or modify the design.
[0057] Configuration logic generation
[0058] For all "adaptable" items, the system automatically generates executable configuration files for the device (such as CID files, setting files, and logic configuration files). Specifically:
[0059] Fixed value section: The values extracted from the parameter table are directly filled into the corresponding data object attributes in the ICD template.
[0060] Logic section: This is the core. The system has a built-in logic compiler that converts the control logic diagrams or natural language descriptions in the engineering database (such as "circuit breaker tripping conditions = overcurrent stage I action & circuit breaker closed position & protection soft pressure plate engaged") into executable logic equations or program code within the device.
[0061] The underlying logic is as follows:
[0062] Output = Func_AND(Func_AND(Protection_OC1_Start, CB_Position_Close),Prot_SoftPlate_En)
[0063] Among them, Output: Trip command. Protection_OC1_Start: Output signal from the overcurrent protection element inside the device. CB_Position_Close: Circuit breaker position signal (1=closed) from the device's input. Prot_SoftPlate_En: State of the device's soft plate variable. Func_AND: Logical AND function.
[0064] Communication and mapping section: Strictly follow the GSEControl and DataSet configurations defined in the SCD file to generate the device's CID file to ensure the correctness of communication with the station control layer.
[0065] Step 2.3, Data Results:
[0066] Generate a batch of complete configuration files (such as CID, .cfg, .txt, etc.) that are device-specific and can be directly downloaded.
[0067] Generate an engineering variance analysis report, listing all mismatches that require manual intervention.
[0068] Step 3, Batch Download and Verification: Deploy the generated configuration files to multiple target devices in batches using a parallel download method, and verify the download results.
[0069] Multi-threading technology is used to establish concurrent connections with multiple target devices to download configuration files in parallel. The verification process involves calculating the checksum of the configuration file downloaded to the device and comparing it with the checksum of the local configuration file. If they match, the verification passes.
[0070] The check code is a cyclic redundancy check code.
[0071] This step enables the generated configuration to be deployed efficiently and reliably to the field device.
[0072] Step 3.1, Input Data: Device configuration file generated in the previous stage. Target device address list (IP address or physical serial port address).
[0073] Step 3.2, Data Processing Logic and Principles:
[0074] Parallel download engine:
[0075] The system employs multi-threading technology to establish connections with multiple devices simultaneously (MMS / GOOSE or serial port) and download the configuration file to the target device.
[0076] Download tasks are placed in a queue, and idle worker threads retrieve tasks from the queue to execute, which greatly shortens the total deployment time of multiple devices.
[0077] Download verification (Checksum Verification):
[0078] After the file is downloaded, the system automatically reads the activated configuration content from the device and compares it with the downloaded source file.
[0079] Calculate the cyclic redundancy check (CRC32) code of the configuration file downloaded to the device or perform line-by-line content comparison.
[0080] Formula: CRC_Server = Calculate_CRC(Local_Config_File)
[0081] CRC_Device = Read_CRC_From_Device()
[0082] If CRC_Server == CRC_Device, the verification passes; otherwise, mark the device download as failed and try again.
[0083] Step 3.3, Data Results:
[0084] Generate batch download execution reports, clearly listing the download status (success / failure), time consumption, and other information for each device.
[0085] All devices have been loaded with the correct engineering configuration and are ready for commissioning.
[0086] Step 4, Automated Debugging and Verification: Execute a predefined sequence of test cases, apply test signals to the target device, collect its response data, and automatically determine the test results based on preset criteria.
[0087] The control relay protection tester outputs simulated fault current and voltage signals to the target device;
[0088] Real-time acquisition of the target device's action signals, action time, and action values;
[0089] Based on the preset expected action value I_expected and expected action time T_expected in the test case, it is determined whether the collected actual action value I_actual satisfies I_actual ≈ I_expected, and whether the actual action time T_actual satisfies T_actual < T_expected + Δt, where Δt is the allowable error threshold, thereby automatically determining whether the test passes or fails.
[0090] This stage replaces the traditional method of manually verifying each item with a handheld testing device, achieving efficient and standardized closed-loop testing.
[0091] Step 4.1: Input data information:
[0092] Test case library: predefined standardized test cases (such as "overcurrent I-stage verification" and "circuit breaker anti-pumping test").
[0093] Debugging command: The command issued by the system to the testing instrument (digital relay protection tester).
[0094] Data Acquisition Information: Feedback data (action time, action value, generated signal, etc.) collected in real time from the device through the debugging interface.
[0095] Step 4.2, Data Processing Logic and Principles:
[0096] Test sequence execution:
[0097] The system automatically selects test cases, controls the tester to output simulated fault quantities (such as simulating 50Hz, 1.2 times the rated current), and simultaneously monitors the device's response.
[0098] The system controls the tester via IEEE 488.2 (GPIB) or Ethernet protocol, accurately outputting current and voltage waveforms.
[0099] Automatic result determination criteria:
[0100] The system automatically compares the actual action results reported by the device with the expected results of the test cases. Specifically:
[0101] Action time criterion: T_actual < T_expected + Δt (Δt is the allowable error)
[0102] T_actual: The time from when the device receives the trip signal to when the tester starts outputting the fault value.
[0103] T_expected: The time set in the setting sheet.
[0104] Action value criterion: I_actual ≈ I_expected (within the precision range)
[0105] I_actual: The current value output by the tester.
[0106] I_expected: The current setpoint set in the setting sheet.
[0107] The system automatically determines whether each test is "passed" or "failed".
[0108] Step 4.3, Data Results:
[0109] Generate detailed automated debugging reports, including measured data, waveform records, and judgment results for each device and each test item.
[0110] Generate an overall commissioning certificate, indicating whether all devices in the entire project have passed the test.
[0111] Step 5: Results Archiving: Summarize the configuration files, debugging results, and verification reports to generate the final project deliverables and archive them.
[0112] Step 5.1 Input data information: reports, configuration files, and difference analysis results generated in all the preceding stages.
[0113] Step 5.2, Data Processing Logic and Principles:
[0114] The system categorizes and archives all data (final configuration files, all test reports, and download logs) according to project name, time, device model, etc., and generates a summary project implementation report (PDF format). This is achieved using a file management system and report generation engine.
[0115] Step 5.3, Final Data Results:
[0116] A complete set of traceable electronic engineering deliverables for delivery to owners and archiving, providing an accurate data foundation for subsequent operation and maintenance.
Claims
1. A method for engineering adaptation and batch debugging of protection and control devices based on a general platform, characterized in that: The method includes: Step 1: Collect template files of general protection and control devices, system configuration files of the target substation, real-time data of on-site commissioning equipment, and engineering-specific parameter tables, and perform parsing, extraction, and correlation mapping to generate a standardized engineering database; Step 2: Based on the engineering database, generate configuration files for general protection and control devices through difference analysis and matching of engineering requirements; Step 3: Deploy the generated configuration files to each target device in batches using a parallel download method, and verify the download results. Step 4: Execute the predefined test case sequence, apply test signals to the target device, collect response data, and automatically determine the test results based on preset criteria; Step 5: Summarize the configuration files, debugging results, and verification reports to generate the final project deliverables and archive them.
2. The method for engineering adaptation and batch debugging of protection and control devices based on a general platform according to claim 1, characterized in that: The method for collecting template files for general protection and control devices includes: exporting a capability description file from the general device platform, which defines all logical nodes (LN), data objects (DO), configurable protection function blocks, input / output signals, and communication parameters supported by the device; the system configuration file for the target substation is from the final version of the SCD file from the design institute, which includes the primary wiring of the entire substation, the instantiation configuration of all IEDs, communication configuration, and, most importantly, the primary system relationships of the substation; the project-specific parameter table includes a protection setting list, a soft pressure plate activation / deactivation list, a signal point table, and a control logic diagram; the project-specific parameter table; and real-time data from the field commissioning equipment, including actual operating data of the device collected by the commissioning interface gateway during the commissioning phase.
3. The method for engineering adaptation and batch debugging of protection and control devices based on a general platform according to claim 1, characterized in that: The method for generating a standardized engineering database includes: extracting logical nodes, data objects, communication parameters, and primary system association information by parsing system configuration files and template files; reading engineering-specific parameter tables to obtain protection settings, soft pressure plate activation / deactivation status, and signal point table information; and associating the parameters in the engineering-specific parameter tables with the information extracted from the system configuration files and template files through keyword matching and predefined mapping rules to construct the standardized engineering database.
4. The method for engineering adaptation and batch debugging of protection and control devices based on a general platform according to claim 1, characterized in that: The methods for parsing, extracting, and associating mappings include: using an XML parser and a file reader to convert semi-structured and unstructured data into a unified, standardized data model within the system; automatically associating data based on keyword matching and predefined mapping rules, including descriptor specifications and naming conventions; and manually confirming and mapping entries that cannot be automatically associated.
5. The method for engineering adaptation and batch debugging of protection and control devices based on a general platform according to claim 1, characterized in that: The method for generating the configuration file includes: comparing the engineering configuration items defined in the engineering database with the device function items defined in the template file one by one to identify the compatible items and the differences; for the compatible items, filling the setpoint parameters into the corresponding data object of the configuration template; and compiling the control logic description into the logic equations that the device can execute to generate the final configuration file.
6. The method for engineering adaptation and batch debugging of protection and control devices based on a general platform according to claim 5, characterized in that: The method for compiling control logic descriptions into logic equations includes: converting control logic diagrams or natural language descriptions in the engineering database into executable logic equations or program code within the device; and generating the device's CID file according to the GSEControl and DataSet configurations defined in the SCD file for the communication and mapping section.
7. The method for engineering adaptation and batch debugging of protection and control devices based on a general platform according to claim 1, characterized in that: The parallel download and verification methods include: using multi-threading technology to establish concurrent connections with each target device to perform parallel download of configuration files; and calculating the checksum of the configuration file downloaded to the device and comparing it with the checksum of the local configuration file. If they match, the verification passes.
8. The method for engineering adaptation and batch debugging of protection and control devices based on a general platform according to claim 7, characterized in that: The check code is verified using a cyclic redundancy check code or by comparing the content line by line.
9. The method for engineering adaptation and batch debugging of protection and control devices based on a general platform according to claim 1, characterized in that: The method for automatically determining test results based on preset criteria includes: real-time acquisition of the action signal, action time, and action value of the target device; and, based on the preset expected action value I_expected and expected action time T_expected in the test case, determining whether the acquired actual action value I_actual satisfies I_actual ≈ I_expected, and whether the actual action time T_actual satisfies T_actual < T_expected + Δt, where Δt is the allowable error threshold, thereby determining the test result.