Microinverter web monitoring system for solar power generation system, and method thereof
The gateway-based system addresses inefficiencies in micro-inverter monitoring by automating recognition, ensuring version compatibility, and providing advanced UI visualization, thereby improving operational efficiency and safety in solar power systems.
Patent Information
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- DCNCA CO LTD
- Filing Date
- 2025-09-10
- Publication Date
- 2026-07-29
AI Technical Summary
Existing solar power monitoring systems based on centralized inverters struggle with inefficient and inaccurate monitoring of individual micro-inverters due to insufficient automatic recognition, protocol synchronization, emergency handling, and UI-based visualization.
A gateway-based system that automatically scans and registers micro-inverters, performs version compatibility checks, prioritizes emergency data processing, and provides advanced UI-based visualization for real-time monitoring and analysis.
Enhances operational efficiency and safety by enabling accurate, real-time monitoring and visualization of micro-inverter status, facilitating quick identification and response to issues through priority data processing and intuitive graphical interfaces.
Smart Images

Figure 112025104034744-PAT00001_ABST
Abstract
Description
Technology Field
[0001] The present invention relates to a micro-inverter web monitoring system and method for a photovoltaic power generation system, and more specifically, to a micro-inverter web monitoring system and method for a photovoltaic power generation system that can monitor the status of the photovoltaic power generation system in real time on the web, and in particular, automatically recognizes and registers a number of micro-inverters, collects and analyzes the status of each inverter in real time according to a communication protocol, and visualizes detailed information and graph-shaped data for the selected inverter through a web UI. Background Technology
[0004] Existing solar power monitoring systems are based on a centralized inverter structure, which limits their ability to accurately analyze or visualize the individual status of each inverter. With the introduction of micro-inverters, independent status monitoring for each inverter is required; however, existing systems have suffered from reduced operational efficiency and safety due to insufficient features such as automatic recognition, protocol synchronization, emergency handling, and UI-based visualization.
[0005] Accordingly, in this technology field, there is a need for technology development to automatically recognize and register multiple micro-inverters, collect and analyze the status of each micro-inverter in real time according to a communication protocol, and visualize detailed information and graph-type data regarding the selected inverter through a web UI. Prior art literature
[0007] Republic of Korea Patent Application No. 10-2013-0065779 "Solar power generation monitoring method and monitoring system" Republic of Korea Patent Application No. 10-2019-0035336 "Solar power generation fault diagnosis method and system" The problem to be solved
[0008] The present invention aims to solve the above-mentioned problems by providing a gateway-based system capable of automatically scanning and registering micro-inverters, and a communication protocol compatibility determination function that automatically performs synchronization in the event of a version mismatch, and to provide a micro-inverter web monitoring system and method for a photovoltaic power generation system.
[0009] In addition, the present invention is intended to provide a micro-inverter web monitoring system and method for a photovoltaic power generation system, which provides a priority-based data transmission and reception processing function in the event of an emergency and displays the status of each inverter in real time via the web.
[0010] In addition, the present invention is intended to provide a micro-inverter web monitoring system and method for a photovoltaic power generation system, which enables visual analysis by providing an advanced UI-based web monitoring function that magnifies detailed information and power generation graphs of a selected inverter.
[0011] However, the objectives of the present invention are not limited to those mentioned above, and other unmentioned objectives will be clearly understood by those skilled in the art from the description below. means of solving the problem
[0013] To achieve the above objective, a micro-inverter web monitoring system for a photovoltaic power generation system according to an embodiment of the present invention may be characterized by comprising: a plurality of micro-inverters (100) connected to each photovoltaic module to generate voltage, current, power generation amount, and status information; a gateway (200) that collects data from the micro-inverters (100) using a Modbus protocol; and a management server (400) that performs consistency checks and analysis of data collected from the gateway (200) connected through a network (300), and stores the results of the checks.
[0014] At this time, the present invention may provide a micro inverter web monitoring system for a solar power generation system, further comprising: a manager terminal (500) that displays information received from a management server (400) and checks or controls the system status.
[0015] In addition, the present invention may provide a micro inverter web monitoring system for a solar power generation system, further comprising a big data server (600) that stores and analyzes power generation data collected from a micro inverter (100) through a gateway (200) over a long period to perform statistics and anomaly detection.
[0016] In addition, the present invention may provide a micro inverter web monitoring system for a photovoltaic power generation system, characterized in that the management server (400) automatically scans the micro inverters (100) connected to each gateway (200) and registers the newly detected micro inverters in the database (430) by assigning a unique identifier (ID).
[0017] In addition, the present invention may provide a micro inverter web monitoring system for a solar power generation system characterized by including an emergency situation processing module (423) that prioritizes processing emergency situation data received from the micro inverter (100) and performs a warning display on the administrator terminal (500) or monitor screen when an abnormality occurs.
[0018] To achieve the above objective, a micro-inverter web monitoring method for a photovoltaic power generation system according to an embodiment of the present invention may be characterized by comprising: a first step of generating voltage, current, power generation amount, and status information from a plurality of micro-inverters (100) connected to each photovoltaic module; a second step in which a gateway (200) collects the generated information from the micro-inverters (100) using a Modbus protocol; a third step of transmitting the data collected from the gateway (200) to a management server (400) through a network; and a fourth step in which the management server (400) performs a consistency check, analysis, and storage of the check results on the data.
[0019] At this time, the present invention may provide a micro inverter web monitoring method for a photovoltaic power generation system, further comprising the step of, after the fourth step, transmitting information processed by the management server (400) to the administrator terminal (500) to check or control the system status at the administrator terminal (500).
[0020] In addition, the present invention may provide a micro inverter web monitoring method for a photovoltaic power generation system, further comprising the step of, after the fourth step, storing power generation data collected through the gateway (200) in a big data server (600), and analyzing the stored data over a long period to perform statistical compilation and anomaly detection.
[0021] In addition, the present invention may provide a micro inverter web monitoring method for a photovoltaic power generation system, characterized in that the first step further comprises: a step of automatically scanning micro inverters (100) connected to each gateway (200) in a management server (400) to detect a new micro inverter; and a step of assigning a unique identifier (ID) to the new micro inverter (100) and registering it in a database (430).
[0022] In addition, the present invention may provide a micro inverter web monitoring method for a photovoltaic power generation system, characterized in that the second step further comprises: a step in which a management server (400) preferentially processes emergency situation data received from a micro inverter (100); and a step in which, when an abnormality occurs, a warning is displayed on a manager terminal (500) or a monitor screen. Effects of the invention
[0024] A micro-inverter web monitoring system and method for a photovoltaic power generation system according to an embodiment of the present invention provides the effect of increasing convenience for installation and maintenance by automatically scanning and registering installed micro-inverters, and improving the stability and accuracy of data transmission and reception through version compatibility determination and Modbus communication automation.
[0025] In addition, the micro-inverter web monitoring system and method for a photovoltaic power generation system according to another embodiment of the present invention ensures system safety through priority processing of the Emergency channel and provides an effect that increases operational efficiency by enabling managers or maintenance personnel to quickly identify and take action on problematic inverters by intuitively providing expanded information and power generation history graphs of specific inverters.
[0026] Furthermore, the micro-inverter web monitoring system and method for a photovoltaic power generation system according to another embodiment of the present invention provides the effect of improving diagnostic precision and user experience (UX) through graph-based visualization, going beyond conventional simple table-based monitoring. Brief explanation of the drawing
[0028] FIG. 1 is a drawing showing a micro inverter web monitoring system (1) for a photovoltaic power generation system according to an embodiment of the present invention. FIG. 2 is a block diagram showing the components of a management server (400) in a micro inverter web monitoring system (1) for a photovoltaic power generation system according to an embodiment of the present invention. FIG. 3 is a flowchart illustrating the gateway and inverter registration process among the micro inverter web monitoring methods for a photovoltaic power generation system according to an embodiment of the present invention. FIG. 4 is a flowchart illustrating the consistency determination and Modbus data procedure among the micro-inverter web monitoring method for a photovoltaic power generation system according to an embodiment of the present invention. FIG. 5 is a flowchart illustrating emergency channel-based emergency situation processing among micro-inverter web monitoring methods for a photovoltaic power generation system according to an embodiment of the present invention. FIG. 6 is a flowchart illustrating a web UI-based detailed monitoring process among the micro inverter web monitoring methods for a photovoltaic power generation system according to an embodiment of the present invention. Specific details for implementing the invention
[0029] Hereinafter, a detailed description of preferred embodiments of the present invention will be given with reference to the accompanying drawings. In describing the present invention below, if it is determined that a detailed description of related known functions or configurations may unnecessarily obscure the essence of the present invention, such detailed description will be omitted.
[0030] In this specification, when one component 'transmits' data or a signal to another component, it means that the component may transmit said data or the signal directly to the other component, or may transmit said data or the signal to the other component through at least one other component.
[0032] FIG. 1 is a drawing showing a micro-inverter web monitoring system (1) for a photovoltaic power generation system according to an embodiment of the present invention. Referring to FIG. 1, the micro-inverter web monitoring system (1) may include a plurality of micro-inverters (100), a gateway (200), a network (300), a management server (400), a plurality of administrator terminals (500), and a big data server (600).
[0033] The micro inverter (100) is a plurality of micro inverters attached to a solar power generation device, and each micro inverter (100) generates individual power generation data in real time.
[0034] In the present invention, the micro inverter (100) stores voltage, current, power generation amount, status information, etc. in a register, and can respond when the gateway (200), which is a master device, requests this information via Modbus. At this time, the communication priority refers to which information should be requested and processed first, and, for example, important information such as fault status or power generation amount can be set to be processed first.
[0035] Modbus is an industrial protocol for communication between devices in a photovoltaic power generation system and can be used when equipment such as a micro-inverter (100) exchanges data. That is, Modbus is an open standard protocol and is a communication method based on a Master-Slave structure, and Modbus TCP / IP operates based on Ethernet, enabling fast and stable data transmission.
[0036] The gateway (200) acts as a relay between the micro inverter (100) and the upper network, and can aggregate and transmit data collected from the micro inverter (100).
[0037] The network (300) provides a data communication path between the gateway (200), the management server (400), the administrator terminal (500), and the big data server (600). Wired or wireless LAN / WAN technology can be applied.
[0038] The management server (400) is a central control and data processing device for the entire system, and checks the consistency of, stores, and analyzes data received from the gateway (200), and can be linked with the management terminal (500) and the big data server (600).
[0039] Multiple administrator terminals (500) can be various terminals operated by an administrator, such as PCs, tablets, and smartphones, and can access the system monitoring and control interface through each administrator terminal (500).
[0040] The big data server (600) stores and analyzes long-term accumulated power generation data and monitoring information, and supports additional functions such as statistics, performance evaluation, and anomaly detection.
[0041] Through this configuration, the systems can operate in conjunction to efficiently perform real-time data collection, analysis, and monitoring functions for the entire system.
[0042] More specifically, in a solar power plant system where multiple micro-inverters (100) are installed, the micro-inverters (100) can be automatically recognized and registered through a gateway (200), and data from each micro-inverter (100) can be collected at a preset interval (e.g., 10 seconds). The administrator checks the real-time status on a monitor separately provided on the management server (400) or on a web dashboard on the administrator terminal (500), and when the micro-inverter (100) in which an abnormal value has occurred is selected, graphs and detailed information such as the daily power generation trend, instantaneous output, and cumulative power generation of the micro-inverter (100) can be displayed on the screen. The management server (400) can ensure that an immediate notification is delivered to the administrator by performing priority processing settings with a red indicator on the monitor or administrator terminal (400) when an emergency situation of the micro-inverter (100) is detected.
[0044] FIG. 2 is a block diagram showing the components of a management server (400) of a micro inverter web monitoring system (1) for a photovoltaic power generation system according to an embodiment of the present invention. Referring to FIG. 2, the management server (400) may include a transmission / reception unit (410), a control unit (420), and a database (430).
[0045] The transmitting and receiving unit (410) provides a communication interface for transmitting and receiving data from a gateway (200) or other terminals, and supports various communication standards (e.g., TCP / IP, UDP, Modbus, etc.) to ensure stable transmission of data.
[0046] The control unit (420) is a core processing unit of the management server (400) and includes modules such as a registration processing module (421), a data collection module (422), an emergency situation processing module (423), a monitoring module (424), and an additional information provision module (425) inside.
[0047] The registration processing module (421) can perform automatic registration of the gateway (200) and the micro inverter (100) when the solar power generation system is initialized. The registration processing module (421) collects identification information (ID) and initial state data of the micro inverter (100) and registers them in the database (430), and when registering a new inverter, it can determine whether there is a duplicate by comparing it with existing information.
[0048] The data collection module (422) can collect Alive information and Modbus data, etc. from the gateway (200) or the directly connected micro-inverter (100).
[0049] The data collection module (422) can convert the collected raw data into a structured format by applying a data collection cycle, data classification by channel, and a real-time parsing algorithm.
[0050] When Emergency data is received from the micro inverter (100) or gateway (200), the Emergency Processing Module (423) can prioritize processing the data and issue a warning. The Emergency Processing Module (423) executes a rapid response process based on the Emergency data and can provide an immediate notification to the administrator.
[0052] The monitoring module (424) displays real-time monitoring information on a web-based user interface (UI) based on collected data and inverter information of the registered micro inverter (100). The monitoring module (424) may include functions for updating data on a dashboard transmitted to a manager terminal (500) via a network (300), generating graphs and charts, and analyzing abnormal signs.
[0054] The additional information provision module (425) can collect and combine external environmental information of the solar power plant (e.g., weather data, maintenance schedule, power demand forecast, etc.) to provide additional information.
[0056] The database (430) stores and manages all relevant information, such as identification information of registered microinverters (100), collected real-time data, and historical data.
[0057] The database (430) is linked with the big data server (600) and used for long-term data analysis and performance evaluation.
[0058] In this way, each module within the management server (400) performs a mutually complementary role, significantly improving the reliability and real-time processing capability of the entire monitoring and control system.
[0060] FIG. 3 is a flowchart illustrating the gateway and inverter registration process in a micro inverter web monitoring method for a photovoltaic power generation system according to an embodiment of the present invention. Referring to FIG. 3, the management server (400) performs gateway (200) registration (S11).
[0061] More specifically, after initializing a solar power generation system unit composed of a plurality of micro-inverters (100) connected to at least one gateway (200), the management server (400) can receive and register identification information and status data of the gateway (200) within the unit connected via the network (300).
[0062] After step (S11), the management server (400) performs a solar micro-inverter scan (S12). That is, the management server (400) automatically scans all micro-inverters (100) connected to each gateway (200) connected via the network (300), thereby distinguishing between newly detected micro-inverters (100) and existing registered micro-inverters (100) based on the scan results.
[0063] After step (S12), the management server (400) performs micro-inverter registration and ID assignment (S13). That is, the management server (400) assigns a unique ID to the detected new micro-inverter (100) and performs a registration procedure on the database (430), and the registration information is stored in the database (430) so that it can be used for data collection and control thereafter.
[0064] After step (S13), the management server (400) performs micro-inverter array configuration (S14). That is, the management server (400) configures the micro-inverters (100) registered in step (S130) into a logical / physical array structure according to their location, function, or other criteria, thereby making it easy to distinguish and group the micro-inverters (100).
[0065] After step (S14), the management server (400) can start monitoring (S15). That is, after the final registration and arrangement in step (S14) are completed, the management server (400) can start real-time monitoring and continuously collect status information of each micro inverter (100).
[0067] FIG. 4 is a flowchart illustrating the consistency determination and Modbus data procedure among the micro-inverter web monitoring method for a photovoltaic power generation system according to an embodiment of the present invention. Referring to FIG. 4, when power is turned ON (S21), the gateway (200) can perform network initialization and preprocessing for system operation by starting booting according to the power supply.
[0068] After step (S21), in network initialization (S22), the gateway (200) can perform communication initialization through a wired / wireless network interface, thereby enabling IP setting, port opening, etc., for communication with the management server (400) through the network (300).
[0069] After step (S22), in the Alive data transmission (S23) (MAC Address, Protocol, Parsing, Inverter), the gateway (200) transmits a data packet containing initial state information such as MAC Address, Protocol version, Parsing version, and Inverter version along with an Alive signal to the management server (400) through the network (300), thereby notifying the management server (400) that the gateway (200) is operating normally and requesting version verification.
[0070] After step (S23), in version data transmission (S24) (Protocol, Parsing, Inverter), the gateway (200) transmits detailed version data, such as the currently loaded Protocol version, Parsing version, and Inverter version, to the management server (400) through the network (300), thereby enabling a comparison of consistency with the version stored on the management server (400).
[0071] After step (S24), in determining whether the version data matches (S25), the management server (400) can perform a comparison between the version data received from the gateway (200) and the standard version information stored in the database (430), thereby allowing the branch flow to proceed to step (S26) / (S30) via the conditional branch described later, depending on whether they match.
[0072] When the result of the judgment in step (S25) determines that the version data does not match (NO) or that the Protocol version does not match (S26a), in performing a Protocol data request (S27a), the management server (400) can proceed to step (S27a) when it confirms that the received Protocol version is different from the server standard version.
[0073] Additionally, when the judgment result of step (S25) determines that the version data does not match (NO) or that the Parsing version does not match (S26b), in performing a Parsing data request (S27b), the management server (400) can proceed to step (S27b) when it confirms that the received Parsing version is different from the server standard version.
[0074] Additionally, when the judgment result of step (S25) determines that the version data does not match (NO) or that the Inverter version does not match (S26c), in performing an Inverter data request (S27c), the management server (400) can proceed to step (S27c) when it confirms that the received Inverter version is different from the server standard version.
[0075] That is, in steps (S27a, S27b, S27c), the management server (400) can send the latest data request packet for each mismatch item (Protocol, Parsing, Inverter) to the gateway (200) through the network (300).
[0076] After steps (S27a, S27b, S27c), in the configuration and transmission start of each Protocol, Parsing, and Inverter data frame according to the reception request (S28), the gateway (200) configures the requested Protocol, Parsing, and Inverter data frame to the management server (400) via the network (300) and then starts transmitting the configured data frame to the management server (400) via the network (300), and may perform data transmission following a binary or JSON structure.
[0077] After step (S28), in the processing of the memory updater for the received Protocol, Parsing, and Inverter data system structure (S29), the management server (400) can complete the preparation for Modbus communication in accordance with the latest communication standards and parsing methods by updating the version data (Protocol, Parsing, Inverter) received according to step (S28) into the internal system memory structure.
[0078] After step (S29), if the version data matches as a result of the judgment in step (S25) (YES), in the verification of the match of all version information (Protocol, Parsing, Inverter) on the server side (S30), the version consistency verification is completed, and the management server (400) confirms that all version information (Protocol, Parsing, Inverter) received from the gateway (200) through the network (300) matches the server standard version, and can proceed to the Modbus data collection procedure after step (S31) when all items match.
[0079] After step (S30), in the sequential Modbus data transmission per channel (S31), the management server (400) can collect inverter operation status and power generation data by transmitting sequential requests per channel based on the Modbus485 protocol to the gateway (200) connected to the network (300) for each micro inverter (100) connected to the gateway (200).
[0080] After step (S31), in the data classification and storage (S32) based on parsing data after receiving a Modbus485 response, the gateway (200) can classify and store data according to data type (voltage, current, temperature, etc.) by analyzing the Modbus response data received from each micro-inverter (100) using a specified parsing method.
[0081] After step (S32), in the transmission of inverter structure information to the server (S33) when data of one inverter is completed, the gateway (200) can transmit the structured data object to the management server (400) through the network (300) after receiving and analyzing all data of one inverter among the plurality of operating micro-inverters (100) connected to it.
[0082] In step (S33), in the application of received data update processing (S34), the management server (400) can update and store real-time status information, power generation amount, abnormality status, etc. based on the received inverter data, thereby enabling real-time updates of the monitoring screen and reflection of analysis logic.
[0084] FIG. 5 is a flowchart illustrating an Emergency channel-based emergency situation processing among a micro-inverter web monitoring method for a photovoltaic power generation system according to an embodiment of the present invention. Referring to FIG. 5, in receiving Emergency data (S41), a management server (400) or a gateway (200) may receive Emergency data indicating an abnormal operating state from each micro-inverter (100). This Emergency data may be data that is automatically transmitted in situations that may be directly related to system safety, such as when the micro-inverter (100) rises above a threshold, when the output is suddenly interrupted, or when an overcurrent or reverse current is detected.
[0085] After step (S41), in the case of priority transmission (S42a) when Emergency data occurs, Modbus sequential transmission processing (transmission at intervals of about 1 second) to the Emergency setting channel and transmission of response result to the server (S42b), when Emergency data is received, the management server (400) processes the transmission of the corresponding Emergency channel with priority separately from the request for general status information data in step (S42a), that is, in the event of an emergency, it preempts data processing for the corresponding micro-inverter (100) over all general status communications and can intensively allocate system resources.
[0086] At the same time as step (S42a), in step (S42b), the management server (400) can transmit sequential status check commands at 1-second intervals via Modbus communication based on the channel number set in the micro inverter (100) where the Emergency is detected, and receive the response data.
[0087] For example, when an abnormal output due to overheating is detected in channel 3 of the micro inverter (100), the gateway (200) quickly requests the temperature, output voltage, current, internal error code, etc. of the channel in sequence, and the transmission cycle is set to approximately 1 second. This short interval data collection greatly improves the real-time responsiveness of the system.
[0088] After steps (S42a) and (S42b), in receiving the Emergency result (S43), the Emergency response result collected from the requested micro-inverter (100) is transmitted in real time to the management server (400) through the gateway (200), so that the management server (400) can analyze the real-time data to evaluate whether the emergency situation is continuing, its severity, etc.
[0089] After step (S43), in the transition to a system warning and execution of an administrator alarm (S44), the evaluation result generated by the management server (400) is switched to a warning state within the system, and the information can be transmitted to the administrator in real-time as an alarm via a web-based UI or a mobile administrator terminal (500) through the network (300) (S44). At this time, the alarm can be implemented in various ways, such as a visual notification (red flashing), an audible notification, or a push notification, and can also be delivered via email or SMS depending on the settings.
[0090] For example, when the PV input voltage drops sharply in a specific micro inverter (100) within a solar power plant, and at the same time the output power is detected as 0 and the internal temperature rises abnormally, the gateway (200) immediately transmits the information to the management server (400) via the network (300) through the Emergency channel, and the management server (400) interprets this and determines it to be an “overheating / output cutoff” situation, displays a red warning indicator on the management UI, and at the same time sends a message to the administrator via smartphone notification saying “Inverter No. 3 overheating — output stopped. Immediate inspection required.”
[0091] Thus, the present invention provides the effect of maximizing the stability and operational efficiency of a photovoltaic power generation system through emergency situation detection and response functions using an Emergency channel, and enables immediate action through real-time data processing and administrator warning functions.
[0093] FIG. 6 is a flowchart illustrating a web UI-based detailed monitoring process among a micro inverter web monitoring method for a photovoltaic power generation system according to an embodiment of the present invention. Referring to FIG. 6, in displaying the entire inverter list and status on the UI (S51), the management server (400) can transmit the list and status information of the entire micro inverter (100) to the administrator terminal (500) via the network (300) so that it can be displayed on the UI screen of the administrator terminal (500).
[0094] After step (S51), in step (S52), the manager terminal (500) can wait for the selection of a specific micro inverter (100) by receiving selection input information based on the manager's input on the UI screen.
[0095] After step (S52), in outputting monitoring information for the selected micro-inverter (S53), the management server (400) can transmit real-time monitoring information (voltage, current, output, power generation amount, etc.) corresponding to a specific micro-inverter (100) selected by the manager to the manager terminal (500) via the network (300) so that it can be displayed on the UI screen of the manager terminal (500).
[0096] Here, the management server (400) can provide detailed information (voltage, current, output, cumulative power generation, etc.) regarding the selected micro inverter (100), a graph of power generation on a daily / weekly / monthly basis, automatic analysis of abnormal signs, and color warnings to the administrator terminal (500) via the network (300). That is, by providing detailed data pop-up and graphing functions based on administrator interaction, the management server (400) can generate detailed information such as voltage / current / output / temperature / cumulative power generation when the administrator selects a specific micro inverter (100), and can provide information to the administrator terminal (500) via the network (300) to output the daily / weekly / monthly power generation of the selected inverter as a dynamic graph based on the time axis, which is automatically generated and updated.
[0097] In addition, as another embodiment of the present invention, unlike existing systems that merely listed the status of microinverters (e.g., ON / OFF, voltage / current, etc.) in text form, the present invention can provide a complex, intuitive, and analysis-oriented user UI as follows.
[0098] First, the management server (400) can generate a real-time visualization map of the entire inverter status and provide it to the administrator terminal (500).
[0099] That is, the management server (400) can configure a physical array-based or ID-based inverter UI and generate an overall map with automatic color differentiation (e.g., green / yellow / red) according to normal / caution / failure status to provide a system-wide status summary and status statistics (e.g., 5 or more status warnings out of 100 total).
[0100] Additionally, the management server (400) can provide real-time color warning and annotation message (e.g., "Output instability detected") display information for each micro inverter (100) detected by an AI-based automatic detection of abnormal signs and color warning algorithm, by performing an abnormality detection algorithm according to preset criteria (e.g., output abnormal deviation, temperature abnormal rise rate, etc.) for each micro inverter (100), to the manager terminal (500) via the network (300).
[0101] Here, the management server (400) can provide a remote reboot or inspection command function via the network (200) by the manager terminal (500) for the micro inverter (100) by sending a push notification or email via the network (300) to the manager terminal (500) operated by a pre-designated manager when an abnormal sign occurs through notification linkage and remote control connection.
[0103] Looking at the additional extension example of FIG. 6, the entire list of micro-inverters can be arranged according to the physical placement order or logical ID order connected to the network (300), and the status of each micro-inverter (100) is represented with a color icon or a real-time value. The management server (400) can collect status information of each micro-inverter (100) and transmit key status values such as temperature, output, current, voltage, internal fault code, and accumulated power generation to the manager terminal (500) via the network (300) as UI information visualized in real-time.
[0104] When a selection signal for a micro inverter (100) is received on the UI of the administrator terminal (500), the administrator terminal (500) receives detailed data of the micro inverter (100) selected according to the request from the management server (400) via the network (300) and displays it in a separate popup or extended UI area. At this time, each item (e.g., voltage, current, output, power generation amount, etc.) can be dynamically generated as a time-series graph in daily / weekly / monthly units as well as numerical values and provided visually. The graph is automatically generated based on time-series log data stored in the management server (400) and can be implemented using Highcharts, Chart.js, or an SVG-based Canvas API.
[0105] In particular, the management server (400) of the present invention can automatically detect abnormal signs by receiving setting information through the administrator terminal (500) in advance regarding the normal range of the micro inverter (100) or by analyzing abnormal deviations in past power generation data using machine learning or rule-based algorithms, and the micro inverter (100) can be visualized on the administrator terminal (500) as a color warning (e.g., red highlighting, flashing, etc.) and an alarm message on the UI.
[0106] For example, if a decrease in output of more than 20% compared to the average output over the past 7 days is detected and at the same time the rate of temperature rise increases rapidly, the management server (400) may be configured to automatically display a 'performance degradation' or 'overheating risk' warning for the micro inverter (100), and this information may be delivered to the administrator terminal (500) as a push notification or warning message.
[0107] As such, the UI configuration of the present invention can provide an advanced monitoring interface that integrates user interaction-based multidimensional data provision, automated visualization, anomaly analysis, and alarm functions, rather than a simple list of numerical values.
[0109] In another embodiment of the present invention, when a total of 128 micro-inverters (100) are installed in a solar power plant in an 8-column × 16-row structure, the status of each micro-inverter (100) is displayed in a column / row-based matrix form on the UI of the administrator terminal (500). When micro-inverter (100) #(number)3(column)-12(row) is normally green (normal state) but is displayed as yellow (caution) because an abnormal deviation in output current occurred during the last 2 hours, and when a selection signal for the micro-inverter (100) displayed on the administrator terminal (500) is input, the administrator terminal (500) can output detailed information corresponding to the returned monitoring information in response to a request for monitoring information regarding the selected micro-inverter (100) to the management server (400) via the network (300), and then output a warning message stating that the output current is 30% lower than the reference value and the temperature rise rate is abnormally high. In addition, the administrator terminal (500) can utilize monitoring information to display a graph of daily / weekly / monthly power generation at the bottom, so that the output of the micro inverter (100) has been gradually decreasing over the past few days, allowing visual confirmation.
[0110] In addition, as another embodiment of the present invention, an emergency situation is detected in micro inverter (100) #5-7 and a warning message is transmitted to the management server (400) through the Emergency channel of the gateway (200), and the management server (400) can automatically analyze data regarding the detected micro inverter (100) and provide monitoring information to make the micro inverter (100) flash red on the UI of the administrator terminal (500) through the network (300).
[0111] Since the administrator can check abnormal data in the real-time status window on the administrator terminal (500), the administrator terminal (500) can immediately transmit a reset command for the micro inverter (100) connected to the gateway (200) via the network (300) according to the input of a remote reset command for the micro inverter (100) via the web UI.
[0113] According to another embodiment of the present invention, a micro-inverter web monitoring method for a photovoltaic power generation system can be provided, comprising a UI interface that intuitively enlarges and displays detailed information of a selected micro-inverter (100) and a method of operation thereof.
[0114] More specifically, in this embodiment, when the status of all micro-inverters (100) is displayed in real time on a matrix UI (e.g., 8 rows × 16 columns), a detailed popup interface for a specific micro-inverter (100) is automatically generated and displayed in an enlarged form when input is made by clicking (or touching) on the administrator terminal (500). This popup is generated centered on the location of the selected micro-inverter (100), and the list of other inverters is blurred or translucent to improve visual focus.
[0115] The enlarged popup UI includes the following key technical elements.
[0116] First, a zoomable UI for the administrator terminal (500) can be created based on a structured information object containing real-time data (voltage, current, temperature, output, cumulative power generation, etc.) of the selected inverter, using a zoomable inverter detailed information UI configuration module (ZoomDetailUI Module) on the management server (400). In this case, the inverter detailed information UI configuration module performs rendering using dynamic components based on React or Vue.js, and can control the maintenance of a real-time data stream between the management server and the administrator terminal through WebSocket or Server-Sent Events. Here, the time series graph is dynamically generated using Chart.js, D3.js, or WebGL-based SVG, and can reflect changes in data in real time.
[0117] Next, as a technical element corresponding to a mouse hover or touch-based event handler (SelectionEventHandler) on the management server (400), a selection signal (click / touch) is detected on the administrator terminal (500), and an expansion request is triggered based on the ID, location, and status code of the selected inverter. When an event occurs, the management server (400) can query the database (430) for the last 24 hours of power generation logs for the selected inverter and return a JSON response packet containing detailed time-series data.
[0118] In addition, a time series graph is automatically generated on a daily / weekly / monthly basis for items such as power generation, output, temperature, and voltage through a series dynamic graph and anomaly detection visualization module (GraphView + AnomalyOverlay) on the management server (400). The series dynamic graph and anomaly detection visualization module provides a visual warning by highlighting the corresponding point with a red line or area in the event of a deviation from the normal range (e.g., deviation of more than 20% from the average, rapid temperature rise, etc.). Additionally, depending on the administrator's interaction, functions such as zooming in on the graph, specifying sections, and comparison mode (e.g., comparison with other inverters) can also be provided.
[0119] Additionally, the management server (400) provides a button-shaped interface to the manager terminal (500) so that remote commands such as 'reset', 'view detailed log', 'download log', and 'set function restriction' can be executed immediately within the enlarged detailed information window through the Remote Command UI function. When a click occurs on the manager terminal (500), a command packet is internally transmitted to the management server (400) via the network (300), and a flow of Gateway (200) → Modbus command transmission → response reception → result UI update for the corresponding micro inverter (100) can be implemented.
[0120] Additionally, the administrator server (400) can set inverter items that are frequently referenced by each administrator (e.g., view only voltage and temperature) or standard ranges (e.g., abnormality notification when output is 200W or more) by providing a user customization interface (Custom View Template) to the administrator terminal (500), and the settings can be automatically reflected in the configuration form and display items of the enlarged UI according to the administrator account.
[0122] The present invention can also be implemented as computer-readable code on a computer-readable recording medium. A computer-readable recording medium includes all types of recording devices in which data that can be read by a computer system is stored.
[0123] Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage devices, and also include those implemented in the form of carrier waves (e.g., transmission over the Internet).
[0124] In addition, computer-readable recording media are distributed across networked computer systems, allowing computer-readable code to be stored and executed in a distributed manner. Furthermore, functional programs, codes, and code segments for implementing the present invention can be easily inferred by programmers in the technical field to which the present invention belongs.
[0126] As described above, preferred embodiments of the present invention have been disclosed in this specification and drawings. Although specific terms have been used, they are used merely in a general sense to facilitate the explanation of the technical content of the invention and to aid in understanding the invention, and are not intended to limit the scope of the invention. It is obvious to those skilled in the art that, in addition to the embodiments disclosed herein, other variations based on the technical concept of the present invention may be implemented. Explanation of the symbols
[0128] 1 : Microinverter Web Monitoring System for Solar Power Generation Systems 100 : Microinverter 200 : Gateway 300 : Network 400 : Management Server 410 : Transmitter / Receiver 420 : Control unit 421 : Registration Processing Module 422 : Data collection module 423 : Emergency Handling Module 424 : Monitoring Module 425 : Additional Information Provision Module 430 : Database 500 : Administrator terminal 600 : Big Data Server
Claims
Claim 1 delete Claim 2 delete Claim 3 delete Claim 4 delete Claim 5 delete Claim 6 A first step in which a management server (400) performs gateway (200) registration, wherein, after initializing a solar power generation system unit composed of a plurality of micro-inverters (100) connected to at least one gateway (200), it receives identification information and status data of the gateway (200) within the unit connected via a network (300) and registers them; A second step in which the management server (400) performs a solar micro-inverter scan, by scanning all micro-inverters (100) connected to each gateway (200) connected via the network (300), and distinguishes between newly detected micro-inverters (100) and existing registered micro-inverters (100) according to the scan results; a third step in which the management server (400) performs micro-inverter registration and ID assignment, by assigning a unique ID to the detected new micro-inverter (100), performing a registration procedure on the database (430), and storing the registration information in the database (430); a fourth step in which the management server (400) performs micro-inverter array configuration, by configuring the array structure according to criteria including the location and function of the micro-inverter (100) registered in the third step, and performing distinction and grouping among the micro-inverters (100); and a fourth step in which the management server (400) starts monitoring, by starting real-time monitoring after the array is completed in the fourth step, and continuously monitors the status information of each micro-inverter (100). A fifth step of collecting; wherein the first step comprises: a first-1 step in which the gateway (200) starts booting upon power supply for consistency determination and Modbus data procedures; and a first-2 step in which the gateway (200) performs IP setting and port opening for communication with the management server (400) through the network (300) by performing communication initialization through a wired / wireless network interface.Step 1-3, in which the gateway (200) transmits a data packet containing initial state information including MAC Address, Protocol version, Parsing version, and Inverter version along with an Alive signal to the management server (400) via the network (300), thereby notifying the management server (400) that the gateway (200) is operating normally and requesting version verification; Step 1-4, in which the gateway (200) performs a request for consistency comparison with the version stored on the management server (400) side following the transmission of version data including the currently installed Protocol version, Parsing version, and Inverter version to the management server (400) via the network (300); The management server (400) performs a comparison between the version data received from the gateway (200) and the standard version information stored in the database (430), thereby proceeding with a branching flow to a conditional branch depending on whether they match. If the judgment result indicates that the version data does not match, and thus indicates a Protocol version mismatch, a Parsing version mismatch, or an Inverter version mismatch, the management server (400) transmits a request packet for the latest data regarding each mismatch item (Protocol, Parsing, Inverter) to the gateway (200) via the network (300). The gateway (200) constructs the requested Protocol, Parsing, and Inverter data frames and transmits them to the management server (400) via the network (300). The management server (400) updates the received version data in an internal system memory structure to switch to a Modbus communication readiness state that matches the latest communication standards and parsing methods. When the switch is completed or the version data matches as a result of the judgment, the management server (400) classifies the version consistency verification as complete and proceeds to the Modbus data collection procedure. Steps 1-5;Step 1-6, in which a management server (400) collects inverter operation status and power generation data by transmitting channel-specific sequential requests based on the Modbus 485 protocol to a gateway (200) connected to a network (300) for each micro-inverter (100) connected to the gateway (200); Step 1-7, in which the gateway (200) performs classification and storage according to data types including voltage, current, and temperature by analyzing Modbus response data received from each micro-inverter (100) using a specified parsing method; Step 1-8, in which the gateway (200) transmits a structured data object to the management server (400) via the network (300) after completing the reception and analysis of data from one of the plurality of operating micro-inverters (100) connected to it; and Step 1-9, in which the management server (400) switches to a state where real-time monitoring screen updates and analysis logic can be reflected by updating and storing real-time status information, power generation amount, and abnormality status based on the received inverter data. The above 5th step includes: a 5-1 step in which a management server (400) or a gateway (200) receives Emergency data indicating an abnormal operating state from each micro-inverter (100); a 5-2 step in which the management server (400) processes the transmission of the Emergency channel with priority separately from the request for general status information data, preempts data processing for the corresponding micro-inverter (100) with priority over general status communication when an emergency occurs, and intensively allocates system resources, and simultaneously, the management server (400) transmits sequential status check commands at preset time intervals via Modbus communication based on the channel number set for the micro-inverter (100) where the Emergency was detected, and receives response data.In receiving Emergency results, the Emergency response result collected from the requested micro-inverter (100) is transmitted in real time to the management server (400) through the gateway (200), thereby allowing the management server (400) to analyze real-time data and evaluate whether the emergency situation persists and its severity, in step 5-3; the evaluation result generated by the management server (400) is recorded as warning status information in the system internal database, and the management server (400) transmits the converted warning information in the form of a real-time alarm to a web-based UI or a mobile administrator terminal (500) through the network (300), in step 5-4; A 6-1 step in which, after the 5th step, the management server (400) transmits a list and status information of all micro inverters (100) to the administrator terminal (500) via the network (300) so as to display it on the UI screen of the administrator terminal (500); a 6-2 step in which the administrator terminal (500) waits for a selection operation of a specific micro inverter (100) by receiving selection input information based on the administrator's input on the UI screen; and a 6-3 step in which the management server (400) transmits information including voltage, current, output, and power generation amount as real-time monitoring information corresponding to the selected specific micro inverter (100) to the administrator terminal (500) via the network (300) so as to display it on the UI screen of the administrator terminal (500).Including, in the above 6-3 step, the management server (400) provides detailed information including voltage, current, output, and cumulative power generation information for the selected micro inverter (100), a daily / weekly / monthly power generation graph, automatic analysis of abnormal signs, and color warnings to the administrator terminal (500) via the network (300); generates a real-time visualization map of the overall inverter status and provides it to the administrator terminal (500), configuring a physical array-based or ID-based inverter UI, and generates an overall map through automatic color classification distinguished by green / yellow / red according to normal / caution / fault status to provide a summary of the overall system status and status statistics; and through an AI-based automatic abnormal sign detection and color warning algorithm, performs an abnormal detection algorithm for each micro inverter (100) according to preset criteria including output abnormal deviation and temperature abnormal rise rate, thereby providing real-time color warning and annotation message display information for the detected abnormal micro inverter (100) to the administrator terminal (500) via the network (300). A micro inverter web monitoring method for a solar power generation system, characterized in that when an abnormal sign occurs, a management server (400) transmits a push notification or email to a manager terminal (500) operated by a pre-designated manager via a network (300) through notification linkage and remote control connection, thereby providing a remote reboot or inspection command function via a network (200) by the manager terminal (500) for the micro inverter (100). Claim 7 In claim 6, the 6-3 step comprises: the entire list of micro-inverters provided to the management server (400) being arranged according to a physical placement order or logical ID order connected to the network (300); the status of each micro-inverter (100) being represented with a color icon or real-time numerical value; the management server (400) collecting status information of each micro-inverter (100) and transmitting status values including temperature, output, current, voltage, internal fault code, and accumulated power generation amount as real-time visualized UI information to the administrator terminal (500) via the network (300); when a selection signal for a micro-inverter (100) is received on the UI of the administrator terminal (500), the administrator terminal (500) receives detailed data of the micro-inverter (100) selected according to the request from the management server (400) via the network (300) and displays it in a separate popup or extended UI area, and each item including numerical values including voltage, current, output, and power generation amount as well as daily / weekly / monthly A web monitoring method for a micro inverter for a solar power generation system, characterized in that it includes a time series graph, the graph is automatically generated based on time series log data stored in a management server (400), and is implemented using Highcharts, Chart.js, or an SVG-based Canvas API, and the management server (400) receives setting information regarding the normal range of the micro inverter (100) in advance through a manager terminal (500) or analyzes abnormal deviations in past power generation data using machine learning or a rule-based algorithm to automatically detect abnormal signs, and provides the micro inverter (100) that is outside the normal range to the manager terminal (500) as color warning and alarm message information on the UI. Claim 8 delete Claim 9 delete Claim 10 delete