Power supply system and photovoltaic system
By introducing the master-slave election mechanism and parameter synchronization mechanism in the power supply system, the problem of easy loss of system parameters in the existing technology is solved, real-time parameter backup and system stability guarantee are achieved.
Patent Information
- Application Number
- CN202411970559.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-05-28
- Filing Date
- 2024-12-27
- Publication Date
- 2025-04-08
AI Technical Summary
When the core control unit is damaged, failed or replaced, the existing power supply system is likely to lose system parameters, and the cloud backup method cannot backup all parameters in real time, which is a high risk.
By introducing a master-slave campaign mechanism in the power supply system, the host and the slave confirm each other by requesting heartbeat frames and responding heartbeat frames, and the host broadcasts parameters and synchronizes frames to realize real-time parameter backup of each power supply device.
It effectively avoids the loss of system parameters, ensures that the power supply system can still operate stably under the damage of the host or slave, and reduces the load on the communication network.
Smart Images

Figure CN119787337A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the technical field of power supply equipment, and in particular, relates to a power supply system and a photovoltaic system. Background Art
[0002] The power supply device can perform AC / DC conversion and voltage conversion on the electrical energy input from photovoltaic and other power sources. Photovoltaic power stations generally adopt a structure with multiple power supply devices in parallel to achieve sufficient power output and flexible power adjustment.
[0003] The communication control of a multi-power supply device usually requires the additional setting of a central controller or data collector, which is used as the core control unit for control. When the core control unit is damaged, fails or replaced, the multi-power supply device will lose control, and user configuration parameters and device operation data may be lost.
[0004] At present, most people use cloud backup to regularly back up the parameters of power supply devices. However, this method cannot back up all the real-time parameters of the power supply device, and the risk of system parameter loss is still relatively high. Summary of the invention
[0005] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes a power supply system and a photovoltaic system, which can effectively avoid the loss of system parameters.
[0006] In a first aspect, the present application provides a power supply system, comprising:
[0007] A plurality of power supply devices, the plurality of power supply devices are communicatively connected with each other, and the plurality of power supply devices are used to perform a master-slave election to determine a master and a slave of a power supply system;
[0008] The host is used to send a parameter synchronization frame to the slave, and the slave performs parameter setting of the slave itself based on the host device identifier, the device synchronization parameter and the parameter version identifier corresponding to the device synchronization parameter in the parameter synchronization frame;
[0009] The host is used to send a request heartbeat frame to the slave, and the slave feeds back a response heartbeat frame to the host based on the host device identifier and parameter version identifier in the request heartbeat frame. The host is used to determine whether the host sends the parameter synchronization frame to the slave based on the host device identifier, slave device identifier and synchronization request identifier in the response heartbeat frame.
[0010] According to the power supply system of the present application, through multiple power supply devices communication connection, the host and the slave confirm each other through requesting heartbeat frames and responding to heartbeat frames, the host broadcasts parameter synchronization frames, and various parameters are backed up in real time in each power supply device of the power supply system, effectively avoiding parameter loss.
[0011] According to one embodiment of the present application, the host is used to send the parameter synchronization frame when a device setting parameter of the power supply system is changed.
[0012] According to one embodiment of the present application, the host is used to send the parameter synchronization frame when the synchronization request identifier in the received response heartbeat frame is a request for synchronization.
[0013] According to one embodiment of the present application, the slave machine is used to feed back to the host the response heartbeat frame with a synchronization request identifier as requesting synchronization when it is determined that the host device identifier of the received request heartbeat frame matches its own host device identifier and when it is determined based on a parameter version identifier comparison algorithm that the parameter version identifier of the request heartbeat frame is newer than its own parameter version identifier.
[0014] According to an embodiment of the present application, when the timing duration of receiving the parameter synchronization frame reaches a first timing duration, the slave sends the response heartbeat frame to the host.
[0015] According to one embodiment of the present application, the host sends one of the parameter synchronization frame and the request heartbeat frame at a first time interval.
[0016] According to an embodiment of the present application, when the slave machine fails to receive the parameter synchronization frame or the duration of the request heartbeat frame is greater than a second duration threshold, the slave machine sends the parameter synchronization frame based on its own parameters.
[0017] According to one embodiment of the present application, the slave machine is used to synchronize device setting parameters and device read-only parameters based on the device synchronization parameters of the parameter synchronization frame when it is determined that the host device identifier of the parameter synchronization frame matches its own host device identifier and the parameter version identifier of the parameter synchronization frame is newer than its own parameter version identifier.
[0018] According to one embodiment of the present application, the slave machine is used to synchronize device read-only parameters based on the device synchronization parameters of the parameter synchronization frame when it is determined that the host device identifier of the parameter synchronization frame matches its own host device identifier and the parameter version identifier of the parameter synchronization frame is not updated compared to its own parameter version identifier.
[0019] According to one embodiment of the present application, the slave is also used to send a parameter setting frame to the host, and the host is also used to update its own parameters based on the host device identifier, slave device identifier and setting parameter information in the parameter setting frame, and send the parameter synchronization frame corresponding to the parameter setting frame.
[0020] According to one embodiment of the present application, the multiple power supply devices include at least two first power supply devices that determine themselves as the host, different first power supply devices sense each other through the request heartbeat frame, different first power supply devices set parameters through the parameter synchronization frame, and the at least two first power supply devices perform master-slave competition to determine one of the hosts of the power supply system.
[0021] According to an embodiment of the present application, the first power supply device is used to perform its own parameter settings according to the received parameter synchronization frame when the parameter version identifier of the received parameter synchronization frame is newer than its own parameter version identifier.
[0022] According to an embodiment of the present application, the first power supply device is used to send the parameter synchronization frame corresponding to its own parameters when the parameter version identifier of the received parameter synchronization frame or the request heartbeat frame is not updated compared to its own parameter version identifier.
[0023] According to one embodiment of the present application, when the parameter version identifiers of the parameter synchronization frames or the request heartbeat frames received by the at least two first power supply devices are the same as their own parameter version identifiers, the at least two first power supply devices perform master-slave competition to determine one of the hosts of the power supply system.
[0024] According to one embodiment of the present application, the host has a first timing module, which is used to generate a first random duration and time the first random duration to trigger the host to send one of the parameter synchronization frame and the request heartbeat frame.
[0025] According to an embodiment of the present application, when a device setting parameter of the power supply system is changed within the first random duration, the first timing module times the first random duration to trigger the host to send the parameter synchronization frame;
[0026] When the equipment setting parameters of the power supply system are not changed within the first random duration, the first timing module times the first random duration to trigger the host to send the request heartbeat frame.
[0027] According to one embodiment of the present application, the slave machine has a second timing module, which is used to generate a second random duration and perform timing when the slave machine receives the request heartbeat frame. The second timing module is used to time the second random duration to trigger the slave machine to feedback the response heartbeat frame.
[0028] According to one embodiment of the present application, when the parameter synchronization frame sent by the host does not have a slave device identifier, the slave in the power supply system that receives the parameter synchronization frame performs parameter settings of the slave itself based on the host device identifier, device synchronization parameters and parameter version identifier corresponding to the device synchronization parameters in the parameter synchronization frame.
[0029] According to one embodiment of the present application, when the parameter synchronization frame sent by the host has a slave device identification, the slave is used to set its own parameters based on the host device identification, device synchronization parameters and parameter version identification corresponding to the device synchronization parameters in the parameter synchronization frame when it is determined that the slave device identification of the parameter synchronization frame matches its own slave device identification.
[0030] In a second aspect, the present application provides a photovoltaic system, comprising:
[0031] A photovoltaic component and a power supply system as described in the first aspect above, wherein the photovoltaic component is electrically connected to the power supply system.
[0032] According to the photovoltaic system of the present application, through communication connection of multiple power supply devices, the host and the slave confirm each other through requesting heartbeat frames and responding to heartbeat frames, the host broadcasts parameter synchronization frames, and various parameters are backed up in real time in each power supply device of the power supply system, effectively avoiding parameter loss.
[0033] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:
[0035] Figure 1 is a schematic diagram of the structure of the power supply system provided in an embodiment of the present application;
[0036] Figure 2 It is a flowchart of operations performed by a host in a power supply system provided by an embodiment of the present application;
[0037] Figure 3 It is one of the flowcharts of the slave machine performing the operation in the power supply system provided by the embodiment of the present application;
[0038] Figure 4 This is the second flowchart of the slave machine performing the operation in the power supply system provided by the embodiment of the present application;
[0039] Figure 5It is a schematic diagram of the process of parameter setting of the power supply system provided in the embodiment of the present application;
[0040] Figure 6 It is a schematic diagram of the process of host switching of the power supply system provided in an embodiment of the present application;
[0041] Figure 7 It is a schematic diagram of the host-slave interaction of the power supply system provided in an embodiment of the present application.
[0042] Reference numerals:
[0043] Power supply device 100 , communication bus 210 , networking device 220 , cloud 230 . DETAILED DESCRIPTION
[0044] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.
[0045] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0046] The power supply system provided in the embodiment of the present application and the photovoltaic system including the power supply system are described in detail below through specific embodiments and their application scenarios in combination with the accompanying drawings.
[0047] like Figure 1 As shown, the power supply system of the embodiment of the present application includes multiple power supply devices 100, and the multiple power supply devices 100 are communicatively connected with each other.
[0048] The power supply device 100 is a device that can perform AC-DC conversion and voltage conversion on input electrical energy, such as an inverter, a converter, etc.
[0049] It is understandable that the electrical connection between multiple power supply devices 100 can be in parallel to achieve sufficient power output and flexible power adjustment.
[0050] In this embodiment, a plurality of power supply devices 100 may be communicatively connected via a communication bus 210 , and the communication bus 210 may be a CAN bus, Fast Ethernet (FE), Wi-Fi, or the like.
[0051] In actual implementation, the communication network formed by multiple power supply devices 100 may also include networking devices 220 such as routers and switches, so that the multiple power supply devices 100 can communicate with each other while also communicating with the cloud 230, sending data to the cloud 230, or receiving control instructions issued by the cloud 230.
[0052] In this embodiment, a plurality of power supply devices 100 are used to perform a master-slave election to determine a master and a slave of the power supply system.
[0053] It can be understood that the host of the power supply system can be equivalent to the system console. The host can send signals or control instructions to the slave to control the slave to perform certain operations. The power supply system is communicatively connected between multiple power supply devices 100, and the host and slave can communicate.
[0054] In actual implementation, after multiple power supply devices 100 are networked, a master-slave election can be conducted through a preset master-slave election mechanism to elect one power supply device 100 in the power supply system as the master and the other power supply devices 100 as slaves.
[0055] In this embodiment, the master and slave of the power supply system communicate at least through parameter synchronization frames, request heartbeat frames and response heartbeat frames.
[0056] The parameter synchronization frame includes a host device identifier, a device synchronization parameter, and a parameter version identifier corresponding to the device synchronization parameter.
[0057] In the parameter synchronization frame, the host device identifier is a unique identifier used to characterize the host, the device synchronization parameter is a parameter that needs to be synchronized by the power supply device 100 in the power supply system (for example, user configuration parameters or device operation data, etc.), and the parameter version identifier characterizes the parameter version corresponding to the device synchronization parameter.
[0058] In actual implementation, the parameter version identifier may include at least one of parameter generation time information, a parameter cycle (CRC) check value, and a parameter serial number.
[0059] It should be noted that the parameter version identifier corresponds to the device synchronization parameter. When the host sends a new parameter that needs to be synchronized through a parameter synchronization frame, the parameter version identifier will change accordingly.
[0060] For example, at the current moment, the host sends a parameter synchronization frame A, which includes a host device identifier H, a device synchronization parameter A1 to be synchronized, and a corresponding parameter version identifier A2.
[0061] At the next moment, the host sends a parameter synchronization frame B, which includes the host device identifier H, the device synchronization parameter B1 to be synchronized, and the corresponding parameter version identifier B2.
[0062] It can be understood that when the host does not change, the host device identifier of the parameter synchronization frame does not change, and the parameter version identifier changes with the user's setting command and the operation of the power supply device 100.
[0063] In this embodiment, the host is used to send a parameter synchronization frame to the slave, and the slave sets its own parameters based on the host device identifier, the device synchronization parameters, and the parameter version identifier corresponding to the device synchronization parameters in the parameter synchronization frame.
[0064] It should be noted that the parameters set by the master and the slave include system parameters of the power supply system and device parameters of the power supply device 100 .
[0065] In actual implementation, when there are parameters that need to be updated synchronously in the power supply system, the host sends a parameter synchronization frame to the slave, and the slave receives the parameter synchronization frame. The slave sets its own parameters to the parameters that need to be updated synchronously in the power supply system according to the parameter synchronization frame.
[0066] It is understandable that, before sending the parameter synchronization frame, the host may set its own parameters to the parameters that need to be synchronously updated by the power supply system, and then send the parameter synchronization frame to the slave.
[0067] The slave can determine whether the parameter synchronization frame is sent by the master of the system to which it belongs based on the master device identifier in the parameter synchronization frame, and perform master identity authentication through the master device identifier.
[0068] The slave compares the parameter version identifier in the parameter synchronization frame with the parameter version identifier corresponding to its own parameters to determine whether the current parameters of the power supply system are updated compared to the current parameters of the slave itself. The timeliness of the parameter setting command of the parameter synchronization frame is confirmed by the parameter version identifier, which can avoid re-synchronization of the parameters that have been synchronized.
[0069] After the slave completes the analysis of the host device identification and parameter version identification, it updates its own parameters according to the device synchronization parameters in the parameter synchronization frame.
[0070] It should be noted that the master and slave confirm each other through request heartbeat frames and response heartbeat frames.
[0071] In this embodiment, the host is used to send a request heartbeat frame to the slave, and the slave feeds back a response heartbeat frame to the host based on the host device identifier and the parameter version identifier in the request heartbeat frame.
[0072] The request heartbeat frame may include a host device identifier and a parameter version identifier, and the response heartbeat frame may include a host device identifier, a slave device identifier, and a synchronization request identifier.
[0073] The slave can determine whether the request heartbeat frame is sent by the host of the system to which it belongs based on the host device identifier of the request heartbeat frame.
[0074] The slave compares the parameter version identifier of the request heartbeat frame with the parameter version identifier corresponding to its own parameters to determine whether the current parameters of the power supply system are updated compared to the current parameters of the slave itself, and then feeds back the corresponding response heartbeat frame to the host.
[0075] In this embodiment, the host is used to determine whether to send a parameter synchronization frame to the slave based on the host device identifier, the slave device identifier and the synchronization request identifier in the response heartbeat frame.
[0076] It can be understood that the response heartbeat frame sent by the slave includes a host device identifier and a slave device identifier, the host device identifier indicates which host the slave belongs to, and the slave device identifier indicates the identity identifier of the slave.
[0077] The host can determine whether the slave that sends the response heartbeat frame is a slave belonging to its own system based on the host device identifier and the slave device identifier of the response heartbeat frame.
[0078] In this embodiment, the synchronization request flag is used to indicate whether the slave requests the host to send a parameter synchronization frame, so that the slave can set its own parameters according to the parameter synchronization frame.
[0079] After the host determines that the slave sending the response heartbeat frame is a slave of its own system based on the host device identifier and the slave device identifier of the response heartbeat frame, when the synchronization request identifier represents that the slave requests the host to send a parameter synchronization frame, the host sends the parameter synchronization frame to the slave; when the synchronization request identifier represents that the slave does not request the host to send a parameter synchronization frame, the host does not send a parameter synchronization frame to the slave.
[0080] In the related art, a central controller or a data collector is usually provided in the system of a multi-power supply device as a core control unit. When the core control unit is damaged, fails or is replaced, user configuration parameters and device operation data are easily lost. The commonly used cloud backup method cannot back up all real-time parameters, and the risk of parameter loss is relatively high.
[0081] In the embodiment of the present application, the power supply system does not need to set up additional core control units such as a central controller or a data collector. In the decentralized communication network architecture formed by multiple power supply devices 100, the host and the slave confirm each other through request heartbeat frames and response heartbeat frames. The host broadcasts parameter synchronization frames, and the slave identifies whether the parameters need to be updated through the parameter version identifier. Both the host and the slave update the parameters, and various parameters can be backed up in real time. When the host or the slave is damaged, fails or replaced, the power supply equipment 100 other than the damaged device retains and backs up various parameters, effectively preventing the loss of parameters of the power supply system.
[0082] It should be noted that the parameter synchronization frame contains device synchronization parameters, and the frame length of the parameter synchronization frame is longer than that of the request heartbeat frame. For example, the frame length of the parameter synchronization frame can reach several thousand bytes, and the frame length of the request heartbeat frame can be within a hundred bytes. By judging whether to broadcast the parameter synchronization frame through the response heartbeat frame of the slave machine, the sending frequency of the parameter synchronization frame can be reduced, thereby avoiding congestion of the communication network composed of multiple power supply devices 100.
[0083] According to the power supply system provided in the embodiment of the present application, a plurality of power supply devices 100 are communicatively connected, the host and the slave confirm each other by requesting heartbeat frames and responding to heartbeat frames, the host broadcasts parameter synchronization frames, and various parameters are backed up in real time in each power supply device 100 of the power supply system, thereby effectively avoiding parameter loss.
[0084] In some embodiments, the host is configured to send a parameter synchronization frame when a parameter setting of a device in the power supply system is changed.
[0085] In this embodiment, the device setting parameter change of the power supply system may be that the host receives user input and changes the configuration parameters, parameters, etc. of the system.
[0086] When the equipment setting parameters of the power supply system change, the host can first update its own parameters according to the changed parameters, and then broadcast the parameter synchronization frame corresponding to the changed parameters, so that the power supply equipment 100 in the power supply system can synchronize the setting and backup parameters. The parameter version identifier of the parameter synchronization frame is newer than the parameter version identifier of the parameter synchronization frame that has been broadcast before.
[0087] In actual implementation, in a communication network composed of multiple power supply devices 100, the host can receive parameter commands transmitted by the user through the cloud 230, the device setting parameters of the power supply system are changed, the host updates its own parameters, and the host broadcasts parameter synchronization frames. The power supply devices 100 in the power supply system can all synchronize the settings and backup parameters.
[0088] In some embodiments, the host is configured to send a parameter synchronization frame when the synchronization request identifier in the received response heartbeat frame is a request for synchronization.
[0089] The synchronization request flag is used to indicate whether the slave requests the host to send a parameter synchronization frame. The synchronization request flag is a request for synchronization, indicating that the slave needs to update parameters.
[0090] In actual implementation, the synchronization request flag may be a Boolean value, and the synchronization request flag in response to the heartbeat frame is true or false.
[0091] Among them, true can represent that the slave requests the host to send a parameter synchronization frame, and false can represent that the slave does not request the host to send a parameter synchronization frame.
[0092] In this embodiment, when the host determines that the synchronization request identifier in the received response heartbeat frame is a request for synchronization, the host sends a parameter synchronization frame; when the host determines that the synchronization request identifier in the received response heartbeat frame is not a request for synchronization, the host does not send a parameter synchronization frame, and the host can wait until the subsequent timing expires to send a request heartbeat frame.
[0093] It can be understood that the host determines whether to send a parameter synchronization frame based on the synchronization request identifier of the response heartbeat frame. Only when the slave has a parameter change requirement, it sends a parameter synchronization frame with a longer frame length. When the slave does not need to change the parameters, the host and the slave confirm through a heartbeat frame with a shorter frame length. Under the premise of ensuring real-time synchronization of system parameters, the communication volume is reduced, network congestion is avoided, and signal transmission stability is guaranteed.
[0094] In some embodiments, the slave is used to feed back a synchronization request identifier as a response heartbeat frame requesting synchronization to the host when it is determined that the host device identifier of the received request heartbeat frame matches its own host device identifier, and when it is determined based on a parameter version identifier comparison algorithm that the parameter version identifier of the request heartbeat frame is newer than its own parameter version identifier.
[0095] It should be noted that as the parameters are updated, the parameter version identifier changes according to a certain rule, and can be changed from small to large or from large to small.
[0096] For example, at the current moment, the host sends a parameter synchronization frame A, which includes a host device identifier H, a device synchronization parameter A1 to be synchronized, and a corresponding parameter version identifier 01.
[0097] At the next moment, the host sends a parameter synchronization frame B, which includes the host device identifier H, the device synchronization parameter B1 to be synchronized, and the corresponding parameter version identifier 02.
[0098] In actual execution, the slave determines whether the parameter version identifier of the request heartbeat frame is newer than its own parameter version identifier according to the parameter version identifier comparison algorithm corresponding to the parameter version identifier change.
[0099] In this embodiment, from the current moment to the next moment, the parameter version identifier changes from small to large. When the parameter version identifier in the frame received by the slave is greater than its own parameter version identifier, the parameter version identifier of the frame is updated compared to its own parameter version identifier; when the parameter version identifier in the frame received by the slave is less than or equal to its own parameter version identifier, the parameter version identifier of the frame is not updated compared to its own parameter version identifier.
[0100] In this embodiment, the slave determines that the host device identifier of the received request heartbeat frame matches its own host device identifier, indicating that the slave confirms that the received request heartbeat frame is sent by the host of the system to which it belongs.
[0101] It should be noted that the slave determines that the parameter version identifier of the received request heartbeat frame is newer than its own parameter version identifier, indicating that the host's parameters are updated compared to the slave's own parameters. At this time, the synchronization request identifier in the response heartbeat frame fed back by the slave to the host is a request for synchronization, so that the host can send a parameter synchronization frame based on this response heartbeat frame, and the slave updates its own parameters based on the parameter synchronization frame.
[0102] It is understandable that sending parameter synchronization frames at fixed time periods in the power supply system may cause congestion in the communication network. The host and the slave use request heartbeat frames and response heartbeat frames to identify each other. When the equipment setting parameters of the power supply system are changed, or when the master-slave parameters are detected to be different through the heartbeat frame, parameter synchronization frames are used for parameter synchronization, which can greatly reduce the frame transmission pressure of the communication network.
[0103] In some embodiments, when the timing duration of receiving the parameter synchronization frame reaches the first timing duration, the slave sends a response heartbeat frame to the host.
[0104] In this embodiment, the slave starts timing after receiving the parameter synchronization frame. When the timing duration of the slave receiving the parameter synchronization frame reaches a preset first timing duration, the slave sends a response heartbeat frame to the host, and regularly requests the host to send parameter synchronization frames for parameter update and backup.
[0105] In actual execution, when the host does not receive a response heartbeat frame from the slave within a certain period of time, the host can also send a parameter synchronization frame or a request heartbeat frame to the slave so that the slave can regularly update and back up parameters.
[0106] In some embodiments, the host sends one of a parameter synchronization frame and a request heartbeat frame at a first time interval.
[0107] In this embodiment, the host periodically sends one of a parameter synchronization frame and a request heartbeat frame to the slave at a preset first time interval; the slave receives the parameter synchronization frame and performs parameter synchronization, and receives the request heartbeat frame and feeds back a response heartbeat frame.
[0108] In some embodiments, when the slave does not receive a parameter synchronization frame or a duration of a request heartbeat frame that is greater than a second duration threshold, the slave sends a parameter synchronization frame based on its own parameters.
[0109] In this embodiment, when the slave does not receive a parameter synchronization frame or a request heartbeat frame sent by the host within a period of time (the time corresponding to the preset second time threshold), the slave sends a parameter synchronization frame to the host and / or other slaves in the power supply system based on its own parameters.
[0110] The parameter synchronization frame sent by the slave includes a slave device identifier, a device synchronization parameter, and a parameter version identifier corresponding to the device synchronization parameter.
[0111] It can be understood that the parameter synchronization frame sent by the slave and the parameter synchronization frame sent by the host have the same frame content but different device identifiers.
[0112] It should be noted that the parameter synchronization frame sent by the host includes a host device identifier and may also include a slave device identifier. The number of slave device identifiers in the parameter synchronization frame sent by the host may be 0, 1 or more.
[0113] In some embodiments, when the parameter synchronization frame sent by the host does not have a slave device identifier, the slave that receives the parameter synchronization frame in the power supply system sets its own parameters based on the host device identifier, device synchronization parameters, and parameter version identifier corresponding to the device synchronization parameters in the parameter synchronization frame.
[0114] In this embodiment, when the parameter synchronization frame sent by the host does not include the slave device identification, all slaves in the power supply system that receive the parameter synchronization frame process the parameter synchronization frame.
[0115] In actual execution, the slave sets its own parameters based on the host device identifier, device synchronization parameters and parameter version identifier corresponding to the device synchronization parameters in the parameter synchronization frame. The slave can perform host identity authentication for the slave based on the host device identifier, and the slave confirms the timeliness of the parameter synchronization frame based on the parameter version identifier. After the slave confirms the host device identifier and the parameter version identifier, it updates its own parameters based on the device synchronization parameters in the parameter synchronization frame.
[0116] In some embodiments, when a parameter synchronization frame sent by the host has a slave device identifier, the slave is used to set its own parameters based on the host device identifier, the device synchronization parameters, and the parameter version identifier corresponding to the device synchronization parameters in the parameter synchronization frame when it determines that the slave device identifier of the parameter synchronization frame matches its own slave device identifier.
[0117] In this embodiment, when the parameter synchronization frame sent by the host includes a slave device identification, the slave corresponding to the slave device identification of the parameter synchronization frame in the power supply system processes the parameter synchronization frame, and other slaves do not process the parameter synchronization frame.
[0118] For example, the power supply system includes four slaves, A1, A2, A3 and A4. The parameter synchronization frame sent by the host has the slave device identification corresponding to A1 and A3. A1 and A3 process the parameter synchronization frame sent by the host, and A2 and A4 do not process the parameter synchronization frame sent by the host, and the parameters of the power supply device 100 are updated and backed up in a targeted manner.
[0119] The following is a detailed introduction on how the slave sets its own parameters according to the parameter synchronization frame.
[0120] It should be noted that the parameters of the power supply device 100 can be divided into device setting parameters (Read Write, RW) and device read-only parameters (Read Only, RO).
[0121] The device setting parameters may be parameters that can be set by the user, for example, parameters such as the working mode, voltage limit, and current limit of the power supply device 100 .
[0122] The device read-only parameters may be process parameters of the power supply device 100 , which may change in real time, for example, the amount of electricity purchased by the power supply device 100 . The user does not set these parameters and may analyze the operating status of the power supply device 100 based on these parameters.
[0123] In actual implementation, the device setting parameters can be set by the user. When the device setting parameters change, the parameter version identifier of the parameter synchronization sent by the host is updated. The device read-only parameters have the characteristics of real-time change. When the device read-only parameters change, the parameter version identifier of the parameter synchronization sent by the host may not be updated.
[0124] In some embodiments, the slave is used to synchronize device setting parameters and device read-only parameters based on the device synchronization parameters of the parameter synchronization frame when it is determined that the host device identifier of the parameter synchronization frame matches its own host device identifier and the parameter version identifier of the parameter synchronization frame is newer than its own parameter version identifier.
[0125] In this embodiment, the slave machine can determine, based on a parameter version identifier comparison algorithm, that the parameter version identifier of the parameter synchronization frame is newer than its own parameter version identifier, indicating that the device setting parameters of the power supply system have changed, and the slave machine synchronizes the device setting parameters and device read-only parameters of its own device.
[0126] In some embodiments, the slave is used to synchronize device read-only parameters based on device synchronization parameters of the parameter synchronization frame when it is determined that the host device identifier of the parameter synchronization frame matches its own host device identifier and the parameter version identifier of the parameter synchronization frame is not updated compared to its own parameter version identifier.
[0127] In this embodiment, the slave machine can determine, based on the parameter version identifier comparison algorithm, that the parameter version identifier of the parameter synchronization frame is not updated compared to its own parameter version identifier, indicating that the device setting parameters of the power supply system have not changed, and the slave machine synchronizes the device read-only parameters of its own device.
[0128] For example, if the parameter version identifier is the parameter serial number, Figure 4 As shown, the slave receives the parameter synchronization frame from the host, and determines whether the parameter synchronization frame comes from the host to which the slave device belongs according to the host device identifier. If not, the parameter synchronization frame is discarded.
[0129] The parameter synchronization frame comes from the host to which the slave device belongs, and determines whether the parameter serial number in the parameter synchronization frame is newer than the parameter serial number of the slave device itself.
[0130] If the parameter serial number of the parameter synchronization frame is not updated compared to its own parameter serial number, its own device read-only parameters (RO parameters) are refreshed according to the parameter synchronization frame; if the parameter serial number of the parameter synchronization frame is updated compared to its own parameter serial number, its own device setting parameters (RW parameters) and device read-only parameters (RO parameters) are refreshed according to the parameter synchronization frame.
[0131] It can be understood that the device read-only parameters can be changed in real time. When the slave receives the parameter synchronization frame, regardless of whether the parameter version identifier of the parameter synchronization frame is updated compared to its own parameter version identifier, it synchronizes the device read-only parameters of its own device according to the device synchronization parameters to ensure that the parameters with strong real-time performance can be backed up in time.
[0132] It should be noted that the parameters of the power supply system can be set by the host or the slave, and the host and the slave can also communicate through parameter setting frames.
[0133] In some embodiments, the slave is also used to send a parameter setting frame to the host, and the host is also used to update its own parameters based on the host device identifier, slave device identifier and setting parameter information in the parameter setting frame, and send a parameter synchronization frame corresponding to the parameter setting frame.
[0134] In this embodiment, the slave receives an external signal or instruction, determines that the parameter corresponding to the signal or instruction needs to be synchronized to all power supply devices 100 in the power supply system, and sends a parameter setting frame to the host.
[0135] The parameter setting frame includes a host device identifier, a slave device identifier and setting parameter information, and the setting parameter information is information about parameters that need to be synchronized in the power supply system.
[0136] When receiving the parameter setting frame, the host determines whether the parameter setting frame is sent by its own slave according to the host device identification and the slave device identification of the parameter setting frame.
[0137] In this embodiment, if the host determines that the parameter setting frame is sent by its own slave, the host updates its own parameters according to the setting parameter information in the parameter setting frame, and broadcasts a parameter synchronization frame corresponding to the parameter setting frame, so that all power supply devices 100 in the power supply system can perform parameter synchronization.
[0138] It is understandable that the external input received by the host and the slave can be through a parameter synchronization frame or a parameter setting frame, so that all power supply devices 100 in the power supply system can quickly complete the acquisition of external signals and parameter synchronization.
[0139] For example, Figure 5 As shown, any power supply device 100 of the power supply system receives an external signal.
[0140] The external signal may be an input signal of an external port of the power supply system or a setting signal sent by the cloud 230 .
[0141] The power supply device 100 determines whether all devices in the system need to synchronize parameters according to the external signal. If synchronization is not necessary, the power supply device 100 sets its own parameters.
[0142] When full synchronization is required, if the power supply device 100 is a host, the host broadcasts a parameter synchronization frame, and if the power supply device 100 is a slave, the slave sends a parameter setting frame to the host.
[0143] In the related art, when the core control unit is damaged, fails or replaced, user configuration parameters and device operation data are easily lost, the power supply device will also lose control and stop working, and the replacement of the core control unit is difficult to implement and the engineering complexity is high.
[0144] In an embodiment of the present application, when the host machine of the power supply system is damaged or unable to work, other slave machines can quickly switch to the host machine and continue to control the operation of each power supply device 100 of the power supply system according to the real-time synchronized parameters to ensure the stable operation of the power supply system.
[0145] In some embodiments, multiple power supply devices 100 include at least two first power supply devices that determine themselves as hosts, different first power supply devices sense each other by requesting heartbeat frames, different first power supply devices set parameters through parameter synchronization frames, and at least two first power supply devices compete with each other as a master and a slave to determine a host of the power supply system.
[0146] The first power supply device is a power supply device 100 that confirms itself as a host of the power supply system.
[0147] In this embodiment, there are at least two first power supply devices in the power supply system, one of which is the original host of the power supply system, and the other first power supply device is the host to which the power supply system switches subsequently. When there is more than one host in the power supply system, these first power supply devices need to compete between the master and the slave to elect a host of the power supply system.
[0148] It is understandable that the request heartbeat frame is a frame sent by the host. When a first power supply device serving as a host receives a request heartbeat frame, it indicates that in addition to itself, the power supply system also includes other hosts, and different first power supply devices sense each other through the request heartbeat frame.
[0149] It should be noted that different first power supply devices sense each other by requesting heartbeat frames. Before the master-slave competition, different first power supply devices set parameters through parameter synchronization frames. Different first power supply devices are synchronized to the same parameters, which makes it easier for the subsequently elected host to directly control the slave according to the synchronized parameters.
[0150] In some embodiments, the first power supply device is configured to perform its own parameter settings according to the received parameter synchronization frame when the parameter version identifier of the received parameter synchronization frame is newer than its own parameter version identifier.
[0151] In this embodiment, after receiving the parameter synchronization frame, the first power supply device can determine whether the parameter version identifier of the parameter synchronization frame is newer than its own parameter version identifier based on the parameter version identifier comparison algorithm. When the parameter version identifier of the received parameter synchronization frame is newer than its own parameter version identifier, it indicates that there are unupdated parts of its own parameters. In this case, the parameters of its own device are updated according to the device synchronization parameters of the parameter synchronization frame.
[0152] When the parameter version identifier of the received parameter synchronization frame is not updated compared to the own parameter version identifier, it indicates that the own parameters are the latest synchronized parameters, and there is no need to update the parameters of the own device according to the device synchronization parameters of the parameter synchronization frame.
[0153] In some embodiments, the first power supply device is configured to send a parameter synchronization frame corresponding to its own parameters when the parameter version identifier of the received parameter synchronization frame or the request heartbeat frame is not updated compared to its own parameter version identifier.
[0154] In this embodiment, when the parameter version identifier of the parameter synchronization frame or the request heartbeat frame received by the first power supply device is not updated compared to its own parameter version identifier, it indicates that the device sending the parameter synchronization frame or the request heartbeat frame has some unupdated parameters. The first power supply device sends a parameter synchronization frame corresponding to its own parameters to enable the device with some unupdated parameters to update the parameters.
[0155] For example, the first power supply device C receives a request heartbeat frame E from the first power supply device D. The first power supply device C determines that the parameter version identifier of the request heartbeat frame E is not updated compared to its own parameter version identifier. Then the first power supply device C sends a parameter synchronization frame F corresponding to its own parameters, and the first power supply device D performs parameter synchronization update according to the parameter synchronization frame F.
[0156] In some embodiments, when the parameter version identifiers of the parameter synchronization frames or heartbeat request frames received by at least two first power supply devices are the same as their own parameter version identifiers, at least two first power supply devices perform master-slave competition to determine a host of the power supply system.
[0157] In this embodiment, the parameter version identifiers of the parameter synchronization frames or heartbeat request frames received by all the first power supply devices in the power supply system are the same as their own parameter version identifiers, indicating that the parameters of all the first power supply devices have been synchronized. At this time, the master-slave competition procedure is entered, and a host in the power supply system is selected according to the preset master-slave competition rules.
[0158] It should be noted that when the parameter version identifier of the parameter synchronization frame or the heartbeat request frame received by the first power supply device is different from its own parameter version identifier, the first power supply device determines the parameters to be synchronized by comparing the parameter version identifiers of the parameter synchronization frame and performs parameter synchronization.
[0159] A specific implementation example is described below by taking the parameter version identifier as the parameter serial number as an example.
[0160] like Figure 6 As shown, there are host 1 and host 2 in the power supply system.
[0161] Step 610: Host 2 sends a request heartbeat frame, and host 1 receives the request heartbeat frame. Host 1 determines that there are two hosts in the system.
[0162] In this step, host 1 determines the size of the parameter serial number of the received request heartbeat frame and its own parameter serial number. When host 1's own parameter serial number is greater than the corresponding parameter serial number of host 2, host 1 sends a parameter synchronization frame.
[0163] When the parameter serial number of host 1 itself is small, host 1 continues to wait for the parameter synchronization frame sent by host 2.
[0164] Step 620: Host 1 sends a parameter synchronization frame, and host 2 receives the parameter synchronization frame.
[0165] In this step, host 2 processes the parameter synchronization frame. Host 2 determines the size of the parameter serial number of the received parameter synchronization frame and its own parameter serial number. If the parameter serial number of host 2 is small, it synchronizes according to the parameter synchronization frame sent by host 1. If the parameter serial number of host 2 is large, no operation is performed.
[0166] Step 630: Perform master-slave competition.
[0167] In this step, host 1 and host 2 complete parameter synchronization through parameter synchronization frames, perform master-slave competition according to the master-slave competition strategy, and elect a host of the system to continue to keep the host program working, while other devices switch to slave program working.
[0168] In the embodiment of the present application, any power supply device 100 of the power supply system can be used as a control core. If the current host is damaged or needs to be replaced, the hosts can sense each other by requesting heartbeat frames and performing parameter synchronization through parameter synchronization frames. The control core can be quickly switched to continue controlling the power supply system, without data loss and without shutdown during switching.
[0169] In some embodiments, the host has a first timing module, which is used to generate a first random duration and time the first random duration to trigger the host to send one of a parameter synchronization frame and a heartbeat request frame.
[0170] The first timing module may be a software timer or a timer using a real-time clock (RTC) hardware structure.
[0171] In this embodiment, the first random duration is generated by the first timing module, and the host sends a parameter synchronization frame or a request heartbeat frame according to the first random duration, which can increase the randomness of communication frame sending and reduce the backlog of network messages in a short period of time.
[0172] For example, the first timing module may generate the first random duration according to the following formula.
[0173] t1=a*(1-rand(0.01,0.1))
[0174] Wherein, t1 is the first random duration, a is a fixed value (for example, 10 seconds), and rand(0.01,0.1) represents a random number from 0.01 to 0.1.
[0175] In some embodiments, when a device setting parameter of the power supply system is changed within a first random duration, the first timing module times the first random duration to trigger the host to send a parameter synchronization frame.
[0176] In some embodiments, when the equipment setting parameters of the power supply system are not changed within the first random duration, the first timing module times the first random duration to trigger the host to send a request heartbeat frame.
[0177] In this embodiment, a first random duration is generated by a first timing module, and the host selects to send a parameter synchronization frame or a heartbeat request frame according to whether a device setting parameter of the power supply system is changed within the first random duration.
[0178] When the equipment setting parameters of the power supply system are changed, the host sends a parameter synchronization frame with a longer frame length. This can reduce the communication volume, avoid network congestion, and ensure signal transmission stability while ensuring real-time synchronization of system parameters.
[0179] In some embodiments, the slave has a second timing module, which is used to generate a second random duration and perform timing when the slave receives a request heartbeat frame. The second timing module is used to time the second random duration to trigger the slave to feedback a response heartbeat frame.
[0180] The second timing module may be a software timer or a timer using a real-time clock (RTC) hardware structure.
[0181] In actual implementation, the second timing module can generate the second random duration according to the following formula.
[0182] t2=b*(1-rand(0,1))
[0183] Wherein, t2 is the second random duration, b is a fixed value (for example, 5 seconds), and rand(0,1) represents a random number from 0 to 1.
[0184] In this embodiment, a second random duration is generated by a second timing module. After the slave receives a request heartbeat frame, the request heartbeat frame is processed to determine whether a response heartbeat frame needs to be fed back. When a response frame needs to be fed back, the timing of the second random duration begins. When the timing is up, the slave feeds back a response heartbeat frame to increase randomness and prevent network congestion caused by high concurrency heartbeat frame messages at the same time.
[0185] For example, if the parameter version identifier is the parameter serial number, Figure 3As shown, when the slave receives the request heartbeat frame from the host, it first determines whether it is the host to which its own device belongs based on the host device identifier, and discards it if not.
[0186] If so, continue to judge its own parameter serial number and the parameter serial number in the request heartbeat frame. The parameter serial number in the request heartbeat frame is greater than its own parameter serial number, that is, the parameter serial number in the request heartbeat frame is updated compared to its own parameter serial number. Based on a fixed time as a benchmark, add 10% of the timing disturbance time to start the timer (the second timing module). After the timer expires, reply to the host response heartbeat frame.
[0187] In this embodiment, the parameter serial number in the request heartbeat frame is greater than the own parameter serial number, and the slave machine replies to the master machine with the synchronization request identifier in the response heartbeat frame as requesting synchronization.
[0188] In the embodiment of the present application, the host and the slave confirm each other through requesting heartbeat frames and responding to heartbeat frames. The host broadcasts parameter synchronization frames to update parameters. Various parameters can be backed up in real time. When the host is damaged, fails or replaced, a new host can be quickly switched to ensure the stability of the power supply system operation and avoid the loss of system parameters.
[0189] The following uses the parameter version identifier as the parameter serial number as an example to specifically introduce the process of performing operations on the host.
[0190] like Figure 2 As shown, after the networking is completed, the master and slave machines of the power supply system are determined.
[0191] When the host receives the user parameter setting command, it sets its own parameters, increases the parameter serial number by one, and broadcasts the parameter synchronization frame.
[0192] After broadcasting the parameter synchronization frame, the host adds the timing disturbance time based on the fixed time and starts the timer for timing. During the timing process, if the parameter changes, the host broadcasts the parameter synchronization frame. If the parameter does not change, the host broadcasts a request heartbeat frame.
[0193] After the host broadcasts a request heartbeat frame, it receives a response heartbeat frame from the slave, determines whether the slave requests parameter synchronization based on the synchronization request identifier of the response heartbeat frame, and determines whether it is its own slave device based on the master-slave device identifier of the response heartbeat frame.
[0194] If the current host receives a parameter synchronization frame or a heartbeat request frame from another host, and there are multiple hosts in the system, the current host determines whether its own parameter serial number is greater than the parameter serial number of the received frame.
[0195] If the current host's own parameter serial number is greater than the parameter serial number of the received frame, the current host broadcasts a parameter synchronization frame; if the current host's own parameter serial number is greater than or equal to the parameter serial number of the received frame, the current host determines whether the received frame is a parameter synchronization frame.
[0196] The frame received by the current host is a parameter synchronization frame, and the parameter synchronization frame is processed to synchronize the parameter serial number, RW parameter and RO parameter; the frame received by the current host is not a parameter synchronization frame, and the parameter synchronization frame received from another host is obtained to perform parameter synchronization.
[0197] After the parameters of the current host and another host are synchronized, the master-slave competition is carried out according to the master-slave competition strategy.
[0198] For the current host, if it is a slave after the competition, it switches itself to a slave; if it is still the master after the competition, it sends a parameter synchronization frame or a heartbeat request frame at a random time according to the host process.
[0199] In this embodiment, the parameters of the power supply system can be synchronized in real time to ensure that the parameters are not lost. When the host is damaged and cannot work, other power supply devices 100 can quickly switch to the host for control.
[0200] The interaction of the power supply system is described in detail below.
[0201] like Figure 7 As shown, the power supply system includes a plurality of power supply devices 100 , and the plurality of power supply devices 100 are communicatively connected.
[0202] Step 710: Network communication.
[0203] After multiple power supply devices 100 are networked, a master-slave election can be conducted through a preset master-slave election mechanism to elect one power supply device 100 in the power supply system as the master and the other power supply devices 100 as slaves.
[0204] Step 720: The host sends a request heartbeat frame.
[0205] In this step, the host is set with a random timer. When the timer expires and no parameter changes occur, a heartbeat request frame is broadcast.
[0206] Taking the parameter version identifier as the parameter serial number as an example, the slave receives a request heartbeat frame, determines the size of the parameter serial number in the request heartbeat frame, and feeds back a response heartbeat frame to the host based on whether the parameter serial number in the request heartbeat frame is updated compared with its own parameter serial number.
[0207] Step 730: The slave sends a response heartbeat frame to the master.
[0208] After receiving the response heartbeat frame, the host determines whether it is its own slave according to the host device identification and slave device identification of the response heartbeat frame, and determines whether a parameter synchronization frame needs to be sent according to the synchronization request identification of the response heartbeat frame.
[0209] Step 740: The host sends a parameter synchronization frame.
[0210] The host receives the synchronization request mark of the response heartbeat frame as a request for synchronization. When the host timer expires, the parameter synchronization frame is broadcast.
[0211] The slave processes the parameter synchronization frame, determines whether it is the host to which it belongs according to the host device identification of the parameter synchronization frame, and determines whether to update the RO parameter, or update the RO parameter and the RW parameter according to whether the parameter serial number of the parameter synchronization frame is updated.
[0212] Step 750: The user sets parameters.
[0213] The host receives a signal from the user to set parameters.
[0214] Step 760: The host updates its own device data, adds a parameter serial number, and broadcasts a parameter synchronization frame. All power supply devices 100 in the power supply system can synchronize the user-set parameters.
[0215] In this embodiment, the host and the slave confirm each other through heartbeat frames, update parameters through parameter synchronization frames, and back up various parameters in real time, effectively avoiding parameter loss.
[0216] The embodiment of the present application also provides a photovoltaic system.
[0217] The photovoltaic system comprises: a photovoltaic component and the power supply system as described above, and the photovoltaic component is electrically connected to the power supply system.
[0218] The photovoltaic module can convert light energy into electrical energy and input it into the power supply device 100 of the power supply system. The power supply device 100 can perform AC / DC conversion and voltage conversion on the input electrical energy.
[0219] According to the photovoltaic system provided in the embodiment of the present application, a plurality of power supply devices 100 are communicatively connected, the host and the slave confirm each other through request heartbeat frames and response heartbeat frames, the host broadcasts parameter synchronization frames, and various parameters are backed up in real time in each power supply device 100 of the power supply system, thereby effectively avoiding parameter loss.
[0220] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.
[0221] Although the embodiments of the present application have been shown and described, those skilled in the art will appreciate that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present application, and that the scope of the present application is defined by the claims and their equivalents.
Claims
1. A power supply system, characterized in that: include: A plurality of power supply devices, the plurality of power supply devices are communicatively connected with each other, and the plurality of power supply devices are used to perform a master-slave election to determine a master and a slave of a power supply system; The host is used to send a parameter synchronization frame to the slave, and the slave performs parameter setting of the slave itself based on the host device identifier, the device synchronization parameter and the parameter version identifier corresponding to the device synchronization parameter in the parameter synchronization frame; The host is used to send a request heartbeat frame to the slave, and the slave feeds back a response heartbeat frame to the host based on the host device identifier and parameter version identifier in the request heartbeat frame. The host is used to determine whether the host sends the parameter synchronization frame to the slave based on the host device identifier, slave device identifier and synchronization request identifier in the response heartbeat frame.
2. The power supply system according to claim 1, characterized in that: The host is used to send the parameter synchronization frame when the device setting parameters of the power supply system are changed.
3. The power supply system according to claim 1, characterized in that: The host is used to send the parameter synchronization frame when the synchronization request identifier in the received response heartbeat frame is a synchronization request.
4. The power supply system according to claim 3, characterized in that: The slave is used to feed back to the host the response heartbeat frame with the synchronization request identifier as requesting synchronization when it is determined that the host device identifier of the received request heartbeat frame matches its own host device identifier and when it is determined according to a parameter version identifier comparison algorithm that the parameter version identifier of the request heartbeat frame is newer than its own parameter version identifier.
5. The power supply system according to claim 3, characterized in that: When the timing duration of receiving the parameter synchronization frame reaches the first timing duration, the slave sends the response heartbeat frame to the host.
6. The power supply system according to claim 1, characterized in that: The host sends one of the parameter synchronization frame and the request heartbeat frame at a first time interval.
7. The power supply system according to claim 1, characterized in that: When the slave does not receive the parameter synchronization frame or the duration of the request heartbeat frame is greater than the second duration threshold, the slave sends the parameter synchronization frame based on its own parameters.
8. The power supply system according to claim 1, characterized in that: The slave is used to synchronize device setting parameters and device read-only parameters based on the device synchronization parameters of the parameter synchronization frame when it is determined that the host device identifier of the parameter synchronization frame matches its own host device identifier and the parameter version identifier of the parameter synchronization frame is newer than its own parameter version identifier.
9. The power supply system according to claim 1, characterized in that: The slave is used to synchronize device read-only parameters based on device synchronization parameters of the parameter synchronization frame when it is determined that the host device identifier of the parameter synchronization frame matches its own host device identifier and the parameter version identifier of the parameter synchronization frame is not updated compared to its own parameter version identifier.
10. The power supply system according to claim 1, characterized in that: The slave is further used to send a parameter setting frame to the host, and the host is further used to update its own parameters based on the host device identification, slave device identification and setting parameter information in the parameter setting frame, and send the parameter synchronization frame corresponding to the parameter setting frame.
11. The power supply system according to claim 1, characterized in that: The multiple power supply devices include at least two first power supply devices that determine themselves as the host. Different first power supply devices sense each other through the request heartbeat frame, and different first power supply devices set parameters through the parameter synchronization frame. The at least two first power supply devices perform master-slave competition to determine one of the hosts of the power supply system.
12. The power supply system according to claim 11, characterized in that: The first power supply device is configured to perform its own parameter settings according to the received parameter synchronization frame when the parameter version identifier of the received parameter synchronization frame is newer than its own parameter version identifier.
13. The power supply system according to claim 11, characterized in that: The first power supply device is used for sending the parameter synchronization frame corresponding to its own parameters when the parameter version identifier of the received parameter synchronization frame or the request heartbeat frame is not updated compared with its own parameter version identifier.
14. The power supply system according to claim 11, characterized in that: When the parameter version identifiers of the parameter synchronization frames or the request heartbeat frames received by the at least two first power supply devices are the same as their own parameter version identifiers, the at least two first power supply devices perform master-slave competition to determine one of the hosts of the power supply system.
15. The power supply system according to any one of claims 1 to 14, characterized in that: The host has a first timing module, which is used to generate a first random duration and time the first random duration to trigger the host to send one of the parameter synchronization frame and the request heartbeat frame.
16. The power supply system according to claim 15, characterized in that: When a device setting parameter of the power supply system is changed within the first random duration, the first timing module times the first random duration to trigger the host to send the parameter synchronization frame; When the equipment setting parameters of the power supply system are not changed within the first random duration, the first timing module times the first random duration to trigger the host to send the request heartbeat frame.
17. The power supply system according to any one of claims 1 to 14, characterized in that: The slave has a second timing module, which is used to generate a second random duration and perform timing when the slave receives the request heartbeat frame. The second timing module is used to time the second random duration to trigger the slave to feed back the response heartbeat frame.
18. The power supply system according to any one of claims 1 to 14, characterized in that: When the parameter synchronization frame sent by the host does not have a slave device identifier, the slave in the power supply system that receives the parameter synchronization frame sets its own parameters based on the host device identifier, device synchronization parameters, and parameter version identifier corresponding to the device synchronization parameters in the parameter synchronization frame.
19. The power supply system according to any one of claims 1 to 14, characterized in that: In the case where the parameter synchronization frame sent by the host has a slave device identification, the slave is used to set its own parameters based on the host device identification, device synchronization parameters and parameter version identification corresponding to the device synchronization parameters in the parameter synchronization frame when it is determined that the slave device identification of the parameter synchronization frame matches its own slave device identification.
20. A photovoltaic system, characterized in that: include: A photovoltaic component and a power supply system as described in any one of claims 1 to 19, wherein the photovoltaic component is electrically connected to the power supply system.