CONTROL AND METHODS FOR A WIND ENERGY PLANT AND COMPUTER PROGRAM
Patent Information
- Application Number
- DE502021007212
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-09-16
- Publication Date
- 2025-04-30
- Estimated Expiration
- 2041-09-16
AI Technical Summary
The existing wind turbine control systems require full updates from manufacturers to adapt to changing framework conditions, leading to significant effort and cost, especially when framework conditions vary across different territorial areas or affect individual turbines.
A modular control system for wind turbines that includes an operating software with a core module and customer applications, allowing for the adaptation of operating parameters without full software updates. The system includes programming interfaces and safety devices to protect critical components and ensure safe operation.
Enables regular adaptation of wind turbine operations to changing framework conditions without manufacturer involvement, reducing costs and effort, while ensuring safe and efficient operation by protecting critical components from improper reprogramming.
Description
[0001] The invention relates to a control system for wind turbines. Wind turbines are known and have a control system to regulate their operation. This control system is based on operating software that can execute various operating modes. These operating modes are selected in the operating software, for example, by sensors or operator specifications. The operating modes are configured to enable the operation of the wind turbine throughout its entire service life.
[0002] A typical lifespan for a wind turbine is assumed to be approximately 25 to 30 years. To achieve this, load models are defined for the wind turbine, which then guide the operating modes. During operation, certain modes are designed to induce a short-term overload based on these load models through appropriate turbine control. Such operating modes do not directly damage the wind turbine but merely reduce its overall operating life or the lifespan of individual components. These modes are only selected in rare situations, such as to support a grid or in other unexpected cases that deviate from normal operation, thus statistically ensuring a predetermined lifespan.Thus, the functions of the operating software for executing the operating modes are fixed and are primarily based on the requirements and conditions of the network as well as predefined remuneration standards.
[0003] In the past, operating a wind turbine in this way represented a suitable solution for the operator, when compensation for energy fed into the grid by the turbine was contractually fixed for essentially its entire lifespan and wind turbines did not have any special grid support functions. However, recently, the framework conditions have been changing with increasing frequency over the lifespan of a wind turbine. These changing conditions include political decisions regarding compensation, increasingly stringent environmental regulations, changes in surrounding development, and rising demands from the grid operator. In some cases, these individual changes are directly related to one another. For example, new grid support tasks are rewarded with adjusted compensation when fulfilled by the operator.
[0004] To adapt the operation of the wind turbine to these changing conditions, for example by adding operating modes, an update of the operating software is necessary, which is generally only possible through the wind turbine manufacturer. If the conditions change differently for wind turbines in different regions, the operating software for each group of wind turbines in that region must be individually adapted. This also takes into account changing conditions that affect only individual wind turbines. Therefore, for the wind turbine to operate optimally under the conditions applicable to it, the operating software must be regularly and individually adapted or updated.This leads to increased effort and associated costs, making the already shrinking margins in operating a wind energy plant increasingly unprofitable.
[0005] Document US 2010 / 0274400 A1 discloses a configuration system for a wind turbine in which the settings of a wind turbine are optimized with respect to predefined parameters based on identified preferred ranges or settings. Document US 2020 / 0291924 A1 discloses a method for updating a control system of a wind turbine.
[0006] The object of the invention is therefore to address the problems of the prior art. In particular, the object of the present invention is to enable the operation of a wind turbine to be regularly adapted to changing conditions without requiring a complete update of the operating software by the manufacturer. Furthermore, it is at least an object of the present invention to propose an alternative to the prior art.
[0007] Accordingly, the invention relates to a control system for a wind turbine with operating software for operating the wind turbine according to claim 1.
[0008] The invention relates to a control system for a wind turbine, including operating software for operating the wind turbine. The operating software is configured to regulate or control at least the electrical power output of a wind turbine generator, the rotational speed of a wind turbine generator, the azimuth angle of a wind turbine nacelle, and the pitch angle of at least one rotor blade of the wind turbine rotor. The operating software is therefore particularly useful for controlling or regulating essentially all components of the wind turbine that require regulation or control, preferably those used for generating electrical energy. This includes, for example, direct control or regulation of the corresponding components of the wind turbine by the operating software, as well as indirect control or regulation.In an indirect control system, the operating software, for example, only provides a specification for a further control system connected to the wind turbine's control system, which can also be called a component control system, or another module. The actual control of the component for which the further control system or module is intended is then carried out by this component control system.
[0009] Furthermore, the operating software comprises a core module and at least one customer application. The operating software is therefore preferably modular in structure. The first module of the operating software is thus the core module, and another module of the operating software is a customer application.
[0010] The customer application is further configured to determine a parameter depending on at least one function of the customer application. That is, the customer application includes at least one function that determines a parameter, preferably as an output value. This parameter is then provided by the customer application to the core module. A parameter is preferably any value, such as a variable, that is assigned to a function for operation. An example of a parameter is a setpoint for controlling the active power output of a wind turbine to the grid. Furthermore, a parameter can also be understood as a control command that can be used to switch functions, such as bat protection functions, on or off.
[0011] Furthermore, the core module is configured to detect or predict a load exerted on the wind turbine during operation. If the core module detects or predicts such a load that is below a predefined load limit, the wind turbine is operated according to the parameter provided by the customer application. If the detected or predicted load is above the predefined load limit, the parameter provided by the customer application is adjusted, and the wind turbine is operated according to the adjusted parameter. Preferably, this parameter is adjusted within the core module itself.Alternatively, in the case of a detected load or a predicted load that is above the predefined load limit, the parameter provided by the customer application is disregarded and the wind turbine is operated with a parameter that is determined or stored in the core module.
[0012] Preferably, the predefined load limit is an upper load limit or a reference load limit. An upper load limit describes a limit determined by tests, simulations, and / or calculations that must not be exceeded, as exceeding it would immediately damage the component for which the load limit is defined. A reference load limit, on the other hand, is also a limit determined by tests, simulations, and / or calculations, which, as long as it is not exceeded, normally results in a reference service life, e.g., 20 years. Exceeding a reference load limit would therefore not lead to immediate damage, but would reduce the component's service life compared to the reference service life.
[0013] Preferably, the core module is configured to detect or predict multiple loads applied to the wind turbine during operation. Accordingly, an assigned load limit is defined for each of the applied loads. For example, if all loads are below their assigned load limits, the wind turbine is operated according to the parameter provided by the customer application. If only one load exceeds its load limit, the parameter is adjusted, and the wind turbine is operated according to this adjusted parameter.
[0014] In the case of detected or predicted loads, particular preference is given to those loads that are affected or may be affected by the parameter provided by the customer application.
[0015] Furthermore, the controller has a primary and a secondary programming interface. The primary programming interface is used to program the core module, specifically the load limits or operating functions performed within the core module to operate the wind turbine. The secondary programming interface is used to program the customer application, particularly its functionality. Additionally, the secondary programming interface is designed to prevent the core module from being programmed or reprogrammed via the secondary programming interface.
[0016] Accordingly, the operating software for controlling a wind turbine comprises several modules, each programmable via separate programming interfaces. The core module is used for controlling and regulating the wind turbine, preferably for its automated operation, and for monitoring its load. The core module can execute this operation based on parameters provided by a customer application. However, the core module safeguards the turbine by adjusting or disregarding these parameters if an overload occurs, thus preventing any operating mode from being executed that could damage the wind turbine.Furthermore, the customer application, which can be programmed via a separate programming interface, provides the user with the possibility to specify individual functions for the operation of the wind turbine, the parameters of which are then taken into account by the core module during operation.
[0017] Individual programming of a wind turbine by a customer application to adapt the operating behavior of the wind turbine is thus created, whereas a safe and error-free operation of the wind turbine is still ensured by the core module, which cannot be changed via the programming interface with which the customer application can be programmed.
[0018] This allows the customer or operator to individually adapt the operation of each individual wind turbine without jeopardizing safe operation.
[0019] According to a first embodiment, access to the first programming interface is protected by a first security device. Access to the second programming interface is protected by a second security device, which is preferably different from the first security device. That is, each of the two programming interfaces, namely the first and the second, has its own security device. These security devices are also preferably different. Security devices are generally known and include, for example, user authentication, where the user is authenticated to access the programming interface. For authentication, for example, the entry of a username and password is required.If reference is made here to two different security devices, the difference, according to one embodiment, can already lie in the different access data, such as usernames and / or passwords. Furthermore, it also includes the fact that the first security device is designed to be comparatively more secure than the second security device, for example, by requiring only a username and password for authentication with the second security device, whereas the first security device additionally requires a one-time password or a token for authentication at the first programming interface. Accordingly, a higher level of security is preferably chosen for access to the first programming interface via the first security device than for access to the second programming interface with the second security device.
[0020] This ensures that a person authorized to access the second programming interface can only access the first programming interface in exceptional cases, for example, if they belong to a specific group of people, such as an installer or manufacturer of the wind turbine. The group of people, which includes, for example, the operator who typically has access to the second programming interface, will therefore generally not be able to bypass the first security device and access the first programming interface, thus protecting the core module from reprogramming by this group.This means that an operator or user of the wind turbine can, based on their access authorization via the second security device, access the second programming interface to customize the customer application and thus individually adapt the operation of the wind turbine. In contrast, the core module, which is intended for general safety aspects of the wind turbine, is protected against reprogramming by the operator or user.
[0021] According to a further embodiment, at least one additional customer application can be integrated into the operating software via the second programming interface. This additional customer application preferably contains at least one further function. This additional function also serves to provide at least one or more parameters for the core module. Thus, a user of the wind turbine can not only modify an existing customer application to adapt the operation of the wind turbine, but can even provide any desired functions in new customer applications and integrate them into the operating software. The control of the wind turbine can therefore be adapted by several parameters from different applications.For example, one customer application is used to generate individual time-controlled commands for controlling a bat protection function, while a second customer application specifies setpoints for regulating the energy to be fed into the grid.
[0022] According to a further embodiment, the controller comprises at least one sensor interface. The sensor interface serves to receive one or more sensor data points from sensors of the wind turbine itself or from a unit connected to the wind turbine, such as a wind measurement mast. Furthermore, the core module is configured to provide the sensor data, or sensor data derived from the sensor data using the core module, to the customer application or a further customer application. The customer application or the further customer application is also configured to determine the parameter for the core module based on the at least one function defined in the customer application and additionally based on the sensor data or the derived sensor data.
[0023] The core module can thus directly access sensor data from the wind turbine or a unit connected to the wind turbine, such as a wind measurement mast, in order to incorporate current sensor data when generating the control parameter. Wind turbine control, which is normally performed by the core module, can therefore be fully integrated into a customer application and is thus individually customizable. However, when the customer application is running, the operating software always checks whether this execution could damage the turbine and only intervenes in such cases.
[0024] According to a further embodiment, the operating software comprises an application interface between the core module and the customer application for transferring parameters from the customer application to the core module, as well as for transferring sensor values or status data indicating the operating state of the wind turbine from the core module to the customer application. Preferably, the application interface is configured to transmit a control command or a variable, which in particular includes a setpoint for a control system or a manipulated variable, as a parameter.
[0025] The application interface is thus implemented directly in the operating software, enabling direct communication between the modules of the operating software. Furthermore, the core module and the customer application are clearly separated and secured against each other by the application interface, as it unambiguously defines which data may be exchanged between the customer application and the core module.
[0026] According to a further embodiment, the control system is a component of a wind farm controller or a wind turbine. Alternatively, the control system is a distributed control system and at least partially a component of a control center, a wind farm controller, a wind turbine control system, and / or another, particularly remote, computer. Preferably, the core module is located or can be located in the wind turbine or the wind farm controller. The customer application or the additional customer application is located or can be located in the control center or the additional computer. Furthermore, according to another alternative, different customer applications are located in different and geographically separate computer units, each of which has a second programming interface.
[0027] The invention therefore encompasses control systems that are either fully integrated directly into a wind turbine or wind farm controller, or distributed control systems. Preferably, the core module is integrated into a wind turbine to control it. However, the customer application can be executed, for example, in a control center, which represents a higher-level authority and is connected to multiple wind farms, thus enabling remote control of operations. According to another preferred alternative, the customer application is executed on a separate computer, which could also be a mobile device such as a laptop or mobile phone. This allows parameters for operating the wind turbine to be provided remotely.
[0028] According to a further embodiment, the control system is connected to at least one controllable or adjustable hardware component. The hardware component is preferably a hardware component of the wind turbine. Furthermore, the core module is configured to control or adjust the hardware component. In this case, the core module controls or adjusts the hardware component based on parameters that are control commands or variables and are received from the customer application via the application interface. Such hardware components include components that, in particular, have an impact on the operation of the wind turbine.Such components include, for example, components for regulating or controlling the electrical power of a wind turbine generator, for controlling or regulating the rotational speed of a wind turbine rotor, for controlling or regulating an azimuth angle of a wind turbine nacelle and / or for controlling or regulating at least one pitch angle of at least one rotor blade of the wind turbine rotor.
[0029] According to a further embodiment, the core module includes a conflict management module. The conflict management module is configured to check parameters, preferably comprising control commands or variables, received from the customer application via the application interface, for conflicts with operational functions executed by the core module. Alternatively or additionally, the conflict management module is configured to check parameters received via the application interface for conflicts with parameters received by the customer application via the application interface.
[0030] The conflict management module is therefore used to identify conflicts that arise when the operation of the wind turbine, performed by the core module, leads to an unsafe or faulty state of the wind turbine due to parameters received from the customer application. It also checks whether parameters received from different customer applications would cause such an unsafe or faulty state of the wind turbine. Examples of such conflicts include a parameter received from one customer application requesting a shutdown of the wind turbine, while another customer application transmits a control command via the application interface requesting maximum possible electrical energy generation from the wind turbine.Furthermore, a conflict would also be detected, for example, if the core module has stopped operating the wind turbine due to a maintenance interval, whereas the customer application requests that the wind turbine continue to operate. Different setpoints for the same control system, such as different power reductions for the wind turbine, requested by different customer applications can also be considered a conflict.
[0031] The detection of a conflict therefore does not represent the detection of an overload of the wind turbine, caused, for example, by unsuitable parameters received via the application interface. Rather, the conflict management module uses conflict detection to decide which of the conflicting parameters should be executed. Preferably, in the case of a detected conflict, the parameter(s) received via the application interface are disregarded, and operation is preferably carried out solely based on the parameters and operating functions of the core module. According to a further embodiment, each parameter, or at least some of the parameters, is assigned a priority. In the case of a conflict between two parameters, the prioritization of the parameters is then considered to ensure that the parameter with the higher priority is used during operation.A parameter that triggers, for example, a network support measure is therefore preferably assigned a higher priority than a parameter that triggers bat protection or normal operation.
[0032] According to a further embodiment, the core module includes a remaining service life calculator which, upon receiving a parameter or a modified parameter from the customer application, is configured to determine or estimate the remaining service life of the wind turbine using that parameter and transmit this remaining service life to the customer application. Alternatively or additionally, the core module includes a service life consumption calculator which, upon receiving a parameter or a modified parameter from the customer application, is configured to determine or estimate the service life consumption using that parameter and transmit this to the customer application. The service life consumption calculator can, for example, output a value between a lower value, e.g., 0 or 0.2, and an upper value, e.g., 2 or 3.This value indicates how much of the system's service life or operating time is consumed compared to the reference service life under the current operating conditions. For example, if a customer application results in a value of 2, which can also be called the service life consumption indicator, then the system's service life is reached twice as fast, or halved in absolute terms. A value of 1 means that the service life assumed in the data sheet is reached exactly. Operating conditions with a service life consumption indicator below 1 reflect very gentle operation, resulting in very low service life consumption. These can be, for example, conditions with significantly reduced output power.
[0033] By retrieving the data, an operator can directly draw conclusions about the impact of their individual adjustments to the operation, in order to adapt the customer applications if necessary.
[0034] According to a further embodiment, the controller is connected to a network, namely a data network for data transmission. Furthermore, the controller is configured to transmit data received from the core module, such as the remaining service life, in particular status data of the controller or another unit or component of the wind turbine connected to the controller, such as a sensor, via the network, depending on a function of the customer application.
[0035] Sensor data or status data are therefore provided to the customer application by the core module, and functions of the customer application can be adapted or provided by the customer to enable the transmission of this data over the network, for example to a mobile device such as a mobile phone. In addition to the individual programming of the wind turbine's control system, the customer application also allows the operator to define individual queries regarding the operating status of the wind turbine.
[0036] According to another embodiment, the controller is connected to the network and configured to receive data via the network by the customer application, depending on a function of the customer application. Furthermore, the customer application is configured to transmit the received data, or data derived from it by the function, to the core module via the application interface, particularly as parameters. Thus, the customer application can also be used to receive specific control commands or parameters, such as setpoints, for regulating the wind turbine via the network from a remote device predefined by the customer application, such as a mobile phone, and to adjust the operation of the wind turbine based on this data.
[0037] According to another embodiment, the data received by the customer application via the network is sensor data. Furthermore, the controller is configured to adapt or process the sensor data received by the customer application using a function stored in the customer application, in order to generate control commands or setpoints for controlling the wind turbine and to transmit these as parameters to the core module.
[0038] The customer application can therefore be configured with functions that allow additional sensor data, which may influence the operation of the wind turbine but cannot be provided by the core module, to be directly incorporated into control commands or adjusted setpoints, and these control commands or setpoints to be transmitted to the core module. The operation of the wind turbine can thus be individually supplemented by taking into account additional sensors not typically included in the wind turbine itself.
[0039] According to a further embodiment, the core module contains several operating characteristics, several predefined parameters of an operating function within a permitted or defined parameter space, and / or several predefined operating functions. Furthermore, the controller is configured to execute a call to at least one of the operating functions, the use of one or more of the parameters for the operating function, or the selection of at least one of the stored operating characteristics via the application interface, preferably preventing modification of the operating characteristics, the predefined parameters for the operating function, or the predefined operating functions via the application interface.The application interface is preferably secured in such a way that only the stored operating characteristics and / or the operating functions and / or the parameters for one of the operating functions can be called via the application interface, whereby all other data transmitted from the customer application to the core module is suppressed or ignored by the core module.
[0040] According to this embodiment, the core module only offers the possibility of receiving data from the customer application via the application interface as parameters for selecting operating characteristics or functions to be executed. Completely individual control of the operation is therefore not possible, whereas particularly safe operation of the wind turbine is enabled. The customer application thus offers a degree of individual adaptability of the operation to a predefined extent.
[0041] According to a further embodiment, at least one operating characteristic curve, preferably a speed-power characteristic curve, can be stored in the core module. The core module is further configured to regulate the feed-in power of the wind turbine depending on the operating characteristic curve. Furthermore, the customer application is preferably configured to provide the operating characteristic curve for the core module or to adapt or modify the stored operating characteristic curve.
[0042] Therefore, it is not only necessary to transfer parameters from the customer application, but also to specify complete operating characteristics for the core module.
[0043] Furthermore, the invention comprises a method for a control system according to one of claims 1 to 13, wherein, according to the method, a customer application is programmed or reprogrammed via the second programming interface to adapt the operation of the control system.
[0044] Furthermore, the invention comprises a computer program product comprising instructions which, when executed on a computer, cause the computer to execute the method according to claim 14 or which, when executed on a computer, cause the computer to form a controller according to any one of claims 1 to 13.
[0045] Further embodiments are shown in the exemplary embodiments explained in more detail in the figures. These show: Figure 1 a wind turbine, Figure 2 a control system for a wind turbine according to a first embodiment, Figure 3 a distributed control system for a wind turbine according to a second embodiment of the invention and Figure 4 the steps of an embodiment of the method.
[0046] Figure 1Figure 1 shows a schematic representation of a wind turbine 100 according to the invention. The wind turbine 100 has a tower 102 and a nacelle 104 on the tower 102. An aerodynamic rotor 106 with three rotor blades 108 and a spinner 110 is provided on the nacelle 104. During operation of the wind turbine 100, the aerodynamic rotor 106 is set into rotation by the wind and thus also rotates an electrodynamic rotor or rotor of a wind turbine generator, which is directly or indirectly coupled to the aerodynamic rotor 106. The electric wind turbine generator is arranged in the nacelle 104 and generates electrical energy. The pitch angles of the rotor blades 108 can be changed by pitch motors at the rotor blade roots of the respective rotor blades 108.
[0047] Figure 2Figure 10 shows a controller 10 for a wind turbine 100. The controller 10 includes a memory 12 in which data can be stored. In particular, the memory 12 includes operating software 14. The operating software 14 further includes a core module 16 and a customer application 18. Several functions 20 are stored in the customer application 18, which are executed by means of a processor 22. For this purpose, the processor 22 is connected to the memory 12 via a data connection 23. The functions 20 provide a parameter 24 as an output value, which is transmitted from the customer application 18 to the core module 16 via an application interface 26.
[0048] The core module 16 is configured to operate the wind turbine 100 based on parameter 24 and operating functions 28 stored in the core module 16. During operation of the wind turbine 100, the core module 16 uses the processor 22, and in particular the operating functions 28, to check various sensor values 30 supplied to the processor 22 by sensors 32 during operation of the wind turbine 100.
[0049] Several load limits 34, stored for various components in core module 16, serve to compare the load 36 detected by processor 22 from sensor values 30 or a predicted load 38. The comparison checks in core module 16 whether the detected load 36 or a predicted load 38 is above the corresponding predefined load limit 34. If this is not the case, the wind turbine 100 is operated with operating function 28, taking parameter 24 into account. However, if the load 36 or 38 is above the predefined load limit 34, or if such a case is predicted, parameter 24 is either disregarded in operating function 28, or the wind turbine 100 is operated with a parameter 40 determined in core module 16.
[0050] For operation, for example, a hardware 42 of the wind turbine 100 is connected to the control unit 10, which also delivers its operating status to the processor 22 of the wind turbine 100 in order to determine the load 36, 38 exerted on the wind turbine 100.
[0051] Furthermore, the controller 10 includes a first programming interface 44 and a second programming interface 46. The core module 16 can be programmed or reprogrammed using the first programming interface 44. In particular, the load limits 34 can be set and the operating functions 28 adjusted. The second programming interface 46 is configured to program or reprogram the customer applications 18, specifically their functions 20. However, the second programming interface 46 is also configured to prevent reprogramming of the core module 16 via the second programming interface 46. For this purpose, the controller 10 includes a first safety device 48 and a second safety device 50.The first security device 48 protects the first programming interface 44, ensuring that access to the core module 16 is restricted to authorized personnel, such as the manufacturer of the wind turbine 100. The second security device 50 serves, on the one hand, to protect access to the customer application 18 via the second programming interface 46 from unauthorized access, and on the other hand, to ensure that reprogramming of the core module 16 via the second programming interface 46 is not possible.
[0052] Furthermore, the customer application 18 is also connected to the processor 22 via another data connection 52, which can also be configured as a programming interface. This allows the customer application 18, and in particular its functions 20 according to this embodiment, to receive sensor values 30 from the sensors 32 in order to generate the parameters 24 based on these sensor values 30. Alternatively, according to another embodiment, which is not shown here but is identical except for the following modification, this data connection 52 between the processor 22 and the customer application 18 is not provided. According to this alternative embodiment, the sensor data 30 are therefore also transferred from the core module 16 to the customer application 18 via the application interface 26.This also makes it possible for sensor data 54, derived from sensor data 30 using core module 16, to be transmitted to the customer application 18, rather than the sensor data 30 directly. Furthermore, a lifetime determination module 56 is connected to the processor 22. This module determines a predicted lifetime 57 based on the past operation of the wind turbine 100 and a forecast for its operation with the operating functions 28 to be executed, particularly taking into account the parameters 24. This lifetime is also provided by the processor 22 to the customer application 18 via core module 16 and application interface 26. This allows the application to receive feedback after a customer changes a parameter 24, specifically by adjusting a function 20, indicating how the lifetime 57 of the wind turbine 100 changes when this new parameter 24 is taken into account.
[0053] Figure 3Figure 10 shows a controller 10, which corresponds to a distributed controller 60. The application interface 26 corresponds to a network connection 62, so that the core module 16 and the customer application 18 are geographically separated. However, the operating software 14 still comprises both the core module 16 and the customer application 18. In the embodiment shown here, the function 20 provided in the customer application 18 serves only to select from several operating characteristics 64 stored in the core module 16, which are used to operate the hardware 42, namely, for example, the generator or the rotor. The second programming interface 46 can thus be used, for example, to adjust the function 20 via a mobile phone or other mobile device 66 so that a different operating characteristic 64 than the one previously executed is selected.The operation of wind turbine 100 is then adjusted so that it operates according to the other operating characteristic curve. However, it is ensured that the load limits 34 are not exceeded. For this purpose, for example, the core module 16 automatically switches back to a previous operating characteristic curve that guarantees safe operation.
[0054] Figure 4Figure 7 shows the steps of an exemplary embodiment of the method. In step 70, a wind turbine 100 is operated. Its operation is controlled by an operating function 28 in a core module 16 of the wind turbine 100. Furthermore, in step 72, the wind turbine 100 receives a function 20 from a user via a second data interface 46. In step 74, this function 20 is stored in a customer application 18. In step 76, the function 20 is executed in the controller 10 of the wind turbine 100 and delivers a parameter in step 78. This parameter is transferred to a core module 16 in step 80 and taken into account during operation with the operating function 28, thus adjusting the operation of the wind turbine 100 in step 80.In step 82, load limits 34 are taken into account, and if these are exceeded during the modified operation, in step 84, parameter 24, which was transmitted from the customer application 18 to the core module 16 via the application interface 26, is either modified or replaced by parameter 40, which is stored as a standard parameter in the core module 16. Thus, if load limits 34 are exceeded, the wind turbine 100 is operated again in step 70 with the original operating mode. Furthermore, in step 86, the remaining service life of the wind turbine 100 is determined and made available to the customer application 18.
Claims
1. A controller (10) for a wind turbine (100) with an operating software (14) for operating the wind turbine (100), wherein the operating software (14) is set up to regulate or control at least an electrical output of a wind turbine generator, a speed of a wind turbine rotor (106), an azimuth angle of a wind turbine nacelle (104), and a pitch angle of at least one rotor blade (108) of the wind turbine rotor (106), wherein the operating software (14) comprises a core module (16) and at least one customer application (18), wherein the customer application (18) is set up to determine a parameter (24), in particular a control variable, in particular a target value, depending on at least one function (20) of the customer application (18), and provide it for the core module (16), and wherein the core module (16) is set up to - Detect and / or predict a load (36, 38) acting on the wind turbine (100) during an operation of the wind turbine (100), - In a case where a detected or predicted load (36, 38) lies below a predefined load limit (34), to operate the wind turbine (100) as a function of the parameter (24) provided by the customer application (18), and - In a case where a detected or predicted load (36, 38) exceeds the predefined load limit (34), to adjust the prepared parameter (24) and leave the wind turbine (100) unconsidered as a function of the adjusted parameter (24) or the provided parameter (24), and operate the wind turbine (100) with a parameter (40) determined in the core module (16), wherein the controller (10) further has a first programming interface (44) and a second programming interface (46), wherein the first programming interface (44) is set up to program the core module (16), in particular the load limits (34), and wherein the second programming interface (46) is set up to program the customer applications (18), in particular their function (20), and prevent the core module (16) from being reprogrammed via the second programming interface (46).
2. The controller (10) according to claim 1, wherein access to the first programming interface (44) is protected by a first safety device (48), and access to the second programming interface (46) is protected by a second safety device (50), which preferably differs from the first safety device (48).
3. The controller (10) according to one of the preceding claims, wherein at least one additional customer application (18) can be incorporated into the operating software (14) via the second programming interface (46).
4. The controller (10) according to one of the preceding claims, wherein the controller (10) comprises at least one sensor interface for receiving one or several sensor data (30) from sensors (32) of the wind turbine (100), or from a unit connected with the wind turbine (100), and the core module (16) is set up to provide the sensor data (30) or sensor data (54) derived from the sensor data (30) with the core module (16) for the customer application (18) or the additional customer applications (18), and / or the customer application (18) or additional customer applications is / are set up to determine the parameter (24) for the core module (16) depending on a function (20) stored in the customer application (18) and depending on the sensor data (30) or the derived sensor data (54).
5. The controller (10) according to one of the preceding claims, wherein the operating software (14) has an application interface (26) between the core module (16) and the customer application (18), so as to receive the parameter (24), wherein the parameter (24) preferably comprises a control command or a variable, in particular a target value for regulation in the core module (16) or a manipulated variable.
6. The controller (10) according to one of the preceding claims, wherein the controller (10) is a component of a wind farm regulator or a wind turbine (100), or the controller (10) is a distributed controller (60), which is at least partially a component of a control center, a wind farm regulator, a wind turbine controller and / or another, in particular remote computer, wherein it is preferable that the core module (16) be designed in the wind turbine (100) or the wind farm regulator, and that the customer application (18) or the additional customer application (18) be designed in the control center or the additional computer.
7. The controller (10) according to one of the preceding claims, wherein the controller (10) is connected with at least one controllable or regulatable hardware component (42), and the core module (16) is set up to control or regulate the hardware component (42) as a function of parameters (24) which are received via the application interface (26) from the customer application (18).
8. The controller (10) according to one of the preceding claims, wherein the core module (16) has a conflict management module, which is set up to check parameters (24) received via the application interface (26) from the customer application (18) for conflicts with operating functions (28) implemented by the core module (16), or for conflicts with parameters (24) received from the additional customer application, and in case of a detected conflict, ignore or adjust the parameters (24) received from the customer application (18).
9. The controller (10) according to one of the preceding claims, wherein the controller (10) is connected with a network and set up to transmit data received from the core module (16), in particular state data for the controller (10) or another unit connected with the controller (10), such as a sensor (32), via the network depending on a function (20) of the customer application (18).
10. The controller (10) according to one of the preceding claims, wherein the controller (10) is connected with a network and set up to receive data through the customer application (18) via the network depending on a function (20) of the customer application (18), and to transmit the data or data derived from the latter to the core module (16) via the application interface (26).
11. The controller (10) according to claim 10, wherein the data received from the customer application (18) are sensor data (30), which are adjusted with the function (20) stored in the customer application (18), so as to thereby generate control commands or target values for a controller (10) of the wind turbine (100), in order to transfer them as parameters (24) to the core module (16).
12. The controller (10) according to one of the preceding claims, wherein the core module (16) has several stored operating characteristics (64) and / or several predefined operating functions (28) and / or several predefined parameters of an operating function, and the controller (10) is set up by way of the application interface (26) to retrieve at least one of the operating functions (28) or select one of the stored operating characteristics (64), or implement at least one of the parameters of the operating functions, wherein an ability to change the operating characteristics (64) of the operating functions or the parameters of the operating functions via the application interface (26) is preferably blocked.
13. The controller (10) according to one of the preceding claims, wherein the core module (16) can store at least one operating characteristic (64), in particular a speed / power characteristic, and the core module (16) is set up to regulate a feed-in power of the wind turbine (100) as a function of the operating characteristic (64), wherein the customer application (18) is preferably set up to provide the operating characteristic (64) for the core module (16), or to adjust or change the stored operating characteristic (64).
14. A method for a controller (10) according to one of claims 1 to 13, wherein a customer application (18) is programmed or reprogrammed via the second programming interface, so as to adjust the controller operation.
15. A computer program product, comprising instructions which, when performed on a computer, prompt the computer to implement the method according to claim 14 or which, when performed on a computer, prompt the computer to create a controller according to one of claims 1 to 13.