Photovoltaic power generation system, and apparatus and method for updating firmware of mlpe

Abstract

The present invention provides a photovoltaic power generation system comprising a server that transmits firmware data, a main controller that receives firmware data from the server and sets a version of the firmware data when the reception of the firmware data is completed, and a Module Level Power Electronics (MLPE) that receives firmware data from the main controller, checks the version of the firmware data, and performs an update of the firmware data.

Description

Technology Field

[0001] The present invention relates to a photovoltaic power generation system, a firmware update device and method for an MLPE. Background Technology

[0003] Generally, a photovoltaic power generation system is a system that uses photovoltaic cells to convert solar energy into electrical energy and transmit it to the commercial power grid; this process does not cause environmental pollution and can be used semi-permanently.

[0004] This photovoltaic power generation system includes multiple photovoltaic panels, multiple MLPEs (Module Level Power Electronics), a main controller, and a server.

[0005] A plurality of solar panels can be connected in at least one of series and parallel, and a plurality of MLPEs are provided in each of the plurality of solar panels.

[0006] A plurality of MLPEs are configured to include an optimizer capable of optimizing the power efficiency generated from a solar panel. Here, the optimizer optimizes the power efficiency of the solar panel and transmits power generation information, including the amount of power generated, temperature, and fault information of the solar panel, to a main controller.

[0007] The main controller controls multiple optimizers, aggregates power generation information received from multiple optimizers, and transmits it to a server.

[0008] The server monitors the power generation status of multiple solar panels using power generation information from multiple solar panels.

[0009] Meanwhile, the MLPE is equipped with various components, including an optimizer, implemented on a printed circuit board and molded inside the MLPE case. Consequently, if changes to the operation and control of the MLPE are required after the product is finally shipped and installed on a solar panel, the printed circuit board cannot be physically manipulated directly; therefore, this is resolved through a remote firmware update. Here, firmware refers to software responsible for the control and operation of the MLPE.

[0010] However, if an error occurs during the remote firmware update process, it leads to a failure to reboot the MLPE. In particular, if the firmware update is interrupted and then resumed receiving firmware data, the validity of the data cannot be guaranteed if the versions of the previously stored firmware data and the subsequently received firmware data differ. The problem to be solved

[0012] In order to solve the problems of the prior art as described above, the present invention aims to ensure the validity of data by making the versions of the previously stored firmware data and the subsequently received firmware data identical when firmware data is interrupted during a firmware update and then subsequently received again.

[0013] The technical problems to be solved by the present invention are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below. means of solving the problem

[0015] To solve the above problems, the present invention provides a photovoltaic power generation system comprising a server that transmits firmware data, a main controller that receives firmware data from the server and sets a version of the firmware data when the reception of the firmware data is completed, and a Module Level Power Electronics (MLPE) that receives firmware data from the main controller, checks the version of the firmware data, and performs an update of the firmware data.

[0016] Here, the main controller can increment the version of the firmware data whenever the reception of firmware data is complete.

[0017] In addition, the main controller divides the firmware data into N unit data (where N is a natural number greater than or equal to 2), sequentially transmits the N unit data to the MLPE, and sets an index on the N unit data, wherein the index is increased by 1 each time the MLPE sequentially receives and stores multiple unit data, and the value of the index may be 0 to (N-1).

[0018] Additionally, MLPE deletes the first firmware data based on the need to update the previously stored first firmware data, receives and stores the second firmware data from the main controller, the version of the second firmware data is different from the version of the first firmware data, and the second firmware data can be received as the first unit data.

[0019] Additionally, MLPE receives third firmware data based on the fact that it stopped receiving second firmware data, and the third firmware data can be received as second unit data.

[0020] Additionally, MLPE can receive second unit data based on the fact that it stopped receiving up to the i-th first unit data (where i is a natural number greater than or equal to 1 and less than N) among the first unit data.

[0021] In addition, MLPE can determine whether the version of the second unit data is the same as the version of the first unit data.

[0022] Additionally, MLPE transmits index information of the i-th first unit data to the main controller based on the fact that the version of the second unit data is the same as the version of the first unit data, and the main controller checks the index information of the i-th first unit data and can transmit from the (i+1)-th second unit data among the second unit data to MLPE.

[0023] Additionally, MLPE deletes the second firmware data based on the fact that the version of the second unit data is different from the version of the first unit data, and the main controller can transmit the second unit data starting from the first second unit data to MLPE.

[0024] In addition, the present invention includes a communication unit that sequentially receives firmware data divided into N (wherein N is a natural number greater than or equal to 2) unit data, wherein the version is set and the firmware data is updated by checking the version of the firmware data and the index of the N unit data, wherein the index is set for the N unit data, and the index is increased by 1 each time the N unit data is sequentially received and stored, and the value of the index may be 0 to (N-1).

[0025] Additionally, the processor deletes the first firmware data based on the need to update the previously stored first firmware data, receives and stores the second firmware data, the version of the second firmware data is different from the version of the first firmware data, and the second firmware data can be received as the first unit data.

[0026] Additionally, the processor receives third firmware data based on the fact that it stopped receiving second firmware data, and the third firmware data can be received as second unit data.

[0027] Additionally, the processor may receive second unit data based on the fact that it stopped receiving up to the i-th first unit data (where i is a natural number greater than or equal to 1 and less than N) among the first unit data.

[0028] Additionally, the processor can receive the (i+1)th second unit data based on the fact that the version of the second unit data is the same as the version of the first unit data.

[0029] Additionally, the processor can delete the second firmware data based on the fact that the version of the second unit data is different from the version of the first unit data, and receive the second unit data starting from the first second unit data.

[0030] Additionally, the present invention includes the step of sequentially receiving firmware data divided into N (wherein N is a natural number greater than or equal to 2) unit data, wherein the version is set and the firmware data is divided into N unit data, and the step of increasing the index each time N unit data is sequentially received and stored, and performing an update of the firmware data by checking the index and the version of the firmware data, wherein the step of performing an update of the firmware data includes the step of deleting the first firmware data and receiving and storing the second firmware data based on the fact that the first firmware data stored previously needs to be updated, wherein the index is set for the N unit data, and the index is increased by 1 each time the N unit data is sequentially received and stored, and the value of the index may be 0 to (N-1).

[0031] Additionally, the step of performing an update of firmware data includes, based on the need to update the previously stored first firmware data, a step of deleting the first firmware data and receiving and storing the second firmware data, and a step of receiving the third firmware data based on the interruption of receiving the second firmware data, wherein the version of the second firmware data is different from the version of the first firmware data, the second firmware data is received as first unit data, and the third firmware data is received as second unit data, and the step of receiving and storing the second firmware data may be a step of receiving and storing up to the i-th first unit data (where i is a natural number greater than or equal to 1 and less than N) among the first unit data.

[0032] Additionally, the step of performing an update of firmware data may further include the step of receiving the (i+1)th second unit data among the second unit data based on the fact that the version of the second unit data is the same as the version of the first unit data, and the step of deleting the second firmware data and receiving the first second unit data among the second unit data based on the fact that the version of the second unit data is different from the version of the first unit data. Effects of the invention

[0034] According to the present invention, when firmware data is interrupted during a firmware update and then subsequently received again, the validity of the data can be guaranteed by making the versions of the previously stored firmware data and the subsequently received firmware data identical.

[0035] In addition, according to the present invention, if firmware update is interrupted and firmware data of a different version from previously stored firmware data is received, the previously stored firmware data is deleted and updated with new firmware data to make the versions identical, thereby ensuring the validity of the data.

[0036] The effects obtainable from the present invention are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art from the description below. Brief explanation of the drawing

[0038] FIG. 1 is a drawing illustrating a photovoltaic power generation system according to an embodiment of the present invention. FIG. 2 is a block diagram of a firmware update device for MLPE according to an embodiment of the present invention. FIG. 3 is a diagram illustrating a firmware update sequence of an MLPE according to an embodiment of the present invention. FIG. 4 is a flowchart of a firmware update method for MLPE according to an embodiment of the present invention. Specific details for implementing the invention

[0039] The above-mentioned objectives, means, and resulting effects of the present invention will become clearer through the following detailed description in conjunction with the attached drawings, and accordingly, a person skilled in the art to which the present invention pertains will be able to easily implement the technical concept of the present invention. Furthermore, in describing the present invention, if it is determined that a detailed description of known technology related to the present invention may unnecessarily obscure the essence of the present invention, such detailed description will be omitted.

[0040] In this specification, terms such as “or,” “at least one,” etc., may represent one of the words listed together or a combination of two or more. For example, “or B” and “at least one of B” may include only one of A or B, or may include both A and B.

[0041] In this specification, terms such as 'first,' 'second,' etc., may be used to describe various components, but such components should not be limited by these terms. Furthermore, these terms should not be interpreted as limiting the order of each component, but may be used for the purpose of distinguishing one component from another. For example, 'first component' may be named 'second component,' and similarly, 'second component' may be named 'first component.'

[0043] FIG. 1 is a drawing illustrating a photovoltaic power generation system according to an embodiment of the present invention.

[0044] As illustrated in FIG. 1, a photovoltaic power generation system according to an embodiment of the present invention may be configured to include a plurality of photovoltaic panels (10), a main controller (100), a plurality of MLPEs (Module Level Power Electronics) (200), and a server (300).

[0045] A plurality of solar panels (10) can be connected in at least one of series and parallel, and a plurality of MLPEs (200) can be provided on each of the plurality of solar panels (10).

[0046] A plurality of MLPEs (200) may be configured to include an optimizer (210) capable of optimizing the power efficiency generated from a solar panel (10). Here, the optimizer (210) can optimize power efficiency by operating in buck mode to lower the output voltage when the output voltage is higher than the maximum power point, and by operating in boost mode to raise the output voltage when the output voltage is lower than the maximum power point.

[0047] Multiple optimizers (210) can perform a rapid shutdown to stop the power generation of the solar panel (10) in an emergency situation. Additionally, the multiple optimizers (210) can transmit power generation information, including the amount of power generated, temperature, and fault information of the solar panel (10), to the main controller (100) and receive operation commands from the main controller (100) to optimize power efficiency.

[0048] Here, information transmission and reception between multiple optimizers (210) and main controllers (100) can be performed using Power Line Communication (PLC).

[0049] The main controller (100) can collect power generation information received from a plurality of optimizers (210) and transmit it to a server (300), and the server (300) can monitor the power generation status of a plurality of solar panels (10) using the power generation information of a plurality of solar panels (10).

[0050] Here, information transmission and reception between the main controller (100) and the server (300) can be performed via wired or wireless methods (e.g., serial communication).

[0051] The main controller (100) can control a plurality of optimizers (210) according to the power generation status of the solar panel (10).

[0052] A photovoltaic power generation system according to an embodiment of the present invention may further include an inverter (not shown) between a main controller (100) and a grid (20). Here, the inverter can convert direct current power generated from a plurality of photovoltaic panels (10) into alternating current power and transmit the converted alternating current power to the grid (20).

[0053] In order to monitor the power generation status of a plurality of solar panels (10), the main controller (100) transmits command data to a plurality of optimizers (210), and the plurality of optimizers (210) transmit response data containing power generation information of the solar panels (10) to the main controller (100) in response to the command data. Then, the main controller (100) collects the power generation information of the plurality of solar panels (10) and transmits it to a server.

[0054] Meanwhile, the MLPE (200) is provided with various components, including the optimizer (210), implemented on a printed circuit board and molded inside the case of the MLPE (200). Accordingly, when the product is finally shipped and installed on the solar panel (10), if changes are required to the operation and control of the MLPE (200), the printed circuit board cannot be physically manipulated directly, so the issue is resolved through a remote firmware update. Here, firmware refers to software responsible for the control and operation of the MLPE (200).

[0055] However, if an error occurs during the firmware remote update process, it leads to a failure to reboot the MLPE (200). In particular, if the firmware update is interrupted and then resumed receiving firmware data, the validity of the data cannot be guaranteed if the versions of the previously stored firmware data and the subsequently received firmware data are different.

[0056] Accordingly, the solar power generation system of the present invention proposes a technology that checks the version of the firmware data and proceeds with the update when the firmware update is interrupted and then resumes receiving the firmware data.

[0057] Specifically, the server (300) transmits firmware data to the main controller (100) when a firmware update is required. Accordingly, the main controller (100) receives the firmware data from the server (300), and when the reception of the firmware data is complete, sets a version in the firmware data.

[0058] Here, the main controller (100) can increase the version of the firmware data whenever the reception and storage of the firmware data is completed.

[0059] Additionally, the main controller (100) divides the firmware data into N unit data (wherein N is a natural number greater than or equal to 2) and sequentially transmits the N unit data to the MLPE (200). Here, the main controller (100) can divide the firmware data, which is tens of kbytes in size, into multiple units and transmit them.

[0060] MLPE (200) receives firmware data from the main controller (100), checks the version of the firmware data, and performs an update of the firmware data.

[0061] Specifically, the MLPE (200) can delete the first firmware data based on the need to update the previously stored first firmware data, and receive and store second firmware data from the main controller (100) that has a version different from the first firmware data. Here, the second firmware data may have a higher version than the first firmware data.

[0062] The main controller (100) can divide the second firmware data into N first unit data and sequentially transmit the N first unit data to the MLPE (200).

[0063] Additionally, the main controller (100) sets an index for N first unit data, and the index can be increased by 1 each time the MLPE (200) sequentially receives N first unit data of the second firmware data. Here, the value of the index can be from 0 to (N-1). That is, the initial value of the index is 0, and the final value can be (N-1).

[0064] For example, the main controller (100) can set the index to 0 before the first first unit data of the second firmware data is received, set the index of the second first unit data to 1 when the MLPE (200) confirms that it has received the first first unit data, and set the index to 2 when the MLPE (200) confirms that it has received the second first unit data, and increase the index until the last unit data is received.

[0065] N first unit data may include version information and index information. For example, version information and index information may be included in a certain field on the packet of the first unit data.

[0066] MLPE (200) can receive third firmware data based on the fact that it stopped receiving second firmware data. Here, the third firmware data can be received as second unit data, and the second unit data can include version information and index information.

[0067] For example, MLPE (200) can receive second unit data based on the fact that it stopped receiving up to the i-th first unit data (where i is a natural number greater than or equal to 1 and less than N) of the first unit data.

[0068] Here, MLPE (200) can determine whether the version of the second unit data is the same as the version of the first unit data that has been stored.

[0069] MLPE (200) can transmit index information of the i-th first unit data to the main controller (100) based on the fact that the version of the second unit data is the same as the version of the first unit data.

[0070] And, the main controller (100) can check the index information of the i-th first unit data and transmit the (i+1)-th second unit data among the second unit data to the MLPE (200).

[0071] Accordingly, MLPE (200) can ensure the validity of the data by making the versions of the previously stored first unit data and the subsequently received second unit data identical and maintaining continuity when the firmware update is interrupted and then resumed.

[0072] MLPE (200) deletes the second firmware data based on the fact that the version of the second unit data is different from the version of the first unit data, and the main controller (200) can transmit the first second unit data among the second unit data to MLPE (200). Here, the third firmware data may have a higher version than the second firmware data.

[0073] Accordingly, MLPE (200) can ensure the validity of the data by receiving and storing multiple unit data of the third firmware data from beginning to end instead of the second firmware data, thereby making the versions identical and maintaining continuity.

[0075] FIG. 2 is a block diagram of a firmware update device for MLPE according to an embodiment of the present invention.

[0076] Referring to FIG. 2, a firmware update device for an MLPE according to an embodiment of the present invention may be configured to include a memory (220), a processor (230), and a communication unit (240). Meanwhile, these configurations may be implemented as the configuration of the MLPE (200) itself.

[0077] The memory (220) may store firmware data and algorithms required for the control operation of the MLPE (200). Here, the memory (220) may be a flash memory (ROM) and may include an application (222) that operates according to the stored firmware data and a bootloader (221) that receives firmware data from the main controller (100).

[0078] The communication unit (240) can sequentially receive firmware data from the main controller (100) which is divided into N unit data with a version set.

[0079] Additionally, the processor (230) can perform an update of the firmware data by checking the version of the index and firmware data.

[0080] Here, N unit data have an index set, and the index is incremented by 1 each time N unit data are received and stored sequentially, and the value of the index can be from 0 to (N-1). Also, N unit data may include version information and index information.

[0081] Specifically, the processor (230) can delete the first firmware data based on the need to update the first firmware data stored in the memory (220), and receive and store second firmware data from the main controller (100) that has a version different from the first firmware data. Here, the second firmware data can be received as N first unit data.

[0082] The processor (230) may receive third firmware data based on the fact that it stopped receiving second firmware data. Here, the third firmware data may be received as second unit data.

[0083] Specifically, the processor (230) can receive second unit data based on the fact that it stopped receiving up to the i-th first unit data (where i is a natural number greater than or equal to 1 and less than N) of the first unit data.

[0084] Additionally, the processor (230) can determine whether the version of the second unit data is the same as the version of the first unit data that has been stored.

[0085] The processor (230) can transmit index information of the i-th first unit data to the main controller (100) based on the fact that the version of the second unit data is the same as the version of the first unit data.

[0086] And, the main controller (100) can check the index information of the i-th first unit data and transmit the (i+1)-th second unit data among the second unit data to the MLPE (200).

[0087] Accordingly, the firmware update device of an MLPE according to an embodiment of the present invention can ensure the validity of the data by making the versions of the previously stored first unit data and the subsequently received second unit data identical and maintaining continuity when receiving first unit data during a second firmware update is interrupted and then subsequently received second unit data.

[0088] In contrast, the processor (230) deletes the second firmware data based on the fact that the version of the second unit data is different from the version of the first unit data, and the main controller (200) can transmit the second unit data to the MLPE (200) starting from the first second unit data. Accordingly, the firmware update device of the MLPE according to an embodiment of the present invention can ensure the validity of the data by receiving and storing a plurality of unit data of the third firmware data from beginning to end instead of the second firmware data, thereby making the versions identical and maintaining continuity.

[0090] FIG. 3 is a diagram illustrating a firmware update sequence of an MLPE according to an embodiment of the present invention.

[0091] Referring to FIG. 3, the server (300) and the main controller (100) can transmit and receive data and signals via serial communication (e.g., RS485), and the main controller (100) and the MLPE (200) can transmit and receive data and signals via Power Line Communication (PLC).

[0092] First, when the server (300) transmits firmware data to the main controller (100), the main controller (100) stores it in memory (e.g., flash memory (ROM)). At this time, when the main controller (100) completes receiving and storing the firmware data, it sets a version in the firmware data.

[0093] Next, when the main controller (100) completes receiving and storing firmware data in memory, it transmits a storage completion signal to the server (300). Then, the server (300) transmits an update command to the main controller (100). Here, the update command may include unique information of the MLPE (200) that requires firmware data update.

[0094] Next, the main controller (100) checks the unique information of the MLPE (200) and sends an update command to the MLPE (200) that requires firmware data update. Then, the MLPE (200) checks the space in the memory (220) and, if there is sufficient space in the memory (220), sends an update ready signal to the main controller (100).

[0095] Next, the main controller (100) transmits the version-set firmware data to the MLPE (200). Then, the MLPE (200) stores the version-set firmware data.

[0096] Next, if the MLPE (200) needs to update the stored firmware data, it sends a firmware data reset preparation signal to the main controller (100). Then, the main controller (100) sends a reset command to the MLPE (200).

[0097] Next, MLPE (200) deletes the previously stored firmware data according to the reset command, and performs an update by receiving and storing new firmware data from the main controller (100).

[0099] FIG. 4 is a flowchart of a firmware update method for MLPE according to an embodiment of the present invention.

[0100] Referring to FIG. 4, the firmware update method of an MLPE according to an embodiment of the present invention first controls the MLPE (200) by having a processor (230) execute an application (222) that operates according to first firmware data stored in memory (220) (S10).

[0101] Next, the processor (230) determines whether the first firmware data needs to be updated (S20).

[0102] Next, if the processor (230) needs to update the previously stored first firmware data, it resets the application (S30) and executes the bootloader (221) (S40).

[0103] When the bootloader (221) is executed, the second firmware data is divided into N first unit data and received sequentially.

[0104] Here, N first unit data are set with an index, and the index is increased by 1 each time the MLPE (200) sequentially receives and stores N first unit data, and the value of the index can be from 0 to (N-1). Also, N first unit data may include version information and index information.

[0105] In contrast, if the processor (230) does not require an update of the first firmware data, it controls the MLPE (200) by executing an application (222) that operates according to the first firmware data (S10).

[0106] The processor (230) may receive third firmware data based on the fact that it stopped receiving second firmware data. Here, the third firmware data may be received as second unit data.

[0107] Specifically, the processor (230) can receive second unit data based on the fact that it stopped receiving up to the i-th first unit data (where i is a natural number greater than or equal to 1 and less than N) of the first unit data.

[0108] Next, the processor (230) determines whether the version of the first unit data stored is the same as the version of the second unit data (S50).

[0109] Here, if the version of the second unit data is different from the version of the first unit data, the processor (230) reports this to the main controller (100) (S60). Then, the application (222) is reset (S30), and the bootloader (221) is executed (S40) so that the third firmware data, which has the same version as the second unit data, can be received and stored from the beginning. At this time, the first unit data of the second firmware data that has been stored is deleted.

[0110] Next, the index information of the second unit data is checked to determine if the index value is 0 (S70). If the index value is 0, the third firmware data is received from the beginning, so the update is started anew (S90).

[0111] Next, determine whether the update was successful (S100), and if the update was successful, execute the application (S10).

[0112] Accordingly, the firmware update method of MLPE according to an embodiment of the present invention can ensure the validity of the data by receiving and storing N second unit data of third firmware data from beginning to end instead of second firmware data, thereby making the versions of the N unit data identical and maintaining continuity.

[0113] In contrast, the processor (230) can transmit index information of the i-th first unit data to the main controller (100) based on the fact that the version of the second unit data is the same as the version of the first unit data.

[0114] Next, the main controller (100) checks the index information of the i-th first unit data and transmits the (i+1)-th second unit data among the second unit data to the MLPE (200).

[0115] Next, the MLPE (200) resets the application (222) (S30) and executes the bootloader (221) (S40) to receive the (i+1)th second unit data from the second unit data to the MLPE (200). At this time, since the (i+1)th second unit data has the same version as the first unit data and the index value is not 0, the (i+1)th second unit data is inserted after the i-th first unit data (S80), and the update starts (S90).

[0116] Accordingly, the firmware update device of an MLPE according to an embodiment of the present invention can ensure the validity of the data by making the versions of the previously stored first unit data and the subsequently received second unit data identical and maintaining continuity when receiving first unit data during a second firmware update is interrupted and then subsequently received second unit data.

[0117] Next, it is determined whether the update of the second firmware data was successful (S100). At this time, if the update is successful, an application (222) that operates with the second firmware data is executed (S10), and if the update fails, the application (222) is reset and the boot loader (221) is executed (S40).

[0118] Accordingly, the firmware update method of an MLPE according to an embodiment of the present invention can ensure the validity of data by making the versions of the previously stored first unit data and the subsequently received second unit data identical and maintaining continuity when the second firmware update is interrupted and then resumed.

[0120] Although specific embodiments have been described in the detailed description of the present invention, it is understood that various modifications are possible within the scope of the invention. Therefore, the scope of the present invention is not limited to the described embodiments and should be defined by the claims set forth below and equivalents thereof. Explanation of the symbols

[0122] 100: Topic word 200: MLPE 210: Optimizer 220: Memory 230: Processor 240: Communications Department 300: Server

Claims

Claim 1 A photovoltaic power generation system comprising: a server transmitting firmware data; a main controller receiving the firmware data from the server and setting a version of the firmware data when the reception of the firmware data is completed; and a Module Level Power Electronics (MLPE) receiving the firmware data from the main controller and performing an update of the firmware data by checking the version of the firmware data, wherein the main controller divides the firmware data into N unit data (where N is a natural number greater than or equal to 2) and sequentially transmits the N unit data to the MLPE, and the MLPE receives and stores a second firmware data from the main controller, and receives a third firmware data based on the fact that the reception of the second firmware data was interrupted, wherein the second firmware data is received as a first unit data and the third firmware data is received as a second unit data. Claim 2 A solar power generation system according to claim 1, wherein the main controller increases the version of the firmware data whenever the reception of the firmware data is completed. Claim 3 A solar power generation system according to claim 1, wherein the main controller sets an index for the N unit data, and the MLPE increases the index by 1 each time it sequentially receives and stores the plurality of unit data, and the value of the index is 0 to (N-1). Claim 4 A solar power generation system according to claim 1, wherein the MLPE deletes the first firmware data based on the need to update the previously stored first firmware data, receives and stores the second firmware data from the main controller, and the version of the second firmware data is different from the version of the first firmware data. Claim 5 delete Claim 6 In claim 3, the solar power generation system receives the second unit data based on the fact that the MLPE receives the first unit data up to the i-th (where i is a natural number greater than or equal to 1 and smaller than N)-th first unit data and then stops. Claim 7 In claim 6, the MLPE determines whether the version of the second unit data is the same as the version of the first unit data in a photovoltaic power generation system. Claim 8 A photovoltaic power generation system according to claim 7, wherein the MLPE transmits index information of the i-th first unit data to the main controller based on the fact that the version of the second unit data is the same as the version of the first unit data, and the main controller verifies the index information of the i-th first unit data and transmits from the (i+1)-th second unit data among the second unit data to the MLPE. Claim 9 A photovoltaic power generation system according to claim 7, wherein the MLPE deletes the second firmware data based on the fact that the version of the second unit data is different from the version of the first unit data, and the main controller transmits the first second unit data among the second unit data to the MLPE. Claim 10 A firmware update device for MLPE comprising: a communication unit that sequentially receives firmware data divided into N (wherein N is a natural number greater than or equal to 2) unit data, wherein the version is set; and a processor that performs an update of the firmware data by checking the version of the firmware data and the index of the N unit data, wherein the index of the N unit data is set, and the index is increased by 1 each time the N unit data is sequentially received and stored, and the value of the index is 0 to (N-1), and the processor receives and stores a second firmware data, and receives a third firmware data based on the fact that the reception of the second firmware data was interrupted, wherein the second firmware data is received as a first unit data, and the third firmware data is received as a second unit data. Claim 11 A firmware update device of MLPE according to claim 10, wherein the processor deletes the first firmware data based on the need to update the previously stored first firmware data, receives and stores the second firmware data, and the version of the second firmware data is different from the version of the first firmware data. Claim 12 delete Claim 13 A firmware update device for an MLPE according to claim 10, wherein the processor receives the second unit data based on the fact that it stopped receiving the first unit data up to the i-th (where i is a natural number greater than or equal to 1 and less than N)-th first unit data. Claim 14 In claim 13, the processor is a firmware update device for MLPE that receives from the (i+1)th second unit data among the second unit data based on the fact that the version of the second unit data is the same as the version of the first unit data. Claim 15 In claim 13, the MLPE firmware update device deletes the second firmware data based on the fact that the version of the second unit data is different from the version of the first unit data, and receives from the first second unit data among the second unit data. Claim 16 A method for updating firmware of an MLPE, comprising: a step of sequentially receiving firmware data divided into N (wherein N is a natural number greater than or equal to 2) unit data, wherein the version is set; and a step of increasing an index each time the N unit data are sequentially received and stored, and performing an update of the firmware data by checking the index and the version of the firmware data, wherein the index is set for the N unit data, and the index is increased by 1 each time the N unit data are sequentially received and stored, and the value of the index is from 0 to (N-1), and the step of performing an update of the firmware data comprises: a step of receiving and storing a second firmware data; and a step of receiving a third firmware data based on the interruption of receiving the second firmware data, wherein the second firmware data is received as a first unit data, and the third firmware data is received as a second unit data. Claim 17 A firmware update method for MLPE according to claim 16, wherein the step of receiving and storing the second firmware data includes the step of receiving and storing the second firmware data by deleting the first firmware data based on the need to update the previously stored first firmware data, and receiving and storing up to the i-th first unit data (where i is a natural number greater than or equal to 1 and less than N) among the first unit data, and wherein the version of the second firmware data is different from the version of the first firmware data. Claim 18 A firmware update method for an MLPE according to claim 17, wherein the step of performing the update of the firmware data further comprises: a step of receiving starting from the (i+1)th second unit data among the second unit data based on the fact that the version of the second unit data is the same as the version of the first unit data; and a step of deleting the second firmware data and receiving starting from the first second unit data among the second unit data based on the fact that the version of the second unit data is different from the version of the first unit data.

Images