Wind Turbine Controller with Load-Limited Modular Software
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wind turbine operation software must be frequently updated to adapt to changing framework conditions such as remuneration policies, environmental regulations, and network requirements, leading to increased costs and unprofitability due to the need for individual customization for each wind turbine.
Innovation Solution
A modular controller system for wind turbines with a core module and customer application, where the core module detects and predicts loads, adjusts parameters, and ensures safe operation by preventing overload, while the customer application allows for individual adjustments through separate programming interfaces, ensuring secure and faultless operation without requiring complete software updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the operating software is updated to adapt to changing framework conditions, then the adaptability of the wind turbine operation is improved, but the device complexity and cost increase due to individual customization requirements
Solution Approach 1:
The operating software is segmented into a core module (containing fixed, certified control logic) and a customer application module (allowing flexible configuration). This segmentation enables adaptability through configuration of the customer application while preserving the stability and reliability of the core module, avoiding the need to re-certify the entire software system.
Solution Approach 2:
The system introduces dynamic configurability through the customer application, which can be adjusted during the operational lifetime of the wind turbine. This allows the operating parameters and control strategies to be dynamically adapted to changing framework conditions without modifying the certified core module.
2Adaptability or versatility
If the operating software is updated frequently to adapt to changing conditions, then the operational flexibility is improved, but the loss of time and increased costs for software updates and re-certification occur
Solution Approach 1:
By separating the software into core module and customer application, updates can be made in the customer application without triggering re-certification processes. This eliminates time-consuming re-certification while maintaining operational flexibility.
Solution Approach 2:
The core module is pre-configured with certified control logic that ensures compliance with safety and operational standards. This preliminary configuration allows flexible adjustments in the customer application without needing to re-certify the entire system, saving significant time.
3Adaptability or versatility
If the core module is made programmable to allow full customization, then the adaptability is improved, but the reliability and safety decrease due to potential programming errors
Solution Approach 1:
The system segregates programmable functions (customer application) from critical control functions (core module). The core module remains non-programmable or restricted, ensuring that safety-critical operations are not subject to user errors, while the customer application provides customization for non-critical functions.
Solution Approach 2:
The customer application acts as an intermediary layer between user requirements and the core control module. It translates high-level operational requirements into commands for the core module without allowing direct modification of the core module's safety-critical logic, thus maintaining reliability while enabling adaptability.
4Ease of operation
If separate programming interfaces are provided for core module and customer application, then the ease of operation is improved, but the device complexity increases
Solution Approach 1:
Different programming interfaces are provided for different functional requirements: a simplified interface for the customer application (easy to use) and a restricted interface for the core module (requiring authorization). This local differentiation of interface complexity achieves ease of operation for routine tasks while maintaining security for critical functions.
Data Source
AI summary
The invention relates to a controller for a wind turbine with an operating software for operating the wind turbine, wherein the operating software is set up to regulate or control at least an electrical output of a wind turbine generator, a speed of a wind turbine rotor, an azimuth angle of a wind turbine nacelle, and a pitch angle of at least one rotor blade of the wind turbine rotor, wherein the operating software comprises a core module and at least one customer application. The customer application is set up to determine a parameter, in particular a control variable, in particular a target value, depending on at least one function of the customer application, and provide it for the core module. The core module is set up to detect and/or predict a load acting on the wind turbine during an operation of the wind turbine, and in a case where a detected or predicted load lies below a predefined load limit, to operate the wind turbine as a function of the parameter provided by the customer application, and in a case where a detected or predicted load exceeds the predefined load limit, to adjust the prepared parameter and leave the wind turbine unconsidered as a function of the adjusted parameter or the provided parameter, and operate the wind turbine with a parameter determined in the core module. The controller further has a first programming interface and a second programming interface, wherein the first programming interface is set up to program the core module, in particular the load limits, and wherein the second programming interface is set up to program the customer applications, in particular their function, and prevent the core module from being reprogrammed via the second programming interface. The invention further relates to a method for a controller and a computer program product.