*AERODYN DRIVER

<< Click to Display Table of Contents >>

Navigation:  Flexcom > Data Inputs > $LOAD CASE >

*AERODYN DRIVER

Previous pageNext page

Purpose

To provide a link between the structural (Flexcom) and aerodynamic (AeroDyn) models in a wind turbine simulation.

Theory

Refer to Coupling between Flexcom and AeroDyn for further information on this feature.

Keyword Format

A block of lines which provides the key pieces of information to couple AeroDyn to Flexcom:

HUB=Hub Node

TOWER=Tower Element Set Name

WIND SPEED=Wind Speed

SHEAR EXPONENT=Shear Exponent

ROTOR SPEED=Fixed Rotor Speed

INPUT FILE=Name of AeroDyn Primary Input File

DRIVER FILE=Name of AeroDyn Driver Input File

 

Table Input

Input:

Description

Hub:

The node (number or label) in the finite element model which is located at the hub.

Tower Element Set Name:

The portion (set of elements) of the finite element model which represents the tower.

Wind Speed:

The steady wind speed located at an elevation corresponding to the hub height. The hub height is determined from the vertical elevation of the Hub Node in the structural model. See Note (a).

Shear Exponent:

The power-law shear exponent which defines the wind speed profile as a function of vertical elevation. See Note (a).

Rotor Speed:

The fixed rotor speed (positive clockwise looking downwind).

AeroDyn Primary Input File Name:

The name of the AeroDyn primary input file. The file name must have a .dat file extension. This file may be generated using the $AERODYN section.

AeroDyn Driver Input File Name:

The name of the AeroDyn driver input file. The file name must have a .dvr file extension. This file will be generated by Flexcom when the analysis is run.

Notes

(a)The local undisturbed wind speed, U(x), for any given blade or tower node is determined using the following expression:

 where x is the instantaneous elevation of the blade or tower node above the mean water line. Refer to the AeroDyn documentation for further information.

(b)The file name entries allows you to control the names of the input files created by Flexcom for use by AeroDyn. The actual names chosen are not particularly important, but should be unique for every different load case simulation performed in order to avoid existing files being overwritten. A natural choice for both file names would be the name of the corresponding Flexcom dynamic simulation input file (.keyxm file extension). Note that the AeroDyn primary input file must have a .dat file extension, while the the AeroDyn driver input file must have a .dvr file extension. However all three files can, and ideally should, share the same file stub.