Wind Turbine Device Updates Using Topology-Derived Sequencing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional software and firmware update processes for wind turbines are lengthy, resulting in significant downtime and idle time, as they require stopping the turbine to perform updates across multiple devices connected in a network.

Innovation Solution

A method that utilizes a main computing device to obtain network topology information and update packages, triggering updates in a topology-derived order, starting from the periphery and moving inwards, to minimize interference and accelerate the update process by ensuring devices farther away from the main computing device are updated first, with intelligent restart procedures to maintain communication links.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional update processes are used for wind turbine devices, then all devices can be updated with new software/firmware, but the turbine must be stopped for long periods resulting in significant downtime and loss of power production

Engineering Contradiction:
Improveupdate completenessVSAvoidturbine downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The update process is segmented into multiple phases: download phase (turbine operational), installation phase (performed in topology-derived order), and restart phase (intelligent sequencing). This segmentation allows the turbine to remain operational during the download phase while updates are prepared, reducing overall downtime.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Update packages are downloaded and prepared in advance while the turbine is still operational. The main computing device obtains topology information and prepares update sequences before actual updates are applied, allowing the turbine to resume operation quickly after update initiation.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If devices are updated in parallel without considering network topology, then update speed may increase, but communication links may be interrupted causing update failures and reduced reliability

Engineering Contradiction:
Improveupdate speedVSAvoidupdate success rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The main computing device obtains network topology information in advance and determines the optimal update sequence before initiating updates. This preliminary action ensures that devices are updated in an order that maintains communication link integrity, preventing update failures.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The update process dynamically adjusts the installation sequence based on network topology parameters. Devices farther from the main computing device in the network topology are updated first, optimizing communication efficiency and reducing interruptions.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the turbine is stopped for device updates, then all devices can be safely updated without communication interruptions, but power production is lost and idle time increases

Engineering Contradiction:
Improveupdate safetyVSAvoidpower production
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The update process is divided into operational phase (download) and stationary phase (installation and restart). This allows the turbine to continue generating power during the download phase while updates are prepared, minimizing impact on power production.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The turbine maintains continuous power generation during the update download phase. The system enables updates to be staged and prepared without interrupting the turbine's operational cycle, ensuring continuity of useful action.

Inventive Principle:
Principle #20Continuity of useful action

4Ease of manufacture

If updates are performed in arbitrary order, then the process is simpler to implement, but communication links may be broken during restarts causing updates to fail

Engineering Contradiction:
Improveimplementation simplicityVSAvoidcommunication link stability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The main computing device obtains topology information and determines the optimal update sequence before initiating updates. This preliminary planning ensures communication link stability without requiring complex real-time decision-making during the update process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The update sequence is optimized based on network topology parameters, with devices farther from the main computing device updated first. This parameter-based sequencing maintains communication stability while keeping the implementation relatively simple.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12079614B2Updating software and/or firmware of plural wind turbine devices
Publication Date: 2024.09.03 SIEMENS GAMESA RENEWABLE ENERGY AS
  • US12079614B2 patent drawing

AI summary

Provided is a method of updating software and/or firmware of plural devices of a wind turbine, the plural devices being connected in a communication network to a main computing device, the method including: obtaining information regarding a topology of the communication network at the main computing device; obtaining update packages at the main computing device; triggering, by the main computing device, updating all devices for which an update package is present in a topology derived order, in particular staring at a periphery and continuing inwards.