KR101294343B1 - Method for Managing Wind Power Control System for High Availability in Wind Farm - Google Patents

Abstract

A high availability wind control system management mechanism at the wind farm level is provided. The wind control management mechanism includes a plurality of wind power control systems used to control the operation of the wind turbine and an integrated management control system for monitoring failures occurring in components provided in the wind power control systems. As a result, it is possible to monitor and manage failures generated in the wind power generation system, and to quickly cope with interruption of power generation and unstable power generation.

Description

Mechanism for Managing Wind Power Control System for High Availability in Wind Farm}

The present invention relates to a wind control system management mechanism, and more particularly to a high availability wind control system management mechanism at the wind farm level.

Advances in IT technology have exploded the power consumption of devices operated by electricity in modern society. This has led to increased demand for fossil fuels and increased costs for electricity use.

However, in order to cope with the increasing demand for electricity, the focus on environmentally friendly renewable energy has been focused on the environmental problems of limited fossil fuel and carbon emissions, which are the main causes of air pollution.

Among renewables, wind energy is growing rapidly around the world, and wind power capacity has grown at an average annual rate of over 30% over the past decade. This growth is made possible by many advantages, such as low cost, indefinite, clean and green.

Currently, many wind turbines are installed in coasts and mountains where winds are windy, not only in Korea but also abroad. Due to environmental factors such as vibration and electromagnetic noise, and software and hardware problems of controllers controlling wind turbines A lot of money is being spent.

The present invention has been made to solve the above problems, and an object of the present invention is to provide a method for monitoring and managing a failure occurring in a wind farm and a wind control management system applying the same.

According to the present invention for achieving the above object, the wind control management system, a plurality of wind power control system used to control the drive of the wind turbine; And an integrated management control system for monitoring failures occurring in components provided in the wind power control systems.

In addition, the integrated management control system, it is preferable that the manager that is notified of the failure from the managers for detecting the failure of the components provided in each of the plurality of wind power generation control systems.

In addition, the integrated management control system, it is desirable to identify the applications that were running in the component in which the failure occurs.

The integrated management control system displays at least one of information on a control system in which a failure has occurred, information on a component in which a failure occurs, and at least one of applications running on the component in which the failure occurs. can do.

The integrated management control system is also preferably used to control the driving of the wind turbine.

In addition, the wind power generation control system includes a plurality of components for supporting execution of applications used to control driving of the wind power generator; And middleware for monitoring a failure of the components through communication with the components.

In addition, the integrated management control system, a plurality of components for supporting the execution of applications used to control the operation of the wind turbine; Middleware for monitoring a failure of the components through communication with the components; And a manager for monitoring a failure of the components installed in the wind power control systems through communication with middleware of the wind power control systems.

On the other hand, the wind control method according to the invention, the method comprising the steps of communicating with a plurality of wind power control systems used to control the drive of the wind turbine; And monitoring a failure occurring in components provided in the wind power control systems through the communication in the communication step.

As described above, according to the present invention, it is possible to monitor and manage the failures generated in the wind power generation system, so that it is possible to quickly cope with the interruption of power production and unstable power production. In addition, rapid response can result in lower maintenance costs.

In addition, it can help to prevent problems occurring in one part of the wind power generation control system from spreading to another part.

1 illustrates a high availability wind control system management mechanism at a wind farm level to which the present invention is applicable;
2 is a view showing the structure of the wind power control system shown in FIG.
3 is a diagram illustrating a structure of a packet transmitted by RC;
4 shows the structure of a database for work data;
5 is a diagram illustrating an RC management table, and
6 illustrates an application management table, and
7 is a diagram showing the structure of the integrated management control system shown in FIG.

Hereinafter, with reference to the drawings will be described the present invention in more detail.

1 is a diagram illustrating a high availability wind control system management mechanism at a wind farm level to which the present invention is applicable. As shown in FIG. 1, a wind power generation system to which the present invention is applicable is integrated with wind power generation control systems 100-1, 100-2, and 100-3 for controlling the facilities constituting the wind power generator. The integrated management control system 200 for managing is connected and built to communicate with each other via the Ethernet (10).

The blade control system 100-1, the wind turbine control system 100-2, and the generator control system 100-3, referred to as the wind power generation control system, are merely exemplary. These may be omitted or replaced with other control systems as well as other control systems added.

On the other hand, the integrated management control system 200 may also control one of the facilities constituting the wind power generator. In this case, the integrated management control system 200 manages the entire wind power generation system in addition to the wind power generation facility control.

FIG. 2 is a diagram illustrating the structure of the wind power generation control systems shown in FIG. 1 with reference numeral “100”.

The wind power generation control system 100 shown in FIG. 2 is a high availability fault tolerance control system designed to automatically recover from failures to withstand various failures that may occur.

As shown in FIG. 2, the wind power generation control system 100 performing such a function includes a plurality of applications 110-1 to 110 -M and a plurality of RCs 120-1 to 120 -N. , FTSM 130, hypervisor 140, and hardware 150.

The applications 110-1 to 110 -M are applications that perform a function required for wind power control.

Redundancy Components (RCs) 120-1 through 120-N are components that support the execution of applications 110-1 through 110-M. In the RCs 120-1 to 120-N, daemons 125-1 to 125-N periodically transmit their operating states to the local watchdog manager 137 of the FTSM 130, which will be described later. Prepared.

RCs 120-1 through 120 -N are managed by FTSM 130. Meanwhile, the RCs 120-1 to 120 -N are divided into a general redundancy component (GRC) 120-1 and critical redundancy components (CRCs) 120-2 to 120 -N.

The GRC 120-1 is a component that does not require backup data when transferring a job that is being performed to another component. That is, the GRC 120-1 may be regarded as a component that performs a task that does not require data backup.

Here, when it is necessary to transfer the work being performed to another component, a problem such as a failure or an error occurs in the GRC 120-1.

The CRCs 120-2 to 120 -N are components that require backed up job data when transferring a job that is being performed to another component. That is, the CRCs 120-2 to 120 -N may be regarded as a component that performs a job requiring a backup of job data.

Work data backup is necessary to restore the state of the wind power control system to the state before the problem, in order to ensure the durability of the wind power control system.

Fault-Tolerant Service Middleware (FTSM) 130 provides an interface between the RCs 120-1 through 120 -N and the hypervisor 140. In this case, communication between the FTSM 130 and the RCs 120-1 to 120 -N may be performed according to TCP / IP.

In addition, the FTSM 130 is a high availability middleware employing a redundancy component technique and a backup data backup technique of CRCs 120-2 to 120 -N in order to recover the fault of the wind power control system.

As shown in FIG. 1, the FTSM 130 includes a network interface manager 131, a data manager 133, a system control manager 135, and a local watchdog manager 137.

The managers 133, 135, and 137 constituting the FTSM 130 may communicate with each other through IPC.

The network interface manager (NIM) 131 provides an interface for data transfer with the RCs 120-1 to 120 -N and data transfer between the managers 133, 135, and 137.

The network interface manager 131 receives / analyzes the packet transmitted by the RCs 120-1 to 120-N and delivers the packet to the corresponding manager that should receive the packet.

3 illustrates a structure of a packet transmitted by the RCs 120-1 to 120 -N. As shown in FIG. 3, the packets transmitted by the RCs 120-1 to 120 -N include an RC # field, a Manager field, and a Request field.

1) The RC # field is a field containing the RC number (#m) of transmitting a packet, 2) the Manager field is a field containing a manager to receive the packet, and 3) a request is one of the functions provided by the manager. Corresponds to the field that contains the functionality that the RC wants to request.

The data manager 133 is a manager for backing up work data of the CRCs 120-2 to 120 -N. The job data is classified and stored for each of the CRCs 120-2 to 120 -N.

Specifically, the data manager 133 stores the data requested by the CRCs 120-2 to 120 -N to the hypervisor 140 to be described later along with the request time, and the stored request data corresponds to the job data. .

In order to identify the data requested by the CRCs 120-2 through 120-N to the hypervisor 140, all packets transmitted from the CRCs 120-2 through 120-N to the hypervisor 140 are all data. It may be implemented to be delivered through the manager 133.

In addition, for storing, retrieving, and extracting work data, the data manager 133 includes a repository, and builds a database for work data.

The structure of the database for job data is shown in FIG. As shown in FIG. 4, the database for working data includes an RC # field, a Time field, a Type field, a Data Size field, and a Data field.

1) The RC # field is a field in which the number (#m) of the RC that has requested data from the hypervisor 140 is stored. 2) The Time field is a field containing a data request time. 3) The Type field is a type of data. (Eg, wind direction data, temperature data, etc.), and 4) the Data Size field is a field in which the size of data is stored, and 5) the Data field is a field in which actual data is stored.

The system control manager 135 is a manager that performs management / control such as creation, removal, and recovery of the RCs 121-1 to 120-N.

Specifically, the system control manager 135 assigns priorities to the RCs 121-1 to 120-N, respectively, and designates the RC with the highest priority as the GRC 120-1. In addition, IPs are dynamically allocated to the RCs 121-1 through 120 -N for data communication between the RCs 121-1 through 120 -N and the FTSM 130.

In addition, the system control manager 135 restores the work that was being performed in the RC that cannot perform the work due to a problem to another RC. Upon restoration, the system control manager 135 may 1) store information on the 'applications that were running in the RC where the problem occurred' stored in the local watchdog manager 137 and 2) store the data stored in the data manager 133. Use the working data of the RC in which the problem occurred.

On the other hand, the restoration by the system control manager 135 depends on the type of the failed RC.

If the failed RC is GRC, the system control manager 135

1) Specify another available RC (for example, a RC that is currently not doing anything) or a newly created RC as GRC,

2) From the table of the local watchdog manager 137, which will be described later, identify the applications that were running in the failed GRC and request to execute the newly designated GRC.

3) Remove the broken GRC

The restoration is performed by the process.

On the other hand, if the broken RC is a CRC,

1) The system control manager 135 identifies the applications that were running in the failed CRC from the table of the local watchdog manager 137, and requests to execute the applications identified in another available RC or newly created RC,

2) The executed applications extract work data of the failed CRC from the database of the data manager 133,

3) The system control manager 135 removes the broken GRC.

The restoration is performed by the process.

Local Watchdog Manager 137 monitors the states of RCs 121-1 through 120-N. To this end, the local watchdog manager 137 periodically receives a heartbeat signal from the daemons 125-1 to 125-N provided in the RCs 121-1 to 120-N, respectively.

If there is an RC that does not transmit the heartbeat signal for the period, the local watchdog manager 137 determines that the RC has a problem. If a problem RC occurs, the local watchdog manager 137 notifies the system control manager 135 of the fact.

In addition, the local watchdog manager 137 receives information about applications running in the RCs 121-1 through 120 -N, creates a table along with the states of the RCs, and manages them.

On the other hand, the local watchdog manager 137 transmits the information on the problem RC and the applications running in the RC to the global watchdog manager 245 installed in the integrated management control system 200 to be described later.

5 is a diagram illustrating an RC management table. As shown in FIG. 5, the RC management table includes an RC # field, an IP field, a status field, and an application field.

1) The RC # field is a field that contains the RC number. 2) The IP field is a field that contains the IP address assigned to the RC of the number listed in the RC # field. 3) The Status field is stored in the RC # field. 4) The Application field is a field that contains information on applications running in the RC of the number included in the RC # field.

In addition, the local watchdog manager 137 receives information on operating states of applications running in the RCs 121-1 to 120 -N, creates a table, and manages the information.

6 is a diagram illustrating an application management table. As shown in FIG. 6, the application management table includes an RC # field, an Application field, a CPU% field, a MEM% field, and a Stat field.

1) The RC # field is a field that contains the RC number. 2) The Application field is a field that contains information about the application running in the RC of the number listed in the RC # field. 3) The CPU% field is an Application field. 4) The MEM% field is a field in which the CPU share of the application is recorded in the Application field, and 5) the Stat field is a field in which the process operation state of the application is recorded in the Application field.

The hyper visor 140 allocates and manages the hardware 150 resources used in the wind power control system to the RCs 121-1 to 120-N.

FIG. 7 is a diagram illustrating a structure of the integrated management control system 200 shown in FIG. 1. As shown in FIG. 7, the integrated management control system 200 further includes a global watchdog manager 245 in addition to the components included in the wind power control system 100 illustrated in FIG. 2.

The global watchdog manager 245 monitors the failures occurring in the components 110-1 through 110 -M provided in the wind power generation control systems 100-1, 100-2, and 100-3 and monitors the failures. It is a means for guiding information about the manager.

In addition, the global watchdog manager 245 may monitor failures occurring in the components 210-1 to 210 -M provided in the integrated management control system 200, and information on the generated failures may be guided to the manager. .

To this end, the global watchdog manager 245 establishes a communication connection with the local watchdog managers 137 and 237, and receives information about the failed RC and the applications that were running in the RC. The failure situation can be grasped.

In addition, the global watchdog manager 245 displays information on the control system in which the failure has occurred, information on the RC in which the failure has occurred, and information on applications running in the RC where the failure has occurred, so that an administrator can view it. (Not shown).

Meanwhile, in the control system illustrated in FIGS. 2 and 7, the components except for the hardware 150 and 250 may be implemented by a computer program.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention.

100-1: blade control system 100-2: wind turbine control system
100-3: power generation control system 200: integrated management control system
Applications: 110-1 to 110-M, 210-1 to 210-M
120-1, 220-1: GRC
120-2 to 120-N, 120-2 to 120-N: CRC
125-1 to 125-N, 225-1 to 225-N: daemon
130, 230: FTSM
131, 231: network interface manager
133, 233: data manager 135, 235: system control manager
137, 237: local watchdog manager 140, 240: hypervisor
245: global watchdog manager 150, 250: hardware

Claims (8)

A plurality of wind power control systems used to control the drive of the wind turbine; And
And an integrated management control system for monitoring failures occurring in components provided in the wind power generation control systems.
The wind power generation control system,
A plurality of components for supporting execution of applications used to control the operation of the wind turbine; And
Middleware for monitoring a failure of the components through communication with the components;
The integrated management control system,
A plurality of components for supporting execution of applications used to control the operation of the wind turbine;
Middleware for monitoring a failure of the components through communication with the components; And
A manager for monitoring a failure of the components installed in the wind power control systems through communication with middleware of the wind power control systems;
The plurality of components,
In order to transfer work that was performed in the event of a failure to another component, the first component that is not required to back up the work data and transfer the work that was performed in the event of a failure to another component will need to back up the data for the work environment. A wind control management system comprising at least one second component required.
The method of claim 1,
The integrated management control system,
And a manager that is notified of the failure from the managers for detecting a failure of the components provided in the plurality of wind power control systems, respectively.
The method of claim 1,
The integrated management control system,
A wind control management system characterized by identifying applications that were running on the failed component.
The method of claim 3,
The integrated management control system,
A wind control system characterized by displaying at least one of information on a control system in which a failure has occurred, information on a component in which a failure has occurred, and at least one of applications running on the component in which the failure has occurred. .
The method of claim 1,
The integrated management control system diagram,
Wind control system, characterized in that used to control the driving of the wind turbine.
delete delete The integrated management control system communicating with a plurality of wind power control systems used to control the drive of the wind turbine; And
Monitoring, by the integrated management control system, a failure occurring in components provided in the wind power control systems through communication in the communication step;
The wind power generation control system,
A plurality of components for supporting the execution of applications used to control the driving of the wind turbine and the middleware for monitoring the failure of the components through communication with the components are installed,
The integrated management control system,
A plurality of components for supporting the execution of applications used to control the operation of the wind turbine, the middleware for monitoring the failure of the components through communication with the components, and the middleware of the wind turbine control systems Through, the manager for monitoring the failure of the components installed in the wind power control systems; is installed,
The plurality of components,
In order to transfer work that was performed in the event of a failure to another component, the first component that is not required to back up the work data and transfer the work that was performed in the event of a failure to another component will need to back up the data for the work environment. Wind control system management method comprising at least one second component required.

Images