Inverter and main controller of photovoltaic power generation system and operation method of inverter and main controller

Abstract

An inverter and a master controller of a photovoltaic power generation system, and a method of operating a photovoltaic power generation system are provided. The method of operating a photovoltaic power generation system may include: assigning identification information to each of a plurality of component level power electronics (MLPEs) based on a registration request from each of the plurality of MLPEs connected to a plurality of photovoltaic panels; monitoring the plurality of MLPEs, and determining whether a fault has occurred in the plurality of MLPEs based on a monitoring result; and when determining that at least one MLPE in the plurality of MLPEs has failed, marking a failure mark on the identification information of the at least one MLPE.

Description

Technical Field

[0001] This application relates to an inverter and main controller for a photovoltaic power generation system, as well as a method for operating a photovoltaic power generation system, designed to facilitate the replacement management of module-level power electronics (MLPEs) connected to photovoltaic panels. Background Technology

[0002] A photovoltaic power generation system may include module-level power electronic devices (hereinafter referred to as MLPE) attached to a photovoltaic panel and a main controller.

[0003] The MLPE sends monitoring information, including the power generation and temperature of the photovoltaic panel, to the main controller, enabling the main controller to identify the power generation status.

[0004] When a fault occurs in an MLPE, the MLPE needs to be replaced. In this case, in order for the main controller to recognize the new MLPE, the administrator needs to manually delete the information of the faulty MLPE from the main controller and enter the information of the new MLPE, which is inconvenient. Summary of the Invention

[0005] The purpose of this application is to: when at least one of a plurality of registered component-level power electronic devices (MLPEs) (or photovoltaic panels) fails, use a fault flag to mark the identification information of the failed MLPE, and when a signal from a new MLPE (e.g., a registration request or unique information of the new MLPE) is received, assign the identification information marked with the fault flag as the identification information of the new MLPE, thereby realizing the automatic registration of the new MLPE.

[0006] The purpose of this application is to generate and output a replacement notification when at least one of a plurality of registered MLPEs (or photovoltaic panels) frequently fails, thereby enabling managers to easily identify the timing of replacement.

[0007] According to one aspect of this application, a method for operating a photovoltaic power generation system is provided, the method comprising: assigning identification information to each of the plurality of MLPEs based on a registration request from each of the plurality of component-level power electronic devices (MLPEs) connected to a plurality of photovoltaic panels; monitoring the plurality of MLPEs and determining, based on the monitoring results, whether a fault has occurred in the plurality of MLPEs; and marking a fault flag on the identification information of at least one MLPE when it is determined that a fault has occurred in at least one of the plurality of MLPEs.

[0008] In this application, determining whether a fault has occurred in a plurality of MLPEs may include: periodically receiving monitoring information from each of the plurality of MLPEs; and determining that a fault has occurred in at least one MLPE when no monitoring information is received from at least one MLPE for a first set number of times or more.

[0009] In this application, the method may further include: periodically requesting monitoring information from at least one MLPE that has failed; and when the number of monitoring information received from at least one MLPE that has failed reaches or exceeds a second set number, removing the fault flag marked on the identification information of the at least one MLPE that has failed.

[0010] In this application, determining whether a fault has occurred in a plurality of MLPEs may include: periodically receiving monitoring information from each of the plurality of MLPEs, the monitoring information including: unique information for each MLPE, and a measurement value of at least one of voltage, current, power generation and temperature for each of the plurality of photovoltaic panels; and determining that a fault has occurred in at least one MLPE associated with the measurement value when the measurement value deviates from a preset range.

[0011] In this application, the method may further include: counting the fault history associated with the identification information of at least one MLPE that has failed; and generating and outputting a replacement notification for the at least one MLPE that has failed when the fault history exceeds a set value.

[0012] In this application, the method may further include: when a registration request is received from a new MLPE, assigning the identification information of at least one MLPE marked with a fault flag as the identification information of the new MLPE.

[0013] According to another aspect of this application, a main controller for a photovoltaic power generation system is provided, the main controller comprising: a communication unit and a processor. The communication unit is configured to: receive a registration request from each of a plurality of component-level power electronic devices (MLPEs) connected to a plurality of photovoltaic panels. The processor is configured to: assign identification information to each of the plurality of MLPEs based on the registration request; determine whether a fault has occurred in any of the plurality of MLPEs based on monitoring results of the plurality of MLPEs; and when it is determined that a fault has occurred in at least one of the plurality of MLPEs, mark a fault flag on the identification information of at least one MLPE.

[0014] In this application, the processor may also be configured to: periodically receive monitoring information from each of a plurality of MLPEs via a communication unit; and determine that a fault has occurred in at least one MLPE when no monitoring information is received from at least one MLPE for a first set number of times or more.

[0015] In this application, the processor may also be configured to: periodically request monitoring information from at least one MLPE that has failed via a communication unit; and when the number of monitoring information received from at least one MLPE that has failed reaches or exceeds a second set number, remove the fault flag marked on the identification information of at least one MLPE that has failed.

[0016] In this application, the processor may also be configured to: periodically receive monitoring information from each of the plurality of MLPEs via a communication unit, the monitoring information including: unique information of each MLPE, and a measurement value of at least one of voltage, current, power generation and temperature of each of the plurality of photovoltaic panels; and when the measurement value deviates from a preset range, determine that a fault has occurred in at least one MLPE associated with the measurement value.

[0017] In this application, the processor can also be configured to: count the fault history associated with the identification information of at least one MLPE that has failed; and when the fault history exceeds a set value, generate and output a replacement notification for the at least one MLPE that has failed.

[0018] In this application, the processor can also be configured to: when a registration request is received from a new MLPE, assign the identification information of at least one MLPE marked with a fault flag as the identification information of the new MLPE.

[0019] According to another aspect of this application, an inverter for a photovoltaic power generation system is provided, the inverter comprising: a processor and a memory, the memory being operatively connected to the processor and configured to store at least one code executed by the processor, wherein the processor is configured to: receive a registration request from each of a plurality of component-level power electronic devices (MLPEs) connected to a plurality of photovoltaic panels; assign identification information to each of the plurality of MLPEs based on the registration request; determine whether a fault has occurred in the plurality of MLPEs based on the results of monitoring the plurality of MLPEs; and when it is determined that a fault has occurred in at least one of the plurality of MLPEs, mark a fault flag on the identification information of the at least one MLPE.

[0020] In this application, the processor can also be configured to: periodically receive monitoring information from each of a plurality of MLPEs; and determine that a fault has occurred in at least one MLPE when no monitoring information is received from at least one MLPE for a first set number of times or more.

[0021] In this application, the processor may also be configured to: periodically request monitoring information from at least one MLPE that has failed; and when the number of monitoring information received from at least one MLPE that has failed reaches or exceeds a second set number, remove the fault flag marked on the identification information of the at least one MLPE that has failed.

[0022] In this application, the processor may also be configured to: periodically receive monitoring information from each of the plurality of MLPEs, the monitoring information including: unique information of each MLPE, and a measurement value of at least one of voltage, current, power generation and temperature of each of the plurality of photovoltaic panels; and when the measurement value deviates from a preset range, determine that a fault has occurred in at least one MLPE associated with the measurement value.

[0023] In this application, the processor can also be configured to: count the fault history associated with the identification information of at least one MLPE that has failed; and when the fault history exceeds a set value, generate and output a replacement notification for the at least one MLPE that has failed.

[0024] In this application, the processor can also be configured to: when a registration request is received from a new MLPE, assign the identification information of at least one MLPE marked with a fault flag as the identification information of the new MLPE. Attached Figure Description

[0025] The above and other aspects, features, and advantages of certain embodiments of this application will become more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0026] Figure 1 This is a configuration diagram illustrating an example of a photovoltaic power generation system according to an embodiment of this application;

[0027] Figure 2 This is a configuration diagram illustrating another example of a photovoltaic power generation system according to an embodiment of this application;

[0028] Figure 3 This is a configuration diagram illustrating an example of a main controller included in a photovoltaic power generation system according to an embodiment of this application;

[0029] Figure 4 and Figure 5This is a diagram illustrating an example of the operation of a photovoltaic power generation system according to an embodiment of this application;

[0030] Figure 6 This is a diagram illustrating an example of marking fault flags in a photovoltaic power generation system according to an embodiment of this application;

[0031] Figure 7 This is a flowchart describing a method for operating a photovoltaic power generation system according to embodiments of this application; and

[0032] Figure 8 This is a diagram illustrating the power supply structure of a building equipped with photovoltaic panels for a photovoltaic power generation system, according to an embodiment of this application. Detailed Implementation

[0033] Although the terminology used in the embodiments has been selected as much as possible from currently widely used general terms, these terms may vary depending on the intent of those skilled in the art, precedents, or the emergence of new technologies. Furthermore, the applicant may arbitrarily choose terms in specific circumstances, in which case the meaning of these terms will be described in detail in the relevant sections. Therefore, the terms used in this application should be defined according to their meaning and the entirety of the specification, rather than solely based on their names.

[0034] Unless otherwise expressly stated, throughout the specification, when a section is referred to as "including" a component, it means that the section may also include other components, but does not exclude other components.

[0035] Furthermore, the terms containing ordinal numbers (such as "first" or "second") used in this specification may be used to describe various components, but the components are not limited by these terms, and the purpose of these terms is solely to distinguish different components. That is, these terms are only used to differentiate one component from another.

[0036] The embodiments will now be described in detail with reference to the accompanying drawings. However, these embodiments can be implemented in various different forms and are not limited to those described below.

[0037] Figure 1 This is a configuration diagram illustrating an example of a photovoltaic power generation system according to an embodiment of this application. Figure 2 This is a configuration diagram illustrating another example of a photovoltaic power generation system according to an embodiment of this application.

[0038] like Figure 1As shown, according to one embodiment of this application, a photovoltaic power generation system 1 may include: a plurality of photovoltaic panels 10, an inverter 400 including a main controller 100, a plurality of module-level power electronic devices (MLPEs) 200, and a server 300. Alternatively, such as Figure 2 As shown, according to another embodiment of this application, a photovoltaic power generation system may include: a plurality of photovoltaic panels 10, a main controller 100, a plurality of MLPEs 200, an inverter 400, and a server 300.

[0039] In other words, such as Figure 1 As shown, a photovoltaic power generation system according to one embodiment can be configured such that the inverter 400 includes a main controller 100, and alternatively, such as Figure 2 As shown, a photovoltaic power generation system according to another embodiment can be configured such that an inverter 400 is located between the main controller 100 and the power grid 20. Here, the inverter 400 can convert direct current (DC) power generated by multiple photovoltaic panels 10 into alternating current (AC) power and send the converted AC power to the power grid 20.

[0040] For ease of description, the following will be described as follows: Figure 1 The embodiment shown, in which the inverter 400 includes a main controller 100, is described as an example. Furthermore, in the following description, multiple photovoltaic panels 10 and multiple MLPEs 200 will be described together; however, the photovoltaic panels 10 and MLPEs 200 can also be separate from each other and can be configured as different types or models.

[0041] According to an embodiment, each of the plurality of photovoltaic panels 10 can refer to a photovoltaic power generation panel in a module unit. Furthermore, the plurality of photovoltaic panels 10 can be connected in at least one manner, either in series or in parallel, and each of the plurality of MLPEs 200 is provided for each of the plurality of photovoltaic panels 10. Additionally, one MLPE 200 can be connected to one photovoltaic panel 10, or one MLPE 200 can be connected to multiple photovoltaic panels 10.

[0042] In one embodiment, the MLPE 200 can send monitoring information (including at least one of the following: voltage, current, power generation, temperature, and fault information of the photovoltaic panel 10) and unique information of the MLPE 200 (e.g., serial number) to the main controller 100. Furthermore, the MLPE 200 can receive operating signals from the main controller 100 for optimizing power efficiency.

[0043] According to an embodiment of this application, the MLPE 200 is a component that is connected to a corresponding photovoltaic panel 10 and configured to optimize the output power (output voltage) of the connected photovoltaic panel 10.

[0044] In this case, such as Figure 1 As shown, the MLPE 200 can be connected one-to-one with the photovoltaic panel 10. However, depending on the structure adopted by the photovoltaic power generation system 1, the MLPE 200 can also be installed in a many-to-one or many-to-many configuration, and the installation form is not limited to any specific configuration.

[0045] According to embodiments of this application, a plurality of MLPEs 200 may be provided, and these MLPEs 200 are connected in series with each other. Furthermore, an inverter 400 or a main controller 100 may be connected to the opposite ends of the plurality of series-connected MLPEs 200.

[0046] According to embodiments of this application, inverter 400 is a component installed in a power conversion system (PCS) and configured to perform power conversion to supply power generated by photovoltaic panel 10 to a load or the power grid. As described above, Figure 1 As shown, inverter 400 may include main controller 100; alternatively, such as Figure 2 As shown, the inverter 400 can be installed separately from the main controller 100. In the following description, for ease of description, it will be referred to as... Figure 1 The embodiment shown, in which the inverter 400 includes the main controller 100, is described with reference to the operation of the inverter 400, which can be understood as the operation of the main controller 100.

[0047] According to an embodiment of this application, the inverter 400 can identify the maximum power point voltage by performing a Maximum Power Point Tracking (MPPT) operation to track the power and voltage of the photovoltaic power generation system 1 when it generates maximum power. MPPT is an algorithm that continuously adjusts the impedance applied to the photovoltaic panel 10 or an array of multiple photovoltaic panels 10 so that the photovoltaic power generation system 1 can operate near the maximum power point when conditions such as solar radiation, ambient temperature, and load change. According to an embodiment of this application, the inverter 400 can control the MLPE 200 to perform MPPT, thereby maximizing the power generation efficiency of the photovoltaic power generation system 1. Furthermore, by analyzing various types of data received from the photovoltaic panel 10, MLPE 200, load, and power grid, the inverter 400 can monitor the operating status.

[0048] In one embodiment, the main controller 100 can output monitoring information received from multiple MLPEs 200, or send the monitoring information to a server 300 (or an administrator terminal), thereby enabling the administrator to identify the status of each MLPE among the multiple MLPEs 200. Here, the transmission and reception of information between the main controller 100 and the server 300 can be achieved via wired or wireless means.

[0049] Multiple MLPEs 200s can send and receive information with the main controller 100 via power line communication (PLC). When using power line communication, the sending and receiving of information between multiple MLPEs 200s and the main controller 100 does not require separate communication cables or wireless communication technology, thus facilitating the installation and maintenance of the photovoltaic power generation system 1.

[0050] Figure 3 This is a configuration diagram illustrating an example of a main controller included in a photovoltaic power generation system according to an embodiment of this application.

[0051] refer to Figure 3 The main controller 100 may include a communication unit 110, a processor 120, and a memory 130.

[0052] The communication unit 110 can communicate with multiple MLPEs connected to multiple photovoltaic panels, or it can communicate with a server (or administrator terminal).

[0053] In one embodiment, the communication unit 110 may receive registration requests from multiple MLPEs connected to multiple photovoltaic panels.

[0054] Furthermore, the communication unit 110 can periodically receive monitoring information from multiple MLPEs, as well as unique information for each MLPE. Here, the monitoring information may include measurements of at least one of the following: voltage, current, power generation, and temperature of the photovoltaic panel.

[0055] The processor 120 can assign identification information to each of the multiple MLPEs based on a registration request; and can determine whether a fault has occurred in each of the multiple MLPEs based on monitoring results for the multiple MLPEs. In one embodiment, the processor 120 can determine that a fault has occurred in the MLPE when no monitoring information is received from the MLPE via the communication unit 110 for a first set number of times or more. In another embodiment, the processor 120 can determine that a fault has occurred in the MLPE associated with the measured value when the measured value (such as the voltage, current, power generation, and temperature of the photovoltaic panel) in the monitoring information received via the communication unit 110 deviates from a preset range.

[0056] When a fault is determined to have occurred in at least one of a plurality of MLPEs, the processor 120 may mark a fault flag on the identification information of the MLPE that has failed.

[0057] The processor 120 can periodically request monitoring information from the MLPE that has failed via the communication unit 110; and when the number of monitoring information received from the MLPE that has failed reaches a second set number or exceeds the second set number, the processor 120 can remove the fault flag marked on the identification information of the MLPE that has failed.

[0058] In one embodiment, the processor 120 can count the fault history associated with the identification information of the MLPE that has failed; and when the fault history exceeds a set value, the processor 120 can generate and output a replacement notification for the MLPE that has failed, or send the replacement notification to a server (or administrator terminal), thereby enabling the administrator to easily identify when to replace the MLPE.

[0059] When a registration request is received from a new MLPE, the processor 120 can assign the identification information of the MLPE marked with a fault flag as the identification information of the new MLPE.

[0060] According to one embodiment, processor 120 may be implemented as an array of logic gates, or as a combination of a general-purpose microprocessor and memory storing a program executable by the microprocessor. For example, processor 120 may include a general-purpose processor, a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a controller, a microcontroller, a state machine, etc. In some environments, processor 120 may include an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a field-programmable gate array (FPGA), etc. For example, processor 120 may refer to a combination of processing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors incorporating a DSP core, or any other combination of such configurations.

[0061] The memory 130 is hardware that stores various types of data processed within the main controller 100. The memory is operatively connected to the processor 120 and can store programs for processing and control by the processor 120.

[0062] The memory 130 may include: random access memory (RAM) such as dynamic random access memory (DRAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact disk ROM (CD-ROM), Blu-ray or other optical disc storage devices, hard disk drive (HDD), solid state drive (SSD), or flash memory.

[0063] Figure 4 and Figure 5 This is a diagram illustrating an example of the operation of a photovoltaic power generation system according to an embodiment of this application.

[0064] refer to Figure 4 When the main controller 100 receives a registration request from each of the n MLPEs (i.e., the first MLPE 200_#1 to the nth MLPE 200_#n) connected to n photovoltaic panels (i.e., the first photovoltaic panel 10_#1 to the nth photovoltaic panel 10_#n), it can assign identification information to each of the n MLPEs (200_#1 to 200_#n). Here, for example, the n MLPEs (200_#1 to 200_#n) can be connected to the n photovoltaic panels (10_#1 to 0_#n) via a wired connection, and the n MLPEs (200_#1 to 200_#n) can be connected to the main controller 100 via a wireless connection.

[0065] In one embodiment, the main controller 100 may randomly or in the order of received registration requests assign identification information to each of the n MLPEs (200_#1 to 200_#n). The photovoltaic power generation system can extract the unique information of the MLPE from the registration request and store the identification information assigned to that MLPE in association with the unique information in a memory.

[0066] The main controller 100 can monitor the first MLPE 200_#1 to the nth MLPE 200_#n, and as Figure 5 As shown, when it is determined from monitoring results that the first MLPE 200_#1 and the (n-2)th MLPE 200_#n-2 (or the first photovoltaic panel and the (n-2)th photovoltaic panel) have failed, the main controller 100 can mark a fault flag on the first identification information assigned to the first MLPE 200_#1, and mark a fault flag on the (n-2)th identification information assigned to the (n-2)th MLPE 200_#n-2. Here, the fault flag can be, for example, a character, symbol, etc., indicating a fault. In one embodiment, such as... Figure 6 As shown, by recording the character "E" 610 in the memory and associating the character with each of the first identification information of the first MLPE 200_#1 and the (n-2)th identification information of the (n-2)th MLPE 200_#n-2, the main controller 100 can mark the fault flag.

[0067] Figure 7 This is a flowchart describing a method for operating a photovoltaic power generation system according to an embodiment of this application. Here, the method for operating the photovoltaic power generation system can be executed by the main controller (or inverter) of the photovoltaic power generation system.

[0068] refer to Figure 7 In operation S110, based on the registration requests received from multiple MLPEs connected to multiple photovoltaic panels, the main controller can assign identification information to each of the multiple MLPEs.

[0069] In operation S120, the main controller can monitor multiple MLPEs and determine whether a fault has occurred in any of the multiple MLPEs based on the monitoring results.

[0070] In one embodiment, the main controller can periodically receive monitoring information from each of the multiple MLPEs, and when no monitoring information is received from an MLPE for a first set number of times or more, the main controller can determine that a fault has occurred in that MLPE.

[0071] In another embodiment, the main controller can periodically receive monitoring information from each of the multiple MLPEs, including: unique information for each MLPE, and a measurement of at least one of the following: voltage, current, power generation, and temperature of the photovoltaic panel. When a measurement deviates from a preset range, the main controller can determine that a fault has occurred in the MLPE associated with that measurement.

[0072] In operation S130, when it is determined that a fault has occurred in at least one of the multiple MLPEs, in operation S140, the main controller can mark a fault flag on the identification information of the MLPE that has failed.

[0073] In operation S130, when it is determined that at least one of the multiple MLPEs has not failed, the main controller can proceed to operation S120 and monitor the multiple MLPEs.

[0074] In one embodiment, the main controller can periodically request monitoring information from the MLPE that has failed; and when the number of monitoring information received from the MLPE that has failed reaches a second set number or exceeds the second set number, the main controller can remove the fault flag marked on the identification information of the MLPE that has failed.

[0075] The main controller can count the fault history associated with the identification information of the MLPE that has failed; and when the fault history exceeds a set value, the main controller can generate and output a replacement notification for the MLPE that has failed.

[0076] In operation S150, when a registration request is received from a new MLPE, the main controller can assign the identification information of the MLPE marked with a fault flag as the identification information of the new MLPE.

[0077] Figure 8 This is a diagram illustrating the power supply structure of a building equipped with photovoltaic panels for a photovoltaic power generation system, according to an embodiment of this application.

[0078] refer to Figure 8 The photovoltaic panel (or photovoltaic module) 2 can be installed on the roof of the building 800 and generate energy.

[0079] The photovoltaic inverter (or main controller) 6 can convert the energy generated by the photovoltaic panel 2 and supply the generated electricity to the building 800.

[0080] In one embodiment, commercial electricity supplied via utility pole 3 can be provided to the building via transformer 4.

[0081] By selectively receiving at least one of commercial electricity and electricity generated by photovoltaic panels 2, multiple household appliances 7 can be operated. Electricity meters 5 can measure the electrical power consumed in the building 800.

[0082] In addition, when a separate Energy Storage System (ESS) is set up, the energy generated by the photovoltaic panel 2 can also be stored in the ESS.

[0083] When multiple photovoltaic panels 2 are connected, a photovoltaic module string can be formed. This photovoltaic module string is a combination of multiple photovoltaic modules and may include a single output terminal.

[0084] In one embodiment, the photovoltaic panel 2 may include or may be connected to an MLPE.

[0085] MLPE can control power conversion based on photovoltaic modules and can include an optimizer to optimize the generated energy. MLPE can include monitoring functions to monitor the status or power generation of photovoltaic panel 2 and send data to external devices.

[0086] In addition, the MLPE may include a Rapid Shutdown (RSD) function to stop the operation of the photovoltaic panel 2 based on the severity of the fault.

[0087] The photovoltaic panel 2 may include a monitoring device or an RSD device, wherein the monitoring device is configured to monitor the status or power generation of the photovoltaic panel 2, and the RSD device is configured to perform a fast shutdown function.

[0088] In addition, at least one of the photovoltaic panels and the MLPE may include a communication module for power line communication.

[0089] According to embodiments of this application, when at least one MLPE (or photovoltaic panel) among multiple registered MLPEs fails, a fault flag can be marked on the identification information of the failed MLPE. When a signal is received from a new MLPE (e.g., a registration request or unique information for the new MLPE), the identification information of the MLPE marked with the fault flag can be assigned as the identification information of the new MLPE, thereby achieving automatic registration of the new MLPE. Therefore, multiple MLPEs can be easily managed by using predetermined identification information, eliminating the need for an administrator to manually register each new MLPE.

[0090] Furthermore, according to embodiments of this application, when at least one MLPE (or photovoltaic panel) among a plurality of registered MLPEs frequently fails, a replacement notification can be generated and output, thereby enabling the administrator to easily identify the timing of the replacement.

[0091] According to embodiments of this application, multiple MLPEs can be easily managed when at least one of the multiple registered MLPEs (or photovoltaic panels) fails.

[0092] It should be understood that the embodiments described in this specification should be considered only in a descriptive sense and not for limiting purposes. The description of features or aspects in each embodiment should generally be regarded as other similar features or aspects that can be used in other embodiments.

[0093] Although one or more embodiments have been described with reference to the accompanying drawings, those skilled in the art will understand that various changes in form and detail may be made therein without departing from the spirit and scope defined by the appended claims.

Claims

1. A method for operating a photovoltaic power generation system, the method comprising: Identification information is assigned to each of the multiple MLPEs based on the registration request from each of the multiple component-level power electronic devices connected to multiple photovoltaic panels; Monitor the multiple MLPEs and determine, based on the monitoring results, whether a fault has occurred in the multiple MLPEs; as well as When it is determined that a fault has occurred in at least one of the plurality of MLPEs, a fault flag is marked on the identification information of the at least one MLPE.

2. The method according to claim 1, wherein, Determining whether a fault has occurred in the plurality of MLPEs includes: periodically receiving monitoring information from each of the plurality of MLPEs; and determining that a fault has occurred in the at least one MLPE when no monitoring information is received from at least one MLPE for a first set number of times or more.

3. The method according to claim 2, further comprising: The monitoring information is periodically requested from at least one of the MLPEs that has failed. as well as When the number of monitoring messages received from at least one MLPE that has already failed reaches or exceeds the second set number, the fault flag marked on the identification information of the at least one MLPE that has already failed is removed.

4. The method according to claim 1, wherein, Determining whether a fault has occurred in any of the plurality of MLPEs includes: Periodically receive monitoring information from each of the plurality of MLPEs, the monitoring information including: unique information for each MLPE, and measurements of at least one of voltage, current, power generation, and temperature for each of the plurality of photovoltaic panels; and When the measured value deviates from the preset range, it is determined that a fault has occurred in at least one MLPE associated with the measured value.

5. The method according to claim 1, further comprising: Count the fault history associated with the identification information of the at least one MLPE that has failed; as well as When the fault history exceeds a set value, a replacement notification is generated and output for at least one MLPE that has failed.

6. The method according to claim 1, further comprising: When a registration request is received from a new MLPE, the identification information of the at least one MLPE marked with the fault flag is assigned as the identification information of the new MLPE.

7. A main controller for a photovoltaic power generation system, the main controller comprising: The communication unit is configured to receive registration requests from each of the multiple component-level power electronic devices (MLPEs) connected to multiple photovoltaic panels; The processor is configured to: assign identification information to each of the plurality of MLPEs based on the registration request; and determine whether a fault has occurred in the plurality of MLPEs based on the monitoring results of the plurality of MLPEs. And when it is determined that a fault has occurred in at least one of the plurality of MLPEs, a fault flag is marked on the identification information of the at least one MLPE.

8. The main controller according to claim 7, wherein, The processor is further configured to: periodically receive monitoring information from each of the plurality of MLPEs via the communication unit; and determine that a fault has occurred in the at least one MLPE when no monitoring information is received from at least one MLPE for a first set number of times or more.

9. The main controller according to claim 8, wherein, The processor is also configured to: The monitoring information is periodically requested from at least one MLPE that has failed via the communication unit. as well as When the number of monitoring messages received from at least one MLPE that has already failed reaches or exceeds the second set number, the fault flag marked on the identification information of the at least one MLPE that has already failed is removed.

10. The main controller according to claim 7, wherein, The processor is also configured to: The communication unit periodically receives monitoring information from each of the plurality of MLPEs, the monitoring information including: unique information for each MLPE, and a measurement value of at least one of voltage, current, power generation, and temperature for each of the plurality of photovoltaic panels; and When the measured value deviates from the preset range, it is determined that a fault has occurred in at least one MLPE associated with the measured value.

11. The main controller according to claim 7, wherein, The processor is also configured to: Count the fault history associated with the identification information of the at least one MLPE that has failed; and When the fault history exceeds a set value, a replacement notification is generated and output for at least one MLPE that has failed.

12. The main controller according to claim 7, wherein, The processor is further configured to: when a registration request is received from a new MLPE, assign the identification information of the at least one MLPE marked with the fault flag as the identification information of the new MLPE.

13. An inverter for a photovoltaic power generation system, the inverter comprising: processor; as well as A memory operatively connected to the processor and configured to store at least one piece of code executed by the processor. The processor is configured to: receive a registration request from each of a plurality of component-level power electronic devices (MLPEs) connected to a plurality of photovoltaic panels; assign identification information to each of the plurality of MLPEs based on the registration request; determine whether a fault has occurred in the plurality of MLPEs based on monitoring results of the plurality of MLPEs; and mark a fault flag on the identification information of the at least one MLPE when it is determined that a fault has occurred in at least one of the plurality of MLPEs.

14. The inverter according to claim 13, wherein, The processor is further configured to: periodically receive monitoring information from each of the plurality of MLPEs; and determine that a fault has occurred in the at least one MLPE when no monitoring information is received from at least one MLPE for a first set number of times or more.

15. The inverter according to claim 14, wherein, The processor is further configured to: periodically request the monitoring information from the at least one MLPE that has failed; and when the number of monitoring information received from the at least one MLPE that has failed reaches or exceeds a second set number, remove the fault flag marked on the identification information of the at least one MLPE that has failed.

16. The inverter according to claim 13, wherein, The processor is also configured to: periodically receive monitoring information from each of the plurality of MLPEs, the monitoring information including: unique information for each MLPE, and a measurement of at least one of voltage, current, power generation, and temperature for each of the plurality of photovoltaic panels; and when the measurement deviates from a preset range, determine that a fault has occurred in at least one MLPE associated with the measurement.

17. The inverter according to claim 13, wherein, The processor is also configured to: count the fault history associated with the identification information of the at least one MLPE that has failed; and when the fault history exceeds a set value, generate and output a replacement notification for the at least one MLPE that has failed.

18. The inverter according to claim 13, wherein, The processor is further configured to: when a registration request is received from a new MLPE, assign the identification information of the at least one MLPE marked with the fault flag as the identification information of the new MLPE.

Images