Method, medium, and apparatus for compatible variable frequency drives in flow battery management systems

Abstract

The application provides a method, medium and device compatible with a frequency converter in a flow battery management system. When adjusting a control mode of a target frequency converter, setting a control parameter or performing start-stop control, the standardized control mode instruction, parameter setting instruction or start-stop control instruction is converted into a control mode command, parameter setting command or start-stop control command recognizable by the target frequency converter and sent to the target frequency converter. When receiving state information or fault information from the target frequency converter, the state information or fault information is mapped into standardized state information or fault information. Thus, the flow battery management system can uniformly manage frequency converters from different manufacturers, avoid large-scale modification of the system architecture of the existing flow battery management system, reduce design cost and system risk, modularize the control compatibility functions of multiple frequency converters, and make the flow battery management system more flexible.

Description

Technical Field

[0001] This invention relates to the field of battery management technology, and in particular to a method, medium, and device for a flow battery management system compatible with frequency converters. Background Technology

[0002] Currently, the management and control information provided by flow battery inverters from different manufacturers is not the same. Using a flow battery management system to manage inverters from different manufacturers requires providing compatible management and control modules, which necessitates large-scale modifications to the existing technical architecture of the flow battery management system, increasing design costs and system risks.

[0003] Therefore, a technical solution is needed that can achieve compatible control of multiple frequency converters, support the control and management of frequency converters from different manufacturers, and meet the application needs of energy storage in multiple scenarios. Summary of the Invention

[0004] One objective of this application is to provide a method, medium, and device for a flow battery management system compatible with frequency converters, in order to solve the problems of needing to modify the system architecture, wasting software development resources, and increasing system risks when implementing management and control of frequency converters from different manufacturers in the existing flow battery management system.

[0005] To achieve the above objectives, some embodiments of this application provide a method for compatibility with frequency converters in a flow battery management system, the method comprising:

[0006] When the control mode of the target frequency converter is adjusted, the preset standardized control mode command is obtained, the standardized control mode command is converted into a control mode command that the target frequency converter can recognize and sent to the target frequency converter.

[0007] When the control parameters of the target frequency converter are set, the preset standardized parameter setting instructions are obtained, the standardized parameter setting instructions are converted into parameter setting commands that the target frequency converter can recognize, and then sent to the target frequency converter.

[0008] Upon receiving status information from the target inverter, the status information is mapped to preset standardized status information so that the flow battery management system can identify the inverter status based on the standardized status information.

[0009] When performing start-stop control on the target frequency converter, obtain the preset standardized start-stop control command, convert the standardized start-stop control command into a start-stop control command that the target frequency converter can recognize, and send it to the target frequency converter.

[0010] When a fault information is received from the target frequency converter, the fault information is mapped to a preset standardized fault information so that the flow battery management system can implement control and protection strategies based on the standardized fault information.

[0011] Furthermore, the system acquires preset standardized control mode commands and converts these commands into control mode commands recognizable by the target frequency converter, including:

[0012] Obtain preset remote control mode commands. Standardized control mode commands include remote control mode commands and local control mode commands.

[0013] The remote control mode commands are converted into communication command control mode commands. The target frequency converter can recognize the control mode commands, including button control mode commands, terminal control mode commands, and communication command control mode commands.

[0014] Furthermore, the system acquires preset standardized parameter setting instructions and converts these instructions into parameter setting commands that the target frequency converter can recognize, including:

[0015] Obtain preset standardized parameter setting instructions, which include target frequency setting instructions, upper limit operating frequency setting instructions, and lower limit operating frequency setting instructions;

[0016] Convert the target frequency setting command into parameter setting commands that the target frequency inverter can recognize, including:

[0017] Convert the target frequency setting command into a frequency command selection command and a communication setting value address command;

[0018] Convert the operating frequency upper limit setting command into parameter setting commands that the target frequency inverter can recognize, including:

[0019] Convert the operating frequency upper limit setting command into a frequency command selection command and an operating frequency upper limit command;

[0020] Convert the operating frequency lower limit setting command into parameter setting commands that the target frequency inverter can recognize, including:

[0021] Convert the lower limit setting command for the operating frequency into a frequency command selection command and an operating frequency lower limit command.

[0022] Furthermore, the status information of the target frequency converter includes:

[0023] Power-on disabled state, power-on ready state, power-on state, operation enabled state.

[0024] Furthermore, upon receiving status information from the target frequency converter, the status information is mapped to preset standardized status information, including:

[0025] When the received status information from the target frequency converter is in the state of power-on disabled, power-on ready, or power-on, the status information is mapped to the standby state in the preset standardized status information. The standardized status information includes standby state and running state.

[0026] When the received status information from the target frequency converter indicates that the operation is enabled, the status information is mapped to the operating status in the standardized status information.

[0027] Furthermore, the system acquires preset standardized start-stop control commands and converts these commands into start-stop control commands recognizable by the target frequency converter, including:

[0028] Obtain preset standardized start-stop control commands, which include start commands and stop commands;

[0029] When the standardized start-stop control command is a start command, the start-stop control command to be sent is determined according to the current state of the state machine corresponding to the target frequency converter and sent to the target frequency converter.

[0030] When the standardized start-stop control command is a stop command, the stop command is converted into a parking control command that the target inverter can recognize and sent to the target inverter.

[0031] Furthermore, the target inverter's fault information includes overheating faults, overcurrent faults, communication faults, motor faults, and no faults.

[0032] Furthermore, upon receiving fault information from the target frequency converter, the fault information is mapped to preset standardized fault information, including:

[0033] When receiving fault information from the target frequency converter, such as overheating fault, overcurrent fault, communication fault, or motor fault, the fault information is mapped to the fault information in the preset standardized fault information, which includes fault information and no fault information.

[0034] When a fault message is received from the target frequency converter indicating no fault, the fault message is mapped to the no-fault message in the standardized fault information.

[0035] Some embodiments of this application also provide a computer-readable medium having computer-readable instructions stored thereon, which can be executed by a processor to implement the aforementioned method for a frequency converter compatible with a flow battery management system.

[0036] Some embodiments of this application also provide an electronic device including a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein when the computer program instructions are executed by the processor, the electronic device performs the method of the aforementioned flow battery management system compatible with a frequency converter.

[0037] Compared with existing technologies, the solution provided in this application achieves the following: when adjusting the control mode, setting control parameters, or performing start-stop control on the target frequency converter, standardized control mode commands, parameter setting commands, or start-stop control commands are converted into control mode commands, parameter setting commands, or start-stop control commands that the target frequency converter can recognize and sent to the target frequency converter; when receiving status information or fault information from the target frequency converter, the status information or fault information is mapped to standardized status information or fault information. This enables the flow battery management system to uniformly manage frequency converters from different manufacturers, avoiding large-scale modifications to the existing system architecture of the flow battery management system, reducing design costs and system risks. At the same time, the control compatibility function for multiple frequency converters is modularized, making the flow battery management system more flexible. When it is necessary to support frequency converters from different manufacturers, the compatibility function module is loaded; when it is not necessary to support frequency converters from different manufacturers, the compatibility function module is unloaded, reducing the consumption of software operating resources. It can also meet the needs of multiple energy storage application scenarios, promote the standardization of flow battery management systems, and achieve the goals of economic applicability, resource sharing, technological advancement, and sustainable development. Attached Figure Description

[0038] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0039] Figure 1 A flowchart illustrating a method for using a compatible frequency converter in a flow battery management system, provided for some embodiments of this application.

[0040] Figure 2 This is a schematic diagram illustrating how adding a middleware system interface layer to a flow battery management system to achieve inverter compatibility in some embodiments of this application.

[0041] Figure 3 This is a schematic diagram illustrating the conversion of remote control mode commands into communication command control mode commands, provided for some embodiments of this application.

[0042] Figure 4 This is a schematic diagram illustrating the conversion of a target frequency setting command into a parameter setting command recognizable by the target frequency converter, provided for some embodiments of this application.

[0043] Figure 5This is a schematic diagram illustrating the conversion of an operating frequency upper limit setting command into a parameter setting command recognizable by the target frequency inverter, provided for some embodiments of this application.

[0044] Figure 6 This is a schematic diagram illustrating the conversion of a lower limit setting command for operating frequency into a parameter setting command recognizable by the target frequency converter, provided for some embodiments of this application.

[0045] Figure 7 This is a schematic diagram illustrating the mapping of the state information of a target frequency converter to standardized state information, provided for some embodiments of this application.

[0046] Figure 8 This is a schematic diagram illustrating the conversion of a start command into a start / stop control command recognizable by the target frequency converter, provided for some embodiments of this application.

[0047] Figure 9 This is a schematic diagram illustrating the conversion of a stop command into a start / stop control command recognizable by the target frequency converter, provided for some embodiments of this application.

[0048] Figure 10 This is a schematic diagram illustrating the mapping of fault information of a target frequency converter to standardized fault information, provided for some embodiments of this application. Detailed Implementation

[0049] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. These embodiments are based on the technical solution of the present invention and provide detailed implementation methods and specific operating procedures. However, the scope of protection of the present invention is not limited to the following embodiments.

[0050] Here, the method for compatible inverters in the flow battery management system of this application embodiment is suitable for scenarios where the flow battery management system controls and manages inverters from different manufacturers.

[0051] In this scenario, the flow battery management system needs to interact with inverters from different manufacturers to control and receive information from them. However, inverters from different manufacturers support different control modes, control parameters, and related commands. To achieve interaction with control or status information from multiple inverters, the usual approach is to add a corresponding information interaction interface for each inverter. However, this approach requires significant modifications to the flow battery management system architecture, additional interface development work, and the corresponding interfaces for multiple inverters need to run in the device, increasing the consumption of computer resources and introducing more system risks, which has an adverse impact on the flow battery management system.

[0052] The method for compatible inverters in a flow battery management system provided in this application embodiment realizes that when adjusting the control mode, setting control parameters, or performing start-stop control on the target inverter, standardized control mode commands, parameter setting commands, or start-stop control commands are converted into control mode commands, parameter setting commands, or start-stop control commands that the target inverter can recognize and sent to the target inverter. When receiving status information or fault information from the target inverter, the status information or fault information is mapped to standardized status information or fault information. This enables unified management of inverters from different manufacturers by the flow battery management system, avoiding large-scale modifications to the existing system architecture of the flow battery management system, reducing design costs and system risks. At the same time, the control compatibility function for multiple inverters is modularized, making the flow battery management system more flexible. When it is necessary to support inverters from different manufacturers, the compatibility function module is loaded; when it is not necessary to support inverters from different manufacturers, the compatibility function module is unloaded, reducing the consumption of software operating resources. It can also meet the needs of multiple energy storage application scenarios, promote the standardization of flow battery management systems, and achieve the goals of economic applicability, resource sharing, technological advancement, and sustainable development.

[0053] In some embodiments of this application, the flow chart of the method for a flow battery management system compatible with a frequency converter is described, with electronic devices serving as the execution subject of the method, such as... Figure 1 As shown, the method may include the following steps:

[0054] Step S101: When adjusting the control mode of the target frequency converter, obtain the preset standardized control mode command, convert the standardized control mode command into a control mode command that the target frequency converter can recognize, and send it to the target frequency converter.

[0055] It is understood that electronic devices may include, but are not limited to, laptops, desktop computers, tablets, mobile phones, wearable devices, head-mounted displays, servers, mobile email devices, portable game consoles, portable music players, e-reader devices, televisions in which one or more processors are embedded or coupled, or other electronic devices capable of accessing networks.

[0056] Here, the method can be implemented in the flow battery management system or in the middleware system interface layer of the flow battery management system. This application embodiment does not impose any specific limitations on this.

[0057] Figure 2 This application illustrates how adding a middleware system interface layer to the flow battery management system to achieve inverter compatibility in some embodiments, such as... Figure 2As shown, the middleware system interface layer can shield the differences between inverters from different manufacturers, reducing the need to modify the original core functional modules of the flow battery management system. These original core functional modules may include, but are not limited to, control mode management modules, parameter setting modules, state machine management modules, fault information modules, and start / stop control modules.

[0058] Because inverters from different manufacturers differ in the implementation of multiple functions, such as the adjustment of the positive and negative pump frequencies of the flow battery, the start and stop of the electrolyte circulation pump of the flow battery, and the control of the inverter, the flow battery management system needs to develop different adaptive control software to control and manage the inverter. This results in repetitive software development work and wasted resources. The significantly different processing logic in different inverters also increases the development difficulty and affects the technical architecture of the flow battery management system, reducing the maintainability of the system.

[0059] In some embodiments of this application, the flow battery management system can simultaneously manage and control multiple inverters from different manufacturers. The inverter currently interacting with the flow battery management system is designated as the target inverter. The flow battery management system achieves interaction between the two by sending control commands to the target inverter or receiving information from the target inverter.

[0060] In some embodiments of this application, when the flow battery management system needs to control the control mode of the target frequency converter, it first obtains a preset standardized control mode instruction, provides the standardized control mode instruction to the middleware system interface layer, and the middleware system interface layer converts the standardized control mode instruction into a control mode command that the target frequency converter can recognize, and then sends the control mode command to the target frequency converter to achieve control mode adaptation.

[0061] In some embodiments of this application, obtaining a preset standardized control mode instruction and converting the standardized control mode instruction into a control mode command recognizable by the target frequency converter may include the following steps:

[0062] (1) Obtain the preset remote control mode command;

[0063] Here, standardized control mode commands include remote control mode commands and local control mode commands. Remote control mode commands are used to adjust the control mode of the target inverter remotely, while local control mode commands are used to adjust the control mode of the target inverter locally. In some embodiments of this application, the flow battery management system uses the remote control mode commands from the standardized control mode commands to interact with inverters from different manufacturers.

[0064] (2) Convert remote control mode commands into communication command control mode commands.

[0065] Here, the control modes provided by frequency converters from different manufacturers are not quite the same, but can be generally divided into three categories: button control mode, terminal control mode, and communication command control mode. The corresponding control mode commands that the target frequency converter can recognize include button control mode commands, terminal control mode commands, and communication command control mode commands.

[0066] Figure 3 This illustration demonstrates how remote control mode commands are converted into communication command control mode commands in some embodiments of this application. In some embodiments of this application, the middleware system interface layer uses communication command control mode to interact with inverters from different manufacturers. After receiving a remote control mode command from the flow battery management system, the middleware system interface layer converts the remote control mode command into a communication command control mode command recognizable by the target inverter, and then sends the communication command control mode command to the target inverter. The target inverter executes the received communication command control mode command to complete the adjustment of the control mode.

[0067] Step S102: When setting the control parameters of the target frequency converter, obtain the preset standardized parameter setting instructions, convert the standardized parameter setting instructions into parameter setting commands that the target frequency converter can recognize, and send them to the target frequency converter.

[0068] In some embodiments of this application, when the flow battery management system needs to set the control parameters of the target frequency converter, it first obtains a preset standardized parameter setting instruction, provides the standardized parameter setting instruction to the middleware system interface layer, and the middleware system interface layer converts the standardized parameter setting instruction into a parameter setting command that the target frequency converter can recognize, and then sends the parameter setting command to the target frequency converter to achieve parameter setting adaptation.

[0069] In some embodiments of this application, obtaining a preset standardized parameter setting instruction and converting the standardized parameter setting instruction into a parameter setting command recognizable by the target frequency converter may include the following steps:

[0070] (1) Obtain the preset standardized parameter setting instructions;

[0071] Here, the target inverter needs to be set with correct parameters to ensure its safe and stable operation and achieve the goal of accurately controlling the electrolyte flow rate of the flow battery. Inverters from different manufacturers have a wide variety of parameters, which vary considerably. In some embodiments of this application, the flow battery management system uses frequency-related parameters to control the operation of the target inverter, standardizing these parameters into a target frequency value, an upper operating frequency limit, and a lower operating frequency limit. The target frequency value is the frequency at which the flow battery management system expects the target inverter to operate. This frequency value is calculated based on various states of the current flow battery system, such as temperature, flow rate, and voltage, to ensure optimal performance of the flow battery system. The upper operating frequency limit sets the upper limit of the frequency at which the target inverter can operate, preventing safety risks caused by excessively high operating frequencies. The lower operating frequency limit sets the lower limit of the frequency at which the target inverter can operate, preventing the flow battery system from operating at excessively low frequencies that could affect system performance.

[0072] Similarly, the parameter setting instructions of the flow battery management system are standardized in advance. The standardized parameter setting instructions include target frequency setting instructions, upper limit operating frequency setting instructions, and lower limit operating frequency setting instructions. The target frequency setting instructions are used to set the operating frequency of the target inverter to the target frequency. The upper limit operating frequency setting instructions are used to set the upper limit of the operating frequency of the target inverter. The lower limit operating frequency setting instructions are used to set the lower limit of the operating frequency of the target inverter.

[0073] (2) Convert the target frequency setting command into a parameter setting command that the target frequency converter can recognize;

[0074] In some embodiments of this application, the parameter setting commands that the target frequency converter can recognize may include, but are not limited to, frequency command selection commands, communication setting value address commands, upper limit commands for operating frequency, and lower limit commands for operating frequency.

[0075] Figure 4 The illustration shows how, in some embodiments of this application, a target frequency setting command is converted into a parameter setting command recognizable by the target inverter. After receiving the target frequency setting command, the middleware system interface layer converts the target frequency setting command into a frequency command selection command and a communication setting value address command recognizable by the target inverter. The frequency command selection command is used to specify the target frequency value of the target inverter according to the communication method, and the communication setting value address command is used to obtain the target frequency value from the address set by the communication method. After receiving these two commands, the target inverter first executes the frequency command selection command to change to the target frequency value set by the communication method, and then executes the communication setting value address command to obtain the set target frequency value from the corresponding address, thereby realizing the adjustment of the target frequency value.

[0076] (3) Convert the operating frequency upper limit setting command into a parameter setting command that the target frequency converter can recognize;

[0077] Figure 5 The illustration shows how, in some embodiments of this application, the operating frequency upper limit setting command is converted into a parameter setting command recognizable by the target frequency inverter. After receiving the operating frequency upper limit setting command, the middleware system interface layer converts the operating frequency upper limit setting command into a frequency command selection command and an operating frequency upper limit command recognizable by the target frequency inverter. After the target frequency inverter executes these two commands, the operating frequency upper limit value is adjusted.

[0078] (4) Convert the operating frequency lower limit setting command into a parameter setting command that the target frequency converter can recognize.

[0079] Figure 6 The illustration shows how, in some embodiments of this application, the lower limit setting command for the operating frequency is converted into a parameter setting command that the target frequency inverter can recognize. After receiving the lower limit setting command for the operating frequency, the middleware system interface layer converts the lower limit setting command for the operating frequency into a frequency command selection command and an operating frequency lower limit command that the target frequency inverter can recognize. After the target frequency inverter executes these two commands, it adjusts the lower limit value of the operating frequency.

[0080] Step S103: Upon receiving status information from the target inverter, the status information is mapped to preset standardized status information so that the flow battery management system can identify the inverter status based on the standardized status information.

[0081] In some embodiments of this application, when the middleware system interface layer receives status information from the target inverter, it maps the status information to preset standardized status information, and then provides the mapped standardized status information to the flow battery management system. The flow battery management system performs status identification of the target inverter based on the obtained standardized status information, thereby realizing the adaptation of status information.

[0082] Here, the status information of the target frequency converter may include, but is not limited to, power-on disabled state, power-on ready state, power-on state, and operation enabled state.

[0083] In some embodiments of this application, when the middleware system interface layer receives status information from the target frequency converter, it maps the status information to preset standardized status information, which may include the following steps:

[0084] (1) When the received status information from the target frequency converter is power-on disabled, power-on ready or power-on, the status information is mapped to the standby state in the preset standardized status information.

[0085] Here, the preset standardized status information includes standby status and running status. Standby status indicates that the target frequency converter is in standby mode, and running status indicates that the target frequency converter is in running mode.

[0086] (2) When the status information received from the target frequency converter is that the operation is enabled, the status information is mapped to the operation status in the standardized status information. Figure 7 This illustration shows how the state information of the target frequency converter is mapped to standardized state information in some embodiments of this application.

[0087] Step S104: When performing start-stop control on the target frequency converter, obtain the preset standardized start-stop control command, convert the standardized start-stop control command into a start-stop control command that the target frequency converter can recognize, and send it to the target frequency converter.

[0088] In some embodiments of this application, when the flow battery management system needs to perform start-stop control on the target frequency converter, it first obtains a preset standardized start-stop control command, provides the standardized start-stop control command to the middleware system interface layer, and the middleware system interface layer converts the standardized start-stop control command into a start-stop control command that the target frequency converter can recognize, and then sends the start-stop control command to the target frequency converter to achieve start-stop control adaptation.

[0089] In some embodiments of this application, obtaining a preset standardized start-stop control command and converting the standardized start-stop control command into a start-stop control command recognizable by the target frequency converter may include the following steps:

[0090] (1) Obtain preset standardized start / stop control commands;

[0091] Here, standardized start / stop control commands include start and stop commands. Since the start / stop procedures for inverters from different manufacturers vary, it's difficult to standardize them into a single start / stop procedure. Therefore, the start / stop control commands are standardized into start and stop commands. The start command is used to start the inverter, and the stop command is used to stop the inverter. By standardizing the start / stop control commands into start and stop commands, the operation process of the flow battery management system for the inverter can be simplified, thereby reducing software development workload and difficulty.

[0092] (2) When the standardized start-stop control command is a start command, determine the start-stop control command to be sent according to the current state of the state machine corresponding to the target inverter and send it to the target inverter.

[0093] Here, the state machine is used to describe the various states that the target frequency converter needs to go through during the startup process. For example, when a certain manufacturer's frequency converter is started, it needs to go through the power-on disabled state, the power-on ready state, the power-on state, and the running enabled state. After reaching the running enabled state, the frequency converter starts up. Figure 8 The illustration shows how, in some embodiments of this application, a start command is converted into a start / stop control command recognizable by the target frequency converter, such as... Figure 8 As shown, the middleware system interface layer maintains the state machine corresponding to the target inverter. Upon receiving a start command, it checks the current state of the state machine, determines the start / stop control commands to be sent based on the current state, and then sends them to the target inverter. For example, if the current state of the state machine is "power-on disabled," the middleware system interface layer determines that the start / stop control commands to be sent are: a stop control command, a power-on command, and a run enable command. These commands are then sent to the target inverter sequentially, and the target inverter executes them to pass through the corresponding states. In this way, the intermediate processing states can be shielded from the upper-layer application software, achieving the goal of unifying the differences between different inverters.

[0094] (3) When the standardized start-stop control command is a stop command, the stop command is converted into a parking control command that the target inverter can recognize and sent to the target inverter.

[0095] Figure 9 The illustration shows how, in some embodiments of this application, a stop command is converted into a start / stop control command recognizable by the target frequency converter, such as... Figure 9 As shown, when the middleware system interface layer receives a stop command, regardless of the current state of the state machine, it directly converts the stop command into a parking control command and sends it to the target inverter. The target inverter can complete the inverter's stop process by executing the parking control command, thereby simplifying the control process and achieving the goal of unified operation.

[0096] Step S105: When receiving fault information from the target frequency converter, the fault information is mapped to preset standardized fault information so that the flow battery management system can implement control and protection strategies based on the standardized fault information.

[0097] In some embodiments of this application, when the middleware system interface layer receives fault information from the target frequency converter, it maps the fault information to preset standardized fault information, and then provides the mapped standardized fault information to the flow battery management system. The flow battery management system implements the control and protection strategy of the target frequency converter according to the obtained standardized fault information, thereby realizing the adaptation of fault information.

[0098] Here, the fault information of the target frequency converter may include, but is not limited to, overheating fault, overcurrent fault, communication fault, motor fault, and no fault.

[0099] In addition, since the fault information of inverters from different manufacturers is different, the flow battery management system has difficulty unifying the fault information. Therefore, the fault information of inverters is standardized into fault information and no fault information through the middleware system interface layer to achieve unified operation.

[0100] In some embodiments of this application, when the middleware system interface layer receives fault information from the target frequency converter, it maps the fault information to preset standardized fault information, which may include the following steps:

[0101] (1) When the fault information received from the target frequency converter is an overheating fault, overcurrent fault, communication fault or motor fault, the fault information is mapped to the fault information in the preset standardized fault information.

[0102] Here, the preset standardized fault information includes fault information and fault-free information. Fault information is used to indicate that the target frequency converter currently has a fault, and fault-free information is used to indicate that the target frequency converter currently does not have a fault.

[0103] (2) When the fault information received from the target frequency converter is no fault, the fault information is mapped to the no fault information in the standardized fault information. Figure 10 This illustration shows how, in some embodiments of this application, fault information of a target frequency converter is mapped to standardized fault information.

[0104] It is understood that the above-described method of sequentially executing steps S101 to S105 is merely one implementation of the solution of this application and does not constitute a restriction on the execution order of steps S101 to S105. In specific implementation, steps S101 to S105 can be executed in any order as needed.

[0105] Some embodiments of this application also provide a computer-readable medium having computer-readable instructions stored thereon, which can be executed by a processor to implement the aforementioned method for a frequency converter compatible with a flow battery management system.

[0106] Some embodiments of this application also provide an electronic device including a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein when the computer program instructions are executed by the processor, the electronic device performs the method of the aforementioned flow battery management system compatible with a frequency converter.

[0107] In summary, the solution provided in this application can convert standardized control mode commands, parameter setting commands, or start-stop control commands into control mode commands, parameter setting commands, or start-stop control commands recognizable by the target frequency converter and send them to the target frequency converter when adjusting the control mode, setting control parameters, or performing start-stop control. Upon receiving status information or fault information from the target frequency converter, it maps the status information or fault information to standardized status information or fault information. This enables unified management of frequency converters from different manufacturers by the flow battery management system, avoiding large-scale modifications to the existing flow battery management system architecture, reducing design costs and system risks. Furthermore, it modularizes the control compatibility functions for multiple frequency converters, making the flow battery management system more flexible. Compatibility modules are loaded when support for different frequency converters is needed, and unloaded when support for different frequency converters is not required, reducing software resource consumption. It also meets the needs of various energy storage applications, promotes the standardization of flow battery management systems, and achieves the goals of economic applicability, resource sharing, advanced technology, and sustainable development.

[0108] It should be noted that this application can be implemented in software and / or a combination of software and hardware, for example, using an application-specific integrated circuit (ASIC), a general-purpose computer, or any other similar hardware device. In one embodiment, the software program of this application can be executed by a processor to implement the steps or functions described above. Similarly, the software program of this application (including related data structures) can be stored in a computer-readable recording medium, such as RAM memory, magnetic or optical drives, floppy disks, and similar devices. Furthermore, some steps or functions of this application can be implemented in hardware, for example, as circuitry that cooperates with a processor to perform the various steps or functions.

[0109] In a typical configuration of this application, both the terminal and the network device include one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0110] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0111] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include non-transitory computer-readable media, such as modulated data signals and carrier waves.

[0112] Furthermore, a portion of this application can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to this application through the operation of the computer. The program instructions invoking the methods of this application may be stored in a fixed or removable recording medium, and / or transmitted via data streams in broadcast or other signal carrying media, and / or stored in the working memory of a computer device operating according to the program instructions. Here, one embodiment of this application includes a device comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein, when the computer program instructions are executed by the processor, the device is triggered to run methods and / or technical solutions based on the foregoing embodiments of this application.

[0113] It will be apparent to those skilled in the art that this application is not limited to the details of the exemplary embodiments described above, and that this application can be implemented in other specific forms without departing from the spirit or essential characteristics of this application. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of this application is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be embraced within this application. No reference numerals in the claims should be construed as limiting the scope of the claims. Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices recited in the apparatus claims may also be implemented by a single unit or device in software or hardware. The terms "first," "second," etc., are used to indicate names and do not indicate any particular order.

Claims

1. A method for compatibility with frequency converters in a flow battery management system, characterized in that, The method includes: When adjusting the control mode of the target frequency converter, a preset standardized control mode instruction is obtained, and the standardized control mode instruction is converted into a control mode command recognizable by the target frequency converter and sent to the target frequency converter. Obtaining the preset standardized control mode instruction and converting it into a control mode command recognizable by the target frequency converter includes: obtaining a preset remote control mode instruction, wherein the standardized control mode instruction includes remote control mode instructions and local control mode instructions; and converting the remote control mode instruction into a communication command control mode command, wherein the control mode commands recognizable by the target frequency converter include button control mode commands, terminal control mode commands, and communication command control mode commands. When setting the control parameters of the target frequency converter, a preset standardized parameter setting instruction is obtained, the standardized parameter setting instruction is converted into a parameter setting command that the target frequency converter can recognize, and sent to the target frequency converter; Upon receiving status information from the target inverter, the status information is mapped to preset standardized status information so that the flow battery management system can identify the inverter status based on the standardized status information. The status information of the target inverter includes a power-on disabled state, a power-on ready state, a powered-on state, and a running enabled state. When receiving status information from the target inverter, mapping the status information to preset standardized status information includes: when the received status information from the target inverter is a power-on disabled state, a power-on ready state, or a powered-on state, mapping the status information to a standby state within the preset standardized status information, wherein the standardized status information includes a standby state and a running state; when the received status information from the target inverter is a running enabled state, mapping the status information to a running state within the standardized status information. When the target frequency converter is controlled to start and stop, a preset standardized start and stop control command is obtained, the standardized start and stop control command is converted into a start and stop control command that the target frequency converter can recognize and sent to the target frequency converter. Upon receiving fault information from the target frequency converter, the fault information is mapped to preset standardized fault information, so that the flow battery management system can implement control and protection strategies based on the standardized fault information.

2. The method according to claim 1, characterized in that, Obtaining preset standardized parameter setting instructions and converting the standardized parameter setting instructions into parameter setting commands recognizable by the target frequency converter includes: Obtain preset standardized parameter setting instructions, wherein the standardized parameter setting instructions include target frequency setting instructions, upper limit setting instructions for operating frequency, and lower limit setting instructions for operating frequency; Converting the target frequency setting command into parameter setting commands recognizable by the target frequency inverter includes: The target frequency setting instruction is converted into a frequency instruction selection command and a communication setting value address command; Converting the operating frequency upper limit setting command into a parameter setting command recognizable by the target frequency inverter includes: The operating frequency upper limit setting instruction is converted into the frequency instruction selection command and the operating frequency upper limit command; Converting the lower limit setting command for the operating frequency into a parameter setting command recognizable by the target frequency converter includes: The lower limit setting command for the operating frequency is converted into the frequency command selection command and the lower limit operating frequency command.

3. The method according to claim 1, characterized in that, Obtaining preset standardized start / stop control commands and converting these commands into start / stop control commands recognizable by the target frequency converter includes: Obtain preset standardized start-stop control commands, wherein the standardized start-stop control commands include start commands and stop commands; When the standardized start-stop control command is a start command, the start-stop control command to be sent is determined according to the current state of the state machine corresponding to the target frequency converter and sent to the target frequency converter. When the standardized start-stop control command is a stop command, the stop command is converted into a parking control command that the target frequency converter can recognize and sent to the target frequency converter.

4. The method according to claim 1, characterized in that, The fault information of the target frequency converter includes overheating fault, overcurrent fault, communication fault, motor fault, and no fault.

5. The method according to claim 4, characterized in that, Upon receiving fault information from the target frequency converter, the fault information is mapped to preset standardized fault information, including: When the fault information received from the target frequency converter is an overheating fault, overcurrent fault, communication fault, or motor fault, the fault information is mapped to the fault information in the preset standardized fault information, wherein the standardized fault information includes fault information and no fault information. When the fault information received from the target frequency converter is that there is no fault, the fault information is mapped to the fault-free information in the standardized fault information.

6. A computer-readable medium having stored thereon computer-readable instructions that can be executed by a processor to implement the method as described in any one of claims 1 to 5.

7. An electronic device comprising a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein, When the computer program instructions are executed by the processor, the electronic device performs the method as described in any one of claims 1 to 5.

Images