Integrated distributed energy dissipation module typical fault simulation simulation device and test method

Abstract

This invention discloses an integrated simulation device and test method for typical faults of distributed energy-consuming modules. The device includes a peripheral netlist program module, a communication interface with the simulation model, a communication interface with valve control, a communication interface with adjacent modules, and a power module control board netlist program module. The peripheral netlist program module responds to fault simulation commands issued by the operation interface, determines the fault type, and issues control actions. The communication interface with the simulation model connects to a real-time simulator for issuing commands and receiving status information. The communication interface with the valve control connects to a flexible direct current valve control device for transmitting fault information and receiving control commands. The communication interface with adjacent modules allows for the mutual transmission of fault information, control commands, and status information with adjacent paired power modules. The power module control board netlist program module performs fault detection based on the status information and outputs protection signals. By simulating faults in various power modules, permanent damage to the tested module is avoided.

Description

Technical Field

[0001] This invention relates to the field of fault simulation technology, and in particular to a typical fault simulation device and test method for integrated distributed energy-consuming modules. Background Technology

[0002] Flexible DC transmission technology, with its advantages such as independent decoupling control of active and reactive power and no need for AC-side commutation voltage, has been increasingly widely used in long-distance, high-capacity power transmission, offshore wind power grid connection, and asynchronous grid interconnection. The Modular Multilevel Converter (MMC), as the core equipment of a flexible DC transmission system, consists of power modules made up of insulated-gate bipolar transistors (IGBTs), diodes, DC capacitors, and other components, forming the basic building blocks of the converter valve. Because a single converter valve contains a large number of power modules, a failure in any module during operation can affect the safe and stable operation of the entire system. Therefore, the reliability of the power modules is a key factor in the long-term stable operation of flexible DC transmission projects.

[0003] To ensure the reliability and fault response capability of flexible DC valve-controlled systems, comprehensive functional verification of the flexible DC valve-controlled equipment is necessary before commissioning. Currently, the industry commonly employs hardware-in-the-loop (HIL) testing technology for controllers based on real-time simulation platforms. This technology connects the flexible DC valve-controlled system to a hardware-in-the-loop (HIL) simulation platform for testing and verification, and has been applied in several operational flexible DC projects in China. However, because the MMC submodules in existing real-time simulation platforms often use equivalent modeling methods, they cannot simulate the internal physical structure of the power module and the actual operating state of each component in detail. Therefore, it is difficult to effectively simulate various faults at the power module level.

[0004] The aforementioned hardware-in-the-loop testing method based on equivalent modeling has significant limitations when simulating power module-level faults, and cannot fully verify the effectiveness of power module fault detection and protection strategies. Although existing solutions can simulate a few types of faults such as IGBT faults and bypass switch faults, they are insufficient to cover the various fault conditions that may occur during power module operation. Summary of the Invention

[0005] This invention provides an integrated simulation device and test method for typical faults of distributed energy-consuming modules, which solves the technical problem that although existing solutions can simulate a few types of faults such as IGBT faults and bypass switch faults, they are difficult to cover the various fault conditions that may occur during the operation of power modules.

[0006] This invention provides an integrated distributed energy-consuming module typical fault simulation device, including an external netlist program module, a communication interface with the simulation model, a communication interface with the valve control, a communication interface with adjacent modules, and a power module control board netlist program module; The peripheral netlist program module is used to respond to module-level fault simulation commands received from the operation interface, determine the fault simulation type and issue corresponding control action signals to simulate typical faults of integrated distributed energy-consuming flexible DC power modules. The communication interface with the simulation model is connected to the real-time simulator and is used to transmit module control commands to the real-time simulator and receive voltage and status information uploaded by the real-time simulator. The valve control communication interface is connected to an external control and protection device for sending fault information and status information to the external control and protection device, and for receiving control commands sent by the external control and protection device. The communication interface with the adjacent module is connected to the netlist program of the adjacent paired integrated distributed energy-consuming flexible DC power module control board, and is used to send the fault information, the status information and the control command to the netlist program of the adjacent paired integrated distributed energy-consuming flexible DC power module control board, and to receive the fault information, the status information and the control command sent by the netlist program of the adjacent paired integrated distributed energy-consuming flexible DC power module control board. The power module control board netlist program module is connected to the peripheral netlist program module, the communication interface with the simulation model, the communication interface with the valve control, and the communication interface with the adjacent module, respectively, and is used to perform fault detection and output corresponding fault protection control signals based on the fault information and the status information.

[0007] Optionally, when the fault simulation type is a communication fault, the control action signal is used to trigger the disconnection of the uplink direct connection channel and / or downlink direct connection channel in the valve control communication interface, and / or control the disconnection of the uplink cross channel and / or downlink cross channel in the communication interface with the adjacent module.

[0008] Optionally, when the fault simulation type is a state detection type fault, the control action signal is used to replace the voltage value in the state information sent by the real-time simulator with a preset fault value, and output the replaced voltage value and the preset temperature value to the power module control board netlist program module through the communication interface with the simulation model, so that the power module control board netlist program module generates a corresponding fault protection control signal according to the fault value.

[0009] Optionally, when the fault simulation type is an action abnormality fault, the control action command is used to intercept the actuator action command issued by the flexible direct valve control device to the communication interface with the simulation model, replace the action command with the action command of the opposite state, and then output it to the real-time simulator through the communication interface with the simulation model.

[0010] Optionally, when the fault simulation type is a component fault, the control action instruction is used to send the corresponding fault flag information to the power module control board netlist program module. The power module control board netlist program module is also used to generate corresponding fault information based on the fault flag information, and send it to the flexible DC valve control device via the valve control communication interface, so that the flexible DC valve control device can issue corresponding protection commands.

[0011] Optionally, the peripheral netlist program module is also used to disconnect the communication links with the simulation model, the valve control communication interface, and the adjacent module communication interface after the flexible direct current valve control device issues the corresponding protection command, so as to interrupt the fault, status information transmission, and control command issuance. Issue a control action command to stop the operation of the power module control board netlist program module.

[0012] Optionally, when the fault simulation type is a power-on / off fault, the peripheral netlist program module is used to control the connection and disconnection of the communication links of the communication interface with the simulation model, the communication interface with the valve control, and the communication interface with the adjacent module, as well as the start or stop of the power module control board netlist program module, according to the preset voltage threshold and the module voltage value in the status information sent by the real-time simulator.

[0013] Optionally, the external control and protection device is a flexible direct current valve control device; The real-time simulator contains a primary model of a flexible DC transmission system, including an equivalent model of the power module. The power module is an integrated distributed energy-consuming flexible DC power module, including a half-bridge power module or a full-bridge power module. The DC capacitor of the power module has an energy-consuming branch connected in parallel across its terminals. The energy-consuming branch includes a series-connected switching transistor and an energy-consuming resistor.

[0014] The present invention also provides a method for simulating typical faults of integrated distributed energy-consuming modules, applied to the integrated distributed energy-consuming module typical fault simulation device as described in any of the above claims, comprising: Receive module-level fault simulation instructions from the operation interface, and parse the instructions to determine the fault simulation type; Based on the fault simulation type, a corresponding control action strategy is matched from a plurality of preset fault simulation strategies; the fault simulation strategy includes at least one of a communication link control strategy, a status data replacement strategy, an instruction interception and replacement strategy, and a fault flag writing strategy. According to the matched control action strategy, a corresponding control action signal is generated, and the control action signal is sent to at least one of the communication interface with the simulation model, the communication interface with the valve control, the communication interface with the adjacent module, and the power module control board netlist program module for execution, so as to generate the corresponding fault state in the simulation model of the real-time simulator.

[0015] This invention also provides a typical fault test method for integrated distributed energy-consuming modules, applied to the typical fault simulation device for integrated distributed energy-consuming modules as described in any of the above claims, comprising: Start the hardware-in-the-loop simulation test system and clear the preset fault simulation settings in the device; The initial voltage values ​​of each bridge arm power module of the tested converter valve are set through the real-time simulator, and the power-on / off thresholds and overvoltage breakdown thresholds of each power module are set through the operation interface. Various fault simulation commands are sequentially sent to the designated power modules, and the status feedback information of the corresponding power module in the background interface of the flexible DC valve control device is read after each sending. The status feedback information includes at least one of the following: power-on status, communication status, voltage measurement value, bypass status, energy-consuming branch status, and energy-consuming resistor temperature value. The status feedback information is compared with the expected status. If they match, the corresponding type of fault simulation function is determined to be correct.

[0016] As can be seen from the above technical solutions, the present invention has the following advantages: This invention provides an integrated simulation device and testing method for typical faults in distributed energy-consuming modules. The device includes a peripheral netlist program module, a communication interface with the simulation model, a communication interface with the valve control system, and a power module control board netlist program module. The peripheral netlist program module responds to fault simulation commands issued by the operating interface, determines the fault type, and issues control actions. The communication interface with the simulation model connects to a real-time simulator for issuing commands and receiving status information. The communication interface with the valve control system connects to a flexible direct current valve control device for transmitting fault information and receiving control commands. The communication interface with adjacent modules facilitates the mutual transmission of fault and status information with adjacent paired power modules. The power module control board netlist program module performs fault detection based on the status information and outputs protection signals. The device simulates various power module faults through data replacement, command interception, communication link control, and fault flag writing, thereby verifying fault protection strategies without physical testing, reducing costs, shortening the cycle, avoiding permanent damage to the tested module, and effectively covering various fault conditions that may occur during power module operation. Attached Figure Description

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

[0018] Figure 1 This is a schematic diagram of a half-bridge power module topology provided in this embodiment; Figure 2 This is a schematic diagram of a full-bridge power module topology provided in this embodiment; Figure 3 A structural block diagram of a typical fault simulation device for an integrated distributed energy-consuming module provided in an embodiment of the present invention; Figure 4 A detailed structural block diagram of a typical fault simulation device for an integrated distributed energy-consuming module provided in an embodiment of the present invention; Figure 5 This is a structural block diagram of a power module fault simulation system provided in an embodiment of the present invention.

[0019] Reference numerals: 301, Peripheral netlist program module; 302, Power module control board netlist program module; 303, Communication interface with valve control; 304, Communication interface with simulation model; 305, Communication interface with adjacent modules; 306, Integrated distributed energy-consuming flexible DC power module. Detailed Implementation

[0020] In this embodiment, the topology of the integrated distributed energy-consuming flexible DC power module 306 is as follows: Figure 1 and Figure 2 As shown, where Figure 1 This is a schematic diagram of a half-bridge power module topology. Figure 2 This is a schematic diagram of the topology of the full-bridge power module. The main internal components of this integrated distributed energy-consuming flexible DC half-bridge and full-bridge power module include: press-fit IGBTs, fast recovery diodes, DC capacitors, voltage equalizing resistors, bypass switches, soldered IGBT devices for energy-consuming branches, energy-consuming resistors, power supply, redundant power supply, module control board, soldered IGBT driver board, and bypass switch driver board, etc. The only structural difference between the integrated distributed energy-dissipating flexible DC half-bridge and full-bridge power modules and conventional topology power modules is that an energy-dissipating branch is connected in parallel across the positive and negative terminals of the module capacitor. This energy-dissipating branch consists of soldered IGBT devices, energy-dissipating resistors, and connecting copper busbars connected in series. When the power module voltage abnormally rises above the set value of the energy-dissipating branch due to a fault during operation, the power module control board will promptly trigger the IGBT T3 (half-bridge) or IGBT T5 (full-bridge) to open the energy-dissipating branch and connect the energy-dissipating resistor R2 (with a resistance of a few ohms), thereby rapidly discharging the module capacitor and reducing the module voltage to a safe operating range, ensuring that the power module is not damaged by overvoltage.

[0021] In actual operation, the aforementioned integrated distributed energy-consuming flexible DC power module 306 inevitably experiences various faults that cause abnormal module operation, and in severe cases, even damage the module. Typical power module-level faults include: module power-on / off faults, module overvoltage breakdown faults, module uplink / downlink communication faults, module bypass switch malfunction / failure to operate faults, module voltage measurement over / under deviation faults, module power supply faults, module IGBT drive faults, module control board faults, module energy-consuming branch malfunction / failure to operate faults, and module energy-consuming resistor temperature abnormalities. Currently, there are corresponding detection and protection strategies for the typical faults of the aforementioned integrated distributed energy-consuming flexible DC power module 306. Before engineering application, these module-level fault detection and protection strategies must be tested to verify their effectiveness. Currently, the industry often uses real primary components to assemble the power module under test, and then before or during the test, the corresponding type of power module-level fault is actually created on the power module under test to observe the effectiveness of the designed module-level fault detection and protection strategy. However, the above testing methods have disadvantages such as high testing costs, long testing cycles, and the potential to cause permanent damage to the module under test.

[0022] To address this issue, this invention provides a fault simulation device and system for an integrated distributed energy-consuming flexible DC power module 306. This solves the technical problem that while existing solutions can simulate a few types of faults, such as IGBT faults and bypass switch faults, they are insufficient to cover the various fault conditions that may occur during power module operation. Simultaneously, by simulating typical faults of the integrated distributed energy-consuming flexible DC power module 306 in a real-time simulation hardware-in-the-loop testing system, the effectiveness of the designed module-level fault detection and protection strategy can be observed. The test results are the same as those obtained by conducting a real power module test, but the test cost is lower, the test cycle is shorter, and there is no risk of permanent damage to the tested module.

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

[0024] Please see Figure 3 , Figure 3 The present invention provides a structural block diagram of a typical fault simulation device for an integrated distributed energy-consuming module.

[0025] The present invention provides an integrated distributed energy-consuming module typical fault simulation device, including an external netlist program module 301, a communication interface with the simulation model 304, a communication interface with the valve control 303, a communication interface with the adjacent module 305, and a power module control board netlist program module 302. The peripheral netlist program module 301 is used to respond to the module-level fault simulation command received from the operation interface, determine the fault simulation type and issue the corresponding control action signal to simulate the typical fault of the integrated distributed energy-consuming flexible DC power module 306. The communication interface 304 with the simulation model is connected to the real-time simulator and is used to transmit module control commands to the real-time simulator and receive voltage and status information uploaded by the real-time simulator. The valve control communication interface 303 is connected to an external control and protection device for sending fault information and status information to the external control and protection device, and receiving control commands sent by the external control and protection device. The communication interface 305 with the adjacent module is connected to the netlist program of the control board of the adjacent paired integrated distributed energy-consuming flexible DC power module 306. It is used to send the fault information, the status information and the control command to the netlist program of the control board of the adjacent paired integrated distributed energy-consuming flexible DC power module 306, and to receive the fault information, the status information and the control command sent by the netlist program of the control board of the adjacent paired integrated distributed energy-consuming flexible DC power module 306. The power module control board netlist program module 302 is connected to the peripheral netlist program module 301, the communication interface with the simulation model 304, the communication interface with the valve control 303, and the communication interface with the adjacent module 305, respectively, and is used to perform fault detection and output corresponding fault protection control signals based on the fault information and the status information.

[0026] The peripheral netlist program module 301 refers to a logic functional unit written in a hardware description language (such as Verilog HDL or VHDL) and running in a field-programmable gate array (FPGA) device. This module generates a configuration file using EDA (Electronic Design Automation) tools such as synthesis and placement and routing, and then downloads it to the FPGA to form a fixed hardware logic circuit.

[0027] In this device, the peripheral netlist program module 301 serves as the scheduling core for fault simulation. Its input terminal receives fault setting instructions (including fault type codes and associated parameters) from the background operation interface via a parallel bus. Its output terminals are connected to the control ports of the simulation model communication interface 304, the valve control communication interface 303, and the power module control board netlist program module 302, respectively. After decoding the received fault setting instructions, this module generates corresponding enable signals and mode selection signals, which are then distributed to each downstream module. For example, when a "bypass malfunction" instruction is received, the module sets the enable bit of the action instruction replacement logic high and simultaneously writes the replacement target value ("on") into the instruction cache register.

[0028] The communication interface 304 with the simulation model refers to the physical layer and data link layer communication channel connecting the power module fault simulation device and the real-time simulator. This interface is hardware-based, consisting of a high-speed fiber optic transceiver (typically an SFP (Small Form-factor Pluggable) optical module) and a serializer / deserializer (SerDes) within the FPGA. The communication protocol uses the Aurora protocol or a custom high-speed serial protocol.

[0029] In this device, the communication interface of the simulation model is a bidirectional transmission channel. Uplink (from the simulator to the device), it receives power module status information (including module voltage values, module bypass switch status, voltage across the energy-consuming resistor, etc.) from the real-time simulator. After level conversion and protocol parsing, this information is written into the device's internal status register. Downlink (from the device to the simulator), it encapsulates module control commands (such as IGBT turn-on / turn-off commands and bypass switch action commands) output by the external netlist program module 301 or the power module control board netlist program module 302 into a data frame format recognizable by the simulator, and sends it to the real-time simulation model for execution via the fiber optic link. This interface internally has independent transmit FIFO (First In First Out) and receive FIFOs to achieve data transmission and reception buffering.

[0030] The valve control communication interface 303 refers to the communication channel connecting the power module fault simulation device and the flexible DC valve control device. In terms of hardware, this interface consists of a fiber optic transceiver (using a transmitting optical module in the uplink direction and a receiving optical module in the downlink direction) and a protocol processing unit inside the FPGA. The communication protocol adopts the standard fiber optic communication protocol of the flexible DC valve control device (usually a serial protocol based on HDLC (High-Level Data Link Control) or a custom frame format).

[0031] In this device, the valve control communication interface 303 is also a bidirectional transmission channel. Uplink, it encapsulates fault information (including fault type code, fault occurrence time, etc.) and module status information (such as power-on status, communication status, module capacitor voltage, module bypass switch status, etc.) output by the power module control board netlist program module 302 into a data frame format that the valve control device can parse, and sends it to the flexible DC valve control device via optical fiber. Downlink, it receives control and protection commands (including module bypass commands, IGBT trigger pulse commands, etc.) issued by the flexible DC valve control device, and writes them into the device's internal command register after protocol parsing for the power module control board netlist program module 302 to read. This interface has two independent optical fiber links: an uplink direct connection channel and a downlink direct connection channel, corresponding to the two transmission directions respectively.

[0032] The power module control board netlist program module 302 refers to the logic function unit running inside the FPGA chip on this device. This module and the peripheral netlist program module 301 can physically run in different logic areas of the same FPGA chip, or they can run in different FPGA chips.

[0033] In this device, the input of the power module control board netlist program module 302 is connected to the status register of the communication interface 304 with the simulation model via an internal bus, reading status information such as module voltage, module bypass switch status, and voltage across the energy-consuming resistor sent by the real-time simulator; its output is connected to the transmit FIFO of the communication interface 303 with the valve control via an internal bus, encapsulating the detected fault information and sending it to the flexible DC valve control device. This module integrates a netlist program for power module-level fault detection and protection strategies, including but not limited to module voltage over-limit detection logic (comparing the received module voltage value with internally preset overvoltage and undervoltage thresholds), module temperature over-limit detection logic, IGBT drive fault detection logic, and communication status detection logic. When any detection logic outputs a fault trigger signal, the module generates a corresponding fault protection control signal according to the preset protection strategy, including encoding the fault information and sending it to the flexible DC valve control device via the communication interface 303, and issuing an IGBT lockout command to the communication interface 304 with the simulation model via the internal bus. All detection and judgment logic in this module is executed in parallel by hardware logic circuits, without relying on the sequential execution of software programs.

[0034] In this embodiment, the background operation interface displays icons for various fault simulation types and multiple configuration items. Users can trigger the fault simulation type icons by clicking, swiping, or touching them. The configuration items allow users to configure parameters for different fault simulation types. After the user triggers any fault simulation type icon in the background operation interface, the module-level fault simulation command generated by the operation interface first enters the peripheral netlist program module 301. This module decodes the command and generates corresponding control action signals, which are then distributed to the other four modules. The communication interface 304 with the simulation model continuously receives module status information from the real-time simulator and writes it to the simulation model. The data in the status register can be read by both the peripheral netlist program module 301 and the power module control board netlist program module 302. The power module control board netlist program module 302 performs fault detection based on the read status information. The detection results are sent to the flexible DC valve control device via the valve control communication interface 303, and also fed back to the peripheral netlist program module 301 as the trigger for fault simulation. Control commands issued by the flexible DC valve control device are received via the valve control communication interface 303, processed by the peripheral netlist program module 301 (which may replace or intercept them), and then sent to the real-time simulator for execution via the simulation model communication interface 304. All modules achieve synchronization and coordination through handshake signals and status flags, ensuring the orderly and consistent transmission of data between modules.

[0035] The power module control board netlist program module 302 and the adjacent module communication interface 305 are communicatively connected; the adjacent module communication interface 305 refers to the communication channel connecting the fault simulation unit of this power module and the fault simulation unit of the adjacent power module. This interface is hardware-based, consisting of an optical fiber transceiver (including a transmitting optical module and a receiving optical module) and a cross-communication control unit inside the FPGA. The communication protocol uses a high-speed serial communication protocol (such as a dedicated link protocol based on SerDes).

[0036] In this embodiment, the communication interface 305 with the adjacent module is a bidirectional transmission channel. Its input end is connected to the control port of the peripheral netlist program module 301 and the status output port of the power module control board netlist program module 302, and its output end is connected to the corresponding receiving port of the adjacent power module fault simulation unit. This interface mainly includes at least two independent communication links: a downlink cross channel for receiving fault information, status information, and control commands sent by the adjacent module, and an uplink cross channel for sending fault information, status information, and control commands to the adjacent module.

[0037] Specifically, through this interface, the power module control board netlist program module 302 can obtain the operating status of adjacent power modules and the control commands of this module. When an abnormality is detected in an adjacent module (such as communication interruption), this module can adjust its own fault protection strategy or synchronously trigger associated fault simulation.

[0038] For example, when the peripheral netlist program module 301 receives an "uplink cross-connection failure" command, it controls the uplink cross-connection channel in this interface to shut down, preventing adjacent modules from receiving fault, status information, and control commands sent by this module. This manifests as a communication loss fault on the adjacent module's side. This interface has an independent channel enable register. The peripheral netlist program module 301 can software-shut down the corresponding channel by rewriting the channel enable / disable flag in this register, without physically disconnecting the fiber optic connection.

[0039] In one example of this application, when the fault simulation type is a communication fault, the control action signal is used to trigger the disconnection of the uplink direct connection channel and / or downlink direct connection channel in the valve control communication interface 303, and / or control the disconnection of the uplink cross channel and / or downlink cross channel in the communication interface 305 with the adjacent module.

[0040] In this embodiment, when the fault simulation type is a communication fault, the peripheral netlist program module 301, based on the received fault setting instruction, sends a channel on / off control signal to the valve control communication interface 303 and / or the adjacent module communication interface 305 to disconnect the corresponding communication link. Communication faults specifically include four types: uplink direct communication fault, downlink direct communication fault, uplink cross-connection communication fault, and downlink cross-connection communication fault, corresponding to communication interruptions in different transmission directions between this device and the flexible DC valve control device, and between this device and adjacent module devices. The peripheral netlist program module 301's rewriting of each flag bit in the channel enable register is a real-time hardware logic write operation. The effective time of disconnection is determined by the register write cycle, typically completed within nanoseconds, thus accurately simulating communication loss scenarios caused by sudden fiber optic link interruption or poor contact in actual operation. After the fault simulation ends, the background interface sends a clear command, and the peripheral netlist program module 301 restores the corresponding channel's flag bit to "1", instantly restoring the link communication function.

[0041] like Figure 4 As shown, specifically, the uplink and downlink communication faults of the power module can be set independently online through the background operation interface of the fault simulation device. The setting instructions are issued by the background interface to the peripheral netlist program within the fault simulation device. Specifically, the uplink direct connection communication fault simulation is achieved by the peripheral netlist program controlling the valve control communication interface 303 through channel 2 to close the uplink direct connection channel; the downlink direct connection communication fault simulation is achieved by the peripheral netlist program controlling the valve control communication interface 303 through channel 2 to close the downlink direct connection channel; the uplink cross communication fault simulation is achieved by the peripheral netlist program controlling the communication interface 305 of the adjacent module through channel 3 to close the uplink cross communication channel; and the downlink cross communication fault simulation is achieved by the peripheral netlist program controlling the communication interface 305 of the adjacent module through channel 3 to close the downlink cross communication channel.

[0042] In one example of this application, when the fault simulation type is a state detection type fault, the control action signal is used to replace the voltage value in the state information sent by the real-time simulator with a preset fault value, and output the replaced voltage value, the preset temperature value, and other information to the power module control board netlist program module 302 through the communication interface 304 with the simulation model, so that the power module control board netlist program module 302 generates a corresponding fault protection control signal according to the fault value.

[0043] In this embodiment, when the fault simulation type is a state detection fault, the peripheral netlist program module 301 sends a data replacement control signal to the simulation model communication interface 304 according to the fault setting instruction (including fault type identifier and preset fault value parameters) issued by the background interface. The simulation model communication interface 304 internally contains a data replacement logic unit, located in the data receiving path and connected in series between the protocol parsing module and the status register write port. The module status information sent by the real-time simulator via the fiber optic link is parsed into parallel data frames. After these data frames enter the data replacement logic unit, the peripheral netlist program module 301 determines the data field to be replaced based on the fault type identifier. If the fault is a module voltage measurement deviation, the voltage field in the data frame is located; if the fault is a power-consuming resistor temperature measurement deviation, the temperature field in the data frame is located. The data replacement logic unit reads and discards the original value of the located field, and simultaneously reads the preset fault value from the fault value register and writes it to the corresponding bit of the field, while keeping the original values ​​of the other fields unchanged. The complete data frame after replacement is then written to the status register for the power module control board netlist program module 302 to read. After the power module control board netlist program module 302 reads the replaced status information, its internally integrated voltage over-limit detection logic compares the received voltage value with the preset over-voltage threshold, or the temperature over-limit detection logic compares the temperature value with the preset over-temperature threshold. Since the replaced fault value has exceeded the corresponding threshold, the detection logic outputs a fault trigger signal, and the power module control board netlist program module 302 then generates a corresponding fault protection control signal, including encoding the fault information and sending it to the flexible DC valve control device through the valve control communication interface 303. During the period when the enable signal of the peripheral netlist program module 301 is continuously valid, the data replacement process performs a replacement operation on each frame of uploaded data, so that the power module control board netlist program module 302 continuously detects abnormal state values, simulating the fault of continuously high or low measured values ​​caused by drift of the module voltage / temperature measurement circuit or damage to the sampling chip during actual operation.

[0044] like Figure 4As shown, in another example of this application, the simulation of module voltage deviation faults can be implemented in the following way: Module voltage measurement deviation faults can be set independently online in the background operation interface of the fault simulation device. The set false module voltage value is sent by the background interface to the peripheral netlist program in the fault simulation device. Module voltage measurement too high fault simulation: The peripheral netlist program controls the communication interface 304 with the simulation model through channel 1, replacing the real module voltage value sent by the real-time simulator with the "false value of module voltage too high received from the background interface," and then sends the replaced "false value of module voltage too high" to the power module control board netlist program for use; Module voltage measurement too low fault simulation: The peripheral netlist program controls the communication interface 304 with the simulation model through channel 1, replacing the real module voltage value sent by the real-time simulator with the "false value of module voltage too low received from the background interface," and then sends the replaced "false value of module voltage too low" to the power module control board netlist program for use.

[0045] The simulation of abnormal module power consumption resistor temperature faults can be achieved through the following steps: The abnormal module power consumption resistor temperature value can be set independently online in the background operation interface of the fault simulation device. The set abnormal resistor temperature value is sent to the external netlist program in the fault simulation device by the background interface. Module power consumption resistor temperature abnormality fault simulation: The external netlist program sends the "received abnormal module power consumption resistor temperature value sent from the background interface" to the communication interface 304 with the simulation model via channel 1. Then, the communication interface 304 with the simulation model sends it to the power module control board netlist program via channel 6. Because the simulation model does not have a power consumption resistor temperature calculation program, the real-time simulation model cannot send the module power consumption resistor temperature value.

[0046] In one example of this application, when the fault simulation type is an action abnormality fault, the control action command is used to intercept the actuator action command issued by the flexible direct valve control device to the simulation model communication interface 304, replace the action command with the action command of the opposite state, and output it to the real-time simulator through the simulation model communication interface 304.

[0047] In this embodiment, when the fault simulation type is an action anomaly fault, the peripheral netlist program module 301 sends an instruction to the simulation model communication interface 304 to intercept and replace control signals according to the fault setting instruction sent by the background interface. The simulation model communication interface 304 internally has an instruction interception and replacement logic unit located in the downlink data path, connected in series between the protocol parsing module and the transmission buffer module. This unit is used to intercept the actuator action instructions sent by the flexible direct current valve control device to the simulation model communication interface 304 via the valve control communication interface 303.

[0048] After receiving a malfunction command, the peripheral netlist program module 301 sends a replacement enable signal and target status parameters to the command interception and replacement logic unit. When the actuator action command data frame from the flexible DC valve control device arrives at this unit, the unit parses the action type identifier and action status value in the command field, discards the original action status value, and simultaneously reads the opposite status value written by the peripheral netlist program module 301 from the target status register and writes it to the corresponding bit of the command field, while the remaining fields remain unchanged. The replaced data frame continues to be sent to the real-time simulator along the downlink path via the transmit buffer and optical module. If the simulated actuator malfunction is detected, the original command "off" is replaced with "on," causing the corresponding actuator in the real-time simulation model to perform an unintended action if it does not receive a valid action command or receives an opposite command. If the simulated actuator refusal to operate is detected, the original command "on" is replaced with "off," causing the corresponding actuator in the real-time simulation model to maintain its original state and not execute after receiving the action command.

[0049] like Figure 4 The device structure shown, taking bypass switch malfunction as an example: When the flexible DC valve control device does not issue a bypass command, there is no bypass command frame in the downlink data path of the communication interface 304 with the simulation model. At this time, the peripheral netlist program module 301 actively generates a "bypass switch on" command frame through the control command interception and replacement logic unit and inserts it into the downlink data stream, replacing the idle frame and sending it to the real-time simulator to simulate the working condition of bypass switch malfunction. Among them, the bypass switch malfunction fault and failure to operate fault of the module can be set independently online in the background operation interface of the fault simulation device. The set command is sent by the background interface to the peripheral netlist program in the fault simulation device. For the bypass malfunction fault simulation, the peripheral netlist program controls the communication interface 304 with the simulation model through channel 1, forcibly replacing the module bypass switch action command transmitted from channel 5 with "on", and then sends the replaced module bypass switch "on" command to the real-time simulation model for execution. For the bypass failure simulation, the external netlist program controls the communication interface 304 between channel 1 and the simulation model, forcibly replacing the module bypass switch action command transmitted from channel 5 with "off", and then sends the replaced module bypass switch "off" command to the real-time simulation model for execution.

[0050] Taking the failure of the IGBT in the energy-consuming branch as an example: After the flexible DC valve control device issues the IGBT turn-on command, the command interception and replacement logic unit replaces the turn-on state in the command with the turn-off state and sends it to the real-time simulator, so that the IGBT in the energy-consuming branch in the simulation model remains off and the energy-consuming resistor cannot be connected, simulating the fault scenario where the IGBT refuses to conduct due to gate drive failure or junction over-temperature protection. Specifically, if the fault is a false trip of the module energy-consuming branch T3 / T5, it can be set independently online in the background operation interface of the fault simulation device. The set command is sent by the background interface to the peripheral netlist program in the fault simulation device. The peripheral netlist program controls the communication interface 304 with the simulation model through channel 1, forcibly replacing the module energy-consuming branch T3 / T5 tube action command transmitted from channel 5 with "turn on / turn on", and then sends the replaced module energy-consuming branch T3 / T5 tube "turn on / turn on" command to the real-time simulation model for execution, simulating the false trip of the module energy-consuming branch T3 / T5.

[0051] In one example of this application, when the fault simulation type is a component fault, the control action instruction is used to send the corresponding fault flag information to the power module control board netlist program module 302; The power module control board netlist program module 302 is also used to generate corresponding fault information based on the fault flag information, and send it to the flexible DC valve control device via the valve control communication interface 303, so that the flexible DC valve control device can issue corresponding protection commands.

[0052] In this embodiment, when the fault simulation type is a component fault, the peripheral netlist program module 301, based on the fault setting command (including fault type identifier, such as power supply fault, IGBT drive fault, module control board fault, etc.) issued by the background interface, searches for the flag bit code corresponding to the fault type from the internally preset fault flag mapping table, and sends the code to the fault flag register of the power module control board netlist program module 302 via the internal data bus. The power module control board netlist program module 302 has a fault flag scanning logic that polls each bit of the fault flag register at a fixed period. When a flag bit is detected as high, the fault flag scanning logic matches the flag bit code with the internally preset fault protection strategy table to determine the fault information code and uploading priority corresponding to the fault type. Subsequently, the power module control board netlist program module 302 encapsulates the fault information code into an uplink data frame according to the communication protocol format of the valve control communication interface 303, writes it into the transmit FIFO of the valve control communication interface 303, and sends it to the flexible DC valve control device via the optical fiber link. After receiving the fault information, the flexible DC valve control device issues the corresponding protection command (such as the module bypass command) according to the internal preset protection strategy. After receiving the command through the downlink channel of the valve control communication interface 303, it is transmitted to the power module control board netlist program module 302, which then sends it to the real-time simulator for execution through the simulation model communication interface 304.

[0053] Taking a power supply failure as an example, after the power module control board netlist program module 302 sends the power supply failure information, the flexible DC valve control device issues a bypass command for the module, and the module exits the system. Simultaneously, the power module control board netlist program module 302 latches the power supply failure flag and continues to send the failure information until the failure is cleared, preventing false protection resets due to automatic flag reset. Specifically, the module's power supply failure can be set independently online in the background operation interface of the fault simulation device. The setting command is sent from the background interface to the peripheral netlist program within the fault simulation device. The peripheral netlist program first sends the power supply failure flag of the module to the power module control board netlist program via channel 4. After receiving the information, the power module control board netlist program transmits the module's power supply failure information to the flexible DC valve control device via the uplink direct connection channel. Upon receiving the information, the flexible DC valve control device then issues a module bypass command, which is sequentially sent to the real-time simulation model for execution via the downlink direct connection channel and channel 5. After the testing period, the peripheral netlist program will control the communication interface 304 with the simulation model via channel 1, and shut down the bidirectional communication transmission of channels 5 and 6; control the communication interface 303 with the valve control via channel 2, and shut down the bidirectional communication transmission of the downlink direct connection channel and the uplink direct connection channel; control the communication interface 305 with the adjacent module via channel 3, and shut down the bidirectional communication transmission of the downlink cross channel and the uplink cross channel; and control the power module control board netlist program via channel 4, causing it to stop working.

[0054] For the simulation of IGBT drive faults in the power module, the external netlist program first sends the IGBT drive fault flag of the module to the power module control board netlist program through channel 4. After receiving the information, the power module control board netlist program sends the IGBT drive fault information of the module to the flexible DC valve control device through the uplink direct connection channel. After receiving the information, the flexible DC valve control device sends the module bypass command, which is then sent to the real-time simulation model for execution through the downlink direct connection channel and channel 5 in sequence. Simultaneously, the power module control board netlist program sends the IGBT lockout command of the module to the real-time simulation model through channel 5.

[0055] In one example of this application, the peripheral netlist program module 301 is further configured to disconnect the communication links with the simulation model communication interface 304, the valve control communication interface 303, and the adjacent module communication interface 305 after the flexible DC valve control device issues a corresponding protection command, so as to interrupt the uploading of status information and the issuance of control commands; and issue control action commands to stop the operation of the power module control board netlist program module 302.

[0056] In this embodiment, the peripheral netlist program module 301 is internally equipped with protection action monitoring logic. This logic continuously monitors the downlink data path of the valve control communication interface 303 via an internal bus, and detects the protection command frames issued by the flexible direct current valve control device in real time. When the monitoring logic identifies a protection command (such as a module bypass command) for this module, it starts an internally preset delay counter to start timing. After the delay counter reaches the preset time setting value, the peripheral netlist program module 301 performs the following operations in sequence: First, it writes "0" to the flag bits corresponding to the fifth and sixth channels in the channel enable register of the communication interface 304 with the simulation model, so that the sending and receiving links of the fifth channel (the device sends commands to the simulator) and the sixth channel (the simulator sends status to the device) are simultaneously turned off, interrupting all data interaction between the module and the real-time simulator; Second, it writes "0" to the flag bits corresponding to the uplink direct connection channel and the downlink direct connection channel in the channel enable register of the communication interface 303 with the valve control device. First, all data interaction between the interrupt module and the flexible DC valve control device is interrupted. Second, "0" is written to the flag bits of the corresponding uplink and downlink cross channels in the channel enable register of the communication interface 305 with the adjacent module, interrupting all data interaction between the interrupt module and the adjacent module. Finally, a stop operation command is sent to the control port of the power module control board netlist program module 302. After receiving the command, the power module control board netlist program module 302 jumps to the state machine of all its internal timing logic to the idle state, sets all output ports to the high impedance state, and no longer responds to any changes in input signals. After the above operations are completed, the power module fault simulation device completely withdraws from data interaction with external devices, and the power module control board netlist program module 302 stops all detection and protection functions, simulating the actual physical process of the power module completely losing power and all communication being interrupted due to severe damage to internal components (such as control board burnout or power supply failure).

[0057] For example, the module control board fault can be set independently online through the background operation interface of the fault simulation device. The setting command is issued by the background interface to the peripheral netlist program in the fault simulation device. The peripheral netlist program first issues the fault flag of the module's control board to the power module control board netlist program through channel 4. After receiving the power module control board netlist program, it transmits the module control board fault information to the flexible DC valve control device through the uplink direct connection channel. After receiving the information, the flexible DC valve control device issues a module bypass command, which is then issued to the real-time simulation model for execution through the downlink direct connection channel and channel 5 in sequence. Afterward, the peripheral netlist program controls the communication interface 304 with the simulation model through channel 1 to close the bidirectional communication transmission of channels 5 and 6; controls the communication interface 303 with the valve control through channel 2 to close the bidirectional communication transmission of the downlink direct connection channel and the uplink direct connection channel; controls the communication interface 305 with the adjacent module through channel 3 to close the bidirectional communication transmission of the downlink cross channel and the uplink cross channel; and controls the power module control board netlist program through channel 4 to stop it from working.

[0058] In one example of this application, when the fault simulation type is a power-on / off fault, the peripheral netlist program module 301 is used to control the connection and disconnection of the communication links of the communication interface 304 with the simulation model, the communication interface 303 with the valve control, and the communication interface 305 with the adjacent module, as well as the start or stop of the power module control board netlist program module 302, according to the preset voltage threshold and the module voltage value in the status information sent by the real-time simulator.

[0059] In this embodiment, the peripheral netlist program module 301 internally includes voltage monitoring and state machine control logic. This logic reads the module voltage value sent by the real-time simulator from the status register of the communication interface 304 with the simulation model via an internal data bus. Simultaneously, the peripheral netlist program module 301 internally includes a power-on threshold register and a power-off threshold register. The values ​​of these two registers are written by the background interface when issuing fault setting commands. After comparing the read module voltage value with the two thresholds, the voltage monitoring and state machine control logic controls the on / off state of each communication interface within the device and the start / stop state of the power module control board netlist program module 302.

[0060] Internally, this logic maintains a state machine containing three states: power-down state, power-on process, and normal operation state. When the state machine is in the power-down state, if the detected module voltage value is greater than or equal to the power-on threshold, the state machine jumps to the power-on process state, and the output voltage monitoring and state machine control logic performs the following operations in sequence: write "1" to the flag bits corresponding to the fifth and sixth channels in the channel enable register of the communication interface 304 with the simulation model to restore bidirectional communication between the device and the real-time simulator; write "1" to the flag bits corresponding to the uplink direct connection channel and the downlink direct connection channel in the channel enable register of the communication interface 303 with the valve control to restore bidirectional communication between the device and the flexible direct valve control device; write "1" to the flag bits corresponding to the uplink cross channel and the downlink cross channel in the channel enable register of the communication interface 305 with the adjacent module to restore bidirectional communication with the fault simulation unit of the adjacent module; and send a start-up command to the control port of the power module control board netlist program module 302, which switches from the idle state to the running state and begins to execute periodic fault detection logic. When the state machine is in normal operation, if the detected module voltage value is less than or equal to the power-down threshold, the state machine jumps to the power-down state and executes the reverse operation in sequence, that is, shutting down all communication channels and stopping the operation of the power module control board netlist program module 302.

[0061] Taking the module power-down simulation as an example: In the real-time simulator, the capacitor voltage of the module gradually decreases. When the module voltage value read by the voltage monitoring and state machine control logic drops below the power-down threshold, all communication channels are immediately shut down, the power module control board netlist program module 302 stops working, and the flexible DC valve control device reports a communication fault because it cannot receive the uplink information of the module. This is consistent with the physical process of the actual power module powering down due to undervoltage of the power supply.

[0062] Specifically, such as Figure 4 As shown, the power-on and power-off thresholds U of the (N-1)th power module 上电 U 下电 The power-on and power-off thresholds can be set independently online in the background operation interface of the fault simulation device. After the power-on and power-off thresholds are set, the background interface sends them to the external netlist program within the fault simulation device. The external netlist program receives the voltage value U of this module from the real-time simulator in real time through channel 1. sm .

[0063] When the external netlist program detects the module voltage value U sm ≥ Power tapping threshold U 上电The system will restore bidirectional communication between channels 5 and 6 via channel 1 and the simulation model communication interface 304; restore bidirectional communication between the downlink direct-connect channel and the uplink direct-connect channel via channel 2 and the valve control communication interface 303; restore bidirectional communication between the downlink cross channel and the uplink cross channel via channel 3 and the adjacent module communication interface 305; and control the power module control board netlist program via channel 4 to start it working. This simulates the module power-on process.

[0064] When the external netlist program detects the module voltage value U sm ≤Power-off threshold U 下电 The system will control the communication interface 304 with the simulation model via channel 1, disabling bidirectional communication between channels 5 and 6; control the communication interface 303 with the valve control via channel 2, disabling bidirectional communication between the downlink direct-connect channel and the uplink direct-connect channel; control the communication interface 305 with the adjacent module via channel 3, disabling bidirectional communication between the downlink cross channel and the uplink cross channel; and control the power module control board netlist program via channel 4, causing it to stop working. This simulates the module power-down process.

[0065] Furthermore, for power module overvoltage breakdown simulation, the fault simulation can be performed through the following process: the module's overvoltage breakdown threshold U 击穿 The breakdown threshold can be set independently online via the background operation interface of the fault simulation device. After the threshold is set, it is sent from the background interface to the external netlist program within the fault simulation device. sm When the external netlist program detects the module voltage value U sm ≥ Overvoltage breakdown short-circuit threshold U 击穿 The power module control board netlist program will be controlled through channel 4 to issue a command to simultaneously turn on the T1+T2 transistors of the half-bridge module, the T1+T2 transistors of the full-bridge module, or the T3+T4 transistors. This command is sent to the real-time simulation model through channel 5 for execution, and the module voltage drops to 0 instantaneously, simulating the overvoltage breakdown of the module.

[0066] In one example of this application, the external control and protection device is a flexible direct current valve control device; The real-time simulator contains a primary model of a flexible DC transmission system, which includes an equivalent model of the power module.

[0067] In one example of this application, the power module is an integrated distributed energy-consuming flexible DC power module 306, which includes a half-bridge power module or a full-bridge power module. The power module has an energy-consuming branch connected in parallel across the DC capacitor. The energy-consuming branch includes a series-connected switching transistor and an energy-consuming resistor.

[0068] In this embodiment, the external control and protection device is a flexible DC valve control device, that is, the converter valve control device of the flexible DC transmission system, which is responsible for generating trigger pulses and monitoring the operating status of each power module of the converter valve.

[0069] The real-time simulator contains a primary model of a flexible DC transmission system that includes equivalent models of power modules. This primary model covers the electromagnetic transient simulation models of the equivalent power supply of the AC system, the converter transformer, the bridge arm reactor, and the three-phase six-bridge arm MMC converter valve. Each power module adopts the Thevenin equivalent or switching function equivalent model to balance simulation accuracy and computational efficiency.

[0070] The power module to be simulated is an integrated distributed energy-dissipating flexible DC power module 306, which includes two topologies: a half-bridge power module and a full-bridge power module. The difference from conventional topologies lies in the fact that an energy-dissipating branch is connected in parallel across the positive and negative terminals of the DC capacitor in the power module. This energy-dissipating branch is formed by a switching transistor (T3 in the half-bridge module and T5 in the full-bridge module), an energy-dissipating resistor, and a connecting copper busbar connected in series. The activation of this energy-dissipating branch is controlled by the power module control board netlist program module 302 based on the module voltage detection results. When the module voltage abnormally rises above the energy-dissipating branch's operating voltage setting, it is triggered to activate, consuming the energy stored in the capacitor through the energy-dissipating resistor to reduce the module voltage. This device sends activation or deactivation commands for the energy-dissipating branch's switching transistor to the real-time simulator via the simulation model communication interface 304, changing the activation state of the energy-dissipating branch in the simulation model and simulating the normal operation and abnormal behavior of the energy-dissipating branch in the actual power module. By combining the above-mentioned fault simulation types, this device can cover various typical fault scenarios that may occur during the operation of the integrated distributed energy-consuming flexible DC power module 306.

[0071] This application also provides a power module fault simulation system, including: A real-time simulator is used to run a simulation model of the power module, send module status information, and receive execution instructions. Control and protection equipment is used to receive fault information and issue control and protection commands. And a fault simulation device for the integrated distributed energy-consuming flexible DC power module 306 as described in any of the above embodiments, which is communicatively connected to the real-time simulator and the control and protection device, respectively.

[0072] The present invention also provides a method for simulating typical faults of integrated distributed energy-consuming modules, applied to the integrated distributed energy-consuming module typical fault simulation device as described in any of the above claims, comprising: Receive module-level fault simulation instructions from the operation interface, and parse the instructions to determine the fault simulation type; Based on the fault simulation type, a corresponding control action strategy is matched from a plurality of preset fault simulation strategies; the fault simulation strategy includes at least one of a communication link control strategy, a status data replacement strategy, an instruction interception and replacement strategy, and a fault flag writing strategy. According to the matched control action strategy, a corresponding control action signal is generated, and the control action signal is sent to at least one of the communication interface with the simulation model, the communication interface with the valve control, the communication interface with the adjacent module, and the power module control board netlist program module for execution, so as to generate the corresponding fault state in the simulation model of the real-time simulator.

[0073] The peripheral netlist program module refers to a logic functional unit written in a hardware description language and running on an FPGA device. As the scheduling core for fault simulation, it is responsible for decoding fault setting instructions issued from the operating interface and generating corresponding control action signals. Fault simulation type refers to the fault classification identifier carried in the instructions issued from the operating interface, including communication faults, status detection faults, action anomaly faults, component faults, and power-on / off faults. Fault simulation strategy refers to the set of pre-defined control logic within the peripheral netlist program module for different fault types, including communication link control strategy (controlling link connection / disconnection by rewriting the channel enable register), status data replacement strategy (modifying specific fields in status information through data replacement logic units), instruction interception and replacement strategy (intercepting and rewriting downlink instructions through instruction interception and replacement logic units), and fault flag writing strategy (triggering component fault simulation by writing flag bits to the fault flag register).

[0074] In this embodiment, the peripheral netlist program module receives fault setting instructions from the background operation interface via a parallel bus. These instructions include a fault type code and associated parameter fields. The peripheral netlist program module has an internal instruction decoder that parses the received instructions, extracts the fault type code, and matches this code with an internally preset fault-policy mapping table to determine the corresponding control action policy and execution target module for that fault type. Subsequently, the peripheral netlist program module generates corresponding control action signals based on the matching results and distributes them to the corresponding execution modules.

[0075] Taking communication-related faults as an example, after the peripheral netlist program module matches the communication link control strategy, it generates a channel on / off control signal and sends it to the channel enable register of the communication interface with valve control or the communication interface with adjacent modules, and rewrites the corresponding channel flag bit to realize the link on / off.

[0076] Taking a state-detection type fault as an example, after the peripheral netlist program module matches the state data replacement strategy, it sends a replacement enable signal and the target fault value to the data replacement logic unit inside the communication interface with the simulation model. After receiving the state data frame sent by the real-time simulator, the unit locates the voltage field and replaces the original value with the fault value before writing it into the state register.

[0077] Taking an abnormal action type fault as an example, after the peripheral netlist program module matches the instruction interception and replacement strategy, it sends an interception enable signal and target state parameters to the instruction interception and replacement logic unit inside the communication interface with the simulation model. This unit intercepts the actuator action instructions sent by the flexible direct current valve control device, replaces the original action state with the opposite state, and then sends it to the real-time simulator.

[0078] Taking component failure as an example, after the external netlist program module matches the fault flag writing strategy, it looks up the corresponding flag bit code for the fault type from the internally preset fault flag mapping table and writes it to the fault flag register of the power module control board netlist program module via the internal data bus. The execution of each of the above strategies is coordinated by the timing control logic inside the external netlist program module to ensure that the control action signals are sent to each target module in the correct timing.

[0079] This invention also provides a typical fault test method for integrated distributed energy-consuming modules, applied to the typical fault simulation device for integrated distributed energy-consuming modules as described in any of the above claims, comprising: Start the hardware-in-the-loop simulation test system and clear the preset fault simulation settings in the device; The initial voltage values ​​of each bridge arm power module of the tested converter valve are set through the real-time simulator, and the power-on / off thresholds and overvoltage breakdown thresholds of each power module are set through the operation interface. Various fault simulation commands are sequentially sent to the designated power modules, and the status feedback information of the corresponding power module in the background interface of the flexible DC valve control device is read after each sending. The status feedback information includes at least one of the following: power-on status, communication status, voltage measurement value, bypass status, energy-consuming branch status, and energy-consuming resistor temperature value. The status feedback information is compared with the expected status. If they match, the corresponding type of fault simulation function is determined to be correct.

[0080] A hardware-in-the-loop simulation test system refers to a test system that connects real control and protection equipment with a real-time simulator through a physical interface to form a closed-loop test environment. The real-time simulator runs a mathematical model of the controlled object, and the control and protection equipment interacts with the simulator through actual input / output interfaces. The initial voltage value refers to the starting value of the capacitor voltage of each bridge arm power module, manually set in the simulator's backend operation interface, used to establish the initial operating conditions before testing. The power-on and power-off thresholds refer to the voltage boundary values ​​for the power module control board to start and stop working. When the module voltage is higher than the power-on threshold, the device powers on and starts; when it is lower than the power-off threshold, the device powers off and shuts down. The overvoltage breakdown threshold refers to the voltage boundary value that triggers the power module overvoltage breakdown simulation. When the module voltage exceeds this value, an IGBT shoot-through short-circuit simulation is triggered. Status feedback information refers to the operating status data from each power module displayed on the background interface of the flexible DC valve control device, including power-on status (whether the module is powered on), communication status (whether the uplink / downlink communication is normal), voltage measurement value (current voltage of the module), bypass status (whether the module is bypassed), energy consumption branch status (whether the energy consumption branch IGBT is in the on or off state), and energy consumption resistor temperature value.

[0081] In this embodiment, the test operator first performs a reset operation through the background interface of the module-level fault simulation and detection protection device, clearing the various fault flags and channel control values ​​previously set in the registers inside the device, restoring all communication links to the default connected state, and putting the power module control board netlist program module in a ready-to-start state. Then, the device is started. Figure 4 The hardware-in-the-loop simulation test system shown enables the real-time simulator to start running a primary model of the flexible DC transmission system, establishing normal communication between the flexible DC valve control device and the fault simulation device. For any integrated distributed energy-consuming flexible DC power module 306, simulation testing can be performed through the following steps: Step 1: First, operate the backend interface of the module-level fault simulation and detection protection device, reset and clear the previously set module-level faults, and then start. Figure 4 The integrated distributed energy-consuming flexible DC power module 306 real-time simulation hardware-in-the-loop test system shown is the power module fault simulation system in this embodiment; Step 2: In the real-time simulation model, the tested flexible DC converter valve is a three-phase six-bridge MMC with a total number of modules per bridge arm of Nsum. In the simulator's backend operation interface, manually set the voltage of all power modules of the six bridge arms (AU, AD, BU, BD, CU, CD) of the tested flexible DC converter valve in the real-time simulation model to 0V. Step 3: Then, in the background interface of the module-level fault simulation and detection protection device, manually set the power-on threshold of all modules of the 6 bridge arms of the tested flexible DC converter valve to 360V, the power-off threshold to 310V, and the overvoltage breakdown short circuit threshold to 4500V. Step 4: In the simulator's backend operation interface, manually set the voltage of the tested flexible DC converter valve AU arm 1# module to 350V, the voltage of AU arm 2# module to 365V, and the voltage of AU arm 3# module to 305V in the real-time simulation model. Step 5: On the background interface of the flexible DC valve control device, observe the detection results of the flexible DC valve control on the status of AU1, AU2, and AU3 modules. AU bridge arm 1# module should not be powered on and report an uplink communication failure. AU bridge arm 2# module should be powered on and report normal uplink communication. AU bridge arm 3# module should not be powered on and report an uplink communication failure. Step 6: In the simulator's backend operation interface, continue to manually set the voltage of the tested flexible DC converter valve AU bridge arm 2# module in the real-time simulation model to 315V. Then, in the backend interface of the flexible DC valve control device, observe that the AU bridge arm 2# module should be powered on and report normal uplink communication. Step 7: In the simulator's backend operation interface, continue to manually set the voltage of the tested flexible DC converter valve AU bridge arm 2# module in the real-time simulation model to 305V. Then, in the backend interface of the flexible DC valve control device, observe that the AU bridge arm 2# module should not be powered on and should report an uplink communication fault. This verifies that the design of the module's power-on and power-off simulation function is correct. Step 8: In the simulator's backend operation interface, manually set the voltage of the AU bridge arm 4# module of the tested flexible DC converter valve in the real-time simulation model to 4450V. Then, in the backend interface of the flexible DC valve control device, observe that the voltage of the AU bridge arm 4# module should be stable at 4450V and the uplink communication should be reported as normal. Step 9: In the simulator's backend operation interface, continue to manually set the voltage of the AU bridge arm 4# module of the tested flexible DC converter valve in the real-time simulation model to 4550V. Then, in the backend interface of the flexible DC valve control device, observe that the voltage of the AU bridge arm 4# module should drop to 0V instantly and report an uplink communication failure. This verifies that the design of the module's overvoltage breakdown simulation function is correct. Step 10: On the background interface of the flexible DC valve control device, observe that the AU bridge arm 5# module should report normal communication and no fault, and the AU bridge arm 6# module should report normal communication and no fault. Continue to manually set the uplink communication fault of the AU bridge arm 5# module and the downlink communication fault of the AU bridge arm 6# module in the background interface of the module-level fault simulation and detection protection device. Step 11: Then, on the background interface of the flexible DC valve control device, observe that the AU bridge arm 5# module should report an uplink communication failure and bypass, and the AU bridge arm 6# module should report a downlink communication failure and bypass. This verifies that the design of the uplink and downlink communication failure simulation function of the module is correct. Step 12: On the background interface of the flexible DC valve control device, observe that the AU bridge arm 7# module should report normal operation without bypass and the AU bridge arm 8# module should report normal operation without bypass. Continue to manually set the bypass switch malfunction fault of the AU bridge arm 7# module and the bypass switch failure fault of the AU bridge arm 8# module on the background interface of the module-level fault simulation and detection protection device. Step 13: Then, in the background interface of the flexible DC valve control device, manually set the bypass switch closing command of the AU bridge arm 8# module of the tested flexible DC converter valve. This command is sent to the module-level fault simulation and detection protection device for execution. After that, observe that the AU bridge arm 7# module should report the bypass maloperation fault and be bypassed, and the AU bridge arm 8# module should report the bypass failure fault but is not bypassed. This verifies that the design of the module bypass switch abnormal operation fault simulation function is correct. Step 14: In the simulator's backend operation interface, manually set the voltage of the tested flexible DC converter valve AU arm 9# module and AU arm 10# module in the real-time simulation model to 2000V. In the backend interface of the flexible DC valve control device, observe that the voltage value of AU arm 9# module should be 2000V and the voltage value of AU arm 10# module should be 2000V. Step 15: Continue in the background interface of the module-level fault simulation and detection protection device, manually set the voltage measurement value of module 9# of the AU bridge arm of the tested flexible DC converter valve to 3100V and the voltage measurement value of module 10# of the AU bridge arm to 800V. In the background interface of the flexible DC valve control device, observe that the voltage value of module 9# of the AU bridge arm should be 3100V and the voltage value of module 10# of the AU bridge arm should be 800V. This verifies that the design of the fault simulation function for module voltage value measurement deviation is correct. Step 16: On the background interface of the flexible DC valve control device, observe that BD bridge arm 1# module should report normal communication and no fault, BD bridge arm 2# module should report normal communication and no fault, and BD bridge arm 3# module should report normal communication and no fault. Continue to manually set the power supply failure of the tested flexible DC converter valve BD bridge arm 1# module, IGBT drive failure of BD bridge arm 2# module, and module control board failure of BD bridge arm 3# module on the background interface of the module-level fault simulation and detection protection device. Step 17: Then, on the background interface of the flexible DC valve control device, observe that the BD bridge arm 1# module should report power supply failure bypass and uplink communication failure, the BD bridge arm 2# module should report IGBT drive failure bypass, and the BD bridge arm 3# module should report module control board failure bypass and uplink communication failure. This verifies that the design of the module power supply failure, IGBT drive failure, and module control board failure simulation function is correct. Step 18: On the background interface of the flexible DC valve control device, observe that the BD bridge arm 4# module should report normal operation and the energy consumption branch T3 / T5 should be in the off state, and the BD bridge arm 5# module should report normal operation and the energy consumption branch T3 / T5 should be in the off state. Continue on the background interface of the module-level fault simulation and detection protection device, manually set the maloperation fault of the energy consumption branch T3 / T5 of the BD bridge arm 4# module of the tested flexible DC converter valve, and the failure to operate fault of the energy consumption branch T3 / T5 of the BD bridge arm 5# module. Step 19: Then, in the background interface of the flexible DC valve control device, manually set the closing command of the energy consumption branch T3 / T5 of the BD bridge arm 5# module of the tested flexible DC converter valve. This command is sent to the module-level fault simulation and detection protection device for execution. After that, observe that the BD bridge arm 4# module should report the maloperation fault of the energy consumption branch T3 / T5 and be bypassed, and the BD bridge arm 5# module should report the failure to operate the energy consumption branch T3 / T5 but is not bypassed. This verifies that the design of the simulation function of the maloperation fault and the failure to operate the energy consumption branch T3 / T5 is correct. Step 20: In the simulator's backend operation interface, manually set the energy-consuming resistor temperature values ​​of the tested flexible DC converter valve BD arm 6# module and BD arm 7# module in the real-time simulation model to 50℃. In the backend interface of the flexible DC valve control device, observe that the energy-consuming resistor temperature value of BD arm 6# module should be 50℃ and the energy-consuming resistor temperature value of BD arm 7# module should be 50℃. Step 21: Continue in the background interface of the module-level fault simulation and detection protection device, manually set the energy-consuming resistor temperature measurement value of module 6# of the BD bridge arm of the tested flexible DC converter valve to 60℃ and the energy-consuming resistor temperature measurement value of module 7# of the BD bridge arm to 100℃. In the background interface of the flexible DC valve control device, observe that the energy-consuming resistor temperature measurement value of module 6# of the BD bridge arm should be 60℃, there should be no energy-consuming resistor over-temperature fault, and there should be no bypass. The energy-consuming resistor temperature measurement value of module 7# of the BD bridge arm should be 100℃, there should be an energy-consuming resistor over-temperature fault, but there should be no bypass. Step 22: Continue to manually set the closing command for the energy consumption branch T3 / T5 of the tested flexible DC converter valve BD arm 6# module and BD arm 7# module in the background interface of the flexible DC converter device. This command is sent to the module-level fault simulation and detection protection device for execution. After that, observe that the BD arm 6# module should run normally without reporting a fault and the energy consumption branch T3 / T5 is in the closed state. The BD arm 7# module should report the failure to operate the energy consumption branch T3 / T5 and the energy consumption branch T3 / T5 is in the closed state. This verifies that the design of the module energy consumption resistor temperature abnormality fault simulation function is correct. Step 23: Operate the background interface of the module-level fault simulation and detection protection device, reset and clear the various module-level faults set in the above steps, and the simulation ends.

[0082] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and system can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0083] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0084] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0085] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications 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.

Claims

1. A simulation device for typical faults of an integrated distributed energy-consuming module, characterized in that, It includes the peripheral netlist program module, the communication interface with the simulation model, the communication interface with the valve control, the communication interface with adjacent modules, and the power module control board netlist program module; The peripheral netlist program module is used to respond to module-level fault simulation commands received from the operation interface, determine the fault simulation type and issue corresponding control action signals to simulate typical faults of integrated distributed energy-consuming flexible DC power modules. The communication interface with the simulation model is connected to the real-time simulator and is used to transmit module control commands to the real-time simulator and receive voltage and status information uploaded by the real-time simulator. The valve control communication interface is connected to an external control and protection device for sending fault information and status information to the external control and protection device, and for receiving control commands sent by the external control and protection device. The communication interface with the adjacent module is connected to the netlist program of the adjacent paired integrated distributed energy-consuming flexible DC power module control board, and is used to send the fault information, the status information and the control command to the netlist program of the adjacent paired integrated distributed energy-consuming flexible DC power module control board, and to receive the fault information, the status information and the control command sent by the netlist program of the adjacent paired integrated distributed energy-consuming flexible DC power module control board. The power module control board netlist program module is connected to the peripheral netlist program module, the communication interface with the simulation model, the communication interface with the valve control, and the communication interface with the adjacent module, respectively, and is used to perform fault detection and output corresponding fault protection control signals based on the fault information and the status information.

2. The integrated distributed energy-consuming module typical fault simulation device according to claim 1, characterized in that, When the fault simulation type is a communication fault, the control action signal is used to trigger the disconnection of the uplink direct connection channel and / or downlink direct connection channel in the valve control communication interface, and / or control the disconnection of the uplink cross channel and / or downlink cross channel in the communication interface with the adjacent module.

3. The integrated distributed energy-consuming module typical fault simulation device according to claim 1, characterized in that, When the fault simulation type is a state detection type fault, the control action signal is used to replace the voltage value in the state information sent by the real-time simulator with a preset fault value, and output the replaced voltage value and the preset temperature value to the power module control board netlist program module through the communication interface with the simulation model, so that the power module control board netlist program module generates a corresponding fault protection control signal according to the fault value.

4. The integrated distributed energy-consuming module typical fault simulation device according to claim 1, characterized in that, When the fault simulation type is an action abnormality fault, the control action command is used to intercept the actuator action command issued by the flexible direct valve control device to the communication interface with the simulation model, replace the action command with the action command of the opposite state, and then output it to the real-time simulator through the communication interface with the simulation model.

5. The integrated distributed energy-consuming module typical fault simulation device according to claim 1, characterized in that, When the fault simulation type is a component fault, the control action command is used to send the corresponding fault flag information to the power module control board netlist program module. The power module control board netlist program module is also used to generate corresponding fault information based on the fault flag information, and send it to the flexible DC valve control device via the valve control communication interface, so that the flexible DC valve control device can issue corresponding protection commands.

6. The integrated distributed energy-consuming module typical fault simulation device according to claim 1, characterized in that, The peripheral netlist program module is also used to disconnect the communication links with the simulation model, the valve control communication interface, and the adjacent module communication interface after the flexible direct valve control device issues the corresponding protection command, so as to interrupt the fault, status information transmission, and control command issuance. Issue a control action command to stop the operation of the power module control board netlist program module.

7. The integrated distributed energy-consuming module typical fault simulation device according to claim 1, characterized in that, When the fault simulation type is a power-on / off fault, the peripheral netlist program module is used to control the connection and disconnection of the communication links of the communication interface with the simulation model, the communication interface with the valve control, and the communication interface with the adjacent module, as well as the start or stop of the power module control board netlist program module, according to the preset voltage threshold and the module voltage value in the status information sent by the real-time simulator.

8. The integrated distributed energy-consuming module typical fault simulation device according to claim 1, characterized in that, The external control and protection device is a flexible direct valve control device; The real-time simulator contains a primary model of a flexible DC transmission system, including an equivalent model of the power module. The power module is an integrated distributed energy-consuming flexible DC power module, including a half-bridge power module or a full-bridge power module. The DC capacitor of the power module has an energy-consuming branch connected in parallel across its terminals. The energy-consuming branch includes a series-connected switching transistor and an energy-consuming resistor.

9. A simulation method for typical faults of integrated distributed energy-consuming modules, characterized in that, The simulation device for typical faults of integrated distributed energy-consuming modules as described in any one of claims 1 to 8 includes: Receive module-level fault simulation instructions from the operation interface, and parse the instructions to determine the fault simulation type; Based on the fault simulation type, a corresponding control action strategy is matched from a plurality of preset fault simulation strategies; the fault simulation strategy includes at least one of a communication link control strategy, a status data replacement strategy, an instruction interception and replacement strategy, and a fault flag writing strategy. According to the matched control action strategy, a corresponding control action signal is generated, and the control action signal is sent to at least one of the communication interface with the simulation model, the communication interface with the valve control, the communication interface with the adjacent module, and the power module control board netlist program module for execution, so as to generate the corresponding fault state in the simulation model of the real-time simulator.

10. A typical fault test method for integrated distributed energy-consuming modules, characterized in that, The simulation device for typical faults of integrated distributed energy-consuming modules as described in any one of claims 1 to 8 includes: Start the hardware-in-the-loop simulation test system and clear the preset fault simulation settings in the device; The initial voltage values ​​of each bridge arm power module of the tested converter valve are set through the real-time simulator, and the power-on / off thresholds and overvoltage breakdown thresholds of each power module are set through the operation interface. Various fault simulation commands are sequentially sent to the designated power modules, and the status feedback information of the corresponding power module in the background interface of the flexible DC valve control device is read after each sending. The status feedback information includes at least one of the following: power-on status, communication status, voltage measurement value, bypass status, energy-consuming branch status, and energy-consuming resistor temperature value. The status feedback information is compared with the expected status. If they match, the corresponding type of fault simulation function is determined to be correct.

Images