KR20170122150A - The Monitoring System for Photovoltaic Power Generation and the Method Thereof - Google Patents

Abstract

The present invention relates to a system for monitoring solar power generation, which can improve the compatibility with an existing legacy system by allowing data integration between monitoring systems using different types of protocols on the basis of a metamodel, and automatically generates a code capable of processing data to also automatically generate a program capable of processing a protocol through the generated code, such that even a user who does not know the protocol well, can easily connect devices, and to a method thereof. The method for monitoring solar power generation using a plurality of solar power generating facilities installed and distributed in each local area, and an integrated server for integrally managing the solar generating facilities comprises the steps of: generating an integrated communications protocol applied to both of a plurality of solar power generating facilities and an integrated server; individually modeling a communications protocol individually used in each of the solar power generating facilities in order to provide collected data for the integration server on the basis of a metamodel; generating the communications protocol individually modeled on the basis of the metamodel as code; and mapping the generated code to an integrated metamodel designed in the integrated server.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a monitoring system for a photovoltaic power generation,

The present invention relates to a solar monitoring system and method thereof, and more particularly, to a solar monitoring system for integrating data based on a meta model so as to be compatible with servers using different types of communication protocols, It is about the method.

Recently, the international community is facing increasing problems of energy depletion due to the continuous increase of the world population, oil price instability and limited resources, and the interest in renewable energy is increasing.

Renewable energy refers to renewable energy such as fuel cells, hydrogen, coal liquefaction, and gas, and renewable energy such as solar, solar, bio, wind, hydro, marine, and geothermal. It refers to the energy that transforms and uses renewable energy including sunlight, water, geothermal, precipitation, and biological organisms.

In particular, PV modules are attracting attention as new and renewable energy sources have been attracting attention because the price of solar modules has fallen and the efficiency has been enhanced due to the development of solar energy technology.

However, because solar energy stores energy as electricity, there is a risk of fire, and due to the large size of the structure, damage to structures caused by natural disasters can cause damage to people. In addition, solar power generation requires rapid management in order to achieve an efficient power generation rate because of rapid change of power production due to the change of climate such as sunshine. In Korea, it is mandatory to provide an integrated monitoring system for improving the energy production, operation status and utilization rate of photovoltaic power generation facilities. However, the power generation facilities in the unit of Eup / Myeon / Dong are often not managed. In addition, solar energy facilities can not be operated after the maintenance period is over, and if the developers or constructors are bankrupt or withdrawn from the domestic branch office, they will no longer be able to perform technical support and maintenance.

For example, Korean Patent No. 10-1415163 (hereinafter referred to as "Patent Document 1") discloses a photovoltaic power generation system for a photovoltaic Power generation monitoring system.

The above patent document 1 relates to a photovoltaic power generation monitoring system for monitoring the real-time monitoring of a photovoltaic power generation system installed in each area through a network to facilitate maintenance, and it converts solar energy into electric energy A photovoltaic power generation unit provided in each of the photovoltaic power generators, and various information measured by the photovoltaic power generation unit, the photovoltaic power generation unit being connected to the photovoltaic power generation unit, And a solar power monitoring unit for monitoring the solar power.

However, in the above-described Patent Document 1, the type of protocol used between the solar power generation unit and the power generation measurement unit may be different by monitoring through the network. In this case, a description of a method of interoperating or integrating heterogeneous protocols is not disclosed in the above-mentioned Patent Document 1.

Patent Document 1: Korean Patent No. 10-1415163

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems of the prior art, and it is possible to integrate data between monitoring systems using different types of protocols based on a meta model, thereby improving compatibility with existing legacy systems.

In addition, the present invention can automatically generate a code capable of processing data, and a program capable of processing a protocol through the generated code is also automatically generated, so that even a user who does not know the protocol can easily connect the devices.

A monitoring method for solar power generation according to the present invention is a monitoring method for a solar power generation using a plurality of solar power generation facilities distributed in each region and an integrated server for integrally managing the solar power generation facilities, Wherein the step of generating an integrated communication protocol to be applied to both the facility and the integrated server comprises the steps of: A protocol modeling step of individually modeling protocols based on a meta model; A code generation step of automatically generating a communication protocol individually modeled based on the meta model with a program code capable of analyzing a disparate protocol of each photovoltaic power generation facility; And an integrated metamodel mapping step of performing the generated program code and mapping the collected monitoring data to elements of an integrated metamodel designed in the integration server, and mapping the collected monitoring data to the integrated metamodel, The protocol generating unit automatically generates a protocol code corresponding to a rule stored in the utility class and stores the program in a data class, and the integrated metamodel mapping step includes: Analyzing the heterogeneous protocol, receiving the monitoring data collected from each solar power generation facility through the analyzed heterogeneous protocol, storing the received monitoring data in the data class, Getter of data class Using the mapping is characterized in that in connection with the elements of the integrated metamodel of the Integration Server.

The monitoring method of solar power generation according to the present invention may be implemented in an auxiliary facility located in a power generation section of each of the plurality of solar power generation facilities, and may include the protocol modeling step of individually modeling heterogeneous communication protocols of the solar power generation facilities And the data type and size of the heterogeneous protocol are written, and the data is modeled into block-shaped elements arranged in accordance with the data order of the heterogeneous protocol, and the modeled block-shaped elements Stored data is stored in a local server of each photovoltaic power generation facility, and all components of the data of the heterogeneous protocol are modeled by block elements, After performing all the sub-blocks, move to the first block on the right side. It is gong.

In the monitoring method of solar power generation according to the present invention, the code generation step includes a transmission / reception class for transmitting / receiving the dissimilar communication protocol, wherein the transmission / reception class includes a transmission API and a reception API, The receiving API obtains byte data to be used for the serial port in the data class, and the receiving API reads the received byte data sequentially when receiving the protocol, and inputs the byte data to the data class.

In addition, the monitoring method of solar power generation according to the present invention is characterized in that the data class generates data in the order inputted in the data protocol model.

According to another aspect of the present invention, there is provided a method of monitoring solar power generation, wherein the utility class includes a pre-built utility API, the utility API is determined according to the type of data input to the data protocol model, .

In the method of monitoring solar power generation according to the present invention, the integrated metamodel of the integrated server includes a PlatDisplay element, an Inverters element, a Sensors element, and a JunctionBoxes element as an integrated metamodel element.

Further, in the monitoring method of solar power generation according to the present invention, the PlatDisplay element includes the current output amount, the current day, the previous day, the current month, the previous month, and the total generation amount information in which the overall monitoring result can be seen, And the warning information of the inverter, and the Sensors element includes information measured by the sensor of the photovoltaic power generation system, such as horizontal solar radiation amount An inclined solar irradiance, a module temperature, an external temperature, a concentration of co2, and a slope, and the JunctionBoxes element can obtain the voltage and current of the photovoltaic power generation facility.

In addition, the monitoring system of solar power generation according to the present invention is dispersed and installed in a plurality of regions, and a solar power generation facility including a power generation unit and a local server, and an integrated management system for integrating and managing the plurality of distributed solar power generation facilities Wherein the power generation unit of each solar power generation facility models a different communication protocol to successfully receive the monitoring data collected at the local server of each of the solar power generation facilities installed in the area, And a code generating means for generating a communication protocol that is different from the received communication protocol by program code, wherein the integrated server interprets the heterogeneous communication protocol in the generated program code, Data into an element of an integrated metamodel formed in the integration server Characterized in that the ping.

In addition, the monitoring system of the solar power generation according to the present invention is characterized in that the power generation unit includes a solar cell module that receives sunlight, and an auxiliary facility that collects and converts energy and measurement data generated in the solar cell module, A connection box for connecting the array of the power generation units, and an inverter for receiving data from the connection box and transmitting the data to the local server.

In addition, the monitoring system of the solar power generation according to the present invention uses an existing legacy system unique to a protocol for monitoring an internal apparatus constituting each solar power generation facility, wherein the local server uses the legacy system And monitors the connection box and the inverter of the power generation unit.

In addition, the solar power generation monitoring system according to the present invention is characterized in that the integration server includes a data collector for receiving data from the local server, a data storage for storing data received in the data collector in a database, And a data analyzer for analyzing the data stored in the data storage.

In addition, the solar power generation monitoring system according to the present invention is characterized in that the data analyzer is configured to perform the target load demand forecasting service, the real-time solar energy prediction service, the integrated control service, the optimal control state, Based big data system is used.

In addition, the monitoring system of the solar power generation according to the present invention is characterized in that the integrated server further comprises a web application that enables access to the data storage device from the outside.

The monitoring system and method of the photovoltaic generation according to the present invention can integrate data between monitoring systems using different kinds of protocols based on meta-model and change or modify the existing monitoring system that has been already used It is possible to save the budget by improving utilization rate of the neglected monitoring system.

In addition, the monitoring system and method of the photovoltaic power generation according to the present invention can manage the power generation facilities in a long distance and can cope with the problems quickly, and can monitor the production amount and operation status of the facilities in real time It is useful for managing the power generation amount of renewable energy generated by the facility.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a diagram showing a configuration of a monitoring system for photovoltaic power generation according to an embodiment of the present invention. Fig.
FIG. 2 is a diagram specifically illustrating a configuration of a Nth power generation unit and an integration server of a monitoring system for photovoltaic power generation according to an embodiment of the present invention; FIG.
3 is a diagram illustrating a structure of a software platform relating to a monitoring system method of photovoltaic generation according to an embodiment of the present invention.
4 is a flow chart of a method of monitoring a solar power generation system according to an embodiment of the present invention.
5 illustrates a metamodel of a metamodel-based protocol model according to an embodiment of the present invention.
FIG. 6 is a diagram illustrating a structure of a code generated through a metamodel-based protocol model according to an embodiment of the present invention; FIG.
7 illustrates a metamodel of an integrated model according to an embodiment of the present invention.
8 is a diagram illustrating a meta model-based protocol processing structure according to an embodiment of the present invention.

The solar power generation monitoring system according to the embodiment of the present invention can monitor and manage the amount of power collected from the solar cell, the temperature, and information of the tilt sensor. Since the energy collected from the sunlight has electrical characteristics, there is a risk of fire, and if the structure is broken, there is a fear of human injury.

Hereinafter, a solar photovoltaic generation monitoring system according to the present invention will be described with reference to FIGS. 1 and 2. FIG. FIG. 1 is a view illustrating a configuration of a solar power generation monitoring system according to an embodiment of the present invention. FIG. 2 is a block diagram illustrating a configuration of a Nth power generation unit and an integration server of a solar power generation monitoring system according to an embodiment of the present invention. Fig.

1, the photovoltaic power generation monitoring system 1 includes a power generation unit 110-1, ..., 110-N and local servers 120-1, ..., 120-N. Based on the data collected from the solar power generation facilities 100-1 to 100-N and the solar power generation facilities 100-1 to 100-N, And an integration server 220 that manages the server.

The photovoltaic power generation facilities 100-1, ..., 100-N are locally distributed. Therefore, it is necessary to integrally manage the data measured or collected in the distributed photovoltaic power generation facilities 100-1, ..., 100-N in one place.

The power generation units 110-1 to 110-N and the local servers 120-1 to 110-N are disposed in the vicinity of the solar power generation facilities 100-1 to 100- 1,..., 120-N, and the monitoring data collected by the respective power generation units 110-1, ..., 110-N is transmitted to the local servers 120-1, ..., , 120-N. Since the power generation units 110-1 to 110-N and the local servers 120-1 to 120-N are located relatively close to each other, RS232 or RS422 / 485 communication.

A database of the local servers 120-1, ..., and 120-N collected and configured in each area is transmitted to the integration server 200 and is transmitted to the respective solar power generation facilities 100- 1, ..., 100-N are integrated in one place, and each of the solar power generation facilities 100-1, ..., 100-N and the integration server 200 are relatively far from each other It is preferable to use TCP / IP communication.

Next, each of the solar power generation facilities 100-1, ..., 100-N has basically the same configuration. Hereinafter, the N solar power generation facility 100-N and the integration server 200 shown in FIG. 2 will be described in detail.

First, the Nth solar power generation facility 100-N includes an Nth power generation unit 110-N and an Nth local server 120-N.

The Nth power generation unit 110-N includes an Nth solar cell module 111-N that specifically receives direct sunlight, an Nth solar cell module 111-N that collects and converts energy generated from the Nth solar cell and measured data, And an auxiliary equipment 112-N.

The Nth auxiliary facility 112-N includes an Nth connection box 113-N for connecting the array of the Nth power generator 110-N, and an Nth connection box 113- And an Nth inverter (114-N) for receiving data and transmitting the data to the Nth local server (120-N).

The Nth inverter 114-N collects and receives analog data of the Nth solar cell module 111-N from the Nth connection box 113-N, (120-N) and converts the DC electric energy generated by the Nth solar cell module (111-N) into AC electrical energy.

The Nth solar power generation facility 100-N may transmit information such as the amount of power, temperature, tilt sensor, and the like to the Nth local server 120-N through the Nth inverter 114- Or may transmit a value measured by various kinds of sensors installed in the Nth solar cell module 111-N to the Nth local server 120-N.

Next, the components of the integration server 200 will be described. The integration server 200 includes a data collector 210 for receiving data transmitted from the Nth local server 120-N, a data storage 220 for storing the collected data, A data analyzer 230 for analyzing data of the data storage 220 and a web application 240 for externally accessing the data storage 220.

The data collector 210 collects the data transmitted from the Nth local server 120-N and transmits the collected data to the data storage 220 do. The integrated server 200 is installed to monitor the photovoltaic power generation facilities 110-1 to 110-N installed in the respective dispersed regions, and the local servers 120-1, ... 120-N may be collected by the data collector 210. [

The data storage 220 collects and stores data transmitted from the data collector 210, and analyzes the data in the data analyzer 230. The data analyzer 230 performs analysis using data stored in the data collector 210 when necessary, and uses Hadoop to analyze the data using the big data system.

The data analyzer 230 can perform any one of a target load demand forecasting service, a real time solar energy prediction service, an integrated control service, an optimal control state and an operation service, and an integrated monitoring service, ) Can be added or deleted.

In order to enable the user to directly access the data storage 220 and inquire the user from outside for analyzing various information using the data stored in the data storage 220, . The web application 240 serves data to be inquired by the user on the Internet, and may store or print the inquired data as needed.

The solar power generation monitoring system 1 may receive data from the local servers 120-1 to 120-N of different types installed in different areas to one integrated server 200 do. However, because different types of servers use different kinds of protocols, data transmission and reception is not smooth or impossible. Therefore, there is a need for a method that enables compatibility of different kinds of protocols.

There are two ways to make the different kinds of protocols compatible. The first method integrates all the communication protocols connecting the power generation units 110-1, ..., 110-N and the local servers 120-1, ..., 120-N into the same type . The second method is a method of integrating communication protocols with the integration server 200 using the existing ones of the solar power generation facilities 100-1, ..., 100-N.

In the first method, it is troublesome to replace all existing apparatuses and facilities using the same communication protocol. Therefore, in the embodiment of the present invention, the existing solar power generation facilities 100-1, ..., 120-N), and a self-communication protocol for connecting the power generators 110-1, ..., 110-N and the local servers 120-1, ..., An embodiment of a method for integrating communication between the local server 120-1, ..., 120-N and the integration server 200 regardless of the type of the local server 120-1 will be described.

In order to integrate communication between the local servers 120-1,..., 120-N and the integration server 200, a software platform 300 as shown in FIG. The software platform 300 includes a metamodel framework 320, a serial communication middleware 330, a TCP / IP communication middleware 340, a Hadoop 350, and a visualization middleware 390.

The metamodel framework 320 is constructed to integrate heterogeneous data protocols 310-1,..., 310-N based on a metamodel. The protocol thus configured incorporates the serial communication middleware 330 based on the meta model. The collected protocol data is stored in the database 360 and attempts to analyze the Hadoop 350 based big data in order to perform analysis when necessary. In addition, in order to monitor the web, it is configured to be executed through the visualization middleware 390 using the PC 370 and the web 380.

In order to make different protocols compatible with each other as described above, there is a method of using a standard, a method of creating an adapter, and a method of using a model conversion. The method using the standard is easy to link because it uses one unified version, but it is difficult to apply it to the existing system. In addition, the method using the adapters is a method of continuously creating an adapter and generating a system capable of processing the adapter each time the conversion protocol is created. As the number of systems to be connected increases, the number of adapters may increase exponentially.

The model conversion is a method of creating a single model based on a meta model and generating a heterogeneous model through the model. In the embodiment of the present invention, the model conversion method is used to successfully So that they can be interlocked.

Therefore, in the present invention, a method of integrating heterogeneous protocol data based on a meta model using the model conversion will be described in detail.

Generally, protocol data can be distinguished between transmission and reception. Usually, when you transmit data, you do not interpret the data, but input the command as it is. However, since data must be read and processed at the time of reception, data must be read and parsed. The data protocol for each transmission and reception is as follows.

Example) Send: # 1NQ110000 $

    Response: # 1NR1100010004000A00290000000000000384000000000000 $

There is a difficulty in separately writing the program codes by understanding the different kinds of protocols when writing the above-mentioned operations in the program code. Accordingly, in the present invention, a process of modeling heterogeneous protocols based on a meta model is preceded, and a code capable of processing the data of the modeled protocol is automatically generated without separately generating individual codes, thereby facilitating rapid development.

In particular, modeling a protocol based on a metamodel is effective because it enables modeling by inputting only desired information without understanding the complex heterogeneous protocol.

4, a communication protocol between each of the solar power generation facilities 100-1, ..., 100-N and the integration server 200 is modeled based on a metamodel, (S2), and maps the generated program code to the integrated meta model of the integration server (200) (S3). Then, the heterogeneous system So that it can be interlocked freely.

Each step of the metamodel-based heterogeneous communication protocol integration method will be described in detail below with reference to FIGS. 4 to 8. FIG.

(1) Metamodel-based protocol modeling (S1)

As described above, the metamodel-based protocol modeling process S1 is performed in order to automatically perform code generation, which will be described later. In particular, the metamodel-based protocol modeling process S1 is modeled based on a metamodel designed in the photovoltaic power generation facility, The concrete procedure is as follows.

Hereinafter, the metamodel-based protocol modeling (S1) will be described in detail with reference to FIG. 5 is a diagram illustrating a metamodel 400 of a metamodel-based protocol model.

The ProtocolModel 410 may receive the name information of the model as the top node. A packet is a unit of data that can be transmitted at one time in a bundle unit defined by the protocol. Therefore, there must be one packet in the model.

The Packet may have several types. The Type is composed of Start, Header, Command, Data, Parity Bit, and End, and each Type has size information. The size information is the size of data, and the unit is byte. For example, a size of 4 bytes is entered as 4.

The metamodel-based protocol model metamodel 400 is divided into a SendPacket 420 for transmission and a RecvPacket 430 for reception. The two types of Packets have Type. The SendPacket 420 includes a SendType 421 and the RecvPacket 430 includes RecvType 431.

The CoreType 440 includes a Start 441, an End 442, and a Parity Bit 443 that are used jointly by the SendPacket 420 and the RecvPacket 430 types. ).

The ParityBit 443 is used to check whether the transmitted data value has been transmitted without error in the middle. The parity bit 443 sends a value added for all the values to be transmitted for confirmation and adds it to the receiving side. When the same value is obtained, .

The SendType 421 has the CoreType 440 and the Command 422 in addition to the CoreType 440. The RecvType 431 includes a Header 432 and a Data 433 in addition to the CoreType 440.

The Header 432 and the Data 433 may input information of the NameElement 460. The NameElement 460 has a name and a data type. The data type is an actual data type, and is used to distinguish whether it is a string or a number when parsing data.

The Command 422, the Start 441, and the End 442 may input information of the TokenElement 450. The TokenElement 450 may have a unique character. For example, tokens starting with $ and ending with # are Start and End, respectively. The token type is a value indicating which type of data is to be represented by the token and is used to distinguish the data type from a string or a number.

Table 1 shows the notation used to create the metamodel-based protocol model. The data is modeled as block-shaped elements arranged in accordance with the data order of the heterogeneous protocol, and then stored data is formed based on the modeled block-shaped elements.

That is, the type of the data is written in the element of the block type, so that it is possible to confirm which data type. "{1}" next to the name indicates the size of the data, which represents 1 byte.

[Table 1] Metamodel-based protocol model notation

Table 2 shows the modeling of the following data protocol example 1 using the metamodel-based protocol model metamodel (400).

Example 1) Send: # 1NQ110000 $

Response: # 1NR1100010004000A00290000000000000384000000000000

[Table 2] Example of metamodel-based protocol modeling 1

Table 3 shows the stored data format of the metamodel-based protocol modeling shown in Table 2 above. Table 3 shows the structure of the file in which the protocol of Example 1 is stored.

[Table 3] Example of Metamodel-based Protocol Modeling The stored data format

In the metamodel-based protocol modeling of Table 2, all the components except the ProtocolModel and the packet are in order. Therefore, the order must be observed at the time of modeling.

That is, in the metamodel-based protocol modeling, block-shaped elements are arranged in a tree form and have a predetermined order.

The above procedure is based on left to right, and if there is a lower block, it carries out all the lower blocks and then moves to the first block on the right side. This can prevent the modeling from becoming too long when the modeling is sequentially arranged side by side.

(2) Generate protocol processing code (S2)

Hereinafter, a method (S2) for automatically generating program code for processing data of a metamodel-based protocol model formed in step S1 will be described in detail with reference to FIG. 6 is a diagram illustrating a structure of a code generated through a metamodel-based protocol model.

The program code automatically generates the modeled protocol by inputting the modeled protocol to the code generation means. The automatically generated program code is used for mapping to an integrated meta model of the integration server 200, which will be described later, and the code generation means is used to analyze all the protocols.

Referring to FIG. 6, the generated code 500 is divided into three classes. The first is a transmission / reception class 510 that provides a protocol to be processed when it is sent and received. The second is a Data class 520 in which data generated in the protocol is stored. The third is an API Stored Util class 530.

The transmission / reception class 510 includes the Data class 520 internally to read and process data, and allows the transmission / reception class 510 to receive the Data class 520 when it is generated at the time of code generation .

The send / receive class 510 has two APIs: a send API 511 and a recv API 512. The send API 511 can obtain byte data to be used for a serial port when sending data, and the recv API 512 reads received byte data and inputs data to the Data class 520.

In accordance with this configuration, the operation mechanisms of the three classes formed in the generated code will be described in detail below with examples respectively.

First, the send API 511 is processed according to the elements and attributes of the tree-shaped block elements formed in the metamodel-based protocol model 410. For example, if there is a transmission example of the metamodel-based protocol model shown in Table 4 below, it is automatically generated as shown in Table 5.

[Table 4] Example of Transmission of Metamodel-based Protocol Model

[Table 5] Example of generating send API code

The contents of the send API 511 should be output in the form of byte data. Therefore, the data is collected using the ArrayList, and finally the ArrayList is converted into a byte array and returned. All of the above conversion processes are processed in the Util class 530.

In Table 5, the code of the send API 511 is preceded by the SEND keyword, which is added to prevent collision with the data of the recv API 512.

In order to transmit the data in the send API 511, START is first used in the transmission example of the metamodel-based protocol model of Table 4 above. The START is obtained from the Data class 520 and input into the ArrayList. In this case, the input may be a string value or a byte value. Since the Util class 530 can process both types, regardless of the type, Is automatically generated. In addition, the PARITY BIT described at the end of Table 4 can also be processed through the API of the Util class 530.

Next, the recv API 512 sequentially reads the received data and inputs the read data to the respective data. For example, when a model as shown in Table 6 below is defined, the recv API (512) code generation is generated as shown in Table 7.

[Table 6] Example of receiving meta-model-based protocol model

[Table 7] Code generation example of recv API

In the above table 6, since the recv API 512 must sequentially read data, it has an index variable. In Table 6 and Table 7, data having a token value such as START and END are not used for reading data, but used for checking errors in input data. Accordingly, the START and END data values are fetched, and when the data value is different from the currently input data value, false is returned, so that it is confirmed that the transmitted data value is wrong.

The data input of the recv API 512 is sequentially processed using the setter function of the Data class 520 and the processing of the data is processed in the Util class 530, You only need to enter data without processing.

Since the recv API (512) code is sequentially executed, the increment / decrement value of the index value changes according to the size value 470 of the metamodel-based protocol model 400. Also, some data should be read by 2 bytes instead of 1 byte, and this UIC class 530 is processed by using a pre-created API.

Next, the Data class 520 generates data in the order entered in the metamodel-based protocol model 400. At this time, if the data type is STRING, it is made into string data. If the data type is a token, it is made unchangeable and read only data. Otherwise, declare the data as an int.

For example, an example of receiving the metamodel-based protocol model of Table 6 above creates a Data class 520 as shown in Table 8 below.

[Table 8] Example of Data class

The Util API is determined according to the type of data input to the modeled protocol. The Util API is converted as shown in Table 9 below, and the API list used in the Util class is shown in Table 10.

[Table 9] Util API according to input data type

[Table 10] Util class API

(3) mapping to the integrated metamodel (S3)

Data can be collected in the Data class 520 using the code 500 generated through the meta model based protocol model 400 through the protocol processing code generation step S2. Therefore, data generated from heterogeneous protocols can be easily collected into an integrated model.

The collected data is mapped to a metamodel of the integrated model shown in FIG. 7 (S3), and a plurality of different types of local servers (120-1, ..., 120-N) By integrating the data generated by the protocol, it is possible to monitor remotely through the integration server 200 without changing the existing legacy system.

Referring to FIG. 7, an element included in the meta model of the integrated model is a SolarEnergyModel (610) element having an ID and a transmission time of the power plant as attributes. The SolarEnergyModel 610 element includes PlatDisplay 620, Invertes 630, Sensors 640, and JunctionBoxes 650 as child elements.

The PlatDisplay 620 element sends the current amount of power, the current day, the previous day, the current month, the previous month, and the total power generation amount to see the entire monitoring result. In addition, the Inverters 630 element sends information that can be obtained from the Inverter 631. The inverter 631 can know current power generation amount, output current, voltage, input power, current, voltage, frequency, and warning information of the inverter.

In addition, the Sersors 640 element sends the horizontal radiation dose, the oblique radiation dose, the module temperature, the external temperature, the concentration of co2, and the slope as information of the sensors. In addition, the JunctionBoxes (650) element can obtain voltages and currents of the photovoltaic module connected to the junction box (651).

As described above, the integrated model implemented as a meta model through the three steps shown in FIG. 4 requires a method capable of transmitting and receiving with each other. That is, both the local servers 120-1,..., 120-N and the integration server 200 can be created and sent according to the meta-model rules of the communication protocol, as shown in FIG. That is, the model data of the meta model uses XMI, which is basically string data, so that the meta model data can be exchanged via TCP / IP.

1 PV monitoring system
100-1, ..., 100-N solar power generation facilities 110-1, ..., 110-
111-1, ..., 111-N solar battery modules 112-1, ..., 112-N auxiliary facilities
113-1, ..., 113-N connection boxes 114-1, ..., 114-
120-1, ..., 120-N local server 200 integrated server
210 data collector 220 data storage
230 Data Analyzer 240 Web Application
300 PV monitoring system software platform structure
400 metamodel-based protocol model
500 structure of code generated through metamodel-based protocol model
Metamodel of 600 integrated model

Claims (13)

1. A monitoring method of solar power generation using a plurality of solar power generation facilities distributed in each region and an integrated server for integrally managing the solar power generation facilities,
Wherein the step of generating an integrated communication protocol to be applied to both the plurality of photovoltaic power generation facilities and the integration server comprises:
A protocol modeling step of separately modeling heterogeneous communication protocols used individually in each of the photovoltaic power generation facilities based on a metamodel in order to provide monitoring data collected from each photovoltaic power generation facility to an integrated server;
A code generation step of automatically generating a communication protocol individually modeled based on the meta model with a program code capable of analyzing a disparate protocol of each photovoltaic power generation facility; And
And mapping the collected monitoring data to an element of the integrated meta model designed in the integration server by performing the generated program code,
Wherein the code generation step automatically generates the modeled communication protocol as a program code corresponding to a rule stored in the utility class by the code generation means of the utility class and stores the generated communication protocol in the data class,
The integrated meta-model mapping step may include analyzing the heterogeneous protocol by executing the program code generated in the code generation step, and analyzing the monitoring data collected from the respective solar power generation facilities through the analyzed heterogeneous protocol Stores the received data in the data class,
Wherein the monitoring data stored in the data class is mapped to an element of the integrated metamodel of the integrated server using a getter function of the data class.
The method according to claim 1,
Wherein the protocol modeling step of separately modeling heterogeneous communication protocols of the solar power generation facilities is performed in an auxiliary facility located in a power generation section of each of the plurality of solar power generation facilities,
The data format and order of the heterogeneous protocol are determined, the type and size of the data are written, and the data is modeled into block-shaped elements arranged in accordance with the data order of the heterogeneous protocol, and based on the modeled block- The formed storage data is stored in a local server of each photovoltaic power generation facility,
All the components of the data of the heterogeneous protocol are modeled as block elements, and left to right in the basic order. When there is a sub-block, all the sub-blocks are performed and then moved to the upper first block on the right side. How to monitor solar power generation.
The method according to claim 1,
Wherein the code generation step includes a transmission / reception class for sending and receiving the heterogeneous communication protocol,
Wherein the transmission / reception class includes a transmission API and a reception API,
The sending API obtains byte data to be used for a serial port from the data class when sending a protocol,
Wherein the receiving API sequentially reads the received byte data when receiving the protocol and inputs the read byte data to the data class.
The method according to claim 1,
Wherein the data class generates data in the order entered in the data protocol model.
The method according to claim 1,
The utility class includes a pre-built utility API,
Wherein the utility API is determined according to the type of data input to the data protocol model and utilized for protocol analysis of the code generation step.
The method according to claim 1,
The integrated metamodel of the integration server includes:
A PlatDisplay element, an Inverters element, a Sensors element, and a JunctionBoxes element as an integrated metamodel element.
The method according to claim 6,
The PlatDisplay element includes the current output amount, the current day, the previous day, the current month, the previous month,
The Inverters element includes current, current, current, total power, output current, voltage, input power, current, voltage, frequency and warning information of the inverter,
The Sensors element includes information on the measured values of the sensor of the photovoltaic power generation system, including a horizontal solar radiation amount, an oblique solar radiation amount, a module temperature, an external temperature, a concentration of co2,
Wherein the JunctionBoxes element is capable of obtaining voltage and current of the photovoltaic power generation facility.
A plurality of solar power generation facilities including a power generation unit and a local server,
And an integration server for integrating and managing the plurality of distributed photovoltaic power generation facilities,
In order to successfully receive the monitoring data collected at the local server of each of the photovoltaic power generation facilities installed in the area, the power generation unit of each photovoltaic power generation facility models the different communication protocol and programs the modeled communication protocol And code generation means for generating code from the generated program code,
Wherein the integration server maps the local server monitoring data received through the analyzed heterogeneous communication protocol to an element of the integrated metamodel formed in the integration server.
9. The method of claim 8,
The power generation unit includes a solar cell module receiving sunlight and an auxiliary equipment for collecting and converting energy and measurement data generated in the solar cell module,
Wherein the accessory includes a connection box for connecting the array of the power generation units, and an inverter for receiving data from the connection box and transmitting the data to the local server.
10. The method of claim 9,
The existing legacy system is used as a protocol for monitoring the internal devices constituting each solar power generation facility,
Wherein the local server monitors the connection box and the inverter of the power generation unit using the legacy system.
9. The method of claim 8,
Wherein the integration server comprises a data collector for receiving data from the local server,
A data store for storing data received in the data collector in a database,
And a data analyzer for analyzing the data of the data store according to the integrated communication protocol.
12. The method of claim 11,
The data analyzer is characterized in that a Hadoop-based Big Data System is used for performing a target load demand forecasting service, a real-time solar energy forecasting service, an integrated control service, an optimal control status, an operation service, Photovoltaic monitoring system.
12. The method of claim 11,
Wherein the integration server further comprises a web application for enabling the external to access the data storage device.

Images