A pumped storage unit semi-physical joint debugging and rehearsal method and system, electronic equipment and storage medium

Abstract

This invention relates to the field of pumped storage power station construction, commissioning, and simulation technology, and particularly to a semi-physical hardware-in-the-loop (HIL) simulation method, system, electronic equipment, and storage medium for pumped storage units. The method includes: acquiring control logic-related data from the actual pumped storage power station unit and configuring this data into an electrical HIL simulation platform, enabling the HIL simulation platform to execute control logic consistent with the actual unit. This invention achieves high-fidelity replication of control logic by importing the actual unit's control logic and adapting it to the HIL simulation platform; it establishes a library of multiple commissioning scenarios to comprehensively verify the control logic; it drives synchronous closed-loop commissioning of primary and secondary modules, proactively identifying problems and reducing the risk and timeframe of actual unit commissioning; it quantitatively evaluates control logic performance from four dimensions, automatically detecting logic conflicts and timing deviations; and it provides data support for subsequent optimization scheme generation and secondary verification to form a closed-loop optimization, ensuring safe unit operation.

Description

Technical Field

[0001] This invention relates to the field of construction, commissioning and simulation technology of pumped storage power stations, and in particular to a semi-physical commissioning and pre-simulation method, system and electronic equipment and storage medium for pumped storage units. Background Technology

[0002] As the core peak-shaving and frequency-regulating power source of the new power system, the pumped storage power station's overall control logic covers complex processes such as unit start-up / shutdown, pumping / generation / phase regulation switching, fault protection actions, and multi-equipment collaborative linkage. It involves the coordinated control of multiple core equipment such as computer monitoring systems, relay protection devices, SFC, excitation systems, and speed regulation systems.

[0003] Currently, the full-station control logic integration testing before actual equipment commissioning mainly relies on direct integration testing with the actual equipment or conventional hardware-in-the-loop (HIL) simulation testing. While direct integration testing with the actual equipment can reflect actual operating conditions, new equipment has not been fully validated, and there are risks such as control logic conflicts and parameter mismatches, which may lead to equipment malfunctions, shutdowns, or even damage. At the same time, HIL integration testing is limited by equipment installation progress, site environment, and power grid dispatch, making it difficult to conduct continuous full-scenario testing, and the integration testing cycle is usually as long as 1-3 months. Existing HIL simulation platforms are mostly used for operation and maintenance training or new equipment verification, and have not built a full-process integration testing system for control logic integration testing before actual equipment commissioning. Moreover, the scenario coverage is incomplete (such as the difficulty in simulating complex scenarios such as extreme operating conditions and compound faults), and they lack core functions such as control logic conflict detection, timing deviation analysis, and fault tracing.

[0004] The aforementioned existing technologies have the following drawbacks: First, real-machine joint debugging is risky and inefficient, and it is inconvenient to simulate extreme working conditions and complex faults, resulting in insufficient scenario coverage. Second, existing hardware-in-the-loop simulation platforms do not focus on joint debugging scenarios before real-machine commissioning, and lack quantitative evaluation standards for the accuracy, real-time response, collaborative adaptability, and logical integrity of control logic actions. The joint debugging results rely on the experience judgment of operation and maintenance personnel, making it difficult to identify hidden risks. Third, there is a lack of automated logic conflict detection, timing deviation location, and fault tracing mechanisms, resulting in low problem-solving efficiency and difficulty in forming a closed-loop process. Summary of the Invention

[0005] In view of this, the purpose of the present invention is to provide a semi-physical commissioning simulation method, system, electronic equipment, and storage medium for pumped storage units.

[0006] In a first aspect, embodiments of the present invention provide a semi-physical commissioning and pre-simulation method for pumped storage units, comprising: Acquire the control logic-related data of the actual pumped storage power station and configure the control logic-related data into the electrical hardware-in-the-loop simulation platform of the pumped storage power station so that the hardware-in-the-loop simulation platform executes the control logic consistent with the actual machine; Construct a set of joint debugging test cases, which includes multiple joint debugging scenarios for verifying the performance of control logic under different operating conditions; Based on the joint debugging test case set and the preset joint debugging pre-drill parameters, drive the primary equipment simulation module, simulated switch module, interface conversion module and secondary physical panel module in the semi-physical simulation platform to run synchronously in a closed loop, and collect the full process operation data; Based on full-process operation data, the performance of the control logic is quantitatively evaluated from multiple dimensions, including at least action accuracy, real-time response, collaborative adaptability, and logical integrity, and logical conflicts or timing deviations in the control logic are automatically detected.

[0007] In conjunction with the first aspect, the steps of acquiring the control logic-related data of the actual pumped storage power station and configuring this data into the pumped storage power station electrical hardware-in-the-loop simulation platform include: The control logic file of the real machine is parsed, and the parameters of the real machine are automatically mapped to the primary equipment simulation module and the secondary physical cabinet module. The communication protocol between the semi-physical simulation platform and the control logic is also configured. Generate a control logic replication verification report to verify the consistency between the replicated logic and the actual device logic.

[0008] In conjunction with the first aspect, the steps for constructing a set of integration test cases include: Establish a set of joint debugging test cases that includes at least the following scenarios: normal operating condition joint debugging scenarios, extreme operating condition joint debugging scenarios, fault protection joint debugging scenarios, and multi-device collaborative joint debugging scenarios. Among them, the conventional operating condition joint commissioning scenarios include at least one of the following: unit pumping start-up, power generation start-up, operating condition switching, normal shutdown, excitation regulation, speed regulation, and static frequency converter start-up and shutdown control; the extreme operating condition joint commissioning scenarios include at least one of the following: grid voltage surge or drop, grid frequency fluctuation, unit overload or low load operation, continuous operating condition switching, simultaneous start-up or shutdown of multiple units, islanded operation, and N-1 maintenance mode; the fault protection joint commissioning scenarios include at least one of the following: single fault, compound fault, protection device failure to operate or maloperation, and fault reclosing; the multi-equipment collaborative joint commissioning scenarios include at least one of the following: unit local control unit and computer monitoring system collaboration, relay protection device and static frequency converter start-up or excitation system collaboration, multi-unit local control unit collaboration, DC system and secondary equipment collaboration, and fire protection system and fault protection collaboration.

[0009] In conjunction with the first aspect, the steps for constructing a set of integration test cases also include: In response to custom extension instructions, add new scenes by importing scene configuration files.

[0010] In conjunction with the first aspect, the steps for synchronously and in a closed loop operating system, involving the primary equipment simulation module, analog switch module, interface conversion module, and secondary physical control panel module in the hardware-in-the-loop simulation platform, and collecting full-process operation data, include: Initialize the primary equipment simulation module, simulation switch module, interface conversion module and secondary physical panel module, load the control logic, the joint debugging scenarios in the joint debugging test case set and the preset joint debugging pre-run parameters; Control commands are issued through the coordination control module or locally through the unit's local control unit; The secondary physical panel module executes control logic and outputs signals, which are then transmitted to the primary equipment simulation module and the analog switch module via the interface conversion module. Feedback signals from the primary equipment simulation module and the analog switch module are transmitted back to the secondary physical panel module via the interface conversion module, forming a closed loop; The data acquisition unit within the coordination and control module collects timestamped runtime data; When an anomaly is detected, a tiered alert or simulation pause is triggered, the abnormal data is recorded, and fault tracing is initiated.

[0011] In conjunction with the first aspect, it also includes: Based on the results of the quantitative assessment and the problems detected, an optimization scheme is generated, and the optimized control logic is then subjected to secondary joint testing and verification.

[0012] In conjunction with the first aspect, the steps of generating an optimized scheme based on the results of the quantitative evaluation and the detected optimization scheme, and then performing secondary joint debugging and verification on the optimized control logic, include: Generate a joint debugging rehearsal report that includes a comprehensive score, a problem list, and joint debugging process data; For the detected problems, optimization solutions are generated, including adjusting logic priorities, adding interlocking mechanisms, correcting action delay parameters, adjusting protection settings, optimizing communication protocol configuration, or supplementing abnormal handling logic. The optimized control logic is then subjected to secondary joint debugging and verification, including full reproduction and verification of the original problem scenario and sampling verification of the target joint debugging scenario where no problem is involved. When the overall score of the second joint debugging verification reaches the preset score, the optimization is deemed qualified.

[0013] Secondly, a semi-physical hardware-in-the-loop (HIL) simulation system for pumped storage units is applied to an electrical HIL simulation platform for pumped storage power stations. The HIL simulation platform includes a primary equipment simulation module, an interface conversion module, a simulated switch module, a secondary physical control panel module, and a coordination control module. The system includes: The control logic replication and adaptation module is used to acquire the control logic related data of the real machine and configure the control logic related data of the real machine to the hardware-in-the-loop simulation platform; the control logic replication and adaptation module has a built-in logic parsing engine and consistency verification unit; The integration testing scenario library construction module is used to build and store integration testing case sets; The joint debugging and pre-drill parameter configuration module is used to configure the joint debugging and pre-drill parameters; The semi-physical closed-loop joint debugging and execution module is connected to the primary equipment simulation module, interface conversion module, analog switch module, and secondary physical panel module respectively. It is used to drive the modules to operate synchronously in a closed loop and collect full-process operation data. The semi-physical closed-loop joint debugging and execution module has a built-in timing synchronization control unit and an anomaly monitoring unit. The control logic quantitative evaluation module, connected to the semi-physical closed-loop joint debugging and execution module, is used to quantitatively evaluate the control logic performance from multiple dimensions and automatically detect problems; the control logic quantitative evaluation module has a built-in problem localization engine and data visualization unit; The optimization scheme generation and verification module is connected to the control logic quantitative evaluation module and the control logic replication and adaptation module to generate optimization schemes and support secondary joint debugging and verification. The control logic replication and adaptation module, the joint debugging scenario library construction module, the joint debugging pre-simulation parameter configuration module, the semi-physical closed-loop joint debugging execution module, the control logic quantitative evaluation module, and the optimization scheme generation and verification module interact with the coordination control module through standardized interfaces.

[0014] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the above-described method.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the method described above.

[0016] The embodiments of the present invention bring the following beneficial effects: The present invention provides a semi-physical commissioning and pre-simulation method, system, electronic equipment, and storage medium for pumped storage units. The method includes: acquiring control logic-related data of the actual pumped storage power station and configuring the control logic-related data into the electrical semi-physical simulation platform of the pumped storage power station so that the semi-physical simulation platform executes control logic consistent with the actual machine; constructing a joint commissioning test case set, which includes multiple joint commissioning scenarios for verifying the performance of the control logic under different operating conditions; driving the primary equipment simulation module, simulated switch module, interface conversion module, and secondary physical cabinet module in the semi-physical simulation platform to operate synchronously in a closed loop according to the joint commissioning test case set and preset joint commissioning and pre-simulation parameters, and collecting full-process operation data; based on the full-process operation data, quantitatively evaluating the performance of the control logic from multiple dimensions including at least action accuracy, response real-time performance, collaborative adaptability, and logical integrity, and automatically detecting logical conflicts or timing deviations in the control logic.

[0017] This invention achieves high-fidelity replication of control logic by importing real machine control logic and adapting it to a hardware-in-the-loop simulation platform; it builds a library of multiple joint debugging scenarios to comprehensively verify the control logic; it drives synchronous closed-loop joint debugging of primary and secondary modules to identify problems in advance and reduce the risk and cycle of real machine joint debugging; it quantitatively evaluates the performance of control logic from four dimensions and automatically detects logic conflicts and timing deviations; it provides data support for the generation of subsequent optimization schemes and the formation of closed-loop optimization through secondary verification, ensuring the safe commissioning of the unit.

[0018] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0019] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0020] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0021] Figure 1 This is a schematic diagram of the overall architecture of the semi-physical interconnection and pre-simulation system according to an embodiment of the present invention; Figure 2 This is a flowchart of the semi-physical integration and pre-simulation method according to an embodiment of the present invention; Figure 3 This is a schematic diagram of the electronic device structure provided in an embodiment of the present invention.

[0022] Figure label: 1-Control logic replication and adaptation module, 11-Logic parsing engine, 12-Consistency verification unit, 2-Integration debugging scenario library construction module, 3-Integration debugging pre-simulation parameter configuration module, 4-Semi-physical closed-loop integration debugging execution module, 41-Timing synchronization control unit, 42-Anomaly monitoring unit, 5-Control logic quantitative evaluation module, 51-Problem localization engine, 52-Data visualization unit, 6-Optimization scheme generation and verification module, 7-Primary equipment simulation module, 8-Interface conversion module, 9-Analog switch module, 10-Secondary physical panel module, 14-Coordination control module; 130 - Processor, 131 - Memory, 132 - Bus, 133 - Communication interface. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0024] To facilitate understanding of this embodiment, the technical terms used in this invention will be briefly introduced below.

[0025] A hardware-in-the-loop simulation platform: a system that connects real physical equipment (such as secondary control panels and control and protection devices) with computer simulation models (such as primary equipment electrical models) through an interface conversion module to achieve closed-loop testing. The platform in this invention includes a primary equipment simulation module 7, an interface conversion module 8, a simulated switch module 9, a secondary physical control panel module 10, and a coordination control module 14.

[0026] Primary Equipment Simulation Module 7: A software or hardware module that performs real-time numerical simulation of the electrical behavior and mechanical characteristics of primary equipment such as generator motors, main transformers, transmission lines, circuit breakers, and disconnect switches based on electromagnetic transient simulation algorithms.

[0027] Secondary physical control panel module 10: refers to physical control and protection equipment of the same model as the real machine, including unit LCU cabinet, SFC control and protection cabinet, relay protection cabinet, excitation regulation cabinet, speed controller cabinet, etc., used to execute the control logic of the real machine.

[0028] Coordination and Control Module 14: The core control unit of the hardware-in-the-loop simulation platform, responsible for the initialization of simulation tasks, timing synchronization, data acquisition, anomaly monitoring, and communication coordination with other modules.

[0029] SFC: Static Frequency Converter, used to drive pumped storage units from a stationary state to rated speed, enabling startup in pumping or phase-shifting operation.

[0030] LCU: Local Control Unit, responsible for local monitoring, control and protection of the unit, communicating with the computer monitoring system, and executing remote or local commands.

[0031] Control logic replication: The process of importing control logic files (such as ladder diagrams, function block diagrams, and configuration files) stored in the real PLC, protection devices, and monitoring systems into the hardware-in-the-loop simulation platform, and then using operations such as parsing, parameter mapping, and protocol adaptation to make the control logic executed by the platform completely consistent with that of the real machine.

[0032] Joint Commissioning Scenario Library: A collection of predefined test scenarios based on the actual operational needs of pumped storage power stations. Each scenario includes triggering conditions, operating parameters, expected results, and termination conditions. The scenario library covers four categories of scenarios: normal operating conditions, extreme operating conditions, fault protection, and multi-device collaboration.

[0033] Fault injection: During the semi-physical commissioning process, by modifying the parameters of the simulation model or sending simulated fault signals to secondary equipment, equipment failures or power grid anomalies are artificially created to verify the correctness of the protection actions of the control logic.

[0034] Quantitative evaluation system: Based on four dimensions—action accuracy, response timeliness, collaborative adaptability, and logical integrity—a system that sets up secondary evaluation indicators and assigns weights, and uses a weighted comprehensive scoring method to objectively score the performance of control logic.

[0035] After introducing the technical terms involved in this invention, the application scenarios and design concepts of the embodiments of this invention will be briefly described below.

[0036] The commissioning of pumped storage units is risky and time-consuming, and it is difficult to simulate extreme operating conditions and complex faults. Existing hardware-in-the-loop simulation platforms do not focus on pre-commissioning commissioning, lack quantitative assessment and logical conflict detection functions, and are difficult to form closed-loop optimization.

[0037] Based on this, embodiments of the present invention provide a semi-physical commissioning and pre-simulation method and system for pumped storage units.

[0038] Example 1 This invention provides a semi-physical hardware-in-the-loop simulation method for pumped storage units, applied to an electrical semi-physical simulation platform for pumped storage power stations, combined with... Figure 1 As shown, the hardware-in-the-loop simulation platform includes a primary equipment simulation module 7, an interface conversion module 8, a simulation switch module 9, a secondary physical control panel module 10, and a coordination control module 14. Combined with... Figure 2 As shown, the method includes: S110: Obtain the control logic-related data of the actual pumped storage power station and configure the control logic-related data into the electrical hardware-in-the-loop simulation platform of the pumped storage power station so that the hardware-in-the-loop simulation platform executes the control logic consistent with the actual machine.

[0039] S120, Construct a set of joint debugging test cases. The set of joint debugging test cases includes multiple joint debugging scenarios for verifying the performance of control logic under different operating conditions.

[0040] S130, based on the joint debugging test case set and preset joint debugging pre-drill parameters, drives the primary equipment simulation module, analog switch module, interface conversion module and secondary physical cabinet module in the hardware-in-the-loop simulation platform to run synchronously in a closed loop, and collects the entire process operation data.

[0041] S140, based on full-process operation data, quantitatively evaluates the performance of control logic from multiple dimensions, including at least action accuracy, real-time response, collaborative adaptability, and logical integrity, and automatically detects logical conflicts or timing deviations in the control logic.

[0042] This invention achieves high-fidelity replication of the actual machine control logic through S110, avoiding logic distortion; S120 constructs multiple joint debugging scenarios, covering normal, extreme, fault, and collaborative operating conditions, solving the problem of incomplete scenario coverage; S130 drives closed-loop joint debugging of primary and secondary modules based on the joint debugging test case set and pre-drill parameters, collecting full-process operation data; S140 quantitatively evaluates and automatically detects problems such as logic conflicts and timing deviations from four dimensions, providing objective quantitative standards to provide data support for further generating optimization schemes, conducting secondary verification, and forming closed-loop optimization, ensuring the safe commissioning of the unit.

[0043] In conjunction with the first aspect, step S110 acquires the control logic-related data of the actual pumped storage power station and configures the control logic-related data into the pumped storage power station electrical hardware-in-the-loop simulation platform, specifically including: S111 parses the control logic file of the real machine, automatically maps the parameters of the real machine equipment to the primary equipment simulation module and the secondary physical cabinet module, and configures the communication protocol between the semi-physical simulation platform and the control logic.

[0044] Parse the control logic file of the real machine. Through the logic parsing engine 11 built into the control logic replication and adaptation module 1, the imported control logic file of the real machine is automatically parsed. The control logic file includes, but is not limited to, IEC 61131-3 standard format files (such as function block diagrams, sequential function diagrams), PLC ladder diagram format files, and protection device configuration file format files.

[0045] The parsing process includes lexical analysis and syntax tree transformation of the input and output variables, logical judgment conditions, and action execution instructions of the control logic, extracting the complete logical hierarchy relationship, generating a visual logical flowchart, and performing syntax verification on the logical statements, automatically marking missing variable definitions or conflicting logical conditions.

[0046] The parameters of the actual equipment are automatically mapped to the primary equipment simulation module 7 and the secondary physical control panel module 10. The equipment parameter table of the actual equipment (such as the rated capacity of the generator motor, the rated voltage and impedance value of the main transformer, the rated current of the SFC, the control parameters of the excitation system and the speed regulation system, etc.) and the protection setting sheet (such as the overcurrent protection setting value, the overvoltage protection setting value, etc.) are imported. Through the parameter automatic mapping mechanism, the above parameters are accurately configured into the primary equipment simulation module 7 (used to simulate the electrical behavior of the main circuit) and the secondary physical control panel module 10 (including LCU, protection devices, SFC control cabinet, etc. of the same model as the actual equipment) to ensure that the parameters of the simulation model and the actual equipment are consistent with those of the actual equipment.

[0047] Furthermore, based on the actual communication standards used in the prototype device, the communication parameters of the interface conversion module 8 and the coordination control module 14 are configured, supporting mainstream industrial protocols including IEC 61850 MMS / GOOSE, Modbus, and Profibus. Through protocol adaptation, real-time data interaction is achieved between the primary equipment simulation module 7, the secondary physical panel module 10, and the control logic execution unit, ensuring that communication latency and transmission accuracy meet simulation requirements.

[0048] S112, Generate a control logic replication verification report to verify the consistency between the replicated logic and the real device logic.

[0049] A control logic replication verification report is generated, ensuring that the consistency between the replicated logic and the original logic meets the preset verification requirements. After completing the above parsing, parameter mapping, and communication adaptation, the consistency verification unit 12 performs dual verification on the replicated control logic and the original original logic: first, it uses a point-by-point parameter comparison method to check whether the mapping deviation between equipment parameters and protection settings is within the preset allowable range; second, it verifies whether the action execution results of the replicated logic and the original logic are consistent under all preset operating conditions through logic link traversal simulation. After verification, a replication verification report is generated to ensure that the consistency between the replicated logic and the original logic meets the preset verification requirements (e.g., consistency compliance threshold ≥ 99.5%), thereby ensuring the authenticity and reliability of subsequent joint debugging and pre-rehearsal.

[0050] In conjunction with the first aspect, the steps in step S120 for constructing the joint debugging test case set include: S121. Establish a set of joint debugging test cases that include at least the following scenarios: normal operating condition joint debugging, extreme operating condition joint debugging, fault protection joint debugging, and multi-device collaborative joint debugging.

[0051] Among them, the conventional operating condition joint commissioning scenarios include at least one of the following: unit pumping start-up, power generation start-up, operating condition switching, normal shutdown, excitation regulation, speed regulation, and static frequency converter start-up and shutdown control; the extreme operating condition joint commissioning scenarios include at least one of the following: grid voltage surge or drop, grid frequency fluctuation, unit overload or low load operation, continuous operating condition switching, simultaneous start-up or shutdown of multiple units, islanded operation, and N-1 maintenance mode; the fault protection joint commissioning scenarios include at least one of the following: single fault, compound fault, protection device failure to operate or maloperation, and fault reclosing; the multi-equipment collaborative joint commissioning scenarios include at least one of the following: unit local control unit and computer monitoring system collaboration, relay protection device and static frequency converter start-up or excitation system collaboration, multi-unit local control unit collaboration, DC system and secondary equipment collaboration, and fire protection system and fault protection collaboration.

[0052] In this embodiment, the joint commissioning test case set refers to a set of predefined joint commissioning scenarios designed to comprehensively verify the correctness, reliability, and robustness of the control logic before the pumped storage unit is put into operation.

[0053] The conventional operating condition commissioning scenario is used to verify the correctness of the control logic of pumped storage units under daily operating conditions such as normal start-up and shutdown, operating condition switching, and load regulation. It includes at least one of the following: pumping start-up, power generation start-up, operating condition switching, normal shutdown, excitation regulation, speed regulation, and start-up / shutdown control of the static frequency converter (SFC). For example, the pumping start-up scenario requires verification of the entire process logic of the SFC-driven unit from standstill to rated speed, excitation pressure build-up, phase switching switch closing, and grid connection; the operating condition switching scenario requires verification of the timing coordination of control commands and smooth parameter transitions during switching processes such as pumping-power generation, power generation-phase regulation, and phase regulation-pumping.

[0054] Extreme operating condition commissioning scenarios refer to the control logic response of the power grid or generating units under extreme operating conditions, including sub-scenarios such as sudden rise or fall of grid voltage (e.g., ±10% of rated voltage), grid frequency fluctuation (e.g., ±5% of rated frequency), overload operation of generating units (e.g., 110% of rated load) or stable combustion under low load (e.g., 10% of rated load), continuous multiple switching of operating conditions (e.g., pumping-generating-phase adjustment-pumping five times in a row), simultaneous start-up or shutdown of multiple generating units, islanded operation mode, and control logic response under N-1 maintenance mode.

[0055] The fault protection commissioning scenario is used to verify the correctness of the protection action of the control logic under equipment fault or abnormal conditions. It covers sub-scenarios such as single fault (e.g., generator stator grounding, main transformer inter-turn short circuit, line single-phase grounding or two-phase and three-phase short circuit, SFC commutation failure, excitation system demagnetization, speed control system failure, etc.), compound fault (e.g., main transformer inter-turn short circuit + circuit breaker failure, line high-resistance grounding + CT saturation, SFC commutation failure + excitation system false excitation, etc.), redundant response under protection device failure or false operation simulation, fault reclosing logic, and fault isolation and recovery control logic.

[0056] Multi-device collaborative commissioning scenarios are used to verify the collaborative control capabilities between different secondary devices and between secondary devices and primary devices. These include sub-scenarios such as collaborative control between the unit LCU and the computer monitoring system, collaborative operation between relay protection devices, SFC and excitation system, collaborative control between multiple unit LCUs, collaborative power supply control between DC system and secondary equipment, collaborative control between fire protection system and fault protection, and collaborative control between gate control system and unit start-up and shutdown.

[0057] By establishing the above four types of joint commissioning scenarios, we can fully cover all the operating conditions that need to be verified before the pumped storage unit is put into operation, and ensure the reliability and safety of the control logic under various normal, abnormal and extreme conditions.

[0058] As an example, the typical joint commissioning scenarios under normal operating conditions may include the following 12 sub-scenarios: unit pumping start-up (SFC start-up-excitation pressure building-speed regulation-grid connection), unit generating start-up (self-synchronous start-grid connection-load power increase), pumping-generating mode switching, generating-phase regulation mode switching, phase regulation-pumping mode switching, normal unit shutdown (generating shutdown, pumping shutdown, phase regulation shutdown), load distribution of multiple units operating in parallel, execution of remote control commands from the computer monitoring system, execution of local control commands from the unit LCU, excitation system regulation (voltage regulation, reactive power regulation), speed regulation system regulation (speed regulation, load regulation), and SFC start-up and switching control. Extreme operating condition commissioning scenarios can include eight sub-scenarios: sudden rise / fall in grid voltage (±10% of rated voltage), grid frequency fluctuation (±5% of rated frequency), unit overload operation (110% of rated load), stable combustion under low load (10% of rated load), continuous operating condition switching (pumping-generating-phase adjustment-pumping continuously for 5 times), simultaneous start / stop of multiple units, islanded operation mode, and N-1 maintenance mode. Fault protection commissioning scenarios can include 15 sub-scenarios: single fault (generator stator grounding, main transformer inter-turn short circuit, line single-phase grounding / two-phase / three-phase short circuit, SFC commutation failure, excitation system demagnetization, speed control system failure), compound fault (main transformer inter-turn short circuit + circuit breaker failure, line high-resistance grounding + CT saturation, SFC commutation failure + excitation system false excitation), protection device failure to operate / false operation simulation, fault reclosing logic, and fault isolation and recovery control logic. Multi-device collaborative commissioning scenarios can include six sub-scenarios: collaboration between unit LCU and computer monitoring system, collaboration between relay protection device and SFC and excitation system, collaboration between multiple unit LCUs, collaboration between DC system and secondary equipment, collaboration between fire protection system and fault protection, and collaboration between gate control system and unit start-up and shutdown.

[0059] In conjunction with the first aspect, step S120 also includes: S121, responding to custom extension instructions, adds a new scene by importing a scene configuration file.

[0060] To adapt to the personalized commissioning needs of different power plants or generating units, the commissioning scenario library supports custom expansion functions. Users can write scenario configuration files in a standard format (e.g., XML format) according to actual needs. These configuration files include basic scenario information tags (scenario name, type, applicable generating unit type), trigger condition tags (preceding equipment status, parameter thresholds, command triggering method), operating parameter tags (control logic execution thresholds, allowable deviations in action timing, fault injection parameters, etc.), expected result tags (action response requirements for each device, parameter change range, control logic execution result), and termination condition tags (normal termination judgment criteria, abnormal termination triggering conditions). After importing the configuration file, the system automatically performs format validation and parameter rationality verification. Once verification is successful, the new scenario is added to the commissioning scenario library and can be directly called and executed during subsequent commissioning rehearsals.

[0061] In conjunction with the first aspect, in step S130, the primary equipment simulation module, analog switch module, interface conversion module, and secondary physical cabinet module in the hardware-in-the-loop simulation platform operate synchronously in a closed loop, and collect full-process operation data, specifically including: S131, initialize the primary equipment simulation module, analog switch module, interface conversion module and secondary physical cabinet module, load the control logic, the joint debugging scenarios in the joint debugging test case set and the preset joint debugging pre-run parameters.

[0062] Before the semi-physical closed-loop commissioning rehearsal begins, the coordination control module 14 first initializes all modules involved in the simulation platform, ensuring that all modules are in their predetermined initial states (e.g., circuit breaker open, unit shutdown, simulation model parameters zeroed). Simultaneously, the control logic adapted in step S110, the commissioning scenario selected in step S120, and the rehearsal parameters configured in step S130 are loaded into their respective modules. Specifically, the control logic is loaded into the secondary physical control panel module 10 (e.g., unit LCU, protection devices, SFC control cabinet), while the commissioning scenario and rehearsal parameters are loaded into the coordination control module 14 and the primary equipment simulation module 7. After loading, the coordination control module 14 uniformly confirms the readiness status of each module. Only when all modules are ready is the subsequent closed-loop commissioning process allowed. This initialization and loading process is fundamental to ensuring the stable operation of the commissioning rehearsal according to the predetermined plan, avoiding malfunctions caused by missing parameters or inconsistent states.

[0063] S132 issues control commands through the coordination control module or through the unit's local control unit.

[0064] There are two methods for issuing control commands, which can be flexibly selected according to the needs of the joint commissioning scenario. The first method involves the coordination control module 14 simulating the role of the real machine's computer monitoring system, remotely issuing control commands to the secondary physical control panel module 10, such as issuing commands to start pumping, switch operating conditions, or clear faults. This method is suitable for verifying remote automatic control logic. The second method involves the unit's local control unit (LCU) in the secondary physical control panel module 10 simulating local operation and directly issuing control commands, such as triggering start-up or shutdown operations via the LCU touchscreen or buttons. This method is suitable for verifying local manual control logic and the collaboration between the LCU and the monitoring system. Both methods can realistically replicate the source of control commands during real machine operation, ensuring the realism of the joint commissioning rehearsal. During execution, the coordination control module 14 records the issuance time, content, and source of each control command, providing raw data for subsequent timing analysis.

[0065] S133, the secondary physical panel module executes control logic and outputs signals, which are transmitted to the primary equipment simulation module and the analog switch module via the interface conversion module.

[0066] After receiving control commands, the secondary physical control panel module 10 (including the same model as the actual unit's LCU cabinet, SFC control and protection cabinet, relay protection cabinet, excitation regulation cabinet, speed governor cabinet, etc.) performs calculations and judgments based on the loaded control logic and outputs corresponding control signals. For example, in a pumping start-up scenario, the SFC control cabinet will output a commutation switch closing command, and the excitation regulation cabinet will output an excitation voltage build-up command. The voltage levels, communication protocols, and physical interfaces of these control signals may be incompatible with the primary equipment simulation module 7 and the analog switch module 9. Therefore, they need to be electrically matched, signal conditioned, and converted through the interface conversion module 8. The interface conversion module 8 converts the switching signals (such as opening and closing commands) output by the secondary equipment into digital or analog signals that the simulation module can recognize. At the same time, it converts the analog signals such as voltage and current fed back by the simulation module into standard signals that the secondary equipment can receive (such as 4-20mA or GOOSE messages). Through the interface conversion module, a seamless connection between the real secondary equipment and the virtual primary equipment is achieved.

[0067] S134, the feedback signals from the primary equipment simulation module and the analog switch module are transmitted back to the secondary physical panel module via the interface conversion module, forming a closed loop.

[0068] The primary equipment simulation module 7 calculates the electrical and mechanical quantities of main equipment such as generators, transformers, and transmission lines in real time based on electromagnetic transient simulation algorithms (such as DDRTS software), including voltage, current, power, speed, and power angle. The simulated switch module 9 simulates the position status and operation process of switching equipment such as circuit breakers, disconnectors, and phase-changing disconnectors, such as simulating the arc transient during closing or the arc extinguishing process during opening. The feedback signals generated by these two modules (such as voltage establishment completion signal, speed reaching rated value signal, and switch position status) are transmitted back to the secondary physical control panel module 10 via the interface conversion module 8 as the basis for the next judgment of the control logic. For example, the SFC control cabinet will only issue an excitation voltage build-up command when it detects that the phase-changing disconnector has been closed and the unit speed has reached the set threshold; the excitation regulating cabinet will only issue a grid connection permission signal when it detects that the terminal voltage has reached the rated value. This closed-loop mechanism enables the secondary physical control panel module 10 to dynamically adjust the control output according to the real-time status feedback from the simulation system, thereby highly replicating the interaction between the control logic and the primary equipment during actual machine operation.

[0069] S135, collects timestamped running data through the data acquisition unit within the coordination control module 14.

[0070] The high-speed data acquisition unit built into the coordination control module 14 collects various operational data in real time throughout the entire commissioning process at a high sampling frequency (≥1kHz), and adds a high-precision timestamp (accuracy ≤1μs) to each data point to ensure the accuracy of subsequent time-series analysis. The collected data includes four main categories: control command data (such as the content, time, and source of the issued command), equipment status data (such as switch positions, protection action signals, and unit operating status), parameter change data (such as real-time waveforms of voltage, current, power, and speed), and communication interaction data (such as message transmission and reception time, protocol type, and data correctness). For example, in a pumping start-up scenario, the data acquisition unit records key timing nodes such as the SFC start-up command issuance time (t=0ms), the commutation switch closing time (t=200ms), the time for the generator motor to reach its rated speed (t=18000ms), and the time for excitation voltage build-up to complete (t=18035ms). All collected data is tagged and categorized according to a unified timestamp format and stored in a database, which can be used for real-time monitoring, offline analysis, and quantitative evaluation.

[0071] S136: When an anomaly is detected, a graded alert or simulation pause is triggered, the abnormal data is recorded, and fault tracing is initiated.

[0072] During the joint debugging and rehearsal process, the anomaly monitoring unit 42 employs a multi-dimensional real-time monitoring mechanism to classify and monitor four types of problems during the execution of control logic: parameter exceeding thresholds, action timeouts, communication anomalies, and logic conflicts. Parameter exceeding thresholds (such as voltage or current exceeding protection settings) and communication anomalies (such as data packet loss or timeouts) are set as Level 1 warnings, triggering real-time alerts and being highlighted in the visualization interface. Action timeouts (such as excitation voltage build-up delay exceeding allowable deviation after SFC startup) and logic conflicts (such as simultaneous triggering of mutually exclusive commands) are set as Level 2 warnings, automatically triggering simulation pauses to prevent erroneous logic from continuing to execute and causing simulation state chaos. When the simulation pauses, the system automatically records the scenario information at the time of the anomaly (such as the current joint debugging scenario name and executed steps), equipment status (key parameter values ​​of each module), and the complete anomaly data stream, and immediately initiates the fault tracing process.

[0073] Fault tracing involves four steps: abnormal data extraction (extracting data segments from stored data during abnormal periods), problem type determination (determining whether it's a timing deviation, setting mismatch, logical conflict, or communication anomaly based on preset rules), fault node location (identifying the specific module, logic statement, or communication link causing the problem through logical link analysis), and root cause analysis (analyzing the underlying cause of the anomaly, such as incorrect parameter settings, logical design flaws, or communication interference). Complete fault tracing results are automatically incorporated into the problem list of the subsequently generated joint debugging and pre-rehearsal report, providing precise basis for optimization solutions.

[0074] Understandably, the joint debugging and pre-run parameters can be configured after step S120, and can be pre-configured and stored. The specific steps for configuring the joint debugging and pre-run parameters include: S1301, Configure the control logic execution threshold, and ensure that the deviation of the execution threshold meets the preset accuracy requirements.

[0075] Based on the actual machine's protection setting sheet and equipment technical manual, action thresholds are set for various control logic parameters, such as overcurrent protection operating current, overvoltage protection operating voltage, and speed regulation range. The deviation of the configured execution thresholds must meet the preset accuracy requirements to ensure that the action triggering conditions in the joint commissioning and rehearsal are consistent with the actual machine's operating conditions.

[0076] For example, the allowable deviation of overcurrent protection operating current is ≤ ±2%, the allowable deviation of overvoltage protection operating voltage is ≤ ±2%, and the deviation of speed regulation range is ≤ ±2%. Add to S132: For example, the maximum allowable delay from SFC start-up to excitation voltage build-up is ≤ 50ms, and the maximum allowable delay from grid connection command issuance to circuit breaker closing is ≤ 30ms. Add to S133: Grounding resistance can be set to 0.1Ω~100Ω, and short-circuit current can be set to 1~5 times the rated current. Add to S134: Load change rate ≤ 5% rated load / second. Add to S135: Communication timeout threshold ≤ 100ms.

[0077] S1302, Configure the allowable deviation of action timing, which includes the timing deviation threshold of each device's actions during unit start-up, shutdown, and operating condition switching.

[0078] Based on the time requirements for the linkage of pumped storage power station equipment, a timing deviation threshold is set for the action sequence of each device. The allowable timing deviation includes the timing deviation threshold of each device's action during unit startup, shutdown, and operating condition switching. For example, the maximum allowable delay from SFC startup to excitation voltage build-up, the maximum allowable delay from grid connection command issuance to circuit breaker closing, etc., are used to subsequently evaluate the real-time response performance of the control logic.

[0079] S1303, Configure fault injection parameters. Fault injection parameters include fault type, fault occurrence time, fault duration, and fault severity.

[0080] Fault simulation parameters are set for the fault protection commissioning scenario. The fault injection parameters include fault type (such as single-phase grounding, phase-to-phase short circuit, turn-to-turn short circuit, commutation failure, etc.), fault occurrence time (i.e. the moment when the fault is injected during commissioning), fault duration, and fault severity (such as grounding resistance value, short-circuit current multiple, etc.) to verify the correctness of the protection action of the control logic under abnormal operating conditions.

[0081] S1304, Configure operating condition switching parameters, including load change rate.

[0082] For scenarios where the unit switches between different operating conditions, control parameters are set during the switching process. These parameters include the load change rate (such as the rate limit of load increase or decrease when switching from pumping to power generation) to ensure that the switching process is smooth and conforms to the actual operating characteristics of the unit.

[0083] S1305, Configure communication parameters, including communication timeout threshold.

[0084] To set communication rules for data interaction between modules in the hardware-in-the-loop simulation platform, communication parameters include communication timeout thresholds, which are the upper limit of time for judging communication abnormalities. They may also include communication protocol type, data transmission rate, etc., to ensure real-time and reliable transmission of control commands and feedback signals.

[0085] S1306, export the configured joint debugging and pre-run parameters as a parameter configuration file, or import the joint debugging and pre-run parameters from a saved parameter configuration file.

[0086] The parameters for joint debugging and pre-testing can be reused. Users can export the currently configured parameters as a parameter configuration file with one click (e.g., in encrypted format, containing information such as parameter name, value range, applicable scenarios, and configuration time). Alternatively, saved parameter configuration files can be directly imported during subsequent joint debugging or secondary verification, eliminating the need for reconfiguration. After importing, the system automatically matches the parameters with the device parameters of the current hardware-in-the-loop simulation platform. If the deviation exceeds the preset range, an adaptation warning log is generated.

[0087] In conjunction with the first aspect, step S140 includes: S141 sets at least one secondary evaluation index for each of the four dimensions of action accuracy, real-time response, collaborative adaptability and logical integrity, and assigns a corresponding weight to each secondary evaluation index.

[0088] The secondary evaluation indicators for the action accuracy dimension include command execution accuracy, action parameter accuracy, protection action accuracy, and timing matching accuracy, used to measure the consistency between the control logic output and the expected results. The secondary evaluation indicators for the real-time response dimension include command response delay, action execution duration, fault response delay, and communication transmission delay, used to evaluate the control logic's response speed to input changes. The secondary evaluation indicators for the coordination and adaptability dimension include equipment linkage adaptability, communication interaction adaptability, parameter matching adaptability, and operating condition switching adaptability, used to examine the coordination and cooperation capabilities between various devices and between devices and logic. The secondary evaluation indicators for the logic integrity dimension include scenario coverage integrity, anomaly handling integrity, redundant logic integrity, and fault recovery integrity, used to determine whether the control logic comprehensively covers various operating conditions and abnormal situations. Each secondary evaluation indicator is assigned a corresponding weight value according to its importance to overall performance; for example, action accuracy can be assigned a higher weight, and logic integrity a lower weight. Specific weight values ​​can be pre-set based on engineering experience or industry standards.

[0089] S142, based on the weights of each secondary evaluation indicator, uses a weighted comprehensive scoring method to calculate the comprehensive score of the control logic.

[0090] Specifically, each secondary evaluation indicator is first scored independently, based on the degree of deviation between the collected operational data and preset standards. For example, for instruction execution accuracy, full marks are awarded if the deviation between the actual execution result and the expected result is within a preset allowable range; otherwise, points are deducted proportionally. Then, the score of each secondary evaluation indicator is multiplied by its corresponding weight to obtain a weighted score. Finally, the weighted scores of all secondary evaluation indicators are summed to obtain the overall score of the control logic. The overall score is typically expressed as a percentage, with higher scores indicating better control logic performance.

[0091] Table 1 lists the correspondence between the indicator system and the weights.

[0092]

[0093] Referring to Table 1, step S150 uses action accuracy, real-time response, collaborative adaptability, and logical integrity as primary evaluation indicators. Each primary indicator has several secondary evaluation indicators, each assigned a differentiated weight. A weighted comprehensive scoring method is used to calculate the comprehensive score of the control logic's joint debugging and pre-performance. Subsequently, the scoring criteria are quantified: Accuracy of action: Full marks are awarded if the deviation between the execution of the instruction and the expected result is ≤ ±2%, 60 marks are awarded if the deviation is 2%~5%, and 0 marks are awarded if the deviation is > 5%. Real-time response: Full marks are awarded for response delay ≤ timing tolerance, 60 marks are awarded for delay exceeding tolerance but ≤ 1.5 times tolerance, and 0 marks are awarded for delay > 1.5 times tolerance. Collaborative Adaptability: Full marks for no device linkage conflicts and normal communication interaction; 60 marks for minor conflicts that do not affect core functions; 0 marks for serious conflicts that cause functional failure. Logical completeness: Full marks are awarded for covering all preset scenarios and having a complete exception handling mechanism; 60 marks are awarded for omitting 1-2 important scenarios or having an incomplete exception handling mechanism; and 0 marks are awarded for omitting 3 or more important scenarios.

[0094] S143. Determine the control logic performance level based on the comparison between the comprehensive score and the preset threshold.

[0095] The preset thresholds can be set with multiple level cutoff values. For example, a comprehensive score of ≥90 is excellent (indicating that the control logic can be directly used for real machine integration testing), 80 to 90 is good (indicating that minor optimization is needed), 60 to 80 is acceptable (indicating that major optimization is needed), and below 60 is unacceptable (indicating that redesign or complete modification is needed). The performance level determination results can directly guide subsequent optimization work and clarify the priority of control logic improvement.

[0096] S144 automatically detects logical conflicts, timing deviations, setpoint mismatches, communication anomalies, or functional deficiencies in the control logic.

[0097] Based on the detailed operational data collected during the quantitative evaluation process and the intermediate results of the scores of each indicator, the system automatically identifies the specific problem type through preset detection rules.

[0098] Logical conflict detection: Identify mutual interference between different control logics, such as the simultaneous triggering of grid connection command and fault blocking command, or the simultaneous issuance of mutually exclusive protection actions.

[0099] Timing deviation detection: Specific steps in the positioning equipment's action timing that exceed the allowable deviation, such as the delay in excitation voltage build-up after SFC startup exceeding a set threshold.

[0100] Setting mismatch detection: Identify problems where protection settings or control parameters do not match the actual operating requirements of the equipment, such as overcurrent protection settings being lower than the equipment's rated current, leading to malfunctions.

[0101] Communication anomaly detection: Identifies communication-level problems such as communication timeouts, data packet loss, protocol incompatibility, or incorrect message formats.

[0102] Functional Missing Detection: Discovers missing exception handling branches, redundant protection mechanisms, or fault recovery processes in the control logic.

[0103] The above test results will be automatically recorded and summarized by the system to form a problem list.

[0104] In conjunction with the first aspect, the method also includes: S150 generates an optimization scheme based on the results of the quantitative evaluation and the detected problems, and performs secondary joint debugging and verification on the optimized control logic.

[0105] After completing the quantitative assessment and problem detection in step S140, the system automatically generates or assists technical personnel in developing targeted optimization plans based on the assessment results and problem list. The specific type of optimization plan depends on the category of the detected problem: For logical conflict issues: adjust the priority order of control logic (e.g., make fault blocking instructions take precedence over grid connection instructions), or add interlocking mechanisms between conflicting logics to prevent contradictory instructions from taking effect simultaneously.

[0106] For timing deviation issues: correct equipment action delay parameters (such as shortening excitation voltage build-up delay), or adjust the timing of control command issuance (such as issuing grid connection preparation commands in advance) to ensure that the actions of each piece of equipment meet the allowable timing deviation requirements.

[0107] For setting mismatch issues: Adjust the protection settings or control parameters based on the joint commissioning and pre-operation data (for example, adjust the overcurrent protection starting current from 6kA to 5.8kA) to match the rated parameters and operating characteristics of the equipment, and keep the deviation within the allowable range.

[0108] For communication anomalies: optimize communication protocol configuration (such as adjusting message retransmission strategy, shortening communication timeout threshold), or add redundant communication channels (such as dual network redundancy) to ensure the accuracy and real-time performance of data transmission.

[0109] For missing functionality issues: supplement missing exception handling logic (such as adding an automatic recovery process after a fault) or redundant protection mechanisms (such as adding backup protection delay) to improve the scenario coverage completeness of the control logic.

[0110] After the optimization plan is formulated, the optimized control logic needs to be subjected to secondary integration testing and verification to confirm the effectiveness of the optimization measures. The secondary integration testing and verification adopts a differentiated verification strategy, balancing comprehensiveness and efficiency: Complete reproduction verification: Perform the exact same reproduction verification as the initial joint debugging for the specific joint debugging scenario where the original problem occurred, as well as other scenarios related to the problem (such as similar scenarios under the same equipment or operating conditions), to ensure that the problem has been completely resolved and no new defects have been introduced.

[0111] Sampling verification: For other joint debugging scenarios that are not involved in the problem, a sampling verification method is adopted, with a sampling ratio of not less than 30% (for example, randomly selecting at least 4 sub-scenarios from 12 sub-scenarios under normal working conditions for testing) to verify that the optimization measures have no negative impact on the unmodified logic.

[0112] The overall score for the secondary integration and verification is calculated using the same quantitative evaluation system as step S140. When the overall score reaches the preset qualification standard (e.g., ≥80 points, corresponding to the "good" level), the optimization is deemed qualified, indicating that the control logic is ready for actual machine integration and testing; if the overall score is still lower than the qualification standard, the above optimization and verification process is repeated until the requirements are met.

[0113] Through S150, this invention forms a closed-loop iterative mechanism of joint debugging-evaluation-optimization-re-verification, ensuring that the control logic reaches a safe and reliable level before the actual machine is put into operation, further shortening the joint debugging cycle of the actual machine and reducing the risk of on-site debugging.

[0114] In conjunction with the first aspect, step S150 includes: S151 generates a joint debugging rehearsal report that includes the overall score, a list of issues, and data from the joint debugging process.

[0115] After completing the quantitative assessment and problem detection, the system automatically summarizes all results of this joint debugging rehearsal and generates a structured joint debugging rehearsal report. This report contains at least the following three core components: Overall Score: A weighted composite score (out of 100) based on four dimensions: action accuracy, real-time response, collaborative adaptability, and logical integrity. A corresponding performance level is given (Excellent ≥ 90 points, Good 80-89 points, Pass 60-79 points, Unsatisfactory < 60 points). The overall score directly reflects the overall performance level of the current control logic, facilitating rapid evaluation of the integration results by technical personnel.

[0116] Problem List: This list details each detected control logic problem, including problem type (logic conflict, timing deviation, setting mismatch, communication anomaly, function missing), occurrence scenario (e.g., "inter-turn short circuit in main transformer"), occurrence time (absolute or relative time from startup), scope of impact (which devices or functional modules are involved), and fault tracing results (abnormal data extraction, problem type determination, fault node location, and cause analysis). The problem list provides a precise basis for developing subsequent optimization solutions.

[0117] The integration testing process data is presented in the form of timing diagrams, logic flowcharts, and parameter trend charts. For example, timing diagrams can simultaneously overlay the times when control commands are issued, equipment actions are responded to, and feedback signals are returned, facilitating the location of timing deviations; logic flowcharts support reverse tracing of fault nodes, highlighting the specific logic statements or parameter settings that caused the problem; parameter trend charts support simultaneous comparative analysis of parameters from multiple devices (such as voltage, current, and speed), making it easy to observe whether parameter changes exceed thresholds. Furthermore, the report includes scenario reproduction steps to help technicians understand the complete process of the problem.

[0118] The joint debugging and pre-debugging report can be exported as a PDF or Word document, which can be used for internal technical review or archived as a reference document before actual machine joint debugging.

[0119] S152, for the detected problems, generate optimization solutions including adjusting logic priorities, adding interlocking mechanisms, correcting action delay parameters, adjusting protection settings, optimizing communication protocol configuration, or supplementing exception handling logic.

[0120] Based on the specific problem types listed in the problem list, the system automatically matches or assists technical personnel in developing targeted optimization solutions. Typical optimization strategies for various problem types are as follows: Adjusting logic priorities: When a logic conflict is detected (such as the simultaneous triggering of grid connection command and fault blocking command), the optimization scheme suggests re-sorting the priority order of control logic, so that logic with a high safety level (such as fault protection) takes precedence over normal operation logic (such as grid connection), or adding conditional mutual exclusion judgment between logics to prevent conflicting commands from taking effect at the same time.

[0121] Add interlocking mechanisms: For logic combinations with competition risks (such as accidental triggering of excitation during SFC startup), the optimization scheme suggests adding hardware or software interlocking conditions to ensure that certain instruction outputs are prohibited under specific operating conditions.

[0122] Correcting action delay parameters: When a timing deviation is detected (e.g., the relay protection action delay is 80ms, exceeding the allowable deviation of 60ms), the optimization scheme suggests correcting the action delay parameters of the relevant equipment (e.g., adjusting the overcurrent protection delay setting of the protection device from 80ms to 55ms), or adjusting the timing of the control command issuance (e.g., issuing the grid connection preparation command in advance).

[0123] Adjusting protection settings: For setting mismatch issues (such as overcurrent protection setting of 6kA being lower than 1.2 times the rated current of the equipment, leading to malfunction), the optimization plan suggests resetting the protection settings based on the joint commissioning and pre-drill data (such as adjusting to 5.8kA) to ensure that they match the rated parameters and actual operating characteristics of the equipment, and that the deviation is controlled within the allowable range.

[0124] Optimize communication protocol configuration: For communication anomalies (such as GOOSE message timeout, data packet loss), the optimization solution suggests adjusting communication parameters (such as shortening the retransmission interval, increasing the communication timeout threshold to 100ms), or adding redundant communication channels (such as dual-network redundancy configuration) to ensure that the accuracy of data transmission is ≥99.99% and the communication latency is ≤10ms.

[0125] Supplementing exception handling logic: For functional deficiencies (such as the lack of an automatic recovery process after a fault), the optimization solution suggests supplementing the missing exception handling branch (such as adding automatic reclosing logic after fault isolation) or redundant protection mechanism (such as adding backup protection delay).

[0126] The optimization plan is output in the form of an optimization suggestion report, which includes information such as the correspondence between problems and optimization measures, the comparison of parameters before and after modification, and the expected improvement effect, for technical personnel to refer to and implement.

[0127] S153, perform secondary joint debugging and verification on the optimized control logic, including full reproduction verification of the original problem scenario and sampling verification of the target joint debugging scenario that does not involve the problem.

[0128] After technicians modify the control logic according to the optimization scheme (e.g., re-importing the adjusted PLC ladder diagram or modifying the protection setting sheet), the system supports quickly importing the optimized control logic into a hardware-in-the-loop simulation platform for secondary integration and verification. To improve verification efficiency and avoid the time cost of full regression testing, a differentiated verification strategy is adopted for secondary integration and verification: Complete Reproduction Verification: For the specific commissioning scenario where the original problem occurred (such as the "inter-turn short circuit of the main transformer") and other scenarios directly related to the problem (such as similar scenarios of the same equipment under different fault types, or other fault injection scenarios under the same operating conditions), perform a reproduction verification that is exactly the same as the initial commissioning. Complete reproduction verification requires strict adherence to the triggering conditions, operating parameters, and expected results of the original scenario to ensure that the problem has been completely resolved and no new defects have been introduced. Typically, the number of scenarios for complete reproduction verification covers all the original scenarios and related scenarios corresponding to all problems in the problem list.

[0129] Sampling Verification: For other integration testing scenarios where no issues were detected during the initial integration testing, sampling verification will be used. The sampling ratio should be no less than 30%, for example, randomly selecting at least 4 sub-scenarios from 12 sub-scenarios under normal operating conditions for testing, and randomly selecting at least 3 sub-scenarios from 8 sub-scenarios under extreme operating conditions for testing. Sampling verification aims to confirm that the optimization measures have no negative impact on the unmodified logic (i.e., regression testing). The sampling strategy can be weighted based on risk priority, prioritizing the verification of scenarios that have indirect interaction with the optimization logic.

[0130] By using differentiated verification, we can ensure the effectiveness of problem fixing and control the verification time cost, so that the secondary joint debugging verification can be completed within a reasonable period.

[0131] S154. When the comprehensive score of the secondary joint debugging verification reaches the preset score, the optimization is deemed qualified.

[0132] After the second round of joint testing and verification, the system again uses the quantitative evaluation system from step S140 (action accuracy 0.35, response timeliness 0.25, collaborative adaptability 0.25, logical integrity 0.15) to calculate the comprehensive score. This comprehensive score is then compared with the preset passing standard. If the overall score is ≥80 points (corresponding to "Good" or above), the optimization is deemed qualified, indicating that the optimized control logic has met the preset performance requirements and is ready for actual machine testing.

[0133] If the overall score is less than 80 points (i.e., "qualified" or "unqualified"), the optimization is deemed unqualified. The optimization and verification process from S152 to S154 needs to be repeated based on the list of new issues generated during the second joint debugging and verification until the overall score reaches the qualified standard.

[0134] Through this closed-loop iterative mechanism, this invention ensures that the control logic, after semi-physical integration testing and optimization, can be deployed for real-machine integration testing with high reliability, thereby shortening the real-machine integration testing cycle and reducing on-site debugging risks. In this embodiment, the initial integration testing score was 80.5 points (good), and after optimization, the second integration testing score improved to 88 points, reaching the preset qualification standard (≥80 points), thus qualifying for optimization and verifying the effectiveness of the mechanism.

[0135] As an example, this method is implemented using an existing electrical hardware-in-the-loop simulation platform built on a large pumped storage power station. This platform includes a primary equipment simulation module 7, an interface conversion module 8, a simulated switch module 9, a secondary physical control panel module 10 (including the unit LCU cabinet, SFC control and protection cabinet, main transformer protection cabinet, excitation regulating cabinet, etc.) based on the domestic electromagnetic transient software DDRTS, and a virtual-physical integrated coordination control module 14. The power station's generators have a rated capacity of 350MW, a main transformer rated voltage of 500kV, and an SFC rated current of 1200A.

[0136] Step S120 selects 20 core scenarios from the joint commissioning scenario library, including: pumping start-up, power generation start-up, pumping-power generation mode switching, power generation-phase adjustment mode switching, normal unit shutdown, grid voltage drop of 10%, three consecutive mode switching, 10% rated load stable combustion, main transformer inter-turn short circuit, line A phase high resistance grounding (300Ω), SFC commutation failure + excitation system erroneous excitation, computer monitoring system collaborative control, and simultaneous start-up of multiple units.

[0137] Step S130 configures the joint commissioning and pre-commissioning parameters: allowable deviation of overcurrent protection operating current ±1%, allowable deviation of overvoltage protection operating voltage ±1%; SFC start-up → excitation voltage build-up timing deviation ≤40ms, grid connection command-circuit breaker closing timing deviation ≤25ms; main transformer inter-turn short-circuit fault injection time t=5s, short-circuit current is twice the rated current, fault duration 0.5s; pumping-generator mode switching load change rate 3% rated load / second; communication timeout threshold 80ms.

[0138] Step S140 takes the inter-turn short circuit scenario of the main transformer as an example. The coordination control module 14 simulates the computer monitoring system issuing the pumping start command, the secondary physical panel module 10 executes the control logic, the primary equipment simulation module 7 simulates the speed increase and voltage establishment process of the generator motor, and the simulation switch module 9 simulates the closing action of the commutation disconnector. The high-speed data acquisition unit (sampling frequency 1kHz, timestamp accuracy 1μs) collects the data of the entire process. When an inter-turn short circuit fault is injected, it is found that the relay protection action delay is 80ms, which exceeds the allowable timing deviation (≤60ms). The system automatically triggers the simulation pause, records the abnormal data, and initiates fault tracing.

[0139] Subsequently, a quantitative evaluation system was used to calculate the comprehensive score: 95 points were scored for the action accuracy dimension (instruction execution accuracy deviation 0.8%, action parameter accuracy deviation 0.5%, protection action accuracy deviation 1.0%, and timing matching accuracy deviation 1.2%); 50 points were scored for the response real-time dimension (fault response delay of 80ms exceeding the 60ms allowable value); 90 points were scored for the coordination and adaptability dimension (no conflicts); and 85 points were scored for the logical integrity dimension (one minor redundancy exists). Calculated with weights of 0.35, 0.25, 0.25, and 0.15, the comprehensive score = 0.35×95 + 0.25×50 + 0.25×90 + 0.15×85 = 80.5 points, which is considered good and requires optimization.

[0140] Optimization plan generation: Adjust the action threshold parameters of the relay protection device (adjust the overcurrent protection starting current from 6kA to 5.8kA) and optimize the judgment process of the protection logic. Secondary joint debugging and verification: Import the optimized control logic, re-execute the same scenario, the relay protection action delay is reduced to 55ms, the comprehensive score is improved to 88 points, reaching the preset qualification standard (≥80 points), and the optimization is judged to be qualified.

[0141] Secondly, this invention provides a semi-physical commissioning and pre-simulation system for pumped storage units. This system is applied to an electrical semi-physical simulation platform for pumped storage power stations. The semi-physical simulation platform includes a primary equipment simulation module 7, an interface conversion module 8, a simulated switch module 9, a secondary physical control panel module 10, and a coordination control module 14. The system further includes: a control logic replication and adaptation module 1, a commissioning scenario library construction module 2, a commissioning and pre-simulation parameter configuration module 3, a semi-physical closed-loop commissioning execution module 4, a control logic quantitative evaluation module 5, and an optimization scheme generation and verification module 6.

[0142] The control logic replication and adaptation module 1 is used to acquire real machine control logic related data and configure the real machine control logic related data to the hardware-in-the-loop simulation platform; the control logic replication and adaptation module 1 has a built-in logic parsing engine 11 and a consistency verification unit 12.

[0143] The control logic replication and adaptation module 1 is used to execute the above step S110, import the real machine control logic file, equipment parameter table, and protection setting sheet, complete control logic parsing, equipment parameter mapping, communication protocol adaptation, and generate a control logic replication verification report. The control logic parsing adopts a syntax tree parsing algorithm based on the IEC 61131-3 standard, performs lexical analysis and syntactic conversion on PLC ladder diagrams, function block diagrams, sequential function charts and other format files, automatically extracts the hierarchical relationship of the control logic's input and output variables, logical judgment conditions, and action execution instructions, and generates a visual logic flowchart. During the parsing process, the logic statements are syntax checked, and problems such as missing variable definitions and conflicting logical judgment conditions are automatically marked, and a parsing verification log is generated. The consistency verification unit 12 adopts a dual verification method of parameter point-by-point comparison + logic link traversal. First, the replicated equipment parameters and protection settings are matched with the real machine parameter table point by point, and an automatic warning is given when the deviation exceeds ±2%. Then, the complete link of the control logic is traversed and simulated to verify the consistency of the action execution results of the replicated logic and the real machine logic, ensuring that there is no logic missing or parameter error.

[0144] Module 2, the integration testing scenario library construction module, is used to build and store integration testing test case sets.

[0145] The joint debugging scenario library construction module 2 is connected to the control logic replication and adaptation module 1. It is used to execute the above step S120, store four types of core joint debugging scenarios: normal working conditions, extreme working conditions, fault protection, and multi-device collaboration, and supports scenario customization, expansion and configuration.

[0146] The joint debugging and pre-drill parameter configuration module 3 is used to configure the joint debugging and pre-drill parameters.

[0147] The joint debugging and pre-drill parameter configuration module 3 is connected to the joint debugging scenario library construction module 2. It is used to execute the above step S130, configure pre-drill parameters such as control logic execution threshold, action timing allowable deviation, and fault injection parameters, and supports parameter export and import.

[0148] The semi-physical closed-loop joint debugging and execution module 4 is used to drive the primary equipment simulation module 7, the analog switch module 9, the interface conversion module 8 and the secondary physical panel module 10 to operate synchronously and collect full-process operation data; the semi-physical closed-loop joint debugging and execution module 4 has a built-in timing synchronization control unit 41 and an anomaly monitoring unit 42.

[0149] The semi-physical closed-loop joint debugging execution module 4 is connected to all the above modules and each module of the original semi-physical simulation platform. It is used to execute the above step S140, drive each module to run synchronously, perform closed-loop joint debugging pre-run, and collect full-process operation data.

[0150] The control logic quantitative evaluation module 5 is used to quantitatively evaluate the performance of control logic based on the full-process operation data from four dimensions: action accuracy, response real-time performance, collaborative adaptability, and logical integrity. The control logic quantitative evaluation module 5 has a built-in problem localization engine 51 and a data visualization unit 52.

[0151] The control logic quantitative evaluation module 5, connected to the semi-physical closed-loop joint debugging and execution module 4, is used to execute the above step S150, construct a quantitative evaluation system, calculate a comprehensive score, and achieve accurate source tracing of control logic problems based on a three-layer positioning algorithm of time-series correlation analysis + parameter comparison + logic tracing. The first layer, through time-series correlation analysis, compares the collected timestamped operating data with preset action sequences to locate time nodes exceeding allowable deviations and their corresponding equipment. The second layer, through parameter comparison, compares the operating parameters of the faulty node with rated parameters and control logic execution thresholds to filter out problem types such as parameter mismatch and exceeding thresholds. The third layer, through logic tracing, reversely traverses the control logic link corresponding to the device to locate the specific logic statement, parameter setting, or communication node causing the problem, and highlights the root cause location in the data visualization unit 52. The data visualization unit 52 supports multi-dimensional data display, where the time-series diagram supports the synchronous overlay display of control commands, device actions, and communication data; the logic flowchart supports reverse tracing jumps to faulty nodes; and the parameter trend chart supports simultaneous comparison and analysis of parameters from multiple devices on the same screen.

[0152] The optimization scheme generation and verification module 6 is used to generate joint debugging and pre-drill reports and optimization schemes, and supports secondary joint debugging and verification.

[0153] The optimization scheme generation and verification module 6 is connected to the control logic quantification evaluation module 5 and the control logic replication and adaptation module 1. It is used to perform the above step S160, generate the joint debugging and pre-drill report and optimization scheme, and support the second joint debugging and verification after optimization.

[0154] The control logic replication and adaptation module 1, the joint debugging scenario library construction module 2, the joint debugging pre-simulation parameter configuration module 3, the semi-physical closed-loop joint debugging execution module 4, the control logic quantitative evaluation module 5, and the optimization scheme generation and verification module 6 interact with the coordination control module 14 of the semi-physical simulation platform through standardized interfaces.

[0155] The above six modules are seamlessly integrated with the modules of the original electrical hardware-in-the-loop simulation platform, without changing the original platform's system architecture and communication protocol, and only through standardized interfaces to achieve data interaction and functional expansion.

[0156] In conjunction with the second aspect, the joint debugging scenario library construction module 2 supports the import of custom scenario configuration files; the custom scenario configuration file contains basic scenario information, trigger conditions, running parameters, expected results and termination conditions; after the configuration file is imported, the joint debugging scenario library construction module 2 automatically performs format verification and parameter rationality verification, and after the verification is passed, the new scenario is included in the joint debugging scenario library.

[0157] In conjunction with the second aspect, the joint debugging and pre-simulation parameter configuration module 3 supports exporting the currently configured joint debugging and pre-simulation parameters as a parameter file, as well as importing joint debugging and pre-simulation parameters from a saved parameter file; the exported parameter file includes parameter name, value range, applicable scenario and configuration time; after importing the parameter file, the joint debugging and pre-simulation parameter configuration module 3 automatically matches the imported parameters with the equipment parameters of the current hardware-in-the-loop simulation platform, and generates a parameter adaptation warning log when the parameter deviation exceeds the preset range.

[0158] Thirdly, embodiments of the present invention provide an electronic device, combined with Figure 3 As shown, the electronic device includes a memory 131 and a processor 130. The memory 131 stores a computer program, and the processor 130 runs the computer program to make the electronic device perform the above-described method.

[0159] Furthermore, combined Figure 3 The electronic device shown also includes a bus 132 and a communication interface 133, with the processor 130, the communication interface 133 and the memory 131 connected via the bus 132.

[0160] The memory 131 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 133 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 132 may be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 3 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0161] Processor 130 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 130 or by instructions in software form. Processor 130 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 131, and processor 130 reads the information in memory 131 and, in conjunction with its hardware, completes the steps of the method described in the foregoing embodiments.

[0162] Fourthly, embodiments of the present invention provide a readable storage medium storing computer program instructions, which are read and executed by a processor to perform the above-described method.

[0163] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system and apparatus described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0164] Furthermore, in the description of the embodiments of the present invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0165] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0166] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0167] Finally, it should be noted that the above embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A semi-physical commissioning and pre-simulation method for pumped storage units, characterized in that, include: Acquire the control logic related data of the actual pumped storage power station and configure the control logic related data into the electrical hardware-in-the-loop simulation platform of the pumped storage power station so that the hardware-in-the-loop simulation platform executes the control logic consistent with the actual machine; Construct a set of joint debugging test cases, which includes multiple joint debugging scenarios for verifying the performance of the control logic under different operating conditions; Based on the set of joint debugging test cases and the preset joint debugging pre-drill parameters, drive the primary equipment simulation module, simulated switch module, interface conversion module and secondary physical cabinet module in the semi-physical simulation platform to run synchronously in a closed loop, and collect the full process operation data; Based on the full-process operation data, the performance of the control logic is quantitatively evaluated from multiple dimensions, including at least action accuracy, real-time response, collaborative adaptability, and logical integrity, and logical conflicts or timing deviations in the control logic are automatically detected.

2. The method according to claim 1, characterized in that, The steps of acquiring control logic-related data of a real pumped storage power station and configuring the control logic-related data into an electrical hardware-in-the-loop simulation platform for the pumped storage power station include: The control logic file of the real machine is parsed, and the parameters of the real machine are automatically mapped to the primary equipment simulation module and the secondary physical cabinet module. The communication protocol between the semi-physical simulation platform and the control logic is configured. Generate a control logic replication verification report to verify the consistency between the replicated logic and the actual device logic.

3. The method according to claim 1, characterized in that, The steps for constructing a set of integration test cases include: Establish a set of joint debugging test cases that includes at least the following scenarios: normal operating condition joint debugging scenarios, extreme operating condition joint debugging scenarios, fault protection joint debugging scenarios, and multi-device collaborative joint debugging scenarios. The conventional operating condition commissioning scenarios include at least one of the following: unit pumping start-up, power generation start-up, operating condition switching, normal shutdown, excitation regulation, speed regulation, and static frequency converter start-up and shutdown control; the extreme operating condition commissioning scenarios include at least one of the following: sudden rise or fall in grid voltage, grid frequency fluctuation, unit overload or low load operation, continuous operating condition switching, simultaneous start-up or shutdown of multiple units, islanded operation, and N-1 maintenance mode; the fault protection commissioning scenarios include at least one of the following: single fault, compound fault, protection device failure to operate or maloperation, and fault reclosing; the multi-equipment collaborative commissioning scenarios include at least one of the following: collaboration between the unit's local control unit and the computer monitoring system, collaboration between the relay protection device and the static frequency converter start-up device or excitation system, collaboration between multiple unit local control units, collaboration between the DC system and secondary equipment, and collaboration between the fire protection system and the fault protection system.

4. The method according to claim 1, characterized in that, The steps for constructing the joint debugging test case set also include: In response to custom extension instructions, add new scenes by importing scene configuration files.

5. The method according to claim 1, characterized in that, The steps for driving the primary equipment simulation module, analog switch module, interface conversion module, and secondary physical cabinet module in the hardware-in-the-loop simulation platform to operate synchronously in a closed loop and collecting full-process operation data include: Initialize the primary equipment simulation module, the analog switch module, the interface conversion module, and the secondary physical panel module; load the control logic, the joint debugging scenarios in the joint debugging test case set, and the preset joint debugging pre-drill parameters. Control commands are issued through the coordination control module or locally through the unit's local control unit; The secondary physical panel module executes control logic and outputs signals, which are transmitted to the primary equipment simulation module and the analog switch module via the interface conversion module. The feedback signals from the primary equipment simulation module and the analog switch module are transmitted back to the secondary physical panel module via the interface conversion module, forming a closed loop; The data acquisition unit within the coordination and control module collects timestamped runtime data; When an anomaly is detected, a tiered alert or simulation pause is triggered, the abnormal data is recorded, and fault tracing is initiated.

6. The method according to claim 1, characterized in that, Also includes: Based on the results of the quantitative assessment and the problems detected, an optimization scheme is generated, and the optimized control logic is then subjected to secondary joint testing and verification.

7. The method according to claim 6, characterized in that, Based on the results of the quantitative evaluation and the detected optimization scheme, the steps of performing secondary joint debugging and verification on the optimized control logic include: Generate a joint debugging rehearsal report that includes a comprehensive score, a problem list, and joint debugging process data; In response to the detected problems, optimization solutions are generated, including adjusting logic priorities, adding interlocking mechanisms, correcting action delay parameters, adjusting protection settings, optimizing communication protocol configuration, or supplementing exception handling logic. The optimized control logic is then subjected to secondary joint debugging and verification, including a complete reproduction verification of the original problem scenario and sampling verification of the target joint debugging scenario where no problem is involved. When the overall score of the second joint debugging verification reaches the preset score, the optimization is deemed qualified.

8. A semi-physical commissioning and pre-simulation system for pumped storage units, characterized in that, A hardware-in-the-loop (HIL) simulation platform for pumped storage power stations is provided. The HIL includes a primary equipment simulation module, an interface conversion module, a simulated switch module, a secondary physical control panel module, and a coordination control module. The system includes: The control logic replication and adaptation module is used to acquire real machine control logic related data and configure the real machine control logic related data to the hardware-in-the-loop simulation platform; the control logic replication and adaptation module has a built-in logic parsing engine and consistency verification unit; The integration testing scenario library construction module is used to build and store integration testing case sets; The joint debugging and pre-drill parameter configuration module is used to configure the joint debugging and pre-drill parameters; The semi-physical closed-loop joint debugging and execution module is connected to the primary equipment simulation module, interface conversion module, analog switch module, and secondary physical panel module respectively, and is used to drive the synchronous closed-loop operation of each module and collect the full process operation data; the semi-physical closed-loop joint debugging and execution module has a built-in timing synchronization control unit and an anomaly monitoring unit; The control logic quantitative evaluation module is connected to the semi-physical closed-loop joint debugging and execution module, and is used to quantitatively evaluate the control logic performance from multiple dimensions and automatically detect problems; the control logic quantitative evaluation module has a built-in problem localization engine and data visualization unit. The optimization scheme generation and verification module is connected to the control logic quantification and evaluation module and the control logic replication and adaptation module, and is used to generate optimization schemes and support secondary joint debugging and verification. The control logic replication and adaptation module, the joint debugging scenario library construction module, the joint debugging pre-simulation parameter configuration module, the semi-physical closed-loop joint debugging execution module, the control logic quantitative evaluation module, and the optimization scheme generation and verification module interact with the coordination control module through standardized interfaces.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method described in any one of claims 1-7.

Images