Module-level power electronic device, diagnosis management system and diagnosis management method

Abstract

A module-level power electronics (MLPE) according to an aspect may include a processor that: performs a self-diagnostic mode based on a self-diagnostic request signal received during operation or stop of an inverter connected to the module-level power electronics; in the self-diagnosis mode, detecting whether an installation error exists between the photovoltaic module and the module-level power electronic device or a component error exists in the module-level power electronic device; and transmitting diagnosis result information about whether the installation error and the component error are detected to a diagnosis management system.

Description

Technical Field

[0001] This invention relates to a module-level power electronic device (MLPE), a verification management system, and a verification management method. Background Technology

[0002] Recently, photovoltaic power generation systems have begun to adopt module-level power electronic devices (MLPEs) (or component-level power control devices) to increase power generation under certain conditions, such as when there is shadow on the photovoltaic module.

[0003] At the same time, MLPEs may experience failures, such as failures that occur during the process of connecting to photovoltaic modules or inverters (i.e., installation failures), or failures in the components installed within the MLPE itself (i.e., component failures).

[0004] Typically, MLPEs do not have a dedicated fault verification mode; instead, they notify the user of any anomalies detected during MLPE operation. In this case, a fault can only be detected when the MLPE is installed on the photovoltaic module, connected to the inverter, and capable of generating electricity. Therefore, there is a drawback that a certain amount of time must pass before a fault is detected. Furthermore, because faults cannot be confirmed at the user's expected time, it is difficult to immediately determine whether an installation fault or a module fault exists after MLPE installation. Summary of the Invention

[0005] Technical issues

[0006] The technical problem of the present invention is to provide a module-level power electronic device (MLPE), a verification management system, and a verification management method.

[0007] Solution to the problem

[0008] According to one aspect, the module-level power electronic device (MLPE) may include a processor configured to: execute a self-verification mode based on a self-verification request signal received during operation or shutdown of an inverter connected to the MLPE; detect, in the self-verification mode, whether there is an installation fault between the photovoltaic module and the MLPE or a component fault within the MLPE; and send verification result information regarding whether the installation fault and component fault were detected to a verification management system.

[0009] According to another aspect, the verification management system communicating with the MLPE may include a processor configured to: send a self-verification request signal to the MLPE based on a received user input requesting self-verification; in response to the self-verification request signal, receive verification result information regarding installation faults between the photovoltaic module and the MLPE or component faults within the MLPE; and perform a preset response operation based on the verification result information.

[0010] According to another aspect, the verification management method performed by the MLPE may include: performing a self-verification mode based on a self-verification request signal received during operation or shutdown of the inverter connected to the MLPE, in which the self-verification mode detects whether there is an installation fault between the photovoltaic module and the MLPE or a component fault within the MLPE; and sending verification result information regarding whether installation faults and component faults were detected to the verification management system. Attached Figure Description

[0011] Figure 1 This is a schematic diagram illustrating a photovoltaic module including module-level power electronic devices (MLPE) and a verification management system according to an embodiment.

[0012] Figure 2A and Figure 2B This is a schematic diagram illustrating a photovoltaic power generation system according to an embodiment.

[0013] Figure 3 This is a diagram showing the connection structure between the photovoltaic module and the MLPE according to an embodiment.

[0014] Figure 4 This is an operation flowchart of MLPE according to an embodiment.

[0015] Figure 5 This is an operation flowchart of the MLPE and verification management system according to the first embodiment.

[0016] Figure 6 This is an operation flowchart of the MLPE and verification management system according to the second embodiment.

[0017] Figure 7 This is a diagram used to depict the operation of the photovoltaic power generation system according to the first embodiment.

[0018] Figure 8 This is a diagram used to depict the operation of the photovoltaic power generation system according to the second embodiment.

[0019] Figure 9 This is a diagram used to depict the operation of a photovoltaic power generation system according to the third embodiment.

[0020] Figure 10This is a diagram used to depict the operation of the photovoltaic power generation system according to the fourth embodiment.

[0021] Figure 11 This is a diagram used to depict the operation of the photovoltaic power generation system according to the fifth embodiment.

[0022] Figure 12 This is a diagram illustrating the operational flow between the MLPE and the verification management system according to an embodiment.

[0023] Figure 13 This is a diagram showing the waveform corresponding to fault detection according to the first embodiment.

[0024] Figure 14 This is a diagram showing the waveform corresponding to fault detection according to the second embodiment.

[0025] Figure 15 This is a diagram showing the waveform corresponding to fault detection according to the third embodiment.

[0026] Figure 16 This is a diagram illustrating the power supply structure of a building equipped with photovoltaic modules according to an embodiment. Detailed Implementation

[0027] Best Implementation of the Invention

[0028] According to one aspect, the module-level power electronic device (MLPE) may include a processor configured to: execute a self-verification mode based on a self-verification request signal received during operation or shutdown of an inverter connected to the MLPE; detect in the self-verification mode whether there is an installation fault between the photovoltaic module and the MLPE or a component fault within the MLPE; and send verification result information regarding whether the installation fault and component fault were detected to a verification management system.

[0029] Implementation of the present invention

[0030] Considering the functionality of the current embodiments, the terminology used in this specification has been selected as far as possible from those widely used by those skilled in the art. However, these terms may change depending on the technical intent, precedent, or the emergence of new technologies. Furthermore, the applicant may arbitrarily choose terms in specific circumstances, in which case the meanings of these terms will be described in detail in the corresponding sections of the specification. Therefore, the terms used in this specification should be defined according to their meanings and the entire content of the specification, rather than solely based on their names.

[0031] It should be understood that, unless otherwise defined, throughout the specification, when a component “comprises” or “includes” an element, that component does not exclude other elements and may include other elements.

[0032] Furthermore, terms containing ordinal numbers (such as "first" or "second") used in this specification may be used to describe various components or embodiments, but the components or embodiments are not limited by these terms. The above terms may be used to distinguish one component or embodiment from another.

[0033] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The detailed description set forth below in conjunction with the drawings is intended to describe exemplary embodiments of the invention and is not intended to represent the only embodiments that can be implemented with respect to the present disclosure. In the drawings, portions irrelevant to the description may be omitted for clarity of explanation, and throughout the specification, the same reference numerals may be used to denote the same or similar components.

[0034] Figure 1 This is a schematic diagram illustrating a photovoltaic module including module-level power electronic devices (MLPE) and a verification management system according to an embodiment.

[0035] Figure 1 A photovoltaic module 100, an MLPE 110 included in the photovoltaic module 100, and a verification management system 200 are shown.

[0036] Photovoltaic module 100 can be a module that generates electricity using sunlight. For example, photovoltaic module 100 may include multiple photovoltaic cells. Photovoltaic cells generate electricity by converting solar energy into electrical energy using the photovoltaic effect. Photovoltaic cells may be referred to as solar cells. For example, photovoltaic cells may include at least one of the following: monocrystalline silicon solar cells, polycrystalline silicon solar cells, and thin-film solar cells. For example, photovoltaic cells may include amorphous silicon solar cells, copper indium gallium selenide (Cu-In-Ga-Se, CIGS) based compound thin-film solar cells, cadmium telluride (CdTe) based compound thin-film solar cells, stacked thin-film solar cells, etc. However, examples of photovoltaic cells are not limited to those mentioned above, and various types of photovoltaic cells may exist.

[0037] MLPE 110 is connected to photovoltaic module 100 to optimize the output voltage of photovoltaic module 100. For example, MLPE 110 can optimize the output voltage to maximize the output of photovoltaic module 100. For example, MLPE 110 can improve power generation efficiency by using Maximum Power Point Tracking (MPPT) to calculate the voltage value that maximizes the output power.

[0038] For example, the MLPE 110 can be a direct current (DC) optimizer or a micro inverter.

[0039] For example, if the MLPE 110 is a DC optimizer, a single DC optimizer can be connected to a single photovoltaic module 100. Alternatively, the photovoltaic module 100 can be connected to an inverter. In this case, the DC optimizer can optimize the power output from the photovoltaic module 100 and output the optimized power output to the inverter (e.g., a string inverter). The current converted by this inverter (e.g., converting DC current to AC current) can be output to a load or the power grid.

[0040] As another example, if the MLPE 110 is a microinverter, a single microinverter can be connected to a single photovoltaic module 100. In this case, the microinverter can convert the electricity generated by the photovoltaic module 100, and the converted electricity can be output to a load or the power grid.

[0041] For example, the MLPE 110 can be attached to the back of the photovoltaic module 100 for use. Alternatively, the MLPE 110 can be used in a physically detached state from the photovoltaic module 100. The method of connecting the MLPE 110 and the photovoltaic module 100 is not limited to a specific example and can be implemented in various ways.

[0042] For example, depending on the structure of the photovoltaic power generation system, the MLPE 110 can be connected to the photovoltaic module 100 in various configurations. For instance, the MLPE 110 can be connected one-to-one to each photovoltaic cell included in the photovoltaic module 100. As another example, the MLPE 110 can be connected to the photovoltaic cells included in the photovoltaic module 100 in a many-to-one or many-to-many configuration. The connection configuration between the MLPE 110 and the photovoltaic module 100 is not limited to any particular form.

[0043] The verification management system 200 is connected to the MLPE 110 and can control the operation of the MLPE 110. For example, the verification management system 200 and the MLPE 110 can be connected via wired or wireless communication, and various wired or wireless communication methods can be applied.

[0044] For example, the verification management system 200 can be implemented in an Energy Management System (EMS), but is not limited to this. The verification management system 200 can be implemented as a web page or an application.

[0045] Meanwhile, installation failures may occur during the process of connecting the MLPE 110 to the photovoltaic module 100. Furthermore, component failures may occur, such as damage or malfunction of at least one of the various components included in the MLPE 110. For example, the MLPE 110 may include a voltage converter, a processor, an analog-to-digital converter, a voltage sensor, a current sensor, a gate driver, etc.

[0046] For example, MLPE 110 can operate in both Self-Validation mode (SV mode) and normal mode. MLPE 110 can execute self-validation mode to detect faults. For example, self-validation mode can be executed under fault detection conditions. Alternatively, self-validation mode can be executed in response to a request from a user.

[0047] Even when the MLPE 110 is not in operation, the MLPE 110 can detect faults. For example, the MLPE 110 can initiate self-verification mode immediately after being installed on a photovoltaic module. For example, the MLPE 110 can initiate self-verification mode immediately after the photovoltaic module 100 is installed in a solar power plant or at a location used for photovoltaic power generation (e.g., a residence).

[0048] In addition, the MLPE 110 can perform self-verification mode regardless of whether the inverter connected to it is running.

[0049] For example, when a photovoltaic power generation system includes multiple MLPEs 110, each of the multiple MLPEs 110 can detect faults. Alternatively, a selected MLPE 110 from the multiple MLPEs 110 can detect faults.

[0050] The operation of MLPE 110 and Validation Management System 200 will be described in detail below with reference to the accompanying drawings.

[0051] Figure 2A and Figure 2B This is a schematic diagram illustrating a photovoltaic power generation system according to an embodiment.

[0052] refer to Figure 2A The photovoltaic power generation system 1 may include a photovoltaic module 100, an MLPE 110, a verification management system 200, an inverter 300, and a power grid 400. For example, Figure 2A The MLPE 110 shown can be a DC optimizer.

[0053] Photovoltaic module 100 is a module that generates electricity using sunlight, and multiple photovoltaic modules can be installed in photovoltaic power generation system 1.

[0054] MLPE 110 can be installed on each photovoltaic module 100. MLPE 110 can prevent the overall power generation efficiency of the photovoltaic power generation system 1 from being reduced due to shading on a particular photovoltaic module or performance degradation of a particular photovoltaic module.

[0055] The outputs of multiple MLPE 110s can be connected in series to form a string. For example, multiple strings can exist, and these multiple strings can be connected to inverter 300.

[0056] The verification management system 200 can receive the status of components of the photovoltaic power generation system 1, such as MLPE 110, inverter 300, and grid 400. The verification management system 200 can control the operation of the components of the photovoltaic power generation system 1 based on the status of the components.

[0057] Figure 2A An example of a photovoltaic power generation system 1 with MLPE 110 as a DC optimizer is shown. However, as referenced above... Figure 1 As described, the MLPE 110 can also be a micro-inverter. Figure 2B The image shows an example of a photovoltaic power generation system 1 with a micro-inverter, MLPE 110.

[0058] refer to Figure 2B The photovoltaic power generation system 1 may include a photovoltaic module 100, an MLPE 110, a verification management system 200, and a power grid 400.

[0059] and Figure 2A compared to, Figure 2B The photovoltaic power generation system 1 may not include an inverter 300. For example, the MLPE 110 can convert the power generated by the photovoltaic module 100, so the photovoltaic power generation system 1 may not include a separate inverter.

[0060] Figure 3 This is a diagram showing the connection structure between the photovoltaic module and the MLPE according to an embodiment.

[0061] MLPE 110 may include a voltage converter 111, a processor 112, and a measuring device 113.

[0062] The voltage converter 111 is a device that converts the voltage applied from the photovoltaic module 100 (the output voltage of the photovoltaic module 100). For example, the voltage converter 111 may include a DC optimizer, a DC / AC inverter, or a micro-inverter.

[0063] When the voltage converter 111 is a DC optimizer, it can be implemented as a buck converter that steps down the input voltage. Alternatively, the voltage converter 111 can be implemented as both a buck and boost converter. The detailed structure of the voltage converter 111 is not limited to any particular configuration.

[0064] For example, processor 112 may include a microcontroller unit (MCU) for power control. Processor 112 may execute software such as programs to control at least one other component (e.g., a hardware or software component) of MLPE 110, and may perform various data processing or calculations.

[0065] For example, processor 112 can control the duty cycle of voltage converter 111 to convert (adjust) the output voltage of MLPE 110. Additionally, processor 112 can control the operation of one or more internal switches included in voltage converter 111.

[0066] For example, the measuring device 113 may include a voltage sensor, a current sensor, a temperature sensor, etc.

[0067] The processor 112 can receive the output current Ipv of the photovoltaic module 100, the output voltage Vpv of the photovoltaic module 100, and the temperature Tmlpe of the MLPE 110 from the measuring device 113.

[0068] At the same time, despite Figure 3 As not shown in the diagram, the MLPE 110 may also include a power supply, a gate driver, and an analog-to-digital converter (ADC).

[0069] Figure 4 This is an operation flowchart of MLPE according to an embodiment.

[0070] The processor 112 of the MLPE 110 can execute a self-verification mode (S10) based on a self-verification request signal received during operation or shutdown of the inverter 300 connected to the MLPE 110.

[0071] For example, when MLPE 110 is a DC optimizer, processor 112 can execute self-verification mode regardless of whether inverter 300 is running. Meanwhile, when MLPE 110 is a microinverter, the photovoltaic power generation system 1 may not include inverter 300. In this case, processor 112 can execute self-verification mode in response to a self-verification request signal.

[0072] For example, based on user input requesting self-verification, processor 112 can receive a self-verification request signal from verification management system 200. Processor 112 can execute self-verification mode upon receiving the self-verification request signal.

[0073] In self-verification mode, processor 112 can detect whether there is an installation fault between photovoltaic module 100 and MLPE 110 or a component fault within MLPE 110 (S20).

[0074] If a fault occurs during the installation process between the photovoltaic module 100 and the MLPE 110 (i.e., an installation failure), the current or voltage value at at least one of the output terminals of the photovoltaic module 100, the input terminal of the MLPE 110, or the output terminal of the MLPE 110 may fall outside the predefined range (normal range). Additionally, when the current or voltage value falls outside the normal range, the temperature of the MLPE 110 may also fall outside the normal range.

[0075] The processor 112 can detect installation faults based on fault information indicating at least one of the following (hereinafter referred to as "first fault information"): overvoltage of photovoltaic module 100, overcurrent of photovoltaic module 100, overvoltage of MLPE 110, overcurrent of MLPE 110, and overheating of MLPE 110.

[0076] For example, the first fault information may include bits indicating whether overcurrent, overvoltage, or overheating has occurred. For example, when the photovoltaic module 100 is configured with three strings, the first fault information of the photovoltaic module 100 and MLPE 110 may be configured as shown in Table 1 below.

[0077] Table 1

[0078]

[0079] In the first fault information shown in Table 1, the photovoltaic modules 100 and MLPE 110 configured with three strings can be indicated as Top, Mid, and Bot. For example, in the case of bit 2, it can correspond to information about the output voltage Vpv of the photovoltaic module located at the top of the photovoltaic modules 100 configured with three strings, and this bit can include information about whether an overvoltage has occurred. In another example, in the case of bit 7, it can correspond to information about the output current Ipv of the photovoltaic module located at the bottom of the photovoltaic modules 100 configured with three strings, and this bit can include information about whether an overcurrent has occurred. In yet another example, in the case of bit 8, it can correspond to information about the output voltage Vout of MLPE 110, and this bit can include information about whether an overvoltage has occurred.

[0080] In addition, the processor 112 can receive measurement information obtained by measuring at least one of the following: the output voltage Vpv of the photovoltaic module 100, the output current Ipv of the photovoltaic module 100, the output voltage Vout of the MLPE 110, the output current Iout of the MLPE 110, and the temperature Tmlpe of the MLPE 110.

[0081] For example, the output voltage Vpv of photovoltaic module 100, the output current Ipv of photovoltaic module 100, and the temperature Tmlpe of MLPE 110 can be measured by the measuring device 113 of MLPE 110, such as... Figure 3 As shown. However, the present invention is not limited thereto, and measurement information can be obtained through various means.

[0082] The processor 112 can detect, based on measurement information, whether there is an installation fault caused by at least one of overvoltage, overcurrent, and overheating in the photovoltaic module 100 and MLPE 110. For example, the processor 112 can check whether the current measurement value, voltage measurement value, and temperature measurement value indicated in the measurement information fall outside a predefined range.

[0083] Faults occurring in components of MLPE 110 (i.e., component faults) may include not only rapid shutdown (RSD) operation faults of MLPE 110, but also faults occurring in one of the following: power conversion device 111, measurement device 113, gate driver, power supply, and analog-to-digital converter.

[0084] The processor 112 can detect component failures based on fault information indicating at least one of the following (hereinafter referred to as "second fault information"): fast shutdown operation failure, voltage sensor failure of MLPE 110, current sensor failure of MLPE 110, gate driver failure of MLPE 110, power supply failure of MLPE 110, and analog-to-digital converter failure of MLPE 110.

[0085] For example, the second fault information may include information including bits indicating whether each component has a fault. For example, when the photovoltaic module 100 is configured with three strings, the second fault information of the photovoltaic module 100 and MLPE 110 may be configured as shown in Table 2 below.

[0086] Table 2

[0087]

[0088]

[0089] In the second fault information shown in Table 2, the photovoltaic module 100 and MLPE 110 configured with three strings can be indicated as Top, Mid, and Bot. For example, in the case of bit 3, it corresponds to information about a fault in the voltage sensor or gate driver of the MLPE located at the top of the photovoltaic module 100 configured with three strings, and this bit can include information about whether a fault has occurred.

[0090] In another example, bit 9 may indicate the voltage applied to the power supply of the MLPE 110, and bit 10 may indicate whether the offset voltage of the analog-to-digital converter is applied at an appropriate voltage.

[0091] In another example, bit 11 may correspond to information about the output voltage (input voltage of MLPE 110) Vpv of the top photovoltaic module in a photovoltaic module 100 configured with three strings, and this bit may include information about installation-related faults or hardware-related faults.

[0092] The processor 112 can send verification result information about whether an installation fault or component fault is detected to the verification management system 200 (S30).

[0093] For example, the verification result information may include: information about the occurrence of the detected installation failure or component failure, information about the cause of the installation failure or component failure, and information about the solution to the installation failure or component failure.

[0094] Reference Figure 5 and Figure 6 Describe the subsequent response actions of the verification management system 200.

[0095] As described above, by verifying the MLPE 110 for faults immediately after installation, MLPEs with hardware problems can be identified. Furthermore, the user can be notified whether the MLPE 110 has been installed correctly.

[0096] In addition, users can verify the fault status and installation of the MLPE 110 at any desired time.

[0097] Furthermore, the ability to quickly identify MLPEs with hardware or installation problems reduces the adverse impact of such MLPEs on the total power generation of photovoltaic system 1.

[0098] Figure 5 This is an operation flowchart of the MLPE and verification management system according to the first embodiment.

[0099] Figure 5 Including the above references Figure 4 The content described, and omitting the related Figure 4Detailed explanation of the overlapping content.

[0100] MLPE 110 can receive a self-verification request signal (S510). For example, the verification management system 200 can receive user input requesting self-verification and, in response, send a self-verification request signal to MLPE 110.

[0101] In the following text, the verification management system 200 can be operated through the operation of the processor provided in the verification management system 200. For ease of explanation, the processor 112 of MLPE 110 will be referred to as the first processor, and the processor of the verification management system 200 will be referred to as the second processor.

[0102] For example, the verification management system 200 may have separate input and display units to receive user input.

[0103] The input unit may include at least one input device. For example, the input unit may include a keyboard, a keyboard area, a dome switch, a touch panel, touch keys, a mouse, a menu button, etc.

[0104] For example, the display unit may include a liquid crystal display (LCD), a light-emitting diode (LED) display, an organic light-emitting diode (OLED) display, a micro-electro-mechanical system (MEMS) display, and an electronic paper display.

[0105] In addition, the verification management system 200 can provide a graphical user interface (GUI) for receiving user input, and the GUI can be provided through a display unit, which is implemented as a touch screen display unit in combination with the input unit.

[0106] MLPE 110 can execute self-verification mode (S520) and can detect installation failures or component failures within MLPE 110 (S530). When an installation failure or component failure within MLPE 110 is detected (Yes in S530), the verification result information can be sent to the verification management system 200 (S540).

[0107] When no installation fault or component fault is detected within MLPE 110 (No in S530), MLPE 110 can perform normal operation in normal mode (S550).

[0108] The verification management system 200 can receive verification result information and perform preset response operations based on the verification result information (S560).

[0109] For example, predetermined response actions may include: displaying information about an installation failure or component failure on a monitor, sending a self-verification re-request signal to the MLPE, performing a service call to check the MLPE, or sending a normal mode operation signal to the MLPE.

[0110] The verification management system 200 can display verification result information on a monitor, including information about the occurrence of installation or component failures, information about the cause of the failure, or information about the solution to the failure.

[0111] The verification management system 200 can send a self-verification re-request signal to MLPE 110 (S561) based on the user input that has been received again requesting the self-verification mode. In this case, MLPE 110 can re-execute the self-verification mode (S520).

[0112] Although Figure 5 Not shown, but the second processor of the verification management system 200 can determine whether the self-verification mode needs to be re-executed based on the verification result information, and if so, send a self-verification re-request signal to MLPE110.

[0113] The verification management system 200 can execute a service call (S562) for inspecting MLPEs. The verification management system 200 can execute a service call when it is determined, based on the verification result information, that a separate inspector is needed to resolve the fault information, or when user input requesting a service call is received.

[0114] The verification management system 200 can send a normal mode operation signal to the MLPE 110 (S563) based on user input requesting normal mode operation. In this case, the MLPE 110 can execute normal mode (S550).

[0115] Although Figure 5 Although not shown in the diagram, the second processor of the verification management system 200 can determine whether it needs to run in normal mode based on the verification result information, and if so, can send a normal mode run signal to MLPE110.

[0116] As described above, users can immediately execute the self-verification mode after installing the MLPE 110, enabling them to quickly identify and replace faulty MLPEs. In this case, as long as the MLPE 110 is powered and the verification management system 200 is capable of operating the MLPE 110, the self-verification mode can be executed immediately after installation. Therefore, even if the photovoltaic module 100 is not generating electricity, the self-verification mode can be executed immediately after the MLPE 110 is installed.

[0117] Figure 6 This is an operation flowchart of the MLPE and verification management system according to the second embodiment.

[0118] Figure 6 An example of the process for handling a fault detected during normal operation of the MLPE 110 is shown.

[0119] MLPE 110 can operate in normal mode (S610) and can detect faults (S620).

[0120] For example, while MLPE 110 is operating in normal mode, the first processor can detect installation faults between the photovoltaic module 100 and MLPE 110, or component faults within MLPE 110. Fault detection and handling are related to... Figure 3 The process described in S20 is the same.

[0121] When a fault is detected (Yes in S620), MLPE 110 can stop operating in normal mode (S630). When no fault is detected (No in S620), MLPE 110 can continue operating in normal mode (S610).

[0122] If the number of detections for installation faults or component faults exceeds a preset number, the MLPE 110 can execute a self-verification mode (S640). Alternatively, the MLPE 110 can execute a self-verification mode (S640) if the duration of the fault condition corresponding to the component fault exceeds a preset time. See below for further details. Figures 13 to 15 Describe specific examples related to S640.

[0123] When the number of times an installation fault or component fault is detected exceeds a preset number, or when the duration of the fault condition corresponding to the component fault exceeds a preset time (as in S640), MLPE 110 can automatically switch from normal mode to self-verification mode (S650). For example, MLPE 110 can identify the number of times an installation fault or component fault is detected or the duration of the fault condition corresponding to the component fault based on first fault information and second fault information.

[0124] If the number of detections does not exceed the preset number and the duration of the fault condition corresponding to the component failure does not exceed the preset time (No in S640), then MLPE 110 can continue to operate in normal mode (S610).

[0125] Processing after MLPE 110 switches to self-verification mode Figure 5 The processing after S530 is the same, therefore the omission of... Figure 5 Description of repeated content.

[0126] The MLPE 110 can detect installation failures or component failures of the MLPE in self-verification mode (S660).

[0127] When an installation failure or component failure is detected (in S660), MLPE 110 can send the verification result information to the verification management system 200 (S670).

[0128] When no installation fault or component failure is detected (No in S660), MLPE 110 can perform normal operation in normal mode (S610).

[0129] The verification management system 200 can receive verification result information and execute preset response operations based on the verification result information (S680).

[0130] The verification management system 200 can send a self-verification re-request signal to MLPE 110 (S681) based on the user input that has been received again requesting the self-verification mode. In this case, MLPE 110 can re-execute the self-verification mode (S650).

[0131] The verification management system 200 can execute a service call (S682) for checking MLPEs. For example, if a separate inspector is needed to resolve fault information based on verification result information, or when user input requesting a service call is received, the verification management system 200 can execute the service call.

[0132] Based on the received user input requesting normal mode operation, the verification management system 200 can send a normal mode operation signal to MLPE 110 (S683). In this case, MLPE 110 can execute normal mode (S610).

[0133] Although Figure 6 Although not shown, the second processor of the verification management system 200 can determine whether it needs to run in normal mode based on the verification result information, and if so, can send a normal mode operation signal to the MLPE 110.

[0134] the following, Figures 7 to 11The MLPE 110 shown in the photovoltaic power generation system 1 is an example of a DC optimizer. Therefore, the photovoltaic power generation system 1 may include an inverter 300.

[0135] However, when the MLPE 110 is a micro inverter, the photovoltaic power generation system 1 may not include the inverter 300.

[0136] Figure 7 This is a diagram used to depict the operation of the photovoltaic power generation system according to the first embodiment.

[0137] Reference Figure 7 All of the multiple MLPEs 110 in the photovoltaic power generation system 1 are operating in normal mode. In addition, the inverter 300 is operating and being supplied with current from the multiple MLPEs 110.

[0138] Figure 8 This is a diagram used to depict the operation of the photovoltaic power generation system according to the second embodiment.

[0139] While inverter 300 is operating, multiple MLPEs 110, including those in photovoltaic power generation system 1, can individually execute self-verification mode. At this time, other MLPEs 110 can generate electricity normally in normal mode.

[0140] As mentioned above, since each MLPE can execute the self-verification mode independently, and other MLPEs can perform power generation normally, efficient power generation can be achieved.

[0141] Figure 9 This is a diagram used to depict the operation of a photovoltaic power generation system according to the third embodiment.

[0142] While the inverter 300 is operating, multiple MLPEs 110, including those in the photovoltaic power generation system 1, can collectively perform a self-verification mode.

[0143] As mentioned above, all MLPEs can execute self-verification mode simultaneously, or they can execute self-verification mode individually.

[0144] Furthermore, by enabling all MLPEs included in the photovoltaic power generation system to simultaneously execute self-verification mode, faulty MLPEs can be quickly identified.

[0145] Figure 10 This is a diagram used to depict the operation of the photovoltaic power generation system according to the fourth embodiment.

[0146] While the inverter 300 is shut down, multiple MLPEs 110, including those in the photovoltaic power generation system 1, can individually execute self-verification mode. In this case, the other MLPEs 110 can operate in normal mode.

[0147] Figure 11 This is a diagram used to depict the operation of the photovoltaic power generation system according to the fifth embodiment.

[0148] While the inverter 300 stops operating, multiple MLPEs 110, including those in the photovoltaic power generation system 1, can collectively execute a self-verification mode.

[0149] As mentioned above, MLPE can execute self-verification mode regardless of whether the inverter is running.

[0150] Figure 12 This is an operational flowchart between the MLPE and the verification management system according to an embodiment.

[0151] Figure 12 References are shown Figure 4 and Figure 5 Examples of the content being described.

[0152] Based on the self-verification mode run request from the verification management system 200 (S1210), MLPE 110 can execute self-verification mode (S1220).

[0153] MLPE 110 can change the self-verification state (SV_State) from stopped (SV_STOP) to running (SV_RUN) (S1230-S1240).

[0154] In self-verification mode, MLPE 110 can determine whether there is an installation failure or component failure (SV_HW_Check_State) (S1250).

[0155] Once self-verification is complete (SV_FINISHED) (S1260), MLPE 110 can determine whether a failure has occurred (S1270).

[0156] When a fault has occurred (Yes in S1270), MLPE 110 can send the verification result information to the verification management system 200, and the verification management system 200 can notify the user of the fault (S1280).

[0157] The verification management system 200 can provide guidance on the cause of the fault and checkpoints, and can notify the user that if the problem is not resolved, they can choose to make a service call (S1290), and can terminate the self-verification mode (S1310).

[0158] The verification management system 200 can notify the user to re-execute the self-verification mode (S1300). When the verification management system 200 receives user input requesting re-execution, it can request the MLPE to re-execute the self-verification mode (S1220).

[0159] When no fault occurs (S1270 No), MLPE 110 can send the verification result information to the verification management system 200. The verification management system 200 can notify the user that the system is in a normal state (S1320) and can terminate the self-verification mode (S1330).

[0160] Figure 13 This is a diagram showing the waveform corresponding to fault detection according to the first embodiment.

[0161] Figure 13 It shows about Figure 6 The example of the S640 determines the transition to self-verifying mode based on the number of faults detected during operation in normal mode.

[0162] MLPE 110 can detect installation faults between the photovoltaic module 100 and MLPE 110 or component faults within MLPE 110 while operating in normal mode. For example, MLPE 110 can detect faults based on first fault information as shown in Table 1.

[0163] The MLPE 110 can stop for a preset period of time and then restart based on an installation failure or component failure. In this case, the stop time and the number of failure detections are not limited to a specific example and can be determined actively or passively.

[0164] refer to Figure 13 As shown in the waveform, the MLPE 110 can stop running for 0.2 seconds or 1 minute, and then restart if a fault occurs during normal operation. For example, when three sets of faults occur, 120 times per set, the MLPE 110 can automatically switch to self-verification mode and perform self-verification.

[0165] Figure 14 A diagram showing the waveform corresponding to fault detection according to the second embodiment is shown.

[0166] Figure 14 It shows about Figure 6 The example of the S640 determines the transition to self-verification mode based on the number of faults detected during operation in normal mode.

[0167] MLPE 110 can detect component failures within MLPE 110 while operating in normal mode. For example, as shown in Table 2, MLPE 110 can detect failures corresponding to bits 2 to 10 of the second failure information. MLPE 110 can stop for a preset period of time and then restart based on the component failure. In this case, the stop time and the number of failure detections are not limited to a specific example and can be determined actively or passively.

[0168] refer to Figure 14 As shown in the waveform, the MLPE 110 can stop operating for 5 minutes and then restart if a fault occurs during normal operation. For example, when a fault occurs 9 times, the MLPE 110 can automatically switch to self-verification mode and perform self-verification.

[0169] Figure 15 This is a diagram showing the waveform corresponding to fault detection according to the second embodiment.

[0170] Figure 15 It shows about Figure 6 The example of the S640 determines the transition to self-verifying mode based on the duration of a fault condition during operation in normal mode.

[0171] MLPE 110 can detect component faults within the MLPE while operating in normal mode. For example, as shown in Table 2, MLPE 110 can detect faults corresponding to bits 11 to 13 of the second fault information.

[0172] When the MLPE 110 detects a component failure, it can check the duration of the failure condition corresponding to the component failure.

[0173] If the duration of a fault condition corresponding to a component failure exceeds a preset time, the MLPE 110 can execute a self-verification mode. In this case, the preset time is not limited to a specific example and can be determined actively or passively.

[0174] refer to Figure 15 The waveform shown indicates that during normal operation, if the failure condition following a component failure lasts for more than 10 minutes, the MLPE 110 can automatically switch to self-verification mode and perform self-verification.

[0175] Figure 16 This is a diagram illustrating the power supply structure of a building equipped with photovoltaic modules according to an embodiment.

[0176] refer to Figure 16 Multiple photovoltaic modules 2 can be installed on the roof of building 1 to generate electricity. The photovoltaic modules 2 can be connected together to form a photovoltaic module array.

[0177] Inverter 6 can convert the electricity generated by photovoltaic module 2 and supply the generated electricity to building 1.

[0178] Meanwhile, commercial electricity transmitted through utility pole 3 can be supplied to the building via transformer 4.

[0179] Multiple household appliances 7 can selectively receive at least one of commercial power or power generated by the photovoltaic module 2 and use it for operation. The power meter 5 can measure the electrical power consumed in the building 1.

[0180] Alternatively, when a separate Energy Storage System (ESS) is installed in building 1, the electricity generated by photovoltaic module 2 can also be stored in the ESS.

[0181] When multiple photovoltaic modules 2 are connected, a photovoltaic module array can be configured. For example, a photovoltaic module array can be a component of multiple photovoltaic modules and can include a single output terminal.

[0182] Additionally, photovoltaic module 2 may include MLPE 110.

[0183] For example, MLPE 110 can monitor the status or power generation of photovoltaic module 2 and can send data to external devices. Alternatively, MLPE 110 can perform an emergency shutdown and stop the operation of photovoltaic module 2 based on the degree of failure in photovoltaic module 2.

[0184] In addition, at least one of the photovoltaic module 2 or MLPE 110 may include a communication module for power line communication.

[0185] Furthermore, the methods described above can be programmed into a computer and implemented on a general-purpose digital computer that executes the program using a computer-readable recording medium. Additionally, the data structures used in the methods described above can be recorded on a computer-readable recording medium in various ways. Examples of computer-readable recording media include magnetic storage media (e.g., read-only memory (ROM), random access memory (RAM), universal serial bus (USB), floppy disks, hard disks, etc.) and optically readable media (e.g., compact disc ROM (CD-ROM) and digital video discs (DVD)).

[0186] Those skilled in the art will understand that various modifications in form and detail may be made without departing from the foregoing features. Therefore, the disclosed methods are to be considered illustrative rather than restrictive. The scope of the invention should be defined by the appended claims, not by the foregoing description, and all differences within the equivalent scope of the invention are to be understood to be included in this disclosure.

Claims

1. A module-level power electronic device (MLPE), comprising: The processor is configured to execute a self-verification mode based on a self-verification request signal received during operation or shutdown of the inverter connected to the MLPE. In the self-verification mode, it detects whether there is an installation fault between the photovoltaic module and the MLPE or a component fault within the MLPE, and The verification results regarding whether the installation fault and the component fault were detected are sent to the verification management system.

2. The MLPE according to claim 1, wherein, The processor is also configured to: Based on the user input requesting self-verification, the system receives the self-verification request signal from the verification management system.

3. The MLPE according to claim 1, wherein, The processor is also configured to: The installation fault is detected based on a first fault information indicating at least one of the following: overvoltage of the photovoltaic module, overcurrent of the photovoltaic module, overvoltage of the MLPE device, overcurrent of the MLPE, and overheating of the MLPE.

4. The MLPE according to claim 1, wherein, The processor is also configured to: Receive measurement information obtained by measuring at least one of the following: the output voltage of the photovoltaic module, the output current of the photovoltaic module, the output voltage of the MLPE device, the output current of the MLPE, and the temperature of the MLPE. Based on the measurement information, it is detected whether there is an installation fault caused by at least one of overvoltage, overcurrent, and overheating.

5. The MLPE according to claim 3, wherein, The processor is also configured to: The component fault is detected based on a second fault information indicating at least one of the following: fast shutdown RSD operation fault, voltage sensor fault of the MLPE, current sensor fault of the MLPE, gate driver fault of the MLPE, power supply fault of the MLPE, and analog-to-digital converter fault of the MLPE.

6. The MLPE according to claim 5, wherein, The processor is also configured to: While the MLPE is operating in normal mode, the installation fault between the photovoltaic module and the MLPE or the component fault within the MLPE is detected. Based on the installation failure or the component failure, stop the operation of the MLPE, and If the number of times the installation fault or component fault is detected exceeds a preset number, the self-verification mode is executed.

7. The MLPE according to claim 6, wherein, The processor is also configured to: Based on the fact that the number of detections does not exceed the preset number, the MLPE is run again in the normal mode.

8. The MLPE according to claim 5, wherein, The processor is also configured to: While the MLPE is operating in normal mode, the component failure within the MLPE is detected, and If the duration of the fault condition corresponding to the component failure exceeds a preset time, the self-verification mode is executed.

9. The MLPE according to claim 1, wherein, The verification result information includes: information about the occurrence of the detected installation failure or component failure, information about the cause of the installation failure or component failure, and information about the solution to the installation failure or component failure.

10. A verification management system for communicating with a module-level power electronic device (MLPE), the verification management system comprising: The processor is configured to send a self-verification request signal to the MLPE based on received user input requesting self-verification. In response to the self-verification request signal, verification result information regarding installation faults between the photovoltaic module and the MLPE or component faults within the MLPE is received, and Based on the verification result information, a preset response operation is executed.

11. The verification management system according to claim 10, wherein, The processor is also configured to: The verification result information is displayed on the monitor, and the verification result information includes: information about the occurrence of installation failure or component failure, information about the cause of the failure, or information about the solution to the failure.

12. The verification management system according to claim 11, wherein, The preset response operations include: The operations include displaying information about the installation failure or the component failure on the display, sending a self-verification re-request signal to the MLPE, performing a service call to check the MLPE device, or sending a normal mode operation signal to the MLPE.

13. The verification management system according to claim 12, wherein, The processor is also configured to: Based on the verification result information, and based on the user input that received the request to self-verify again, a self-verification re-request signal for self-verification is sent to the MLPE.

14. The verification management system according to claim 12, wherein, The processor is also configured to: Based on the verification result information, and based on the user input requesting normal mode operation, a normal mode operation signal is sent to the MLPE.

15. A verification management method, performed by a module-level power electronic device (MLPE), the verification management method comprising: Based on the self-verification request signal received during operation or shutdown of the inverter connected to the MLPE, a self-verification mode is executed. In the self-verification mode, it is detected whether there is an installation fault between the photovoltaic module and the MLPE or a component fault within the MLPE. as well as The verification results regarding whether the installation fault and the component fault were detected are sent to the verification management system.

16. The verification management method according to claim 15, wherein, The execution includes: Based on the user input requesting self-verification, the system receives the self-verification request signal from the verification management system.

17. The verification management method according to claim 15, wherein, The detection includes: The installation fault is detected based on a first fault information indicating at least one of the following: overvoltage of the photovoltaic module, overcurrent of the photovoltaic module, overvoltage of the MLPE device, overcurrent of the MLPE device, and overheating of the MLPE.

18. The verification management method according to claim 17, wherein, The detection includes: The component failure is detected based on a second fault message indicating at least one of the following: a fast shutdown RSD operation failure, a voltage sensor failure of the MLPE, a gate driver failure of the MLPE, a power supply failure of the processor, and an analog-to-digital converter failure.

19. The verification management method according to claim 15, further comprising: While the MLPE is operating in normal mode, detect the installation fault between the photovoltaic module and the MLPE or the component fault within the MLPE. Based on the installation failure or the component failure, stop the operation of the MLPE, and If the number of detections of the installation fault or the component fault exceeds a preset number, the self-verification mode is executed.

20. The verification management method according to claim 19, further comprising: While the MLPE is operating in normal mode, a component failure is detected within the MLPE, and If the duration of the fault condition corresponding to the component failure exceeds a preset time, the self-verification mode is executed.

Images