A method for batch configuration of photovoltaic tracking bracket parameters

By employing a batch configuration method that combines dynamic unpacking of functional domains, broadcast retransmission, and multi-round read verification, the problems of low efficiency, poor reliability, and difficulty in fault location during photovoltaic tracking bracket parameter configuration are solved, achieving efficient and reliable parameter configuration and automated operation and maintenance.

CN123123162APending Publication Date: 2026-11-17POWERWAY RENEWABLE ENERGY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611231070.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-14
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing photovoltaic tracking bracket parameter configuration methods are inefficient and unreliable in large-scale deployment scenarios, and fault location is difficult. Broadcast failures result in unreliable configuration results, and full package distribution can easily lead to version compatibility risks and redundant writing.

Method used

The batch configuration method adopts dynamic functional domain unpacking, broadcast retransmission, multi-round machine-by-machine readback verification, and selective comparison. By dynamically generating functional domain parameter packets and continuously retransmitting them in broadcast mode, combined with preset effective time and multi-round machine-by-machine readback, a highly reliable configuration closed loop is achieved, and automatic rewriting is supported.

Benefits of technology

It significantly improves the efficiency and reliability of photovoltaic tracking bracket parameter configuration, reduces the risk of version conflicts, accurately locates faulty equipment and supports automatic rewriting, and reduces operation and maintenance costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123162A_ABST
    Figure CN123123162A_ABST
Patent Text Reader

Abstract

This invention relates to the field of intelligent operation and maintenance technology for photovoltaic power plants, and particularly to a method for batch configuration of photovoltaic tracking bracket parameters. The technical solution provided by this invention avoids redundant parameter writing and reduces version conflict risks through dynamic unpacking and selective comparison of functional domains; it employs a continuous retransmission mechanism in broadcast mode to effectively overcome the defect of frame loss due to lack of response; combined with multi-round, unit-by-unit readback verification after delay, it achieves a highly reliable configuration closed loop in scenarios without feedback; it accurately outputs the identifier of failed devices and supports automatic rewriting, transforming ambiguous faults into executable operation and maintenance actions, significantly improving the deployment efficiency and configuration reliability of large-scale power plants.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of intelligent operation and maintenance technology for photovoltaic power plants, and in particular to a method for batch configuration of photovoltaic tracking bracket parameters. Background Technology

[0002] Currently, photovoltaic tracking bracket parameter configuration technology is a key link in ensuring the efficient operation and precise solar tracking of large-scale photovoltaic power plants. This technology aims to accurately input heterogeneous parameters such as latitude and longitude, slope, protection strategies, and equipment attributes into the controllers of dozens to hundreds of trackers on site, so as to achieve coordinated control and safety protection of all equipment. Its configuration efficiency and reliability directly determine the grid connection and commissioning cycle and subsequent operation and maintenance costs of the power plant.

[0003] Existing methods typically distribute parameters through individual device connections or simple broadcasts. Individual wired / wireless connection configuration involves maintenance personnel using a terminal to sequentially connect to each device and write all parameters. The standard broadcast configuration method uses a preset broadcast address to send a data packet containing all parameters to all devices in the field at once. Additionally, some solutions employ a grouped polling method, dividing devices into groups by area and then sequentially sending the entire parameter packet. While these methods can accomplish the configuration task to some extent, none are specifically optimized for the highly heterogeneous parameters of the tracking brackets and the complex field communication environment.

[0004] However, the aforementioned methods struggle to balance efficiency and reliability in large-scale deployment scenarios. Individual configuration is extremely time-consuming and labor-intensive; ordinary broadcasting lacks a slave response mechanism at the protocol layer, making it impossible to verify the write status of individual devices, thus rendering the configuration results unreliable; and the whole-package delivery method, without functional domain decomposition of parameters, is prone to redundant writing of irrelevant parameters and version compatibility risks, lacks flexibility during localized rectification, and cannot accurately locate the failed device number when a fault occurs. Therefore, a new method for batch configuration of photovoltaic tracking bracket parameters is urgently needed to address these technical problems. Summary of the Invention

[0005] This invention aims to solve the problems of poor reliability caused by no response during broadcast in the batch configuration of existing photovoltaic tracking brackets, high compatibility risks in whole-package distribution, and difficulty in fault location.

[0006] To address the aforementioned technical problems, this invention provides a method for batch configuration of photovoltaic tracking bracket parameters, comprising: S101. In response to the parameter configuration command, the target functional domain selected by the user is obtained from the preset parameter library, and at least one functional domain parameter package is dynamically generated according to the target functional domain; wherein, each functional domain parameter package contains only the configuration parameters belonging to the corresponding target functional domain. S102. According to the configuration mode determined by the parameter configuration instruction, the functional domain parameter package is sent to the target photovoltaic tracking bracket; wherein, the configuration mode includes a broadcast configuration mode or a specified ID range configuration mode; in the broadcast configuration mode, each functional domain parameter package is continuously and repeatedly sent a preset number of times before switching to the next functional domain parameter package; S103. After the functional domain parameter package is issued, wait for the preset effective time, and then perform multiple rounds of read-back operations on the target photovoltaic tracking bracket to obtain the actual configuration data of each device. S104. Selectively compare and verify the actual configuration data with the configuration parameters corresponding to the target functional domain selected by the user, and generate batch configuration results based on the verification results; the batch configuration results include the configuration success status or configuration failure status of each target photovoltaic tracking bracket and the corresponding failure device identifier.

[0007] Furthermore, the step S101 of dynamically generating at least one functional domain parameter package based on the target functional domain specifically involves: Identify the type of the target functional domain; if the target functional domain is a composite functional domain, automatically expand the composite functional domain into multiple sub-functional domain parameter packages according to predefined splitting rules; if the target functional domain is a single functional domain, directly encapsulate it into the corresponding functional domain parameter package; wherein, the composite functional domain includes a component array functional domain, and the sub-functional domain parameter package includes a component size sub-package, an installation angle sub-package, and an array spacing sub-package.

[0008] Furthermore, the functional domain parameter package in step S101 only contains configuration parameters belonging to the corresponding target functional domain, specifically: The header of the functional domain parameter package carries a functional domain code identifier, which is used to characterize the functional domain type to which the parameter package belongs; the data segment of the functional domain parameter package is only filled with configuration parameter values ​​that match the functional domain code identifier, and does not contain parameter data or placeholders of other unselected functional domains.

[0009] Furthermore, in step S102, under the broadcast configuration mode, the function domain parameter packet is repeatedly sent a preset number of times before switching to the next function domain parameter packet. Specifically, this involves: Using a preset broadcast address as the destination address, the current functional domain parameter packet is sent N times consecutively, where N ranges from 2 to 5 times. After the current functional domain parameter packet is sent N times consecutively, the next functional domain parameter packet is immediately loaded and sent. During the entire broadcast configuration process, no response frames are waited for from the target photovoltaic tracking bracket.

[0010] Furthermore, the specified ID range configuration mode in step S102 includes the following sub-steps: S1021. Parse the start device ID and end device ID carried in the parameter configuration instruction, and verify the legality and size relationship of the start device ID and end device ID; S1022. After the verification is successful, the functional domain parameter packet is sent to the target photovoltaic tracking bracket one by one, starting from the starting device ID and ending from the ending device ID, in ascending order of device ID. S1023. For each target photovoltaic tracking bracket, reuse the same parameter package arrangement logic and retransmission mechanism as the broadcast configuration mode to send parameters.

[0011] Furthermore, step S103, which involves performing a multi-round, unit-by-unit readback operation on the target photovoltaic tracking bracket, includes the following sub-steps: S1031. After the preset effective time arrives, send parameter reading requests to each target photovoltaic tracking bracket in sequence according to the device ID list; S1032. Receive the actual configuration data returned by each target photovoltaic tracking bracket, and perform integrity verification and length verification on the actual configuration data; S1033. Repeat S1031 to S1032 for a total of M rounds, where M is at least 2 rounds; the readback data of a device is deemed valid only if the device passes the integrity check and length check in all M rounds of readback.

[0012] Furthermore, the preset effective time in step S103 is specifically as follows: The basic effective duration is determined based on the configuration parameter types contained in the functional domain parameter package, and a communication delay margin is added to the basic effective duration; wherein, the basic effective duration of parameters involving mechanical motion is longer than that of purely electronic parameters.

[0013] Furthermore, step S104, which involves selectively comparing and verifying the actual configuration data with the configuration parameters corresponding to the target functional domain selected by the user, specifically includes: Extract parameter fields corresponding to the target functional domain selected by the user from the actual configuration data; compare the extracted parameter fields one by one with the corresponding configuration parameter values ​​in the functional domain parameter package generated in step S101; ignore parameter fields of other functional domains not selected by the user in the actual configuration data and do not include them in the verification scope.

[0014] Furthermore, the batch configuration result in step S104 also includes a list of failed device identifiers, and the method further includes: A list of failed device IDs is generated by summarizing all device IDs corresponding to the configuration failure status. In response to the user's rewrite command, a new round of configuration process for the specified ID range is automatically triggered with the list of failed device IDs as the target range. The new round of configuration process reuses the complete processing logic of steps S101 to S104.

[0015] Furthermore, before the functional domain parameter package is sent out in step S102, the following steps are also included: A checksum is calculated for each functional domain parameter packet and the checksum is appended to the end of the parameter packet. Accordingly, before the selective comparison verification in step S104, the method further includes: using the checksum to verify the transmission correctness of the actual configuration data obtained by readback, and performing subsequent selective comparison verification only when the verification is successful.

[0016] The technical solution provided by this invention can include the following beneficial effects: by dynamically unpacking and selectively comparing functional domains, redundant parameter writing is avoided, reducing the risk of version conflicts; a continuous retransmission mechanism is adopted in broadcast mode to effectively overcome the defect of frame loss without response; combined with multi-round readback verification after delay, a highly reliable configuration closed loop is achieved in the absence of feedback; the failure device identifier is accurately output and automatic rewriting is supported, transforming fuzzy faults into executable operation and maintenance actions, significantly improving the deployment efficiency and configuration reliability of large-scale power plants. Attached Figure Description

[0017] The present invention will now be described in detail with reference to the accompanying drawings. The above and other aspects of the present invention will become clearer and more readily understood through the detailed description following the accompanying drawings. In the drawings: Figure 1 This is a flowchart illustrating the steps of a method for batch configuring photovoltaic tracking bracket parameters provided in an embodiment of the present invention. Detailed Implementation

[0018] The specific embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0019] The specific embodiments / examples described herein are specific implementations of the present invention, used to illustrate the concept of the invention, and are illustrative and exemplary, and should not be construed as limiting the implementation methods or scope of the present invention. In addition to the embodiments described herein, those skilled in the art can employ other obvious technical solutions based on the content disclosed in the claims and specification of this application. These technical solutions include those that make any obvious substitutions and modifications to the embodiments described herein, all of which are within the protection scope of the present invention.

[0020] Please refer to Figure 1 , Figure 1This is a flowchart illustrating the steps of a method for batch configuring photovoltaic tracking bracket parameters according to an embodiment of the present invention. The method for batch configuring photovoltaic tracking bracket parameters includes the following steps: S101. In response to the parameter configuration command, the target functional domain selected by the user is obtained from the preset parameter library, and at least one functional domain parameter package is dynamically generated according to the target functional domain; wherein, each functional domain parameter package contains only the configuration parameters belonging to the corresponding target functional domain. S102. According to the configuration mode determined by the parameter configuration instruction, the functional domain parameter package is sent to the target photovoltaic tracking bracket; wherein, the configuration mode includes a broadcast configuration mode or a specified ID range configuration mode; in the broadcast configuration mode, each functional domain parameter package is continuously and repeatedly sent a preset number of times before switching to the next functional domain parameter package; S103. After the functional domain parameter package is issued, wait for the preset effective time, and then perform multiple rounds of read-back operations on the target photovoltaic tracking bracket to obtain the actual configuration data of each device. S104. Selectively compare and verify the actual configuration data with the configuration parameters corresponding to the target functional domain selected by the user, and generate batch configuration results based on the verification results; the batch configuration results include the configuration success status or configuration failure status of each target photovoltaic tracking bracket and the corresponding failure device identifier.

[0021] The photovoltaic tracking bracket parameter batch configuration method provided in this invention aims to solve the problems of low parameter configuration efficiency, poor reliability and difficulty in fault location caused by the large number of devices and complex communication environment in large-scale photovoltaic power plants.

[0022] Specifically, this invention introduces a dynamic functional domain splitting mechanism to decouple the massive configuration task into multiple independent functional domain parameter packages. This avoids the risk of overall configuration failure due to a single parameter error, as is common in traditional whole-package distribution methods, while also reducing the transmission overhead of unnecessary parameters. Combined with continuous retransmission and no-response mechanisms in broadcast mode, it significantly improves data delivery rate in weak network environments while ensuring communication efficiency. Furthermore, through multi-round, unit-by-unit readback and selective comparison verification after a preset effective time, a closed-loop feedback mechanism of "distribution-waiting-verification" is constructed. This mechanism can accurately identify abnormally configured devices without relying on real-time responses and automatically generate a list of failed device identifiers to support precise rewriting. This solution achieves standardization, automation, and traceability of the configuration process, significantly reducing on-site operation and maintenance costs and improving the first-time success rate and long-term operational stability of photovoltaic tracking bracket cluster parameter configuration.

[0023] Furthermore, the step S101 of dynamically generating at least one functional domain parameter package based on the target functional domain specifically involves: Identify the type of the target functional domain; if the target functional domain is a composite functional domain, automatically expand the composite functional domain into multiple sub-functional domain parameter packages according to predefined splitting rules; if the target functional domain is a single functional domain, directly encapsulate it into the corresponding functional domain parameter package; wherein, the composite functional domain includes a component array functional domain, and the sub-functional domain parameter package includes a component size sub-package, an installation angle sub-package, and an array spacing sub-package.

[0024] The process of dynamically generating the functional domain parameter package based on the target functional domain in step S101 is essentially a semantic-level structured reorganization of the configuration data. Specifically: First, the parameter configuration command issued by the user is parsed to extract the identifier of the specified target functional domain. Then, a pre-defined functional domain type mapping table is queried to determine whether the target functional domain is a single functional domain or a composite functional domain. A composite functional domain refers to a set of parameters that logically belong to the same business category but are independent in physical implementation or configuration timing. For example, the component array functional domain includes three types of parameters: component size, installation angle, and array spacing. Although these three types of parameters all belong to the array configuration category, their effective conditions, storage addresses, and associated hardware modules are different. When a composite functional domain is identified, it is automatically decomposed into multiple sub-functional domain parameter packages according to predefined splitting rules (such as by parameter address range, by functional sub-module, or by configuration priority). Each sub-package only encapsulates the parameter data of the corresponding sub-function. If it is a single functional domain (such as motor limit parameters), it is directly encapsulated into an independent functional domain parameter package. This mechanism ensures the semantic atomicity and integrity of each parameter package, facilitating subsequent on-demand issuance and verification, and avoiding configuration conflicts caused by cross-functional domain parameter coupling, laying the data structure foundation for subsequent reliable transmission and accurate verification.

[0025] Furthermore, the functional domain parameter package in step S101 only contains configuration parameters belonging to the corresponding target functional domain, specifically: The header of the functional domain parameter package carries a functional domain code identifier, which is used to characterize the functional domain type to which the parameter package belongs; the data segment of the functional domain parameter package is only filled with configuration parameter values ​​that match the functional domain code identifier, and does not contain parameter data or placeholders of other unselected functional domains.

[0026] Step S101 emphasizes that the functional domain parameter package "only contains configuration parameters belonging to the corresponding target functional domain". Its core is to ensure the semantic purity and parsing determinism of the parameter package through protocol layer design.

[0027] In practice, each functional domain parameter package embeds a unique Function Domain Code (FDC) in its header field. This identifier uses a pre-assigned numerical encoding system, such as 0x01 for "motor control domain", 0x02 for "sensor calibration domain", and 0x10 for "component array domain - size sub-package".

[0028] When parsing parameter packets, the receiving device first reads the Function Domain Name (FDC) to determine the functional domain type to which the current packet belongs, and then loads the corresponding parameter parsing template. The data segment is strictly filled only with parameter values ​​that match the FDC, and does not contain parameters, reserved fields, or placeholders from any other functional domain.

[0029] This design eliminates the redundant transmission and parsing ambiguities common in traditional configuration protocols' "full parameter table" model. For example, when only the installation angle needs updating, component dimensions or array spacing parameters will not be mistakenly transmitted, thus avoiding abnormal device behavior caused by irrelevant parameters being accidentally overwritten. Simultaneously, due to the compact data packet structure and clear semantics, the receiving end does not need to perform complex field filtering or conditional judgments, significantly improving parsing efficiency and anti-interference capabilities, and providing a clean and reliable data source for subsequent selective comparison and verification.

[0030] Furthermore, in step S102, under the broadcast configuration mode, the function domain parameter packet is repeatedly sent a preset number of times before switching to the next function domain parameter packet. Specifically, this involves: Using a preset broadcast address as the destination address, the current functional domain parameter packet is sent N times consecutively, where N ranges from 2 to 5 times. After the current functional domain parameter packet is sent N times consecutively, the next functional domain parameter packet is immediately loaded and sent. During the entire broadcast configuration process, no response frames are waited for from the target photovoltaic tracking bracket.

[0031] The broadcast configuration mode described in step S102 adopts a continuous retransmission and no-response strategy, which is a robust transmission mechanism specifically designed for the field communication characteristics of photovoltaic tracking brackets.

[0032] During implementation, a preset global broadcast address (such as 0xFFFF) is used as the destination address. The current functional domain parameter packet to be sent is continuously sent N times (N ranges from 2 to 5 times, with a typical value of 3 times). There is no waiting interval or only a microsecond interval between each transmission, forming a burst data stream. After completing N transmissions, the next functional domain parameter packet is immediately loaded and sent. During the entire broadcast process, no ACK / NACK response frames from terminal devices are listened for or waited for.

[0033] The design is based on the following engineering considerations: photovoltaic tracking brackets are usually deployed in open fields, and the communication links are susceptible to electromagnetic interference, obstruction or multipath effects, resulting in a high packet loss rate for single transmissions; if the traditional request-response mechanism is used, it will cause serious channel congestion and latency accumulation in scenarios with hundreds of devices.

[0034] By retransmitting locally, the probability of at least one successful reception is increased by utilizing time diversity gain; abandoning acknowledgments completely avoids the "acknowledgment storm" problem, reducing broadcast configuration time from minutes to seconds. Although real-time acknowledgment capability is sacrificed, it is compensated for by multiple rounds of back-read verification in subsequent step S103, achieving an optimal balance between efficiency and reliability.

[0035] Furthermore, the specified ID range configuration mode in step S102 includes the following sub-steps: S1021. Parse the start device ID and end device ID carried in the parameter configuration instruction, and verify the legality and size relationship of the start device ID and end device ID; S1022. After the verification is successful, the functional domain parameter packet is sent to the target photovoltaic tracking bracket one by one, starting from the starting device ID and ending from the ending device ID, in ascending order of device ID. S1023. For each target photovoltaic tracking bracket, reuse the same parameter package arrangement logic and retransmission mechanism as the broadcast configuration mode to send parameters.

[0036] The specified ID range configuration mode in step S102 is used to accurately distribute parameters to a specific subset of devices. Its execution process includes strict boundary verification and ordered transmission control.

[0037] First, in S1021, the start device ID (Start_ID) and end device ID (End_ID) carried in the parameter configuration instruction are parsed, and it is verified whether they are valid device addresses (e.g., non-zero, not exceeding the maximum ID limit), and Start_ID≤End_ID is verified to prevent invalid traversal or memory overflow due to user input errors.

[0038] After the verification is successful, proceed to S1022, starting with Start_ID and ending with End_ID, construct unicast frames for each device in ascending order of ID and send functional domain parameter packets.

[0039] Each device's transmission operation reuses the parameter packet orchestration logic and retransmission mechanism (i.e., S1023) in broadcast mode, maintaining the same N consecutive retransmission strategy even with a specified configuration, ensuring consistency of transmission behavior under different configuration modes.

[0040] This mode is suitable for scenarios such as partial debugging, fault repair, or batch upgrades. It retains the high reliability of broadcast mode while also possessing precise device addressing capabilities. By limiting the ID range, it avoids invalid writes to irrelevant devices, reduces network load and device processing overhead, and provides a natural target range definition basis for subsequent rewriting of failed devices.

[0041] Furthermore, step S103, which involves performing a multi-round, unit-by-unit readback operation on the target photovoltaic tracking bracket, includes the following sub-steps: S1031. After the preset effective time arrives, send parameter reading requests to each target photovoltaic tracking bracket in sequence according to the device ID list; S1032. Receive the actual configuration data returned by each target photovoltaic tracking bracket, and perform integrity verification and length verification on the actual configuration data; S1033. Repeat S1031 to S1032 for a total of M rounds, where M is at least 2 rounds; the readback data of a device is deemed valid only if the device passes the integrity check and length check in all M rounds of readback.

[0042] The multi-round, unit-by-unit readback operation in step S103 is a key step in building a closed loop for configuration reliability verification.

[0043] In practice, after the preset effective time has ended, parameter reading request frames are sent to each target photovoltaic tracking bracket in sequence according to the pre-stored device ID list (or a sequence generated from a specified ID range) (S1031).

[0044] After each request is sent, a timeout timer is started to wait for a response; if a reply is received within the set time, integrity verification (such as CRC / Checksum verification) and length verification (checking whether the number of bytes in the data segment is consistent with the expectation) are performed on the returned actual configuration data.

[0045] Any verification failure is considered invalid for the device's readback in this round. After completing one round of traversal, the next round is started immediately, for a total of M rounds (M≥2, typically 3 rounds). Only if a device passes the double verification in all M rounds of readback is its readback data deemed valid and included in subsequent comparisons; otherwise, it is marked as a readback failure.

[0046] This multi-round mechanism effectively addresses temporary anomalies such as momentary communication failures, busy devices, or unready caches, preventing misjudgments due to isolated, occasional errors. While the serial approach sacrifices some speed, it eliminates bus contention and data confusion caused by concurrent requests, ensuring that the verification results of each device are independent and reliable, providing high-quality input for selective comparison.

[0047] Furthermore, the preset effective time in step S103 is specifically as follows: The basic effective duration is determined based on the configuration parameter types contained in the functional domain parameter package, and a communication delay margin is added to the basic effective duration; wherein, the basic effective duration of parameters involving mechanical motion is longer than that of purely electronic parameters.

[0048] The preset effective time in step S103 is not a fixed value, but an adaptive delay that is dynamically calculated based on the physical characteristics of the issued parameters.

[0049] Specifically, the first step is to analyze the parameter types contained in the currently issued functional domain parameter package, distinguishing them as "mechanical motion parameters" (such as tilt angle limit, drive speed, braking delay, etc.) or "pure electronic parameters" (such as communication baud rate, sampling period, threshold voltage, etc.). For mechanical motion parameters, because they involve physical processes such as motor movement, gear meshing, or structural deformation, sufficient time needs to be reserved for the actuator to complete the action and stabilize its state, so a longer basic effective duration (e.g., 500ms~2s) is assigned. Pure electronic parameters, on the other hand, only require register writing or memory refresh, and the basic effective duration is shorter (e.g., 10ms~50ms). On this basis, a fixed communication delay margin (e.g., 50ms) is superimposed to compensate for uncertainties such as bus propagation, queue queuing, and device response jitter.

[0050] Final effective time = base effective time + communication delay margin.

[0051] This mechanism avoids the inefficiency caused by a one-size-fits-all delay or false alarms caused by premature verification, ensuring that the readback operation is always performed after the device has actually completed the parameter application, which significantly improves the accuracy of the verification results and the overall timeliness of the configuration process.

[0052] Furthermore, step S104, which involves selectively comparing and verifying the actual configuration data with the configuration parameters corresponding to the target functional domain selected by the user, specifically includes: Extract parameter fields corresponding to the target functional domain selected by the user from the actual configuration data; compare the extracted parameter fields one by one with the corresponding configuration parameter values ​​in the functional domain parameter package generated in step S101; ignore parameter fields of other functional domains not selected by the user in the actual configuration data and do not include them in the verification scope.

[0053] The selective alignment verification in step S104 is a precise verification strategy oriented towards functional domains. Its core principle is to "verify only the selected functional domains and ignore the rest." In specific implementation: First, based on the user-selected target functional domain and its corresponding functional domain code identifier, a subset of parameter fields related to that functional domain is extracted from the actual configuration data obtained through readback. The extraction can be based on a predefined parameter address offset table or field label mapping relationship.

[0054] Subsequently, the extracted parameter fields are compared byte-by-byte or field-by-field with the corresponding configuration parameter values ​​in the original functional domain parameter package generated in step S101. Other functional domain parameters that exist in the actual configuration data but have not been selected by the user (such as the original configuration of the device or historical residual data) are actively ignored and do not participate in any comparison calculations.

[0055] This design solves the problem of false failure alarms caused by irrelevant parameter differences (such as changes in default values ​​due to different firmware versions) in traditional full comparison. At the same time, because the comparison scope is precisely limited to the set of parameters that the user intends to change, it not only reduces computational complexity but also gives the verification results clear business semantics: success means that the user's configuration intent has been accurately implemented, while failure precisely points to specific abnormal parameters within the target functional domain, greatly improving fault diagnosis efficiency and user experience.

[0056] Furthermore, the batch configuration result in step S104 also includes a list of failed device identifiers, and the method further includes: A list of failed device IDs is generated by summarizing all device IDs corresponding to the configuration failure status. In response to the user's rewrite command, a new round of configuration process for the specified ID range is automatically triggered with the list of failed device IDs as the target range. The new round of configuration process reuses the complete processing logic of steps S101 to S104.

[0057] The batch configuration results generated in step S104 not only include the success / failure status of each device, but also further summarize the IDs of all failed configuration devices to form a structured list of failed device identifiers. This list is stored in the form of an array or linked list, recording the unique ID of each failed device, the failure reason code (such as readback timeout, verification failure, inconsistency, etc.), and the corresponding functional domain information.

[0058] When a user confirms the need for repair, they can trigger a "rewrite" operation via the interface or command. In response to this rewrite command, the list of failed device identifiers is automatically converted into the start / end ID sequence required for the specified ID range configuration mode (or discrete IDs are sorted and grouped). Based on this sequence, the complete S101 to S104 configuration process is retried. This new round of processes reuses the same functional domain parameter packages, retransmission strategies, effective time calculations, and verification logic to ensure that the rewrite behavior maintains the same technical standards as the initial configuration.

[0059] This mechanism transforms the tedious process of manually checking and reconfiguring each configuration into an automated closed-loop process, significantly shortening fault recovery time. Especially in scenarios with large-scale configuration anomalies, it can merge consecutive failure ID ranges to further optimize rewrite efficiency, truly achieving an intelligent operation and maintenance experience of "one-time configuration, automatic error correction, and full traceability".

[0060] Furthermore, before the functional domain parameter package is sent out in step S102, the following steps are also included: A checksum is calculated for each functional domain parameter packet and the checksum is appended to the end of the parameter packet. Accordingly, before the selective comparison verification in step S104, the method further includes: using the checksum to verify the transmission correctness of the actual configuration data obtained by readback, and performing subsequent selective comparison verification only when the verification is successful.

[0061] Before issuing the functional domain parameter packets in step S102, a checksum (such as CRC-16, CRC-32, or MD5 digest) is calculated for each parameter packet, and this checksum is appended to the end of the parameter packet to form a complete transmission unit. Accordingly, before performing selective comparison verification in step S104, the correctness of the transmission of the actual configuration data obtained by readback is verified using the pre-attached checksum.

[0062] Specifically, the receiving end separates the data segment and the tail check code from the readback data, recalculates the check value of the data segment, and compares it with the received check code. Only when the two match is it determined that the data has not undergone bit flipping, truncation, or tampering during transmission, thus allowing it to proceed to the subsequent selective comparison stage; if the check fails, the readback is directly deemed invalid, not counted as a valid sample, and not included in the comparison.

[0063] This pre-verification mechanism forms the first line of defense for data security, effectively filtering out dirty data caused by channel noise, storage corruption, or protocol parsing errors, and preventing transport layer errors from being misjudged as configuration logic errors. By processing transmission integrity verification and business semantic verification in a layered manner, the confidence of the verification results is improved, and the fault attribution path is simplified, providing an underlying guarantee for high-reliability batch configuration.

[0064] In summary, this invention employs a series of collaborative mechanisms, including dynamic functional domain splitting, broadcast retransmission without response, adaptive activation waiting, multi-round read verification, selective comparison, and automatic rewriting, to construct an efficient, reliable, and self-healing method for batch configuration of photovoltaic tracking bracket parameters. Its technical effectiveness is mainly reflected in three aspects: First, semantic decoupling and packet structure optimization improve the transmission efficiency and parsing security of configuration data; second, the asynchronous verification architecture of retransmission and readback achieves high-confidence configuration confirmation even without real-time feedback; and third, precise verification and closed-loop rewriting transform configuration failure from an endpoint into a manageable intermediate state, significantly enhancing the fault tolerance and operational friendliness of the configuration system. These interconnected steps collectively support the industrial implementation needs of parameter configuration in large-scale photovoltaic scenarios.

[0065] Furthermore, it should be noted that the functional domain splitting rules, retransmission count N, readback rounds M, effective time calculation formulas, and verification algorithms in the above embodiments are all preferred implementations and are not intended to limit the present invention. For example, functional domain splitting can be dynamically loaded based on configuration files instead of hard-coding; the number of retransmissions can be adaptively adjusted according to historical channel quality; readback verification can adopt majority voting instead of a pass-all principle; and the checksum can be replaced with HMAC or other integrity protection mechanisms. Similarly, parameter packet format, communication protocol type (such as Modbus, CANopen, proprietary protocols), and device ID addressing method can be flexibly adapted according to the actual hardware platform. These variations are all reasonable extensions of the technical concept of the present invention, and as long as their core still follows the basic idea of ​​functional domain isolation distribution and asynchronous verification closed loop, they should be covered within the protection scope of the present invention.

[0066] The technical solution provided by this invention can include the following beneficial effects: by dynamically unpacking and selectively comparing functional domains, redundant parameter writing is avoided, reducing the risk of version conflicts; a continuous retransmission mechanism is adopted in broadcast mode to effectively overcome the defect of frame loss without response; combined with multi-round readback verification after delay, a highly reliable configuration closed loop is achieved in the absence of feedback; the failure device identifier is accurately output and automatic rewriting is supported, transforming fuzzy faults into executable operation and maintenance actions, significantly improving the deployment efficiency and configuration reliability of large-scale power plants.

[0067] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by hardware related to computer programs or instructions. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0068] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0069] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0070] The embodiments of the present invention have been described above with reference to the accompanying drawings. The disclosed embodiments are merely preferred embodiments of the present invention. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many equivalent changes in form under the guidance of the present invention without departing from the spirit and scope of the claims. All such changes are within the protection scope of the present invention.

Claims

1. A method for batch configuration of photovoltaic tracking bracket parameters, characterized in that, include: S101. In response to the parameter configuration command, the target functional domain selected by the user is obtained from the preset parameter library, and at least one functional domain parameter package is dynamically generated according to the target functional domain; wherein, each functional domain parameter package contains only the configuration parameters belonging to the corresponding target functional domain. S102. According to the configuration mode determined by the parameter configuration instruction, the functional domain parameter package is sent to the target photovoltaic tracking bracket; wherein, the configuration mode includes a broadcast configuration mode or a specified ID range configuration mode; in the broadcast configuration mode, each functional domain parameter package is continuously and repeatedly sent a preset number of times before switching to the next functional domain parameter package; S103. After the functional domain parameter package is issued, wait for the preset effective time, and then perform multiple rounds of read-back operations on the target photovoltaic tracking bracket to obtain the actual configuration data of each device. S104. Selectively compare and verify the actual configuration data with the configuration parameters corresponding to the target functional domain selected by the user, and generate batch configuration results based on the verification results; the batch configuration results include the configuration success status or configuration failure status of each target photovoltaic tracking bracket and the corresponding failure device identifier.

2. The method for batch configuration of photovoltaic tracking bracket parameters according to claim 1, characterized in that, Step S101, which involves dynamically generating at least one functional domain parameter package based on the target functional domain, specifically includes: Identify the type of the target functional domain; if the target functional domain is a composite functional domain, automatically expand the composite functional domain into multiple sub-functional domain parameter packages according to predefined splitting rules; if the target functional domain is a single functional domain, directly encapsulate it into the corresponding functional domain parameter package; wherein, the composite functional domain includes a component array functional domain, and the sub-functional domain parameter package includes a component size sub-package, an installation angle sub-package, and an array spacing sub-package.

3. The method for batch configuration of photovoltaic tracking bracket parameters according to claim 1, characterized in that, The functional domain parameter package in step S101 only contains configuration parameters belonging to the corresponding target functional domain, specifically: The header of the functional domain parameter package carries a functional domain code identifier, which is used to characterize the functional domain type to which the parameter package belongs; the data segment of the functional domain parameter package is only filled with configuration parameter values ​​that match the functional domain code identifier, and does not contain parameter data or placeholders of other unselected functional domains.

4. The method for batch configuration of photovoltaic tracking bracket parameters according to claim 1, characterized in that, In step S102, under the broadcast configuration mode, the function domain parameter packet is repeatedly sent a preset number of times before switching to the next function domain parameter packet. Specifically, this means: Using a preset broadcast address as the destination address, the current functional domain parameter packet is sent N times consecutively, where N ranges from 2 to 5 times. After the current functional domain parameter packet is sent N times consecutively, the next functional domain parameter packet is immediately loaded and sent. During the entire broadcast configuration process, no response frames are waited for from the target photovoltaic tracking bracket.

5. The method for batch configuration of photovoltaic tracking bracket parameters according to claim 1, characterized in that, The specified ID range configuration mode in step S102 includes the following sub-steps: S1021. Parse the start device ID and end device ID carried in the parameter configuration instruction, and verify the legality and size relationship of the start device ID and end device ID; S1022. After the verification is successful, the functional domain parameter packet is sent to the target photovoltaic tracking bracket one by one, starting from the starting device ID and ending from the ending device ID, in ascending order of device ID. S1023. For each target photovoltaic tracking bracket, reuse the same parameter packet arrangement logic and retransmission mechanism as the broadcast configuration mode to send parameters.

6. The method for batch configuration of photovoltaic tracking bracket parameters according to claim 1, characterized in that, Step S103, which involves performing a multi-round, unit-by-unit readback operation on the target photovoltaic tracking bracket, includes the following sub-steps: S1031. After the preset effective time arrives, send parameter reading requests to each target photovoltaic tracking bracket in sequence according to the device ID list; S1032. Receive the actual configuration data returned by each target photovoltaic tracking bracket, and perform integrity verification and length verification on the actual configuration data; S1033. Repeat S1031 to S1032 for a total of M rounds, where M is at least 2 rounds. The read data of a device is considered valid only if it passes the integrity check and length check in all M rounds of reads.

7. The method for batch configuration of photovoltaic tracking bracket parameters according to claim 6, characterized in that, The preset effective time in step S103 is as follows: The basic effective duration is determined based on the configuration parameter types contained in the functional domain parameter package, and a communication delay margin is added to the basic effective duration; wherein, the basic effective duration of parameters involving mechanical motion is longer than that of purely electronic parameters.

8. The method for batch configuration of photovoltaic tracking bracket parameters according to claim 1, characterized in that, Step S104, which involves selectively comparing and verifying the actual configuration data with the configuration parameters corresponding to the target functional domain selected by the user, specifically includes: Extract parameter fields corresponding to the target functional domain selected by the user from the actual configuration data; compare the extracted parameter fields one by one with the corresponding configuration parameter values ​​in the functional domain parameter package generated in step S101; ignore parameter fields of other functional domains not selected by the user in the actual configuration data and do not include them in the verification scope.

9. The method for batch configuration of photovoltaic tracking bracket parameters according to claim 1, characterized in that, The batch configuration result in step S104 also includes a list of failed device identifiers, and the method further includes: A list of failed device IDs is generated by summarizing all device IDs corresponding to the configuration failure status. In response to the user's rewrite command, a new round of configuration process for the specified ID range is automatically triggered with the list of failed device IDs as the target range. The new round of configuration process reuses the complete processing logic of steps S101 to S104.

10. The method for batch configuration of photovoltaic tracking bracket parameters according to claim 1, characterized in that, Before the functional domain parameter package is sent out in step S102, the following steps are also included: A checksum is calculated for each functional domain parameter packet and the checksum is appended to the end of the parameter packet. Accordingly, before the selective comparison verification in step S104, the method further includes: using the checksum to verify the transmission correctness of the actual configuration data obtained by readback, and performing subsequent selective comparison verification only when the verification is successful.