WO2013152776A1

WO2013152776A1 - A configuration system for a wind turbine control system

Info

Publication number: WO2013152776A1
Application number: PCT/DK2013/050103
Authority: WO
Inventors: Chris DAMGAARD; Rasmus Nielsen
Original assignee: Kk-Electronic A/S
Priority date: 2012-04-13
Filing date: 2013-04-12
Publication date: 2013-10-17
Also published as: DK201200260A

Abstract

A configuration system for configuring a generic control software so that the generic control software facilitates control of a specific type of wind turbine chosen from a plurality of different types of wind turbines, the configuration system comprising a control module comprising the generic control software having potential to control the plurality of different types of wind turbines, one or more I/O modules, and a configuration database comprising an I/O table common for at least part of the plurality of different types of wind turbines, wherein a configuration file for the specific type of wind turbine is created based on the content of the configuration database, and wherein the configuration file enables the generic control software to control the specific type of wind turbine by establishing communication between the generic control software and the wind turbine related components connected to the one or more I/O modules.The invention furthermore relates to a method of configuring a generic control software.

Description

A CONFIGURATION SYSTEM FOR A WIND TURBINE CONTROL SYSTEM Background of the invention

The control system of wind turbines is a critical component because even minor errors in the software may have large consequences to the wind turbine or to the production from the wind turbines. Therefore great effort is given to test and ensure that the control systems e.g. are free of errors before a wind turbine is put into operation. This is true for each type of wind turbine on the market today. Brief description of the invention

It is an object of the present invention to provide a configuration system for generic wind turbine control software to enable the generic control software to control a specific wind turbine type. The present invention relates to a configuration system for configuring a generic control software so that the generic control software facilitates control of a specific type of wind turbine chosen from a plurality of different types of wind turbines, the configuration system comprising:

a control module comprising the generic control software having potential to control the plurality of different types of wind turbines,

one or more I/O modules for connecting a plurality of wind turbine related components to the control module, and

a configuration database comprising an I/O table common for at least part of the plurality of different types of wind turbines,

wherein a configuration file for the specific type of wind turbine is created based on the content of the configuration database, and

wherein the configuration file enables the generic control software to control the specific type of wind turbine by establishing communication between the generic control software and the wind turbine related components connected to the one or more I/O modules. It is very advantageous to develop a control module comprising generic control software for controlling a plurality of different types of wind turbines. This enables reuse of the same control module when controlling different types of wind turbines and thereby minimising the time and money spend on development of new control modules and control software for each type of wind turbine.

Because the different types of wind turbines by nature are not completely similar the differences between the different types of wind turbines are complied with in a configuration database. The configuration database may preferably for example comprise a table of all input addresses and output addresses (also referred to as I/O addresses) necessary for controlling the wind turbine related components of the different types of wind turbines.

As mentioned, there are of course differences between the different types of wind turbines. Such differences could be that one type of wind turbine may have additional sensors compared to other types. Furthermore wind turbines with direct drive may have other I/O modules or addresses than wind turbines with gear boxes. These different types of wind turbine may be controlled by the same control module combined with a configuration file created from the content of the configuration database. The configuration file is being specific to the type of wind turbine to be controlled.

It is advantageous that all I/O's from the different types of wind turbines are represented in the I/O table of the configuration database (this is why the I/O table also may be referred to as common I/O table).

When the configuration file is based on the I/O table the configuration file could be said to establish the communication between the generic control software and the I/O module and thereby to the wind turbine related components. In other words the configuration file is then mapping the communication between the generic control software and the wind turbine related components i.e. relating a variable name from the generic control software with an I/O address on an I/O module.

It should be noted that when referring to wind turbine related components reference is made to both internal and external components. By internal components are understood components such as pitch mechanism, generator, converter, yaw mechanism, climate control, etc. By external components are understood components such as sensors for measuring grid values, wind speed and temperature sensors, etc. The type of a wind turbine is defined in production capacity, manufacture, number of blades, etc. Furthermore the type of a wind turbine may also refer to different variants of the same wind turbine type this should be understood as one type of wind turbine may be found in different variations e.g. with different length of blades. These variations may also be referred to as wind turbine types.

It should be noted that the configuration file enables the control module to communicate with the wind turbine components. Hence the configuration file is based on the setup of the specific wind turbine. Typically the configuration file is not used directly but instead the information from the configuration file may be loaded to a core element database which is used by the generic control software in controlling the wind turbine components. Hence the generic control software may use information from the configuration file via the core element database.

In general it is understood that the configuration file may be transmitted/uploaded to one or more control modules so that at least a part of the content of the configuration file may be processed/read and implemented appropriately. Thus, the generic control software may control the specific type of wind turbine in that the content of the configuration file may facilitate establishment of communication between the generic control software and wind turbine related components connected to the one or more I/O modules.

According to an embodiment of the invention the configuration database comprising a variable table common for at least part of the plurality of different types of wind turbines.

It is very advantageous to use generic variable names in the generic control software because the same variable name may then be used across a plurality of different wind turbines.

The variables of the variable table mainly belong to two different groups of variables. The first group of variables is variable names which are mapped via the I/O table to specific I/O addresses. The second group of variable is internal variable names which are used internally in the generic control software as will be explained below.

The common I/O table comprise information of which I/O addresses a variable name should call to activate or read status from a wind turbine related component i.e. the I/O table could be said to be mapping the variable names with I/O addresses to which the wind turbine related components are connected. In other words the common I/O table comprise information of which input address the status of a given variable name is to be read or which output address a given variable name is to be changed. The combination of information from the common variable table and from the common I/O table is very advantageous in that if a sensor is change e.g. from one voltage level to another, from analogue to digital, etc. the input module to which the sensor is connected may have to be changed. In this case if such change of input address is made in the common I/O table of the configuration database a new configuration file can be created and send to the wind turbine to reflect this change. All later created configuration files will then also reflect this change. Variables are defined as names or aliases used in the generic control software e.g. when the generic control software is to communicate with wind turbine related components. Hence when the generic control software is updating a variable name e.g. called wind speed the control software is communicating with the wind speed sensor and is updated with the present wind speed.

When using generic variable names in the generic control software which are present in the common variable table in the configuration database, changes in the variable table will be reflected in later created configuration files for the different types of wind turbine. A change in the variable table could be in variable properties such as time between update of the variable, write access to the variable e.g. if a user is to access the variable for example via a SCADA system According to an embodiment of the invention the configuration database comprising a parameter table common for at least part of the plurality of different types of wind turbines.

It is advantageous to gather parameters used in controlling the different types of wind turbines in a common parameter table in the configuration database.

Some parameter settings are the same across most types of wind turbines. As an example could be mentioned the maximum wind speed, it is normal to start shutting down a wind turbine at a wind speed at 25 meters per second, maximum rotor speed, temperature which activates cooling fan, etc.

Therefore, if it is decided to change a parameter this can be done in the common parameter table in the configuration database and thereby the change will have effect on all the configuration files which are created after the change and which are using the changed parameter. Hence all types of wind turbines using this parameter will then have a new value for this parameter. In the situation a new configuration file is created and uploaded to the wind turbine, hence it could be said that the configuration file is a onetime use only file because it is not updated but replaced by a new configuration file. Parameters are defined as maximum or minimum values, threshold values, control parameters, etc.

According to an embodiment of the invention the configuration database comprising an alarm table common for at least part of the plurality of different types of wind turbines.

It is advantageous to gather alarms used in the different types of wind turbines in a common alarm table in the configuration database. In the common alarm table it can be defined how the wind turbine is to react on different types of alarms. Because the way an alarm is to be handled may be the same in different types of wind turbines it is advantageous to have a common alarm table in the configuration database. Then the configuration file for the different types of wind turbines may include information on how alarms are to be handled. An alarm is defined as a warning from the control software when a parameter is outside its predefined parameter settings. Often an alarm is associated with some kind of corrective action such as derating the production of the wind turbine, shutting down production, change pitch angle, increase coolant flow, etc. Hence due to the generic control software and the content of the configuration database as describe above editing is avoided in the generic control software having potential to control each of the different types of wind turbine. This is advantages because it eliminates the risk of forgetting to make the correction in the control software of a wind turbine type. Furthermore when correction only is needed one central place i.e. in the configuration database the risk of human mistakes such as copy / paste or spelling errors is also minimised if not completely eliminated. Furthermore the risk of making unintentional editing in the control software is eliminated because the correction is made in the configuration database and not in the control software. Because of this it is possible to let a less skilled person configure a wind turbine via a configuration file created from the configuration database.

It should be mentioned that it is preferred that all of the tables of the configuration database are common to all of the plurality of different wind turbine types. According to an embodiment of the invention the configuration file for a specific wind turbine type is available for editing by the user of a wind turbine.

It is very advantageous to be able to allow a user of a wind turbine to edit the configuration file. In this way it is possible for the user of the wind turbine to configure the wind turbine without access to the control software. As an example could be mentioned that if a parameter setting or a voltage area of a sensor is to be changed the user only need to access the configuration file and not the control software. This is very advantageous in that the user then does not risk making unintentional changes in the control software which could have critical impact on the control of the wind turbine.

A user may be defined as a person who in one way or the other needs access to the control system of the wind turbine. As an example could be mentioned the owner of the wind turbine, people which performs service on the wind turbine or repair or replace wind turbine components, etc. A user does not need to have the same programming skills as the person developing the control software.

According to an embodiment of the invention the configuration database comprise a default configuration file for at least part of the plurality of different types of wind turbines. It is advantageous to create a default configuration file at least for a plurality of the different types of wind turbines. Such default configuration file may comprise conservative parameter settings in order to make sure not to overload the wind turbine. The parameter settings may then be changed to optimise the performance of the wind turbine during the entire lifetime of the wind turbine.

Furthermore such default configuration file may map variable names with I/O addresses to which standard wind turbine components are connected according to standard or known hardwire configuration of the wind turbine.

Furthermore it may be advantageous to prepare a default configuration file for each type of wind turbine so that in order for controlling a specific type of wind turbine the generic control module may only need to request a specific configuration file from the configuration database to be able to control a specific type of wind turbine.

According to an embodiment of the invention the content of the configuration database is updated in case a new type of wind turbine is to be controlled by the generic control software. Creating a new configuration file for a new type of wind turbine may be done very easy by taking the configuration file from an existing wind turbine type which is similar to the new type of wind turbine and then edit this configuration file to comply with the variable names, I/O addresses, parameter settings, alarms, etc. of the new type of wind turbine. This may include creating new entities in the tables of the configuration database.

According to an embodiment of the invention the generic control software is the application software enabling the control module to control a specific wind turbine type when a specific wind turbine type configuration file is created from the configuration database. According to an embodiment of the invention the configuration database is located external to the wind turbine.

According to an embodiment of the invention a core element is capable of handling communication between software packages of the generic control software and between the generic control software and the I/O modules.

It is very advantageous to have a core element through which the generic control software communicates both internally and externally e.g. with I/O modules. This is one effective way of enabling generic control software to control specific wind turbine types.

According to an embodiment of the invention the control module may request a new configuration file.

It may be advantageous if the generic control software or other software located at the control module is capable of requesting update of a configuration file e.g. in case a parameter is missing or the mapping of an I/O is not correct According to an embodiment of the invention the generic control software comprises a plurality of independent software packages for controlling different parts of the wind turbine.

Having independent software packages are advantageous in that such modular thinking together with the configuration file enables fast adaption to changes made at the wind turbine.

Furthermore the reuse of software packages is advantageous in that development of a control system for a new type of wind turbine can be made very fast compared to the situation where development has to start from the beginning According to an embodiment of the invention generic control software approved in test, can be used to control a plurality of different types of wind turbines without further tests. This is advantageous in that is saves time and resources in development of a control system to a second type of wind turbine after having developed a control software to a first type of wind turbine.

In advantageous embodiments, said configuration file at least facilitates mapping of communication between the generic control software and the one or more I/O modules.

The invention furthermore relates to a method of configuring a generic control software so that said generic control software facilitates control of a specific type of wind turbine chosen from a plurality of different types of wind turbines, said method comprising: creating a configuration file for the specific type of wind turbine based on the content of a configuration database, said configuration database at least comprising an I/O table common for at least a part of the plurality of different types of wind turbines, said created configuration file enabling the generic control software to control a specific type of wind turbine by establishing communication between the generic control software of a control module and wind turbine related components connected to one or more I/O modules for connecting a plurality of wind turbine related components to the control module, uploading said configuration file to said control module comprising said generic control software having potential to control the plurality of different types of wind turbines, wherein an element of said control module reads and integrates at least a part of the content of said configuration file so as to enable said communication between said generic control software and said wind turbine related components. In advantageous aspects of the method, said integration may comprise that a core element of said control module copies at least some of the content of the configuration file into one or more tables of said control module.

In further aspects of the method, said one or more tables are comprised in an internal core element database of said control module.

In aspects of the method, said configuration file comprises data which when processed by said control module results in a mapping of communication between the generic control software and the one or more I/O modules.

In advantageous aspects of the method, the content of the configuration database is updated in case a new type of wind turbine is to be controlled by the generic control software. In aspects of the method, the configuration database comprises one or more default configuration files for at least part of the plurality of different types of wind turbines.

In some situations the generic control software is ready to control the specific type of wind turbine upon receiving the configuration file and in other situations some typical manually adjustments of the configuration file (and in rare cases also to generic control software) have to be made in order to obtain optimal control of the specific wind turbine. Tilfaje noge torn core databasen

It is generally understood that one or more of the above aspects of the configuration system may also be implemented in further aspects of the above mentioned method of configuring a generic control software. In further aspects, the system and/or method may be used in relation to retrofitting of an existing wind turbine. For example, a wind turbine may be exposed to

service/maintenance which comprises that one or more components are exchanged.

For example an analog meter of a specific type for measuring a parameter such as wind speed, temperature, torque and/or the like may be exchanged with another digitally operating meter for measuring the same parameter. This may e.g. result in a mismatch between the present output format of the analog meter and the new digital meter. Hence, the control module may receive an input by an I/O terminal that the control module is not able to interpret with the respective setting which was adapted to the previous meter. Now. A user may hence configure a new configuration file and have it uploaded to the control module. The control module may hence adapt the generic software so that e.g. the correct I/O terminal is used and/or configured appropriately.

Figures

A few exemplary embodiments of the invention will be described in more detail in the following with reference to the figures, of which fig. 1 illustrates a wind turbine according to an embodiment of the invention, fig. 2 illustrates the configuration system according to an embodiment of the invention, and fig. 3 illustrates control of a wind turbine related component according to an embodiment of the invention. Detailed description of the invention

Fig. 1 illustrates an electrical power generating system in form of a wind turbine 1 according to an embodiment of the invention. The wind turbine 1 comprises a tower 2, a nacelle 3, a hub 4 and two or more blades 5. The blades 5 of the wind turbine 1 are rotatably mounted on the hub 4, together with which they are referred to as the rotor. The rotation of a blade 5 along its longitudinal axial is referred to as pitch. The wind turbine 1 is controlled by a control system comprising a wind turbine controller 6 which is also referred to as control module, sub controllers 7 for controlling different parts of the wind turbine 1 and communication lines 8.

The wind turbine 1 further comprises a plurality of sensors / actuators 9 for measuring or activating wind turbine related components. The wind turbine related components refers to all the controllable parts of the wind turbine 1 such as the pitch and yaw system and to all parts or the wind turbine 1 which is monitored such as temperature of coolant in cooling systems, rotor speed, tower oscillations, etc. It should be mentioned that wind turbine related components also includes components for measuring meteorological conditions such as wind speed, humidity, temperature, etc.

Fig. 2 illustrates the principles of the configuration system according to an embodiment of the invention. As mentioned the present configuration system comprises a configuration database 12. The configuration database 12 comprises a plurality of tables such as a variable table 12A, an I/O table 12B, a parameter table 12C, an alarm table 12D, etc.

The tables 12A-12N comprise information from a plurality of different wind turbine types 1 A-1N and from the generic control software 10. The variable table 12A comprises information of all variable used in the generic control software 10. As mentioned there are two main groups of variables the internal variables and the external variables. The internal variables is used within the generic software 10 e.g. to present status of an operation in one software package e.g. 10A to one or more of the other software packages 10B, IOC, 10D, ... , ION. As an example could be mentioned that software packet 10B need to wait on a brake signal from software packet 10A before starting a pump. Hence an internal variable is set by software packet 10A and read by software packet 10B. This is explained in further details below.

The external variable is often a variable with which a software packet 10A, 10B, IOC, 10D, ... , ION can communicate to the I/O modules to start, stop or read measurements from sensors / actuators related to wind turbine components. Hence the variable starting the pump would be an external variable e.g. from software packet 10B.

The variable table 12A may comprise information on how often a variable is to update, who is allowed to access the variable, etc.

The I/O table 12B is used to map external variables with input or output addresses of the I/O modules 14. Hence when the software packet 10B is to activate e.g. a pump the I/O table has information of which output address the pump variable is to enable. It should be mentioned that when referring to an I/O module reference is made to a module which may comprise only input, only output or a combination. It may also refer to communication using a data bus.

The parameter table 12C holds information on minimum values, maximum values, threshold values, etc. Hence from this table the generic control software 10 may for example learn when to stop production due to high wind or over speed of the rotor. The alarm table 12D holds information on how a specific alarm is to be handled. Some alarms requires emergency stop of the production while other alarms may require derating of production or visit from a service person.

As illustrated in fig. 2 parameters from a plurality of different wind turbine types IAIN are added to the different tables of the configuration database 12.

The configuration system which comprises a control module 6 comprising generic control software 10 facilitating the control module 6 to control a plurality of different types of wind turbines 1 A, IB, 1C, ID, ... IN. In order for the control module 6 to control one specific type of the different types of wind turbines a configuration file 11 specific for the type of wind turbine to be controlled is needed. As illustrated on fig. 2 the generic control software 10 which also can be referred to as application software is build-up of a plurality of independent software packages 10A, 10B, IOC, 10D, ION for controlling different parts of the wind turbine 1. Hence software package 10A may control the pitch system e.g. via a sub controller 7 located near the pitch actuator 9, software package 10B may control the yaw system, power speed control 9 and so on.

The different software packages 10A, 10B, IOC, 10D, 10N are communicating with each other and communicating with I/O modules 14 via a core element 13. The core element 13 comprise a list of all variables and the status hereof which is used in the generic control software 10. This will be explained in further details below.

It should be mentioned that the control module 6 also may comprise other elements but these further elements are not described here since they are not relevant for understanding the present invention. In the example illustrated on fig. 2 the type of wind turbine to be controlled by the control module 6 is a wind turbine of type IB. Therefore to enable the control module 6 to control wind turbine IB a configuration file 11 for wind turbine type IB is to be created.

The configuration file 11 is created based on the information present in the configuration database 12 which is located external to the wind turbine IB. The configuration database could be located at the location of the developer of the control software. Entities in the different tables of the configuration database 12 may be associated with references to one or more wind turbine types. Thereby it becomes easy to find all I/O, variables, parameters, alarms, etc. which are relevant to a specific wind turbine type.

The configuration file 11 is then created either manually or automatically from the configuration database 12 e.g. by filtering the content of the configuration database 12 for references to a specific wind turbine type by putting all the I/O addresses, variable names, parameters, alarms, etc. relevant for the specific wind turbine type IB together in what is referred to as the configuration file 11. The configuration file 11 may e.g. be an XML file and when configuration file 11 is created it is uploaded to the wind turbine IB.

Now from the information from the configuration file 11 the core element 13 is able to manage all communication between the individual software packages 10 and the I/O modules 14 connected to the control module 6. Thereby has the generic control software which has potential to control a plurality of wind turbine types been configured to perform control of a specific wind turbine.

Therefore the configuration file 11 is to be created before the control system developer can control the wind turbine 1. As mentioned a default configuration file 11 could be created for some or all the different types of wind turbines. After the first configuration file 11 is created the wind turbine may not run exactly as desired in all situations. Hence when testing the wind turbine many changes may need to be made to the control system which may require update of the configuration file 11. Sensors could be changed from one type to another type, parameters and alarms may be adjusted, etc.

It should be noted that in some embodiments such as in case of a default

configuration file, not all I/Os from the different types of wind turbine are represented in the I/O table of the configuration database 12. This also applies to the other tables of the configuration database 12 and the table of the core element 13.

Fig. 3 illustrates a more detailed description of how the generic control software 10 makes use of the configuration file 11.

When the configuration file 11 is created it is uploaded to the wind turbine 1. At the wind turbine the core element 13 of the control module 6 which could be the main wind turbine controller is reading the content of the configuration file 11. The core element 13 is then copying the content of the configuration file 11 into its own tables 15 which could be said to be comprised in an internal core element database. Then the core element 13 has the same information about the specific wind turbine type as is present in the configuration database 12 i.e. information about variables such as update frequency, mapping between variables and I/O addresses, etc.

When the core element 13 has received the information from the configuration file 11 and transferred it to its own tables the configuration file does not need to be used any more.

Now the core element 13 is ready to handle communication internal between the software packages 1 OA- ION and from the software packages 1 OA- ION to the I/O modules 14. The principle of this communication is in short described below with reference to the arrows A, B, C, D. As described above software package 10B may need a brake signal from software package 10A before activating a wind turbine related component such as a pump 9. The software package 10A updates the variable va brake, this is read (arrow A) by the core element 13 which updates the value of va brake in its own variable table 15A and presents the va brake variable for the software packet 10B (arrow B).

Then the software packet 10B changes the status of the variable va_pump in order to start the pump which is updated in the variable table 15A by the core element 13 (arrow C). The core element 13 knows form its internal I/O table 15B that when va_pump is changed the output address to which the pump is connected is to be enabled (arrow D).

In the same way with the internal variables, parameters settings, alarms, etc. the core element 13 keeps record of the parameter settings and status of variables and the software packages requests or is presented to this information via the core element 13.

The developer of the control system is not always all the time involved in the optimisation of e.g. a prototype wind turbine. Therefore the present invention is especially advantages due to the fact that all configuration of the wind turbine may happen from the configuration file 11 or configuration database i.e. there is often no need to change the generic control software 10. This is advantageous because hereby the risk of making errors in the generic control software 10 is almost eliminated.

If a change is to be reflected in configuration files to the other wind turbines types the changes must be made in the tables 12A-12n of the configuration database 12 and a new configuration file 11 must be created and uploaded to the wind turbine.

Alternatively in order to update the core table 15 it may also be possible to simply edit the configuration file currently used as basis for part of the information used in the control module 6 to control the wind turbine. Yet another alternative could be editing directly in the core tables 15, this however may require some skils from the person editing. But by doing this, the change will not be reflected in the next configuration file created from the configuration database.

It should be mentioned that it is possible to copy an entity of a table 12A-12n in the configuration database 12 such as a variable from the variable table and then use the copied variable in the configuration file 11 of a specific wind turbine type in order to avoid the change to be reflected in all future configuration files including this variable. As mentioned above the generic control software 10 needs not to be accessed by a user. A programmer makes mistakes no matter how good he is. Hence keeping the programmer out of the generic control software 10 is eliminating one source of errors. By development of generic control software 10 combined with the wind turbine type specific configuration files 11 the risk of making errors due to human mistakes when updating or correcting software is minimised if not completely eliminated.

Furthermore by correcting one place i.e. in the configuration database 12 and not in a plurality of places (in case of use of none generic control software) the risk of forgetting to correct some place (i.e. the control software for controlling one or more types of wind turbine) is minimised or completely eliminated.

Furthermore another advantage with the generic control software 10 is that only one control software needs to be tested. This is because it is the same generic control software which is used in all types of wind turbines. Since the generic control software 10 is not to be accessed due to the fact that configuration takes place in the configuration database / files, the generic control software 10 does not need to be changed after a configuration and therefore does not need to be tested again. It should be mentioned that any time during the life time of the wind turbine it is possible to update the configuration file 11 or create a new configuration file 11 from the configuration database 12. According to an embodiment of the invention the configuration file 11 is only used once. If something is to be changed the changes is made in the configuration database 12 and a new configuration file 11 is created and uploaded to the wind turbine. Alternatively it is possible to edit directly in the core element 13.

The generic control software 10 becomes generic for all types of wind turbines 1 A- IN because of the plurality of control packages 1 OA- ION such as packages for controlling power/speed, pitch, yaw, safety, converter, and so on for all the elements of a wind turbine which needs to be controlled in all types of wind turbines 1 A- IN.

Because of this it may not be all software packages ΙΟΑ-ΙΟη of the generic control software 10 which are in use when controlling all types of wind turbines. Some types of wind turbines may simply not comprise the function for which one of the software packages of the generic control software facilitates control of.

In this case these unused software packages may be used in case the wind turbine is to be updated alternatively not used at all. Alternative such software packages are removed from the generic control software 10.

The control module 6 may then be said to be user defined or wind turbine type specific when the designer of the wind turbine decides e.g. type of sensors for measuring wind speed. Based on the type of wind speed sensor an appropriate input address is decided and this input address is then added to the I/O table 12B of the configuration database 12. Here it is associated with the variable name for wind speed used in the generic control software 10. In this way it is entirely up to the designer or owner of the wind turbine 1 to decide sensors, actuators and other wind turbine related components of which some are illustrated on figure 1 (with reference numbers 2, 3, 4, 5, 9). When these are decided they are preferably associated with the generic control software 10 via the configuration file 11.

According to an embodiment of the invention it is possible to add new type of wind turbines to the configuration database 12 and thereby enabling the generic control software 10 to control the new wind turbine type.

The new type of wind turbine may distinguish from other known types of wind turbines in that a new pressure sensor is needed. To be able to create a configuration file 11 for the new type of wind turbine the different relevant tables of the

configuration database 12 is to be updated with information of this new pressure sensor.

When this is done a new configuration file 11 can be created and when the generic control software 10 via the core element 13 reads the internal variable tables 15 it will detect the new variable and enable or include this variable in the control of the wind turbine.

In case the variable is new to the generic control software 10 it is to be included here before it can be used.

It is generally understood that the invention is not limited to the above examples but may be combined in a multitude of varieties as specified in the claims. Additionally, it is understood that different aspects of the figures and/or the description above may be combined to obtain further embodiments. List of reference numbers

1. Wind turbine

2. Tower

3. Nacelle

4. Hub

5. Blade

6. Wind turbine controller / control module

7. Sub controller

8. Communication line

9. Sensor / actuator / wind turbine related components

10. Generic control software

11. Configuration file

12. Configuration database

13. Core element

14. I/O modules

15. Tables of the core element

Claims

1. A configuration system for configuring a generic control software (10) so that the generic control software (10) facilitates control of a specific type of wind turbine chosen from a plurality of different types of wind turbines, the configuration system comprising: a control module (6) comprising the generic control software (10) having potential to control the plurality of different types of wind turbines, one or more I/O modules (14) for connecting a plurality of wind turbine related components to the control module, and a configuration database (12) comprising an I/O table (12B) common for at least part of the plurality of different types of wind turbines, wherein a configuration file (1 1) for the specific type of wind turbine is created based on the content of the configuration database (12), and wherein the configuration file (1 1) enables the generic control software (10) to control the specific type of wind turbine by establishing communication between the generic control software (10) and the wind turbine related components connected to the one or more I/O modules (14).

2. A configuration system according to claim 1, wherein the configuration database (12) comprises a variable table (12A) common for at least part of the plurality of different types of wind turbines.

3. A configuration system according to any preceding claims, wherein the configuration database (12) comprises a parameter table (12C) common for at least part of the plurality of different types of wind turbines.

4. A configuration system according to any preceding claims, wherein the configuration database (12) comprises an alarm table (12D) common for at least part of the plurality of different types of wind turbines.

5. A configuration system according to any preceding claims, wherein the configuration file (11) for a specific wind turbine type is available for editing by a user of a wind turbine.

6. A configuration system according to any preceding claims wherein the configuration database (12) comprises a default configuration file (11) for at least part of the plurality of different types of wind turbines.

7. A configuration system according to any of the preceding claims, wherein the content of the configuration database (12) is configured for being updated in case a new type of wind turbine is to be controlled by the generic control software (10).

8. A configuration system according to any preceding claims, wherein the generic control software (10) is the application software enabling the control module (6) to control a specific wind turbine type when a specific wind turbine type configuration file (11) is created from the configuration database (12) and uploaded to said wind turbine.

9. A configuration system according to any preceding claims, wherein the

configuration database (12) is located external to the wind turbine (1).

10. A configuration system according to any of the preceding claims, wherein a core element (13) is capable of handling communication between software packages of the generic control software (10) and between the generic control software (10) and the I/O modules (14).

11. A configuration system according to any of the preceding claims, wherein the control module (6) is configured for requesting a new configuration file (11).

12. A configuration system according to any of the preceding claims, wherein the generic control software (10) comprises a plurality of independent software packages (10A, 10B, IOC, 10D, ION) for controlling different parts of the wind turbine.

13. A configuration system according to any of the preceding claims, wherein a generic control software (10) approved in test, can be used to control a plurality of different types of wind turbines without further tests.

14. A configuration system according to any of the preceding claims, wherein said configuration file (11) at least facilitates mapping of communication between the generic control software (10) and the one or more I/O modules (14).

15. A method of configuring a generic control software (10) so that said generic control software (10) facilitates control of a specific type of wind turbine chosen from a plurality of different types of wind turbines, said method comprising: creating a configuration file (11) for the specific type of wind turbine based on the content of a configuration database (12), said configuration database (12) at least comprising an I/O table (12B) common for at least a part of the plurality of different types of wind turbines, said created configuration file (11) enabling the generic control software (10) to control a specific type of wind turbine by establishing communication between the generic control software (10) of a control module (6) and wind turbine related components connected to one or more I/O modules (14) for connecting a plurality of wind turbine related components to the control module (6), uploading said configuration file (11) to said control module (6) comprising said generic control software (10) having potential to control the plurality of different types of wind turbines, wherein an element (13) of said control module (6) reads and integrates at least a part of the content of said configuration file (11) so as to enable said communication between said generic control software (10) and said wind turbine related components.

16. A method according to claim 15, wherein said integration comprises that a core element (13) of said control module (6) copies at least some of the content of the configuration file into one or more tables (15) of said control module.

17. A method according to claim 16, wherein said one or more tables (15) are comprised in an internal core element database of said control module.

18. A method according to claim 15, 16 or 17, wherein said configuration file (11) comprises data which when processed by said control module results in a mapping of communication between the generic control software (10) and the one or more I/O modules (14).

19. A method according to claim any of claims 15-18, wherein the content of the configuration database (12) is updated in case a new type of wind turbine is to be controlled by the generic control software (10).

20. A method according to claim any of claims 15-19, wherein the configuration database (12) comprises one or more default configuration files (11) for at least part of the plurality of different types of wind turbines.