Dynamic management method and device for standard parameters of inverter, and electronic equipment

Abstract

The invention provides a dynamic management method and device for inverter standard parameters and electronic equipment, label table files belonging to different standards are generated in a cloud server, and each label table file comprises a plurality of inverter parameter labels and corresponding parameter values; pulling the tag table file to a monitoring device, and issuing the tag table file matched with a target standard to a corresponding inverter according to the target standard executed by the inverter through the monitoring device; in response to a parameter value modification request of a user, acquiring a parameter modification value corresponding to the inverter parameter tag, and updating the parameter modification value to the tag table file in the corresponding inverter through the monitoring equipment; and packaging the parameter modification value and a hash value corresponding to the inverter parameter tag through the monitoring equipment, and synchronizing the packaged data to the cloud server.

Description

Technical Field

[0001] The present disclosure relates to the field of photovoltaic technology, and in particular to a method, device, and electronic equipment for dynamically managing inverter standard parameters. Background Art

[0002] With the transformation of the global energy structure, photovoltaic power generation has been widely used as a clean and renewable energy source. As the core equipment in the photovoltaic power generation system, the photovoltaic inverter is responsible for converting the DC power output by the photovoltaic module into AC power for use in the power grid. In the application of photovoltaic inverters, different countries have different standard requirements for inverters, involving multiple parameters such as power regulation, operation, protection and off-grid, which can reach thousands of types after subdivision. The diversity and frequent revisions of these national standards make the research and development and maintenance of inverters extremely complicated.

[0003] The traditional method of configuring the parameters of photovoltaic inverters relies on fixed preset values, and users can only modify the parameters manually through local physical buttons or dedicated equipment. This method is not only time-consuming and labor-intensive, but also prone to misoperation and difficult to meet diverse configuration needs. In addition, the parameter adjustment of most inverters needs to be completed on-site and cannot be managed through remote operation. This method is difficult to achieve rapid configuration and dynamic adjustment in the large-scale application scenarios of photovoltaic power stations, which increases the operation and maintenance costs. At the same time, parameter modification requests are usually based on a point-to-point communication mode of complete files or specific registers, with large data transmission redundancy and poor real-time performance. In addition, the system lacks an effective verification mechanism for data synchronization after parameter modification, which may cause data errors or parameter loss. Summary of the invention

[0004] The embodiments of the present disclosure at least provide a method, device, and electronic device for dynamically managing inverter standard parameters, which can realize rapid configuration and efficient data synchronization of photovoltaic inverter standard parameters while having both reliability and safety, thereby meeting the diverse application needs of photovoltaic power generation systems around the world.

[0005] The present disclosure provides a method for dynamically managing inverter standard parameters, including:

[0006] Generate label table files belonging to different standards in the cloud server, each of which contains multiple inverter parameter labels and corresponding parameter values;

[0007] Pulling the label table file to a monitoring device, and sending the label table file matching the target standard to the corresponding inverter through the monitoring device according to the target standard executed by the inverter;

[0008] In response to a parameter value modification request from a user, obtaining a parameter modification value corresponding to the inverter parameter tag, and updating the parameter modification value to the tag table file corresponding to the inverter through the monitoring device;

[0009] The parameter modification value and the hash value corresponding to the inverter parameter tag are packaged by the monitoring device, and the packaged data is synchronized to the cloud server.

[0010] In an optional implementation manner, sending the label table file matching the target standard to the corresponding inverter according to the target standard executed by the inverter specifically includes:

[0011] Comparing the versions of the label table file received by the monitoring device with the existing label table file in the inverter to determine whether the versions of the label table file received by the monitoring device and the existing label table file in the inverter are consistent;

[0012] If the version corresponding to the label table file received by the monitoring device is lower than the version corresponding to the existing label table file in the inverter, then the existing label table file is pulled from the inverter to the monitoring device;

[0013] If the version corresponding to the label table file received by the monitoring device is higher than the version corresponding to the existing label table file in the inverter, the label table file received by the monitoring device is updated to the inverter.

[0014] In an optional implementation manner, the method further includes:

[0015] Performing hash coding on the tag name corresponding to the inverter parameter tag, and converting the tag name into the corresponding hash value;

[0016] During the communication transmission process of the label table file, the hash value and the parameter value are parsed into a communication linked list, so that the label table file is loaded into a random access memory by transmitting the hash value and the parameter value.

[0017] In an optional implementation manner, the inverter parameter tag includes at least a grid-feed power value parameter, an island protection time parameter, and a reactive power parameter;

[0018] The parameter value includes at least a default value, a minimum value, and a maximum value of the inverter parameter corresponding to the inverter parameter tag.

[0019] In an optional implementation manner, in response to a parameter value modification request of a user, obtaining a parameter modification value corresponding to the inverter parameter tag specifically includes:

[0020] In response to the parameter value modification request, obtaining a local label table file uploaded by the user through the local host computer;

[0021] Parsing the hash value corresponding to the inverter parameter tag in the local tag table file;

[0022] Comparing the local label table file with the label table file in the inverter, and locating the inverter parameter label to be modified according to the hash value corresponding to the local label table file and the hash value corresponding to the label table file in the inverter;

[0023] The parameter value corresponding to the inverter parameter tag to be modified is determined in the local tag table file as the parameter modification value.

[0024] In an optional implementation manner, sending the label table file matching the target standard to the corresponding inverter according to the target standard executed by the inverter specifically includes:

[0025] Determine whether the cloud server stores the tag table file with a higher version than that in the monitoring device and the inverter;

[0026] If it exists, the latest version of the label table file in the cloud server is pulled to the monitoring device, and updated to the inverter through the monitoring device.

[0027] The embodiment of the present disclosure also provides a device for dynamically managing inverter standard parameters, including:

[0028] A label table generation module, used to generate label table files belonging to different standards in the cloud server, each of which contains multiple inverter parameter labels and corresponding parameter values;

[0029] A label table sending module, used to pull the label table file to the monitoring device, and send the label table file matching the target standard to the corresponding inverter through the monitoring device according to the target standard executed by the inverter;

[0030] A parameter modification module, configured to obtain a parameter modification value corresponding to the inverter parameter tag in response to a user's parameter value modification request, and update the parameter modification value to the tag table file corresponding to the inverter through the monitoring device;

[0031] The data update synchronization module is used to package the parameter modification value and the hash value corresponding to the inverter parameter tag through the monitoring device, and synchronize the packaged data to the cloud server.

[0032] In an optional implementation manner, the parameter modification module is specifically used to:

[0033] Comparing the versions of the label table file received by the monitoring device with the existing label table file in the inverter to determine whether the versions of the label table file received by the monitoring device and the existing label table file in the inverter are consistent;

[0034] If the version corresponding to the label table file received by the monitoring device is lower than the version corresponding to the existing label table file in the inverter, then the existing label table file is pulled from the inverter to the monitoring device;

[0035] If the version corresponding to the label table file received by the monitoring device is higher than the version corresponding to the existing label table file in the inverter, the label table file received by the monitoring device is updated to the inverter.

[0036] An embodiment of the present disclosure also provides an electronic device, including: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the above-mentioned method for dynamic management of standard parameters of the inverter is executed, or steps in any possible implementation of the above-mentioned method for dynamic management of standard parameters of the inverter are executed.

[0037] The embodiments of the present disclosure also provide a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the computer program executes the above-mentioned method for dynamically managing inverter standard parameters, or the steps in any possible implementation of the above-mentioned method for dynamically managing inverter standard parameters.

[0038] The embodiments of the present disclosure also provide a computer program product, including a computer program / instruction, which, when executed by a processor, implements the above-mentioned method for dynamically managing standard parameters of an inverter, or the steps in any possible implementation of the above-mentioned method for dynamically managing standard parameters of an inverter.

[0039] The embodiments of the present disclosure provide a method, device, and electronic device for dynamically managing inverter standard parameters. Label table files belonging to different standards are generated in a cloud server, each of the label table files containing multiple inverter parameter labels and corresponding parameter values; the label table files are pulled to a monitoring device, and the label table files matching the target standard are issued to the corresponding inverter by the monitoring device according to the target standard executed by the inverter; in response to a user's parameter value modification request, a parameter modification value corresponding to the inverter parameter label is obtained, and the parameter modification value is updated to the label table file in the corresponding inverter by the monitoring device; the parameter modification value and the hash value corresponding to the inverter parameter label are packaged by the monitoring device, and the packaged data is synchronized to the cloud server.

[0040] In order to make the above-mentioned objectives, features and advantages of the present disclosure more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following is a brief introduction to the drawings required for use in the embodiments. The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and are used together with the specification to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can also be obtained based on these drawings without creative work.

[0042] Figure 1 A flow chart of a method for dynamically managing inverter standard parameters provided by an embodiment of the present disclosure is shown;

[0043] Figure 2 A flow chart showing another method for dynamically managing inverter standard parameters provided by an embodiment of the present disclosure is shown;

[0044] Figure 3 A schematic diagram showing a device for dynamically managing inverter standard parameters provided by an embodiment of the present disclosure is shown;

[0045] Figure 4 A schematic diagram of an electronic device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The components of the embodiments of the present disclosure generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the drawings is not intended to limit the scope of the present disclosure for protection, but merely represents the selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present disclosure.

[0047] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0048] The term "and / or" herein only describes an association relationship, indicating that three relationships may exist. For example, A and / or B may represent the following three situations: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "at least one" herein represents any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C may represent including any one or more elements selected from the set consisting of A, B, and C.

[0049] Research has found that the traditional photovoltaic inverter parameter configuration method relies on fixed preset values, and users can only modify parameters manually through local physical buttons or dedicated equipment. This method is not only time-consuming and labor-intensive, but also prone to misoperation and difficult to meet diverse configuration needs. In addition, the parameter adjustment of most inverters needs to be completed on-site and cannot be managed through remote operation. This method is difficult to achieve rapid configuration and dynamic adjustment in large-scale application scenarios of photovoltaic power stations, which increases operation and maintenance costs. At the same time, parameter modification requests are usually based on a point-to-point communication mode of complete files or specific registers, with large data transmission redundancy and poor real-time performance. In addition, the system lacks an effective verification mechanism for data synchronization after parameter modification, which may cause data errors or parameter loss.

[0050] Based on the above research, the present disclosure provides a method, device, and electronic device for dynamically managing inverter standard parameters, generating label table files belonging to different standards in a cloud server, each of the label table files containing multiple inverter parameter labels and corresponding parameter values; pulling the label file to a monitoring device, and issuing the label table file matching the target standard to the corresponding inverter through the monitoring device according to the target standard executed by the inverter; in response to a user's parameter value modification request, obtaining the parameter modification value corresponding to the inverter parameter label, and updating the parameter modification value to the label table file in the corresponding inverter through the monitoring device; and packaging the parameter modification value and the hash value corresponding to the inverter parameter label through the monitoring device, and synchronizing the packaged data to the cloud server.

[0051] To facilitate understanding of this embodiment, a method for dynamically managing inverter standard parameters disclosed in the embodiment of the present disclosure is first introduced in detail. The execution subject of the method for dynamically managing inverter standard parameters provided in the embodiment of the present disclosure is generally a computer device with certain computing capabilities, and the computer device includes, for example: a terminal device or a server or other processing device, and the terminal device can be a user equipment (UE), a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc. In some possible implementations, the method for dynamically managing inverter standard parameters can be implemented by a processor calling a computer-readable instruction stored in a memory.

[0052] See also Figure 1 FIG. 1 is a flowchart of a method for dynamically managing inverter standard parameters provided by an embodiment of the present disclosure, the method comprising steps S101 to S104, wherein:

[0053] S101. Generate label table files belonging to different standards in a cloud server, each of which contains a plurality of inverter parameter labels and corresponding parameter values.

[0054] In the specific implementation, the label table file is a structured data file used to store standardized parameter information of the inverter. Each file is classified according to different technical standards or industry specifications (such as grid-connected standards, island protection standards, etc.). Its main function is to standardize the management of inverter parameter configurations to facilitate the inverter to perform target tasks in different scenarios.

[0055] Here, the content of the label table file mainly includes multiple inverter parameter labels and corresponding parameter values. The inverter parameter labels represent different parameter items of the inverter. Each parameter label has an independent name (such as grid feed power value, island protection time, reactive power, etc.). These parameter labels are closely related to the functions of the inverter.

[0056] Each parameter tag has a corresponding parameter value, which includes the following types: the default value is the initial value at the factory; the minimum value and maximum value are used to define the acceptable valid range of the parameter to avoid exceeding the safety or performance limit.

[0057] Specifically, when generating a tag table file in the cloud server, define the file structure according to the target standard (such as IEEE standard, national grid specification, etc.), create a tag table file template to list the parameter tags that need to be included, and each tag can also be attached with a description (such as unit, data type, etc.). According to technical standards and industry specifications, assign initial parameter values ​​to each parameter tag, including default values, minimum values, and maximum values, and then save the generated tag table file to the database in the cloud server to ensure that it has a unique version number at the file level to achieve version control of the tag table file for subsequent updates, comparisons, and management.

[0058] It should be noted that the cloud server needs to support the generation of different standard label table files and allow multiple label table files to be generated at the same time to meet the standard requirements of different regions, countries or users. When new technical standards emerge, the cloud server can quickly generate new label table files.

[0059] Optionally, the tag table file can use a common file format such as JSON, XML, or CSV to facilitate parsing and communication. The cloud server uses a parameter database to manage the content of each tag table file.

[0060] In this way, the standardization of inverter parameter configuration can be improved, human operation errors can be reduced, and batch generation of tag table files can be supported to improve configuration efficiency. At the same time, parameter files can be quickly adjusted according to needs to improve flexibility.

[0061] S102: Pull the label table file to a monitoring device, and send the label table file matching the target standard to a corresponding inverter through the monitoring device according to the target standard executed by the inverter.

[0062] In the specific implementation, the cloud server stores tag table files belonging to different technical standards, and the monitoring device will pull the required files when the device is initialized, the user configuration is updated, and the version is updated. When a new inverter is connected to the system, the monitoring device needs to pull the tag table file that matches the target standard of the device from the cloud; when the user chooses to change the target standard of the inverter operation, the monitoring device triggers the pull operation; if the tag table file in the cloud server is updated to a higher version, the monitoring device needs to pull the latest file.

[0063] Here, the monitoring device establishes a connection with the cloud server through a wired or wireless communication network (such as Ethernet, Wi-Fi or 4G / 5G), and uses security protocols (such as HTTPS, MQTT) in the process to ensure the integrity and security of communication data.

[0064] Furthermore, the monitoring device sends a request to the cloud server, indicating the target standard or device information of the required tag table file. The cloud server queries the database and finds the corresponding tag table file according to the request parameters. The cloud server packages the matching tag table file and transmits it to the monitoring device via the network. After the file transfer is completed, the monitoring device verifies the integrity of the file (such as checking the MD5 hash value).

[0065] Here, the monitoring device will match the required label table file according to the target standard currently executed by the inverter. The monitoring device obtains the target standard identifier of its operation from the inverter (such as the national grid connection standard, the EU grid connection standard, etc.). The target standard identifier can be determined through the inverter's device information query or user settings.

[0066] The monitoring device searches for a file that is consistent with the inverter's target standard from the pulled tag table file. If there are multiple matching files, the latest version of the tag table file is selected first. After the inverter receives the tag table file, it parses and stores it in the internal memory (such as EEPROM or Flash), and updates the inverter's operating configuration according to the parameter values ​​in the file.

[0067] Optionally, in the process of pulling and issuing tag table files, data storage, transmission and update are involved, and the following security and management measures need to be taken: encryption technology (such as AES) is used during the transmission of tag table files to prevent data tampering or theft; each tag table file is accompanied by a version number, and the monitoring device will perform a strict version comparison before issuing the file; if the file transmission is interrupted or an error occurs, the monitoring device will automatically try to retransmit or roll back to the previous version to ensure the stability of the inverter operation. The monitoring device records the operation log of each tag table file pulling and issuing, including time, version, target inverter and other information, for subsequent tracing.

[0068] Preferably, the monitoring device can adopt a collection stick.

[0069] For example, suppose an inverter switches from the original "IEEE grid-connected standard" to the "EU grid-connected standard", and the user modifies the inverter target standard to the "EU grid-connected standard" on the monitoring device; the monitoring device sends a request to the cloud to pull the label table file corresponding to the "EU grid-connected standard"; the cloud returns the latest version of the file, and the monitoring device downloads it and compares it with the existing file version of the inverter; if the file version is found to be updated, the monitoring device sends the file to the inverter; after receiving the file, the inverter updates the internal configuration and completes the switch.

[0070] As a possible implementation, see Figure 2 As shown, it is a flowchart of another method for dynamic management of inverter standard parameters provided by an embodiment of the present disclosure, the method includes steps S1021 to S1023, wherein:

[0071] S1021. Compare the versions of the label table file received by the monitoring device with the existing label table file in the inverter to determine whether the versions of the label table file received by the monitoring device and the existing label table file in the inverter are consistent.

[0072] S1022: If the version corresponding to the label table file received by the monitoring device is lower than the version corresponding to the existing label table file in the inverter, pull the existing label table file from the inverter to the monitoring device.

[0073] S1023: If the version corresponding to the label table file received by the monitoring device is higher than the version corresponding to the existing label table file in the inverter, update the label table file received by the monitoring device to the inverter.

[0074] In a specific implementation, the monitoring device receives a tag table file pulled from a cloud server, which contains file version number information (such as v1.0, v2.0, etc.). The version number is usually stored in the metadata of the tag table file, such as the file header area. The monitoring device interacts with the inverter through a communication protocol (such as Modbus or TCP / IP) to read the tag table file version number stored inside the inverter. The version number in the inverter may be stored in a storage medium such as EEPROM or Flash.

[0075] Here, if the version number of the label table file received by the monitoring device is the same as the existing version number of the label table file in the inverter, the versions are determined to be consistent and no further operation is required. If the version of the label table file received by the monitoring device is lower than the existing version of the label table file in the inverter (for example: monitoring device version v1.0 < inverter version v2.0), the monitoring device sends an instruction to the inverter, requiring the inverter to return its currently stored label table file. The inverter transmits the existing label table file to the monitoring device. After receiving the complete file, the monitoring device replaces the old version of the label table file.

[0076] Furthermore, if the tag table file version received by the monitoring device is higher than the existing tag table file version in the inverter (for example: monitoring device version v3.0> inverter version v2.0), the monitoring device sends an update command to the inverter, indicating that it is ready to receive a new tag table file, and the monitoring device transmits the new tag table file to the inverter through the communication protocol. After the inverter receives the complete tag table file, it parses the file content and stores it in the internal memory, replacing the old version of the tag table file.

[0077] Here, whether pulling the inverter file or updating the inverter file, the transmission process of the tag table file uses encryption technology (such as SSL / TLS) to prevent data leakage or tampering.

[0078] Optionally, determine whether the cloud server stores a tag table file with a higher version than that in the monitoring device and the inverter; if so, pull the latest version of the tag table file in the cloud server to the monitoring device, and update it to the inverter through the monitoring device. That is, if the cloud server has the latest version of the tag table file, the monitoring device can pull the latest version of the tag table file from the cloud server to update the existing tag table files in itself and the inverter in sequence.

[0079] For example, assume that the label table file version stored in a certain inverter in the system is v2.0, and the file version received by the monitoring device from the cloud server is v3.0. The monitoring device reads the label table file version from the inverter and finds that it is v2.0. After comparing the versions, the monitoring device finds that the local file version v3.0 is higher and decides to update the inverter file. The monitoring device transmits the v3.0 file in segments to the inverter. After receiving it, the inverter replaces the old file. The inverter completes the update and sends a confirmation message, and the monitoring device records the update operation.

[0080] S103. In response to a parameter value modification request from a user, obtain a parameter modification value corresponding to the inverter parameter tag, and update the parameter modification value to the tag table file corresponding to the inverter through the monitoring device.

[0081] In practice, the dynamic modification of inverter parameters is to meet the configuration requirements in different operating scenarios. For example, the user wants to adjust the output power, maximum current limit or operating mode of the inverter. In order to ensure the effectiveness and accuracy of the modification operation, it is necessary to coordinate the user request and the inverter response through the monitoring device.

[0082] Here, the parameter tag (such as MPPT_Voltage) and the corresponding parameter modification value (such as 420V) are parsed from the user request. Before updating the parameter modification value to the inverter, the monitoring device needs to verify the legitimacy of the value to ensure that the input conforms to the expected data format, that the value is within a reasonable range, and that the unit is correct.

[0083] Specifically, obtain the parameter modification value corresponding to the inverter parameter tag through the following steps 1 to 4:

[0084] Step 1: In response to the parameter value modification request, obtain a local label table file uploaded by the user through a local host computer.

[0085] Step 2: Parse the hash value corresponding to the inverter parameter label in the local label table file.

[0086] Step 3: Compare the local label table file with the label table file in the inverter, and locate the inverter parameter label to be modified according to the hash value corresponding to the local label table file and the hash value corresponding to the label table file in the inverter.

[0087] Step 4: Determine in the local label table file the parameter value corresponding to the inverter parameter label to be modified as the parameter modification value.

[0088] In the specific implementation, R&D personnel can manually import the local tag table of the inverter or monitoring equipment through the computer host software or mobile phone app, and automatically locate and modify the parameter values ​​in the inverter. The user uploads the tag table file (such as JSON, XML or other standard format files) through the local host interface. The tag table file content includes the inverter parameter tag, parameter value and corresponding hash value.

[0089] Here, the parameter information in the tag table file is read one by one to extract the parameter tag, parameter value and hash value. The parameter tag is used to identify a specific parameter, the parameter value is used to indicate the target value of the parameter, and the hash value is a unique state generated by the tag name.

[0090] Among them, during the data update process, the inverter compares the newly uploaded hash value of the local uploaded file with the existing hash values ​​in the communication link table one by one. If the hash value corresponding to a tag is the same, it means that the parameters of the tag corresponding to the hash value need to be updated.

[0091] For example, when the inverter receives the combination of hash value and parameter value sent when updating data, it will compare the hash value in the communication link list established by the tag file one by one; after comparison, it is found that the hash value is consistent with the hash value of the tag OutputVoltage; this means that the tag OutputVoltage needs to be modified to the value of 380V, and then the inverter completes the parameter update.

[0092] As a possible implementation method, hash encoding is performed on the tag name corresponding to the inverter parameter tag, and the tag name is converted into the corresponding hash value; during the communication transmission process of the tag table file, the hash value and the parameter value are parsed into a communication linked list, so that the tag table file is loaded into a random access memory by transmitting the hash value and the parameter value.

[0093] In the specific implementation, the master and slave machines import the national tag table file stored in the cloud, calculate the tag hash value in advance when importing, and form a communication link table by parsing the tag, hash value and tag information to achieve unified management of standard parameters, simplify the code writing process, introduce tag names in the communication protocol to identify the transmitted data variables, and simplify the development process. R&D and operation and maintenance personnel can perform relevant coding and monitoring through tag names.

[0094] Here, the tag table file of the inverter is used to store and transmit device parameters and their values. However, since the tag name in the file is long, direct transmission occupies bandwidth and reduces transmission efficiency. Hash coding is used to convert the tag name into a short hash value, and the hash value and parameter value are organized into a compact communication linked list form to reduce the amount of transmitted data. The communication linked list is used to efficiently transmit the tag table file between the cloud server, monitoring equipment, and inverter.

[0095] Among them, the tag name is hashed (such as CRC32) during communication, and the hash value calculated by the parsing module can be directly used to convert the tag name into a hash value of fixed length to reduce the communication byte occupation and improve transmission efficiency. At the same time, the hash algorithm has good uniqueness, which can effectively avoid conflicts and ensure accurate data transmission. In addition, the algorithm has low computational complexity and does not occupy too much CPU resources, thereby maintaining efficient operation of the system.

[0096] Optionally, combining the encryption algorithm in the hash coding process can further improve communication security and prevent potential attacks, such as Modbus continuous address attacks. Even if the national parameter tag table is exposed to the outside world, the outside world cannot know the specific hash algorithm and cannot attack the photovoltaic inverter.

[0097] S104. Packaging the parameter modification value and the hash value corresponding to the inverter parameter tag through the monitoring device, and synchronizing the packaged data to the cloud server.

[0098] In the specific implementation, the monitoring device automatically packages the updated parameter values, integrates and packages the parameter values ​​and hash values ​​corresponding to the labels, and uploads the packaged data to the cloud server to realize the synchronous recording of the label table and parameters. After receiving the data, the cloud server can further analyze, store and distribute the data to ensure the data consistency of the entire system.

[0099] Here, after the monitoring device pulls the tag table and parses it into a communication link table, it needs to automatically package the hash value of the tag to ensure that as much data as possible can be read each time, and the relevant measurement points are updated and the data is reported to the cloud server, which further simplifies the code processing process. That is, after the inverter and the monitoring device update the tag table, there is no need to change the code or firmware at all.

[0100] A method for dynamically managing inverter standard parameters provided by an embodiment of the present disclosure generates label table files belonging to different standards in a cloud server, each of the label table files containing multiple inverter parameter labels and corresponding parameter values; the label files are pulled to a monitoring device, and the label table file matching the target standard is issued to the corresponding inverter by the monitoring device according to the target standard executed by the inverter; in response to a user's parameter value modification request, a parameter modification value corresponding to the inverter parameter label is obtained, and the parameter modification value is updated to the label table file in the corresponding inverter through the monitoring device; the parameter modification value and the hash value corresponding to the inverter parameter label are packaged by the monitoring device, and the packaged data is synchronized to the cloud server.

[0101] Those skilled in the art will appreciate that, in the above method of specific implementation, the order in which the steps are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of the steps should be determined by their functions and possible internal logic.

[0102] Based on the same inventive concept, the embodiment of the present disclosure also provides a dynamic management device for inverter standard parameters corresponding to the dynamic management method for inverter standard parameters. Since the principle of solving the problem by the device in the embodiment of the present disclosure is similar to the dynamic management method for inverter standard parameters in the embodiment of the present disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0103] See also Figure 3 , Figure 3 A schematic diagram of a dynamic management device for inverter standard parameters provided by an embodiment of the present disclosure. Figure 3 As shown in FIG. , the dynamic management device 300 of the inverter standard parameters provided by the embodiment of the present disclosure includes:

[0104] The label table generating module 310 is used to generate label table files belonging to different standards in the cloud server, each of which contains a plurality of inverter parameter labels and corresponding parameter values.

[0105] The label table sending module 320 is used to pull the label file to the monitoring device, and send the label table file matching the target standard to the corresponding inverter through the monitoring device according to the target standard executed by the inverter.

[0106] The parameter modification module 330 is used to respond to the user's parameter value modification request, obtain the parameter modification value corresponding to the inverter parameter tag, and update the parameter modification value to the tag table file corresponding to the inverter through the monitoring device.

[0107] The data update synchronization module 340 is used to package the parameter modification value and the hash value corresponding to the inverter parameter tag through the monitoring device, and synchronize the packaged data to the cloud server.

[0108] For descriptions of the processing flow of each module in the device and the interaction flow between each module, reference may be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.

[0109] An embodiment of the present disclosure provides a dynamic management device for inverter standard parameters, which generates label table files belonging to different standards in a cloud server, each of which contains multiple inverter parameter labels and corresponding parameter values; pulls the label file to a monitoring device, and sends the label table file matching the target standard to the corresponding inverter through the monitoring device according to the target standard executed by the inverter; in response to a user's parameter value modification request, obtains a parameter modification value corresponding to the inverter parameter label, and updates the parameter modification value to the label table file in the corresponding inverter through the monitoring device; and packages the parameter modification value and the hash value corresponding to the inverter parameter label through the monitoring device, and synchronizes the packaged data to the cloud server.

[0110] Corresponds to Figure 1 The present disclosure also provides an electronic device 400, such as Figure 4 FIG. 4 is a schematic diagram of the structure of an electronic device 400 provided in an embodiment of the present disclosure, including:

[0111] Processor 41, memory 42, and bus 43; memory 42 is used to store execution instructions, including memory 421 and external memory 422; memory 421 here is also called internal memory, which is used to temporarily store operation data in processor 41 and data exchanged with external memory 422 such as hard disk. Processor 41 exchanges data with external memory 422 through memory 421. When the electronic device 400 is running, the processor 41 communicates with the memory 42 through bus 43, so that the processor 41 executes Figure 1 and Figure 2 The steps of the dynamic management method of inverter standard parameters in.

[0112] The embodiment of the present disclosure also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method for dynamically managing inverter standard parameters described in the above method embodiment are executed. The storage medium can be a volatile or non-volatile computer-readable storage medium.

[0113] The embodiments of the present disclosure also provide a computer program product, which includes computer instructions. When the computer instructions are executed by a processor, the steps of the dynamic management method of inverter standard parameters described in the above method embodiment can be executed. For details, please refer to the above method embodiment, which will not be repeated here.

[0114] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is implemented as a computer storage medium. In another optional embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).

[0115] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In the several embodiments provided in the present disclosure, it should be understood that the disclosed device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the device or unit can be electrical, mechanical or other forms.

[0116] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0117] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0118] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0119] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed in the present disclosure, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A method for dynamic management of inverter standard parameters, characterized in that: include: Generate label table files belonging to different standards in the cloud server, each of which contains multiple inverter parameter labels and corresponding parameter values; Pulling the label table file to a monitoring device, and sending the label table file matching the target standard to the corresponding inverter through the monitoring device according to the target standard executed by the inverter; In response to a parameter value modification request from a user, obtaining a parameter modification value corresponding to the inverter parameter tag, and updating the parameter modification value to the tag table file corresponding to the inverter through the monitoring device; The parameter modification value and the hash value corresponding to the inverter parameter tag are packaged by the monitoring device, and the packaged data is synchronized to the cloud server.

2. The method according to claim 1, characterized in that Sending the label table file matching the target standard to the corresponding inverter according to the target standard executed by the inverter specifically includes: Comparing the versions of the label table file received by the monitoring device with the existing label table file in the inverter to determine whether the versions of the label table file received by the monitoring device and the existing label table file in the inverter are consistent; If the version corresponding to the label table file received by the monitoring device is lower than the version corresponding to the existing label table file in the inverter, then the existing label table file is pulled from the inverter to the monitoring device; If the version corresponding to the label table file received by the monitoring device is higher than the version corresponding to the existing label table file in the inverter, the label table file received by the monitoring device is updated to the inverter.

3. The method according to claim 1, characterized in that The method further comprises: Performing hash coding on the tag name corresponding to the inverter parameter tag, and converting the tag name into the corresponding hash value; During the communication transmission process of the label table file, the hash value and the parameter value are parsed into a communication linked list, so that the label table file is loaded into a random access memory by transmitting the hash value and the parameter value.

4. The method according to claim 1, characterized in that: The inverter parameter tag at least includes a grid-feed power value parameter, an island protection time parameter, and a reactive power parameter; The parameter value includes at least a default value, a minimum value, and a maximum value of the inverter parameter corresponding to the inverter parameter tag.

5. The method according to claim 1, characterized in that In response to a parameter value modification request from a user, obtaining a parameter modification value corresponding to the inverter parameter tag specifically includes: In response to the parameter value modification request, obtaining a local label table file uploaded by the user through the local host computer; Parsing the hash value corresponding to the inverter parameter tag in the local tag table file; Comparing the local label table file with the label table file in the inverter, and locating the inverter parameter label to be modified according to the hash value corresponding to the local label table file and the hash value corresponding to the label table file in the inverter; The parameter value corresponding to the inverter parameter tag to be modified is determined in the local tag table file as the parameter modification value.

6. The method according to claim 2, characterized in that Sending the label table file matching the target standard to the corresponding inverter according to the target standard executed by the inverter specifically includes: Determine whether the cloud server stores the tag table file with a higher version than that in the monitoring device and the inverter; If it exists, the latest version of the label table file in the cloud server is pulled to the monitoring device, and updated to the inverter through the monitoring device.

7. A dynamic management device for inverter standard parameters, characterized in that: include: A label table generation module, used to generate label table files belonging to different standards in the cloud server, each of which contains multiple inverter parameter labels and corresponding parameter values; A label table sending module, used to pull the label table file to the monitoring device, and send the label table file matching the target standard to the corresponding inverter through the monitoring device according to the target standard executed by the inverter; A parameter modification module, configured to obtain a parameter modification value corresponding to the inverter parameter tag in response to a user's parameter value modification request, and update the parameter modification value to the tag table file corresponding to the inverter through the monitoring device; The data update synchronization module is used to package the parameter modification value and the hash value corresponding to the inverter parameter tag through the monitoring device, and synchronize the packaged data to the cloud server.

8. The device according to claim 7, characterized in that The parameter modification module is specifically used for: Comparing the versions of the label table file received by the monitoring device with the existing label table file in the inverter to determine whether the versions of the label table file received by the monitoring device and the existing label table file in the inverter are consistent; If the version corresponding to the label table file received by the monitoring device is lower than the version corresponding to the existing label table file in the inverter, then the existing label table file is pulled from the inverter to the monitoring device; If the version corresponding to the label table file received by the monitoring device is higher than the version corresponding to the existing label table file in the inverter, the label table file received by the monitoring device is updated to the inverter.

9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and when the machine-readable instructions are executed by the processor, the steps of the method for dynamic management of inverter standard parameters as described in any one of claims 1 to 6 are performed.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for dynamically managing inverter standard parameters according to any one of claims 1 to 6 are executed.

Images