Samtec Wind Turbines Reference

Samcef Wind Turbines Reference Guide
2 | Samcef Wind Turbines | TOC
Contents
1 Reference Guide................................................................................................................................................ 8
2 SWT Command Reference................................................................................................................................9
2.1 Caesam Standard Commands...........................................................................................................11
2.1.1 Availability........................................................................................................................11
2.1.2 Description........................................................................................................................ 11
2.2 Adapt wind data to Wind Turbine....................................................................................................13
2.3 Add Engineering Object in Shared Workspace .............................................................................. 14
2.3.1 Availability........................................................................................................................14
2.3.2 Description........................................................................................................................ 14
2.4 Add missing sensors.........................................................................................................................15
2.4.1 Availability........................................................................................................................15
2.4.2 Description........................................................................................................................ 15
2.4.3 When and how to use........................................................................................................ 15
2.5 Add orientations from file................................................................................................................ 16
2.6 Bacon Postprocessor........................................................................................................................ 16
2.6.1 Availability........................................................................................................................16
2.6.2 When is it used?................................................................................................................ 16
2.6.3 Description........................................................................................................................ 16
2.7 Browse result files ...........................................................................................................................16
2.7.1 Availability........................................................................................................................17
2.7.2 When is it used?................................................................................................................ 17
2.8 Build sensor CCL file.......................................................................................................................17
2.9 Check Model ...................................................................................................................................17
2.9.1 Availability........................................................................................................................18
2.9.2 When is it used?................................................................................................................ 18
2.9.3 Description........................................................................................................................ 18
2.9.4 Remarks.............................................................................................................................20
2.10 Convert LC (on/off-shore)............................................................................................................. 20
2.10.1 Availability......................................................................................................................20
2.10.2 Description...................................................................................................................... 20
2.10.3 Example...........................................................................................................................20
2.11 Create Extreme Load/Fatigue/VL Durability Analysis ................................................................ 21
2.11.1 Availability......................................................................................................................21
2.11.2 Description...................................................................................................................... 21
2.12 Create new functions .....................................................................................................................23
2.12.1 Availability......................................................................................................................23
2.12.2 Description...................................................................................................................... 23
2.13 Create new loadcases..................................................................................................................... 24
2.13.1 Availability......................................................................................................................24
2.13.2 Description...................................................................................................................... 24
2.14 Create Super-Element Restitutions ............................................................................................... 26
2.14.1 Availability......................................................................................................................26
2.14.2 Description...................................................................................................................... 26
2.15 Create Transient/Modal Analyses from load cases .......................................................................26
2.15.1 Availability......................................................................................................................26
2.15.2 Description...................................................................................................................... 27
2.16 Create troubleshooting package..................................................................................................... 27
2.16.1 Availability......................................................................................................................27
2.16.2 Description...................................................................................................................... 27
2.16.3 When and how to use...................................................................................................... 27
2.17 Direct WT connection help table................................................................................................... 28
Samcef Wind Turbines | TOC | 3
2.18 Display Bacon Model.....................................................................................................................29

2.18.1 Availability......................................................................................................................29
2.18.2 When is it used?.............................................................................................................. 29
2.18.3 Description...................................................................................................................... 29
2.19 Export Engineering Object ........................................................................................................... 30
2.19.1 Availability......................................................................................................................30
2.19.2 Description...................................................................................................................... 30
2.20 Export... (a component)..................................................................................................................30
2.20.1 Availability......................................................................................................................30
2.20.2 When is it used?.............................................................................................................. 31
2.20.3 Description...................................................................................................................... 31
2.20.4 Remarks...........................................................................................................................31
2.21 Generate load cases... ....................................................................................................................31
2.21.1 Availability......................................................................................................................31
2.21.2 Description...................................................................................................................... 31
2.21.3 Remarks...........................................................................................................................33
2.22 Show/Hide object ..........................................................................................................................34
2.22.1 Availability......................................................................................................................34
2.22.2 When is it used................................................................................................................ 34
2.22.3 Description...................................................................................................................... 34
2.23 Import Engineering Object ........................................................................................................... 35
2.23.1 Availability......................................................................................................................35
2.23.2 Description...................................................................................................................... 35
2.24 Import results..................................................................................................................................35
2.24.1 What it does.....................................................................................................................35
2.24.2 How to use.......................................................................................................................35
2.24.3 The CSV file....................................................................................................................36
2.25 Link Transient analysis ................................................................................................................. 37
2.25.1 Availability......................................................................................................................37
2.25.2 When is it used?.............................................................................................................. 37
2.25.3 Description...................................................................................................................... 37
2.26 List connectors............................................................................................................................... 38
2.26.1 Availability......................................................................................................................38
2.26.2 Description...................................................................................................................... 38
2.27 Manage of Assembly of Components............................................................................................ 40
2.27.1 Availability......................................................................................................................40
2.27.2 When is it used?.............................................................................................................. 40
2.27.3 Description...................................................................................................................... 40
2.27.4 Remarks...........................................................................................................................42
2.28 Migrate CP file............................................................................................................................... 42
2.28.1 Availability......................................................................................................................42
2.28.2 Description...................................................................................................................... 42
2.28.3 When and how to use...................................................................................................... 43
2.29 Open temporary directory.............................................................................................................. 43
2.30 Pack & Go .....................................................................................................................................43
2.30.1 Availability......................................................................................................................43
2.30.2 Description...................................................................................................................... 43
2.30.3 When to use..................................................................................................................... 43
2.30.4 Remarks...........................................................................................................................44
2.31 Refresh orientations........................................................................................................................44
2.32 Run Analysis .................................................................................................................................44
2.32.1 Availability......................................................................................................................44
2.32.2 Description...................................................................................................................... 45
2.33 Run python file ............................................................................................................................. 45
2.33.1 Availability......................................................................................................................45
2.33.2 When is it used?.............................................................................................................. 46
2.33.3 Description...................................................................................................................... 46
2.33.4 Remarks...........................................................................................................................46
2.34 SamcefField Postprocessing ......................................................................................................... 46
2.34.1 Availability......................................................................................................................46
2.34.2 When is it used?.............................................................................................................. 46
2.34.3 Description...................................................................................................................... 46
2.35 SamcefField Preprocessing ...........................................................................................................47
2.35.1 Availability......................................................................................................................47
2.35.2 When is it used?.............................................................................................................. 47
2.35.3 Description...................................................................................................................... 47
2.36 Shaded / Wireframe ...................................................................................................................... 48
2.36.1 Availability......................................................................................................................48
2.36.2 Description...................................................................................................................... 48
2.37 Show / hide 3D view labels............................................................................................................48
2.38 Show/Hide console ....................................................................................................................... 49
2.38.1 Availability......................................................................................................................49
2.38.2 When to use?................................................................................................................... 49
2.39 Super-Element Conversion ........................................................................................................... 49
2.39.1 Availability......................................................................................................................49
2.39.2 When is it used?.............................................................................................................. 49
2.39.3 Description...................................................................................................................... 50
2.40 Swap component... ........................................................................................................................50
2.40.1 Availability......................................................................................................................50
2.40.2 When is it used?.............................................................................................................. 51
2.40.3 Description...................................................................................................................... 51
2.41 Update 3D View ........................................................................................................................... 51
2.41.1 Availability......................................................................................................................51
2.41.2 When is it used?.............................................................................................................. 52
2.41.3 Description...................................................................................................................... 52
2.42 Update Connectors ........................................................................................................................52
2.42.1 Availability......................................................................................................................52
2.42.2 When is it used?.............................................................................................................. 52
2.42.3 Description...................................................................................................................... 53
2.42.4 Remarks...........................................................................................................................53
2.43 Wind Turbine Initialization ...........................................................................................................53
2.43.1 Availability......................................................................................................................53
2.43.2 When is it used?.............................................................................................................. 54
2.43.3 Description...................................................................................................................... 54
2.43.4 Remarks...........................................................................................................................55
3 Connectors and outstanding nodes.................................................................................................................. 56
3.1 List of connectors............................................................................................................................. 56
3.2 Tower outstanding points and sensors............................................................................................. 57
3.2.1 TOWER_FOUNDATION_LINK_NODE........................................................................57
3.2.2 YAW_BEDPL_LINK_NODE.......................................................................................... 58
3.2.3 YAW_CONTROL_NODE............................................................................................... 58
3.2.4 YAW_OLNK_NODE....................................................................................................... 58
3.2.5 TOWER_FIXED_NODE..................................................................................................58
3.3 Bedplate outstanding points and sensors..........................................................................................59
3.3.1 BEDPL_MNSH_MB1_LINK_NODE..............................................................................59
3.3.2 BEDPL_MNSH_MB2_LINK_NODE..............................................................................59
3.3.3 BEDPL_GENO_iXjY_LINK_NODE.............................................................................. 59
3.3.4 YOKE_GBOX_kY_LINK_NODE................................................................................... 59
3.3.5 BEDPL_YOKES_kY_LINK_NODE............................................................................... 60
3.4 Mainshaft outstanding points and sensors........................................................................................60
3.4.1 MNSH_BEDPL_MB1_LINK_NODE..............................................................................60
3.4.2 MNSH_BEDPL_MB2_LINK_NODE..............................................................................60
3.4.3 MNSH_GBOX_LINK_NODE......................................................................................... 61
3.4.4 HUB_BLADES_LINK_NODE........................................................................................ 61
3.4.5 HUB_CENTER_NODE....................................................................................................61
3.4.6 HUB_BLADES_BLDi_LINK_NODE............................................................................. 61
3.4.7 MNSH_MB1_CONTROL_NODE................................................................................... 61
3.4.8 MNSH_MB2_CONTROL_NODE................................................................................... 62
3.5 Gearbox outstanding points and sensors.......................................................................................... 62
3.5.1 GBOX_MNSH_LINK_NODE......................................................................................... 62
3.5.2 GBOX_HSCS_LINK_NODE........................................................................................... 62
3.5.3 GBOX_YOKE_NEGY_LINK_NODE.............................................................................62
3.5.4 GBOX_YOKE_POSY_LINK_NODE..............................................................................62
3.5.5 GBOX_HSCS_BRAKE_LINK_NODE........................................................................... 63
3.6 Rotor outstanding points and sensors...............................................................................................63
3.6.1 BLADES_HUB_LINK_NODE........................................................................................ 63
3.6.2 BLADES_HUB_BLDi_LINK_NODE............................................................................. 63
3.6.3 PITCHi_CONTROL_NODE............................................................................................ 63
3.6.4 BLADEi_ROOT_LINK_NODE....................................................................................... 64
3.6.5 BLADEi_SEC_NODE_j................................................................................................... 64
3.7 HSCS outstanding points and sensors.............................................................................................. 64
3.7.1 HSCS_GBOX_LINK_NODE........................................................................................... 64
3.7.2 HSCS_GENO_LINK_NODE........................................................................................... 65
3.7.3 HSCS_GBOX_BRAKE_LINK_NODE........................................................................... 65
3.7.4 HSCS_BRAKE_CONTROL_NODE............................................................................... 65
3.7.5 HSCS_BRAKE_PRESSURE_NODE.............................................................................. 65
3.7.6 HSCS_SLIP_CONTROL_NODE.....................................................................................65
3.7.7 HSCS_ELCPL_INPUT_NODE........................................................................................65
3.8 Generator outstanding points and sensors........................................................................................ 66
3.8.1 GENO_HSCS_LINK_NODE........................................................................................... 66
3.8.2 GENO_CONTROL_NODE..............................................................................................66
3.8.3 GENO_BEDPL_iXjY_LINK_NODE.............................................................................. 66
4 SWT error Messages....................................................................................................................................... 68
4.1 Messages related to ConnectorUtil.................................................................................................. 68
4.2 Messages related to AbstractMasher................................................................................................69
4.3 Messages related to AnalyseAddedMethods....................................................................................71
4.4 Messages related to AnalysisBuilder............................................................................................... 73
4.5 Messages related to AnalyseExplorer.............................................................................................. 73
4.6 Messages related to BladeStationTableEditor..................................................................................74
4.7 Messages related to BuildAnalysesFromResults............................................................................. 74
4.8 Messages related to CatiaWorker.....................................................................................................74
4.9 Messages related to ConnectorList.................................................................................................. 75
4.10 Messages related to ConnectorUtil................................................................................................ 76
4.11 Messages related to CsvFunctionReader........................................................................................76
4.12 Messages related to CURVcombinator.......................................................................................... 77
4.13 Messages related to CURVsfrConverterV..................................................................................... 78
4.14 Messages related to CURVsfrToCrv..............................................................................................78
4.15 Messages related to CURVsfrToFlex5.......................................................................................... 79
4.16 Messages related to DataTranslator............................................................................................... 79
4.17 Messages related to DefaultAddedMethods...................................................................................80
4.18 Messages related to DeleteOrientationAction................................................................................81
4.19 Messages related to DependencyFileMethods............................................................................... 82
4.20 Messages related to FEMWPexecutionMethods............................................................................82
4.21 Messages related to FemwpSamcefWorker................................................................................... 83
4.22 Messages related to FunctionEditor............................................................................................... 84
4.23 Messages related to FunctionFileExport........................................................................................ 84
4.24 Messages related to InterpolatedCurves.........................................................................................85
4.25 Messages related to LoadcaseAddedMethods................................................................................85
4.26 Messages related to LoadcaseTranslationMethods........................................................................ 95

4.27 Messages related to MasherBuilder............................................................................................... 95
4.28 Messages related to MatrixUtilities................................................................................................96
4.29 Messages related to MonopileDisplayDriver................................................................................. 96
4.30 Messages related to OffshoreHydroCurveProcessor......................................................................97
4.31 Messages related to OffshoreLoadComputerForMecano.............................................................. 99
4.32 Messages related to OffshoreWLcomputer..................................................................................100
4.33 Messages related to PMsamcefStarterMethods............................................................................102
4.34 Messages related to PMsfieldStarter............................................................................................ 102
4.35 Messages related to S4WTaeroLoadGenerator............................................................................103
4.36 Messages related to S4WTaeroLoadGenerator_0........................................................................104
4.37 Messages related to S4WTCaesamTableComposer.....................................................................105
4.38 Messages related to S4WTcreateELA..........................................................................................106
4.39 Messages related to S4WTcreateFatigue..................................................................................... 108
4.40 Messages related to S4WTcreateRsup......................................................................................... 110
4.41 Messages related to S4WTcreateVLDurability............................................................................111
4.42 Messages related to S4WTcrvTool.............................................................................................. 112
4.43 Messages related to S4WTextremeLoadAnalysis........................................................................113
4.44 Messages related to S4WTfatigueAnalysis..................................................................................115
4.45 Messages related to S4WTinterpolFoilSections.......................................................................... 115
4.46 Messages related to S4WTliftDragMomCoeff............................................................................ 117
4.47 Messages related to S4WTlinkAnalysis.......................................................................................118
4.48 Messages related to S4WTloadGenerator.................................................................................... 118
4.49 Messages related to S4WTmodelChecker....................................................................................121
4.50 Messages related to S4WTorientationCollection......................................................................... 130
4.51 Messages related to S4WTPostProcessAnalysisV....................................................................... 130
4.52 Messages related to S4WTrsupData............................................................................................ 131
4.53 Messages related to S4WTserver................................................................................................. 134
4.54 Messages related to S4WTtransientPost...................................................................................... 134
4.55 Messages related to S4WTVLDurabilityAnalysis....................................................................... 135
4.56 Messages related to SEALibraryModel....................................................................................... 136
4.57 Messages related to SensorGlossarySelectionEditor................................................................... 137
4.58 Messages related to SFieldComponentWorker............................................................................ 137
4.59 Messages related to SfieldSamcefWorker....................................................................................139
4.60 Messages related to SKTEelaWorker.......................................................................................... 140
4.61 Messages related to SKTEresultDataExplorerV.......................................................................... 140
4.62 Messages related to SKTFcrvData............................................................................................... 140
4.63 Messages related to SKTFcsvTableWriter...................................................................................141
4.64 Messages related to SKTFfatigueWorker.................................................................................... 141
4.65 Messages related to SKTUtools................................................................................................... 142
4.66 Messages related to SKTVLExtract3dxml...................................................................................143
4.67 Messages related to SKTVLLogParser........................................................................................ 145
4.68 Messages related to SKTVLScript............................................................................................... 147
4.69 Messages related to SKTVLWorker............................................................................................ 148
4.70 Messages related to StandardHscsDisplayDriver........................................................................ 150
4.71 Messages related to StandardFunctionViewer............................................................................. 150
4.72 Messages related to StdModelsAddedMethod............................................................................. 150
4.73 Messages related to WindAddedMethods....................................................................................177
4.74 Messages related to WindGenerator............................................................................................ 179
4.75 Messages related to WindTurbineInitializationCommand...........................................................179
5 Function types............................................................................................................................................... 180
6 Predefined Frames.........................................................................................................................................185
6.1 Model frame................................................................................................................................... 185
6.2 Tower frame................................................................................................................................... 186
6.3 Bedplate frame............................................................................................................................... 187
6.4 Hub frame.......................................................................................................................................188
6.5
6.6
6.7
6.8
Rotor frame.................................................................................................................................... 189

Blade frames...................................................................................................................................190
Pitch axis frames............................................................................................................................ 191
Blade Section frames......................................................................................................................192
8 | Samcef Wind Turbines | 1 Reference Guide
1 Reference Guide
This manual provides detailed descriptions about several concepts.
It contains:
the list of all Connectors and outstanding nodes for the standard components
a description of all the error messages that can be issued by the program
a description of all the commands available in the program.
the list of all the function types you can create and use
the list of all the predefined frames used for sensor orientations
Samcef Wind Turbines | 2 SWT Command Reference | 9
2 SWT Command Reference

Lists all the available commands.
The following commands are available:
List of commands
Icon
Label
Descriptions
Edit (see page 12)

Rename (see page 12)
Select Same type (see page 13)
Adapt wind data to Wind Turbine (see page
13)
Add Engineering Object in Shared
Workspace (see page 14)
Add missing sensors (see page 15)
Open a new editor for the selection

Rename a component from the tree
Select same type
Adapt load case parameters to reflect WT
properties.
Create a new E.O. in the shared workspace
(preparing general reusable data)
Solve a compatibility issue between V2 and
V3 by adding sensors to components
Import orientations into Wind Turbine model.
Use SAMCEF Command Language
postprocessor (BACON) to debug the finite
element results (advanced feature)
Open a Windows Explorer in the result
directory of the selected analysis
Builds sensor definitions for SamcefField
components
Check the validity of completeness of the
current selection (Components, properties,
loadcases, analyses, etc)
Converts offshore loadcases to onshore and
onshore to offshore.
Create an Extreme Load or Fatigue or
Virtual.Lab durability analysis from a set of
transient analyses.
Add orientations from file (see page 16)

Bacon Postprocessor (see page 16)
Browse result files (see page 16)

Build sensor CCL file (see page 17)
Check Model (see page 17)
Convert LC (on/off-shore) (see page 20)

Create Extreme Load/Fatigue/VL Durability
Analysis (see page 21)
Create new functions (see page 23)

Create new loadcases (see page 24)
Create Super-Element Restitutions (see page
26)
Create Transient/Modal Analyses from load
cases (see page 26)
Create troubleshooting package (see page
27)
Direct WT connection help table (see page
28)
Display Bacon Model (see page 29)
Create a new function in the Shared

Workspace
Create a new loadcase in the Shared
Workspace
Create a 'Super-Element Restitution' analysis
(retrieving results within a super-element)
Create Transient or Modal Analyses from a
selection of load cases
Create a pack with all model and environment
information (hotline purpose)
Help determine connection distances for
Direct Drive components
Use SAMCEF Command Language
preprocessor (BACON) to debug the finite
element model (advanced feature)
10 | Samcef Wind Turbines | 2 SWT Command Reference
Icon
Label
Descriptions
Export Engineering Object (see page 30)
Export the selection items in a .csm file
Export... (a component) (see page 30)
Export a component into a file for reuse
Generate load cases... (see page 31)

Show/Hide object (see page 34)
Extend the selected load case by parameter

variations
Show/Hide the selected components
Import Engineering Object (see page 35)
Import selection items from a .csm file
Import results... (see page 35)
Import Transient Analysis results into the

current document (gathering results from
several documents).
Link a result folder to an existing transient
analysis
Open a window with the list of the available
connectors
Modify the list of selected components and/or
their connectivity table
Link Transient analysis (see page 37)

List connectors (see page 38)
Manage of Assembly of Components (see
page 40)
Migrate CP file... (see page 42)
Open temporary directory... (see page
43)
Pack & Go (see page 43)
Refresh orientations (see page 44)
Run Analysis (see page 44)
Run python file (see page 45)
SamcefField Postprocessing (see page
46)
SamcefField Preprocessing (see page
47)
Shaded / Wireframe (see page 48)
Show / hide 3D view labels (see page 48)

Show/Hide console (see page 49)
Super-Element Conversion (see page 49)
Swap component... (see page 50)
Update 3D View (see page 51)
Update Connectors (see page 52)
Solve a compatibility issue between V2 and

V3: translate an exported component
Open a Windows Explorer in the temporary
directory (root) linked to the model
Gather into one global package all necessary
files
Updates origin, axes directions based on
current Wind Turbine data.
Launch the selected analyses (foreground,
background or remote modes)
Launch a python file execution in the context
of SWT (reserved for maintenance problems)
Use SAMCEF Field for post-processing the
results (animation)
Display the Finite Element model in
SAMCEF Field viewer
Define the display mode of the selected
components
Shows or hides texual annotations for
supported objects in 3D view.
Toggle the visibility of the message console
Translate NASTRAN or ANSYS superelements into a SAMCEF one
Exchange a component with another of the
same type
Refresh the display
Compute the connector locations of the
selected component
Icon
Label
Descriptions
Wind Turbine Initialization (see page 53)
Creates a new wind turbine from scratch
2.1 Caesam Standard Commands

Brief description of Caesam platform commands
This document gives information about different functionalities related to the platform Caesam: Rename,
edit, Select Same Type, Dump, Attach EO to CP, etc
More detailed information can be found in standard CAESAM documentation.
2.1.1 Availability
These commands are available almost everywhere, this is different for each command. Their respective
availability will be given in their corresponding section. Most of the time you can find them in the right
click menu when item(s) is (are) selected.
2.1.2 Description
Caesam is a platform developed by Samtech on which SWT is built. Thanks to Caesam we have a
powerful and flexible interface with many default commands/possibilities. You will find here a list of
commands with their description.
2.1.2.1 Add to Group(s)
This functionality is not useful for SWT. You normally do not have to use it.
2.1.2.2 Attach EO to CP
Should normally not be used. Exceptionally, could be used to add missing properties on SE or SEA which
would be incomplete (because compatibility problem between versions, or any other particular reason).
The function links an object (property) from the shared workspace to the empty place in the SE/SEA.
2.1.2.3 Collapse all
Allow you to close the folder and each sub-folder.
You can use the shortcut CTRL+ALT-Left.
2.1.2.4 Create Group
2.1.2.5 Create New Local EO
This tool is available when selecting an EO (a property) on a SE/SEA. Its aim is to replace the currently
existing EO by a new one of the same type.
2.1.2.6 Create SEA
2.1.2.7 Delete
Delete the selected item. You can use the shortcut BACKSPACE.
Note that it is not recommended to use it on SE/SEA and that deleting an analysis does not delete the
associated directory in caesamexternalfiles.
2.1.2.8 Dump
This commands creates a Java window with all information (classes, components, etc) relative to the
selected item. This functionality is available in SDK mode only.
2.1.2.9 Edit
This command opens a new tab with the editor associated to the currently selected component. Note that
most of the SE/SEA have no specific associated editors. That command is thus useful only on the WT
(whose editor displays the connection table), analyses (whose editors display the main result property),
loadcases, and any EO from the shared workspace.
2.1.2.10 Expand all
Allow you to open the folder and each sub-folder.
You can use the shortcut CTRL+ALT-Right.
2.1.2.11 Export EO in Shared Workspace
This tool is available when selecting an local EO (a property) on a SE/SEA. It places a copy of the EO in
the shared workspace. (to be compared with Publish EO in Shared Workspace)
2.1.2.12 Memory Consumption
Gives detailed information about the memory consumption of the selected item.
2.1.2.13 Move to Group(s)
The command is available only after the creation of one group. This functionality is not useful for SWT.
You normally do not have to use it.
2.1.2.14 Printable Dump
Give information given by the Dump command in a printable format. This functionality is available in
SDK mode only.
2.1.2.15 Properties
Display the main properties of the selected object (among with the internal object name). Oriented to
developers rather than to end-users.
2.1.2.16 Publish EO in Shared Workspace
This tool is available when selecting an local EO (a property) on a SE/SEA. It places the currently selected
EO in the shared workspace, which becomes the owner. The property in the SE/SEA becomes now a link
to the EO in the shared workspace. The property in the SE/SEA is therefore no longer editable (the edition
must be done in the shared workspace). (to be compared with Export EO in Shared Workspace)
2.1.2.17 Rename
Change the name of the selected item.
2.1.2.18 Run
This is a standard CAESAM command, which is available on a selection of analyses.
It asks the user for selecting the run mode (foreground, background or remote) and lauches all analyses
accordingly to the chosen mode (see Run analyses) .
2.1.2.19 Save as XML

Save the content of the selected object into a XML file.
2.1.2.20 Select Group content
The command is available only after the creation of one group. This functionality is not useful for SWT.
You normally do not have to use it.
2.1.2.21 Select Same type
Very useful commands, which allows to extend the current selection to all objects within the tree that have
the same type. E.g., in the "Analyses" tab, where you have transient, modal and ELA analyses, if you select
one single transient analysis and then click on "Select same type", the selection you will get all transient
analyses
2.1.2.22 Unset as current Working set
This command is available only after have used a current working set. This functionality is not useful for
SWT. You normally do not have to use it.
2.1.2.23 Use as current Working set
2.2 Adapt wind data to Wind Turbine

Updates load case wind generator with information gleaned from Wind Turbine
Availability
The command is available on the Load Cases tab in the SWT perspective, see Figure 1: Adapt wind data
to Wind Turbine location within perspective tab (see page 13).
Figure 1: Adapt wind data to Wind Turbine location within perspective tab
Description
The main goal is to set a load case with information from the wind turbine. This feature provides a simple
way to use the same grid height and hub height properties of the Wind Turbine in the load case description.
To use this feature, an initialized Wind Turbine model is required. Go to the LoadCases tab and create a
new load case. Offshore load cases will take into account the water level. To retrieve information from the
Wind Turbine model, it is only necessary to click on the turbine tower icon (Figure 1: Adapt wind data
to Wind Turbine location within perspective tab (see page 13)). Wind generator information will be
updated. Although not all wind generators need grid or hub heights, the following do:
Extreme Direction Change (EDC);
Extreme Wind Shear (EWS);
Extreme Operation Gust (EOG); and
Turbulent Wind.
This feature will work only if one of Wind Generators above is selected.
2.3 Add Engineering Object in Shared Workspace

Create a new EO in the Shared Workspace
This command allows you to Create/Add a new Engineering Object (EO) in the shared workspace
(preparing general reusable data).
2.3.1 Availability
This command is available:
in the Shared Data Tab
An Engineering object is added to the shared workspace through the
button.
2.3.2 Description
When you create/add a new Engineering Object, you obtain the following dialog box:
Figure 2: Creating Engineering Object(s)
You can select different types of Engineering object. The name of the Engineering Object can also be
chosen. If you create several objects, a _ symbol is added to the name followed by the corresponding
number.
When an Engineering Object is created, it can be found in the corresponding folder depending on its type,
in the tree View (Shared Data tab).
Note: If you create a function object, it will be
created automatically in the Functions Tab.
Note: If you create a load case object, it will be
created automatically in the LoadCases Tab.
2.4 Add missing sensors

Upgrades components made with SWT V2 by adding sensors for use with SWT V3.
2.4.1 Availability
This command is available for wind turbine components (Tower, Bedplate, ...) or for the complete wind
turbine assembly which have been created in previous versions of SWT, before the use of sensors.
2.4.2 Description
In SWT versions before V3.1, individual results for an analysis were automatically selected. With this
version, you can select which results to keep and which are not needed for your particular analysis. To
do this, two things must happen. First, each component of the wind turbine must be able to inform SWT
which results can be obtained from it, and second, you must select some, all, or none of the results. This
information is then transmitted to the finite element analysis using sensors, which stores only the requested
results, reducing storage demands.
This command provides the first point by creating the collection, and in many cases can also complete the
second point by specifying a built-in file with sensor definitions for some types. In other cases you will
need to supply SWT with a sensor definition (CCL) file.
2.4.3 When and how to use

Add sensors to components which were created prior to SWT V3.1. In previous versions of the software,
components did not have sensors on them. Components without sensors will lack the Sensors entry in
the list of EOs (See Figure 3: Component without sensors (see page 15)). This command initializes the
component with sensors which can be selected to include or exclude result data. See Figure 4: Component
with sensors (see page 16) for comparison.
Sensors are attached to the component by performing the following steps:
1. Select the components coming from older (prior to SWTV3.1) models.
2. In the compatibility menu (SWT -- Advanced -- Compatibility -- Version 2.2), choose the item Add
missing sensors.
A sensor collection is added to the component if one is not found: no data will be lost with this operation.
For some built-in component types, the sensor definition file (CCL) member of the collection is filled. In
many cases, this saves you a step and you can immediately select sensor results for the analysis.
Figure 3: Component without sensors
Figure 4: Component with sensors
If the document is saved after the components are modified, this operation need be performed only once.
2.5 Add orientations from file

Import CCL-defined reference frames to Wind Turbine.
Loads orientations defined in a CCL file and appends them to the list of orientations (reference frames)
within the Wind Turbine.
Availability
This command is available through the context menu of the Orientations item in the Property View.
For more information about how to write a CCL file for your orientations, please refer to CreateFrame
CCL command.
2.6 Bacon Postprocessor

Launches the Bacon post-processing of an analysis.
This command gives access to Bacon Post-Processor on an analysis after a calculation is done.
2.6.1 Availability
in the Menu Bar > SWT > Advanced > Bacon Post-Processor
You can also used the shortcut CTRL+SHIFT-B.
Note that the finite element results are available only if you have requested to keep the SAMCEF Result
Files in the Analysis Parameters (Option property)
2.6.2 When is it used?

This command can be used only after a calculation is done, if you select the calculated Analysis.
2.6.3 Description
BACON is an advanced pre- and post-processor for SAMCEF models. For a standard post-processing of
your model, use rather the Finite-Element post-processing command. This access to BACON is reserved
for SAMCEF specialists.
2.7 Browse result files

Open a Windows Explorer in the result directory of the selected analysis
This task opens a Windows Explorer window in the result directory associated with the analysis.
2.7.1 Availability
This feature can be used when an analysis is selected in the tree.
Its is launched through item
analysis.
Browse result files, in the popup menu displayed by right-clicking on the

Use this command if you want to examine the result files associated to your analysis (usually for
debugging your run)
2.8 Build sensor CCL file

Builds sensor definitions in a CCL script for SamcefField components and DIGI controller.
Availability
The command is available for all SamcefField components and the DIGI controller via the context menu,
see Figure 5: Build sensor CCL menu (see page 17).
Figure 5: Build sensor CCL menu
Description
Generates a CCL script defining sensors for .SAI result requests in a SamcefField or DIGI component.
SWT is unaware of embedded .SAI codes within SamcefField and DIGI components, so it must be
directed to read these components to extract the required information. For SamcefField models, the .SAI
commands are converted to sensors, while in DIGI controllers, sensors are generated from the input and
output parameters. Extracting and generating sensors for the component allows you to select which results
you would like to save and helps classify them in the analysis curve results.
How to use
1. Prepare your SamcefField or DIGI component for analysis before running this command. To generate
sensors, SamcefField models must have embedded .SAI commands within the component. For
the DIGI controller, input and output parameters must be defined. Both .SAI commands and DIGI
parameters are converted to sensors in the next step.
2. Run this command to generate a CCL file definition of sensors extracted from your model. The
command attaches the generated file automatically to the SamcefField or DIGI component.
3. Select which sensor curve results to save in the Sensors editor.
After you perform the above steps, the analysis will take the selected sensors into account when storing
results. (If you forget to build the CCL file, your results might be filed incorrectly in the Results view.)
2.9 Check Model

Check the validity of completeness of the current selection (Components, properties, loadcases, analyses,
etc)
Check the coherency of the selected item(s).
2.9.1 Availability
This command is always available:
in the Model tab.
in the Shared Data tab.
in the Functions tab.
in the LoadCases tab.
in the Analyses tab.
in the Results tab.
It is launched through the Check
button.
You can also launch this function by selecting it in the pop up menu that appears when you right click on
item.

This command helps you to validate your model before to run a calculation. Messages appears in the
console. If the console is not visible, you can activate it in clicking on .
The command is also automatically launched when an analysis is run.
Notice that some checks cannot be done before the calculation! Consequently it is highly recommended to
look at the console after the end of a calculation if an error occurs.
2.9.3 Description
This commands indicates in the console general information, warning and error messages related to the
model. Information printed depends on the tab selected and also on the selected items.
In SWT, the format of the error/warning message will always be:
ERROR[classname: ID ]
Description of the error message
and
WARNING[classname: ID ]
Description of the warning message
Notice that we can also have:
PROGERROR[classname: ID ]
Description of the programming error message
Programming errors should not normally occur for the user and are not related to bad parameters in the
model.
2.9.3.1 Use in Model tab
Information displayed will change in function of the selected item(s) in the general tree. If Caesam is
selected, no test is carried out. If the Wind Turbine Assembly is selected, tests are done on each element
that composes the wind turbine. If a SEA is selected, tests are done on this SEA and on SE that composes
the SEA. If a SE is selected, tests are done only on this element.
On a SEA, we check if all SE belonging to this SEA have at least one connector. For each connection, tests
done are done to check their coherency.
The connection table is also checked: for each connection the Left Part must be at least found in upper
rows in the Right Part column (or in the first row Left part). This is mandatory to respect the assembly rule.
Connectors defined must also exist.
On a SE, checks are done to ensure parametric data are coherent. For instance, we will check on the
planetary stage if number of teeth are possible or not. By now, tests are done mainly on the Tower, the
Bedplate and the Gear Box.
Note: These checks are only made for parametric
models.
For each object we also test if it contains a field with an URL and if yes if the file is specified. The
existence of the file is also tested.
2.9.3.2 Use in Shared Data tab
selected, no test is carried out. You can check imported object but you will get less messages than if the
check is done on the real model - only URL are checked.
2.9.3.3 Use in Functions tab
selected, no test is carried out. You can check imported object but you will get less messages than if the
check is done on the real model - only URL are checked.
2.9.3.4 Use in LoadCases tab
selected, no test is carried out. Selected items must be the load cases (icon
) and not the category
(i.e. 'Design Loadcase' or 'Advanced Loadcase', etc.). There is also no effect if the folder 'EO Shared
Workspace' is selected.
Tests done are different for each load case, depending on the type (design, advanced, offshore).
It is important to know that the load case is not link to the model! Consequently we cannot on a load case
test the coherency between this load case and the wind turbine. For instance a check on an offshore load
case will not test if the Reference Node (see tab Offshore) introduced belongs or not to the turbine.
2.9.3.5 Use in Analyses tab
selected, no test is carried out. If the Analysis is selected tests will be done:
on the related load case. You will get the same messages as if you had done the check on the load case
itself in the LoadCases Tab.
to verify the coherency between the load case and the model.
If the Wind Turbine (or sub-elements) is (are) selected, effects are the same than in the Model Tab.
2.9.3.6 Use in Results tab

selected, no test is carried out. If the Analysis is selected, effects are the same than in the Analyses Tab. If
the Wind Turbine (or sub-elements) is (are) selected, effects are the same than in the Model Tab.
2.9.4 Remarks
Indications about all warning/error messages can be found in the documentation related to the error
messages.
2.10 Convert LC (on/off-shore)

Converts offshore loadcases to onshore and onshore to offshore.
2.10.1 Availability
This command is available for onshore and offshore load cases in the SWT perspective under SWT >
Convert LC (on/offshore).
2.10.2 Description
Converts one or more selected onshore load cases to offshore load cases, and offshore load cases to
onshore ones. New onshore load case names are prefixed with On_. New offshore load case names are
prefixed with Off_.
Both onshore, offshore and advanced loadcases can be selected at the same time. The conversion tool
works on one loadcase at a time and will generate the appropriate loadcases for each selected loadcase.
2.10.3 Example
The following assumes you already have one or more loadcases in your model.
Selection
In the LoadCases tab of the SWT perspective, select the loadcases you wish to convert. In Figure 6:
Loadcase selection (see page 20), two loadcases are selected: lc1 and lc2.
Figure 6: Loadcase selection
Converting loadcases
To convert the loadcases, select the command from the menu. Since lc1 is an onshore loadcase, an
offshore loadcase will be created. lc2, an offshore loadcase, will be converted to an onshore loadcase.
The result of this command will be five loadcases, the original three plus duplicates of the two selected
loadcases:
Figure 7: Loadcase conversion result
The new loadcases Off_lc1 and On_lc2, as well as the originals are shown in Figure 7: Loadcase
conversion result (see page 20).
2.11 Create Extreme Load/Fatigue/VL Durability Analysis

Create a Fatigue / Extreme Analysis / VL Durability from a set of transient ones
These functions allow you to build an Extreme Load Analysis, build a Fatigue Analysis or build a VL
Durability Analysis.
2.11.1 Availability
These functions are available:
An Extreme Load Analysis is created through the
A Fatigue Analysis is created through the
button.
button.
A VL Durability Analysis is created through the
button.
You can also create an analysis in the right click menu when an item is selected.
To create an Extreme Load Analysis, at least one of the following items must be selected:
Caesam
One or several Transient Analysis
One or several Extreme Load Analysis
To create a Fatigue Analysis, at least one of the following items must be selected:
Caesam
To create a VL Durability Analysis, at least one of the following items must be selected:
Caesam
Note: These function buttons are not available if an
unauthorised item is selected - for instance if you
have a Modal Analysis in the selection.
2.11.2 Description
2.11.2.1 Build an Extreme Load Analysis
If you select multiple Transient Analyses and/or Extreme Load Analyses and click on the
button, an
Extreme Load Analysis (ELA) will be created. This ELA will be related to all the selected items. You can
check the list in the parameter Analysis Data in the Tab EO of the analysis. In this list, you can also see 3
parameters:
factSafety: this a security coefficient. In the related load case of the Transient Analysis, you can select a
value for this coefficient - see Tab Type and check the box Ultimate Loadcase. Parameter factsafety will
have this value if the check box is selected. If not, you will have 1.5 by default if the related analysis is
a Transient analysis and 1.0 if the related analysis is an ELA.
startTime: if the related load case of the Transient Analysis is a Design load case (offshore or not), the
value by default will be the same than the one defined in the tab Design Loadcase in LC Start Time
field. If not, the value by default is 0.
endTime: by default the value is 0. In that case, it means calculation is done until the end.
If you select in the tree the root Caesam an Extreme Load Analysis will be created with only some
Transient Analysis: selected ones are those which the related load case has the Ultimate Loadcase check
box selected - in the tab Miscellaneous.
Note: It is also possible to select the root Caesam
and several Transient Analysis and/or Extreme Load
Analysis to create an Extreme Load Analysis.
2.11.2.2 Build a Fatigue Analysis
If you select multiple Transient Analyses and click on the button, a Fatigue Analysis will be created.
This Fatigue Analysis will be related to all the selected items. You can check the list in the parameter
Analyses Data in the Tab EO of the analysis. In this list, you can also see 4 parameters:
Start Time: Default value is 0 (s).
End Time: Default value is 5000 (s).
Service Time: Default value is 2.592e6 (s).
Number of occurrence: Default value is 500.
If you select in the tree the root Caesam a Fatigue Analysis will be created with only some Transient
Analysis: selected ones are those which the related load case has the Fatigue Loadcase check box selected
- in the tab Miscellaneous.
and several Transient Analysis to create a Fatigue
Analysis.
2.11.2.3 Build a Virtual.Lab Durability Analysis
If you select multiple Transient Analyses and click on the
button, a VL Durability Analysis will be
created. This VL Durability Analysis will be related to all the selected items. You can check the list in the
parameter Analyses Data in the Tab EO of the analysis. In this list, you can also see 7 parameters:
Durability Analysis Name: Default value is Durability_Analysis_index.
Load Function Set Name: Default value is Load_Function_Set_index.
Start Time: Default value is 0 (s).
End Time: Default value is 5000 (s).
Service Time: Default value is 2.592e6 (s).
Number of occurrence: Default value is 500.
Reference: No default value.
If you select in the tree the root Caesam a VL Durability Analysis will be created with only some Transient
Analysis: selected ones are those which the related load case has the VL Durability Loadcase check box
selected - in the tab Miscellaneous.
and several Transient Analysis to create a VL
Durability Analysis.
2.12 Create new functions

Create a new functioon in the Shared WorkSpace.
This command allows you to create a new function in the Shared WorkSpace.
2.12.1 Availability
in the Functions Tab
in the menu bar SWT Function Manager
with the shortcut CTRL-F (which launches the Function Manager)
A function is created through the
button.
2.12.2 Description
If you use the Function Manager, you get the following window:
Figure 8: Creating function(s)
This manager allows you to create, delete, import or export functions. When you create a new load
function (Button 'New function'), you obtain the following dialog box:
Figure 9: Creating function(s)
Five different function types can be created:
Function defined by points
Function defined in a CSV file
Constant function
Analytic function
Step function
The name of the function can also be chosen. If you create several functions, a _ symbol is added to the
name followed by the corresponding number.
Note: You can directly get the dialog box Creating
function(s)' if you click on the button in the
Functions Tab.
2.13 Create new loadcases

Create a new Load Case
This command allows you to create a load case in the Shared WorkSpace.
2.13.1 Availability
in the LoadCases Tab
in the menu bar
SWT
Load case Manager
with the shortcut CTRL-L (which launches the Load case Manager)
A load case is created through the
button.
2.13.2 Description
If you use the Load Case Manager, you get the following window:
Figure 10: Creating load case(s)
This manager allows you to create, delete, import or export load cases. When you create a new load case
(Button 'New load case'), you obtain the following dialog box:
Four different load cases types can be created:

a Design Load case
an Advanced Load case
an Offshore Design Load case
an Offshore Advanced Load case
The name of the load case can also be chosen. If you create several load cases, a _ symbol is added to the
name followed by the corresponding number.
When a load case is created, it can be found in the corresponding folder depending on its type, in the tree
View (LoadCases tab).
Note: You can directly get the dialog box 'Creating

load case(s)' if you click on the button in the
LoadCases Tab.
2.14 Create Super-Element Restitutions

Create a Super-Element Restitution Analysis from a transient one
2.14.1 Availability
This function is available:
To create a Super-Element Restitution Analysis, you must select a Transient Analysis and
press the
button in the tab toolbar
or select the same too in the right click menu.

Note: These function buttons are not available if an
unauthorised item is selected - for instance if you
have selected a Modal Analysis
2.14.2 Description
2.14.2.1 Build a Super-Element Restitution Analysis
If you select a Transient Analysis and click on the
button, a Super-Element Restitution Analysis will
be created. This Super-Element Restitution Analysis will be related to the selected item. You can check its
name in the parameter Analysis Data in the Tab EO of the analysis.
2.15 Create Transient/Modal Analyses from load cases

Create Transient and Modal analyses from a selection of load cases.
These functions allow you to build a Transient Analysis or build a Modal Analysis.
2.15.1 Availability
These functions are available:
in the LoadCases tab.
A Transient Analysis is created through the
A Modal Analysis is created through the
button.
button.
You can also create an analysis in the right click menu.

To create a Transient or a Modal Analysis, at least one load case must be selected.
Note: These function buttons are not available if
an unauthorised item is selected - for instance if
you have the Folder 'EO Shared Workspace' in the

selection.
2.15.2 Description
2.15.2.1 Build a Transient Analysis
If you select x load cases and click on the button, x Transient Analysis will be created. The Transient
Analysis created contains several defaults parameters - see tab Parameters of the Analysis, field Options.
Three different categories can be found:
Options
Curves
Result Files
For each parameter, the default values can be changed in the main Tool bar Edit Preferences
Analysis.
Note: If you change values in Preferences, it will not
affect Transient Analysis already created.
2.15.2.2 Build a Modal Analysis
If you select x load cases and click on the button, x Modal Analysis will be created. The Modal Analysis
created contains several defaults parameters - see tab Parameters of the Analysis, field Options. Two
different categories can be found:
Options
Result Files
For each parameter, the default values can be changed in the main Tool bar Edit Preferences
Analysis.
Note: If you change values in Preferences, it will not
affect Modal Analysis already created.
2.16 Create troubleshooting package

Describes how to use the Caesam command which collects basic information about the SWT running
environment and SWT installation including log files and directory listings which may aid in
troubleshooting any problems encountered.
2.16.1 Availability
This command is available any time.
2.16.2 Description
This command can be used when requested by Samtech to collect some basic information about your
computing environment. This includes environment variables, the SWT installation, Caesam's log file and
preferences. The collected data helps Samtech personnel determine the source of any problems you may be
having.

This command should be used only when you are having problems with SWT and have been directed to
run this command.
To use this command, select it in the menu.
Figure 12: Command location in menu
Once started, this may take some time to collect the necessary information. During this time Caesam
will be unresponsive. When the required information has been collected, Caesam will show a message
specifying where the package has been created.
Figure 13: File gathering result
Like in Figure 13: File gathering result (see page 28), the name of the file will be something like
Samtech_Hotline_YYYY-MM-DD_HHhmm.zip where YYYY-MM-DD_HHhmm represents the date
and time at which the file was created.
Once the zip file is created, it can be emailed to Samtech if it is small. If the file is larger, please contact
Samtech for specific instructions on how to transfer the file.
2.17 Direct WT connection help table

Tool to help you define distances between components for Direct Drive models.
Availability
The command helps you determine where distance errors occur in the connectivity of your Wind Turbine
direct drive component. It is available for the Direct Drive hub, frame and generator components.
When to use
Particular to the direct drive component, the generator and main bearings may or may not be present. This
variability influences the connectors and connection definitions, complicating the process of defining
distances.
Use this command to display a window showing different measurements for the hub, frame and generator
components which impact the inter-component connections. The displayed distances, measured in different
axes, make it easier to correct geometric problems which are otherwise difficult to fix due to the presence
or lack of some bearings.
Description
In the pop-up window, SWT presents a table, Figure 14: Direct Drive WT connectors table (sample) (see
page 29) where:
Columns are associated with horizontal positions
Rows are associated with the following component reference frames:
Frame (positions w.r.t.1 the frame origin);

Frame (positions w.r.t. the hub origin);
Hub (positions w.r.t. the hub origin);
Generator (positions w.r.t. the hub origin);
Generator (positions w.r.t. the generator origin).
Figure 14: Direct Drive WT connectors table (sample)
The table considers two standard assembling scenarios:

Case with MB1:
Frame and hub aligned on MB1.
Hub and generator aligned at the generator coupling.
Case without MB1:
Frame and generator aligned on GB1.
Generator and hub aligned at the generator coupling.
2.18 Display Bacon Model

Display the BACON model of the selected item.
This command creates the Bacon model of the selected item.
2.18.1 Availability
in the Menu Bar > SWT > Advanced > Display Bacon model
You can also used the shortcut CTRL-B. An SEA must be selected before using the command.

It can be used if you want to create the Bacon Model and check it before to run the calculation.
2.18.3 Description
This commands creates the Bacon model and open it with Bacon. You can use it on the whole wind turbine
assembly or on another SEA (not on a SE). When the Bacon model will be built six new windows will
appear: one with the model representation (in the simplified Bacon interface) and 5 other dialog windows.
If you want to close your Bacon model click on the window 'SAMCEF for MECHANICS' > File... > Quit
(in the new dialog box). This will automatically close all BACON windows.
Once the model is created you can open the folder WorkingDirectory/FileName.tmp/pbank/
Wind_Turbine_Assembly/samcef/. This folder contains the data files related to your model:
main_full_ba.dat, main.spy, etc. This is a way to check your data without running an analysis.
For further information about functionalities reefer to the BACON documentation.
Note: When Bacon is opened you cannot have
access to your model through SWT. Close first
Bacon if you want to modify your model.
2.19 Export Engineering Object

Export and EO from the Shared Workspace
This command allows you to Export an Engineering Object (EO) from the shared workspace.
2.19.1 Availability
An Engineering object is exported from the shared workspace through the
button.
2.19.2 Description
The Export button allow you to save an Engineering Object - file extension is csm. We remind you that
Functions and load cases are also some Engineering objects. That explains why we find also the command
in their respective tab. Exported objects can be imported with the Import Engineering Object command.
This command is helpful to save functions, load cases or other elements that you often have to use.
2.20 Export... (a component)

Save a component for use in other wind turbine models.
This command enables you to export a Wind Turbine component for use in another model.
2.20.1 Availability
A component can be exported using the context menu of the component, see Figure 15: Export component
location in context menu (see page 31).
Figure 15: Export component location in context menu

The export feature can be used to save a component for later use in another Caesam document.
2.20.3 Description
Exports a wind turbine component to a file. You will be prompted for a file name and location in which to
save the file.
2.20.4 Remarks
This comment is intimely related to the Wind Turbine Initialization or the Management of Wind Turbine
components ones. Indeed, the files you export using this command will be available in those ones. You
can in that way prepare components and reuse them in other models.
It is advised to rename your component before saving it, in order to be able to distinguish it from the
original one when you try to reuse it.
2.21 Generate load cases...

Command for automatically generating loadcases from a single existing one.
Generate many load cases according to simple rules from an existing load case.
2.21.1 Availability
This feature is available when a load case is selected.
2.21.2 Description
This feature provides a way of generating load cases. Various parameters of the load case are available for
parameterization. One or more of these parameters can be selected for modification. The generator varies
the parameters independently, creating a load case each time.
2.21.2.1 Basics
This command is activated by selecting a load case as a starting point for the generation. This is done by
clicking on a load case in the tree:
Figure 16: Selecting a load case for parameterization
Once the icon is clicked, a window opens to control the generation of load cases.
Figure 17: Load case generation window, with some important features highlighted.
2.21.2.1.1 Naming pattern

Different controls are presented in the dialog window to modify the names of the generated load cases
and what should be parameterized. The naming pattern may contain wildcard characters that are replaced
during load case generation with the value of a parameter.
A specific parameter can be referenced in the naming pattern by referring to its number (circled in red in
the diagram above). Figure 16: Selecting a load case for parameterization (see page 32)For example,
to refer to the Wind speed (y) parameter, a $2 would be used since this is the second parameter.
Special cases
Using "original" name in generated load cases
The name of the starting load case can be used as part of the generated load case names by specifying
$NAME wherever the original name should appear.
Using $ in name
A $ which should appear in the name of the generated load cases should be written as $$.
2.21.2.1.2 Activating parameters
One or more parameters must be enabled before any analyses can be generated. Which values can be
parameterized depends on the type of load case, and may vary from one type of load case to another.
The first task is to activate one or more parameters. In the figure above, Wind speed (x) has been
activated. Activating a parameter enables you to specify the range for the parameter. For numeric
quantities, minimum, maximum and step size values must be specified. For other values, a choice is
available (eg. Yes/No).
Numeric quantity parameters
Numeric values can be specified by using the minimum, maximum and step entries:
Minimum
Lowest value the load case parameter takes.
Maximum
Largest value the load case parameter takes.

The parameter will never take a value larger
than this value.
Note: In some cases, the maximum cannot be
reached from the minimum using the specified
step. In this case, the maximum used value for
the parameter is the largest which is less than
the specified value.
Step
Size of the step used to generate values. For

example, the series 1, 5, 9 has a step of 2.
The only requirement on the minimum, maximum and step is that it must be possible to reach the
maximum by adding one or more steps to the minimum value.
Figure 18: Editing a numeric quantity
Figure 19: Previewing generated values
Flag-style parameters
A flag-style value is one which can be used to represent the state of an object. Though only one flag is used
in each load case, multiple values can be selected. Each value will be represented in the generated load
cases for each of the (other) parameter values.
A flag Pitch 1 error? is shown in Figure 20: Editing a flag-style parameter value (see page 33),
which can be one of two values: Yes and No. For the purpose of parameterization, both values have
been selected, effectively doubling the number of load cases generated: half with Yes, half with No
errors.
Figure 20: Editing a flag-style parameter value
2.21.3 Remarks
Caution: Caution should be used when generating
load cases because with very few parameters it is
possible to generate a very large number of load
cases.
For example, varying the wind speed (x) of a load case from 10 m/s to 50 m/s with steps of 5
m/s will generate 9 load cases. Now we add a parameter to vary the wind speed (y). Let the wind
speed (y) vary from 0 m/s to 30 m/s. Instead of generating 9 load cases, 63 load cases will be
generated.
2.22 Show/Hide object

Switches the visibility of objects
These commands allow you to show/hide the tree components (SE or SEA) in the 3D view.
2.22.1 Availability
Show and Hide components are available in the pop-up menus associated to the SE or to the SEA (menu
obtained with a right click on a selection). You can use multi-selection to show/hide several objects
2.22.2 When is it used

These commands are used to modify the visibility of the components.
Sometimes it is interesting to hide components in order to better see other ones (and obviously to show
them later to get them visible again)
Sometimes, components have been hidden by the system, and the user wants to make them visible.
This is the case e;g. when SAMCEF Field or super-element components are initialized without
implementation (i.e. without any valid file selection). In that case, the system switch their visibility to
hidden. After having selected a valid file, it is also necessary to ask CAESAM ti Show them in order to
get them in the 3D View.
2.22.3 Description
It is worth noticing that in fact, 2 distinct sets of commands exist in the pop-up menu:
Commands associated to the basic displayable object (i.e. the objects to which a display feature is
really defined in CAESAM). In SWT, display features are always associated to SE. The corresponding
Hide and Show commands are presented close to the top of the pop-up menu, without any icon. Since
CAESAM directly manage the display of these entities, it proposes only a relevant choice (Hide only
for visible SE's, Show only for hidden SE's, both for a mixed selection)
Commands associated to compound objects. SWT has added commands to operate on such more
global components (namely, the WT components, or the WT itself). The corresponding Hide and
Show commands are presented deeper in the popup menu with an icon:
for Show and
for Hide.
The availability of these commands cannot be tune by the selection state. They are therefore always
proposed in the pop-up menu associated to a SEA selection. Note that the implementation simply shows
or hides all SE's found under the selected SEA's.
Note:
Note also that the Display menu (in the menu bar)
contains items, which determine what is visible in
the 3D view. Since this menu is a CAESAM one, it
always acts on SE's (objects holding the drawings):
"Show All" and a "Hide All" show or hide all SE's
"Fix Selection in display" and "Remove selection
from display" modify the visibility to keep only
or to hide the selected SE's (and NOT the SE's
belonging to the selected SEA) and freeze it till

the next action modifying the display.
When "Show current selection" or "Hide current
selection" are active, only the selected SE's (and
NOT the SE's belonging to the selected SEA) are
displayed. The display changes according to the
selection.
2.23 Import Engineering Object

Imports an EO into the Shared Workspace.
This command allows you to Import an Engineering Object (EO) into the shared workspace.
2.23.1 Availability
An Engineering object is imported into the shared workspace through the
button.
2.23.2 Description
The Import button allow you to import a previously saved Engineering Object - file extension is csm. We
remind you that Functions and load cases are also some Engineering objects. That explains why we find
also the command in their respective tab.
Note: If you import an EO which is not a Function
(or a load case) in the tab Functions (or LoadCases)
the object will still be imported in the Shared Data
tab.
2.24 Import results...

Explanation of how to import results which do not have an analysis
2.24.1 What it does

This command imports results into a Caesam document by creating new (transient) analyses and
associating the results with it. This task can be performed when you wish to import just the results of
an analysis for further processing, either for a fatigue, VL Durability or extreme load analysis. Another
possible use would be to collect into a single Caesam document results from a number of different
documents residing on different computers. This command then serves to centralize results evaluated on
other computers to a single one for post-processing.
2.24.2 How to use

The command is accessed via the Import results... item on the Advanced sub-menu of the SWT
main menu, see Figure 21: Import analysis results dialog (see page 36).
Figure 21: Import analysis results dialog
The import process examines the analysis result directories, using the information found to construct the
results section of an analysis.2 After creating analyses and importing the results, a message box (Figure 22:
Importing results messages (see page 36)) shows the names of the analyses created.
Figure 22: Importing results messages
A CSV file is required as input. This file is used to specify the locations of the result directories. (More
than one set of results can be imported at a time.) By default, the task attempts to determine the name of
the load case.3 If you would like to rename the analysis when importing, add a name after the analysis
directory path.
2.24.3 The CSV file

The CSV file contains one result directory per line, optionally followed by an analysis name separated by
a ; (semi-colon) delimiter. An example is shown below (see Figure 23: CSV sample content (see page
36)).
c:\SamWork\Sessions\wtmodel.caesamexternalfiles\const_wind_Transient_Analysis
c:\SamWork\Other\sample.caesamexternalfiles
\loadcase_Transient_Analysis; Variable wind Transient analysis
Figure 23: CSV sample content
The first line in the example shows the simple import of a result directory. The second line shows how an
analysis can be renamed during the import process.
A few basic rules are used when reading and writing the CSV files:
Empty lines are ignored
Leading and trailing whitespace is removed. So
c:\Temp\LC
2
3
abc
The results do not constitute a complete analysis. It should not be launched after it is imported since it lacks
necessary input data.
This depends on the analysis neutral file in the result directory, which contains the name of the load case,
under normal conditions.
would be interpreted the same as

c:\Temp\LC;abc
2.25 Link Transient analysis

Link a selected analysis with an analysis that has already been calculated.
Link the selected Analysis to results of an already calculated analysis
2.25.1 Availability
in theAnalyses tab.
The 'Link Analysis' is launched through the
button. This command is run on an Transient Analysis and
is thus available only when a Transient Analysis is selected.

You can use this command in two different cases:
You can have run analyses of the same model in different files. You can create a new model with
'empty' analyses and link them to the calculated analyses. Then you can use all these analyses to do a
fatigue analysis. In other words it is a way to do a fatigue, a VL Durability or an extreme load analysis
based on analyses belonging to different SWT models.
You have run one (or more analyses) and the calculation has been aborted before the end. When a
session crashes, connection to already calculated results is lost. With this command you can now link
your analysis to the folder where calculation was done and thus recover already calculated results.
2.25.3 Description
If an Analysis is selected, you can use the Link Analysis command. The main goal is to link the selected
analysis to an already calculated one. You can thus have in one model analyses that have been run in
several different models. Consequently you can do an extreme load analysis,a fatigue analysis or a VL
Durability analysis on these different analyses. When you click on the button, the following dialog box
appears.
You then have the possibility to select a folder that must contain results of an analysis. If the folder does
not contain the results nothing happens. If results are available they will be loaded in the model and they
can be displayed in the interface as if they were the results of an 'normal' run.
Notice that after a link, it is not possible to directly re-run the analysis - with its original data,
i.e. load case etc. To run the analysis you must select it Go in the tab Parameters Select
CaesamStd_StepProcessParameter Activate the check boxes S4WTWindTurbineOP and
S4WTtransientPost. If you run the analysis, the linked analysis will not be deleted. For example, you have
an analysis named A (in a folder 'C:/Adir') and you link it to an analysis named B (its results are in the
folder 'C:/Bdir'). If you run the Analysis A, new results obtained will be saved in the folder 'C:/Adir' and
results in the folder 'C:/Bdir' will not be deleted.
You can also link the analysis to its own result path. This can be done when the analysis run met a problem
and was not able to be terminated. In that case you can still try to link the analysis to the results to get parts
of the results. This is another interest of this command.
Note: Important remark: if you want to postprocess the linked analysis you need a file named
'sensorinfo.csm' that must be in the caesam external
files folder of the original Transient Analysis. This
file contains the information related to the sensors
of the initial Transient Analysis. This file is not
generated by default in the result folder. To create it
open the czm where the initial Transient Analysis is
located and open the ccl script 'sensorInfoExport.ccl'
- you can find it in the CCL folder at the root of
SWT. Edit in the script the name of the Transient
Analysis to correspond to the analysis you want
to export. Run the script to generate the file. After
that the command 'Link Transient Analysis' can be
used on another analysis to link it towards this initial
Transient Analysis.
Note: If the command is used related to an analysis
that does not have the file 'sensorinfo.csm' a warning
is given to the user. The command will work but you
cannot use this analysis to create a Fatigue/ELA/VL
Durability analysis.
2.26 List connectors

Displays a list of the Wind Turbine connectors in the model.
Allows you to view the list of connectors present in the model in a separate window.
2.26.1 Availability
This command is available at any time. It can be accessed through SWT Server > List connectors in the
menu.
2.26.2 Description
Some Wind Turbine components and load cases allow for arbitrary conditions to be set on the finite
element model. For example, in the standard design load case you can assign additional mass or assign
loads to arbitrary nodes. SWT can use the connector name to place the load or mass in the finite element
model.
You can use this command to help you specify the location for an applied load or additional mass. Figure
24: List connectors window example (see page 39) shows an example listing of the connectors in the
model.
Figure 24: List connectors window example
There are different locations in SWT where the names of connectors are entered as free text. One location
is in the Design load case. For example, assume you wanted to add an additional load at the connector
YAW_BEDPL_LINK_NODE, but were not sure exactly how it was written. Using the menu you call up this
command to see the list of connectors. Finding the connector name, you highlight it with your mouse, then
copy it to the clipboard using Ctrl+C. The connector name can now be pasted (Ctrl+V) into the User
Loads editor.
Figure 25: Use of connector name in load case
Note: When using the copy/paste mechanism to

obtain the connector name, a space is often pasted
with the connector name. This must be removed.
2.27 Manage of Assembly of Components

Adds, removes or modifies components of the wind turbine.
This command enables you to add, remove or modify components making up a Wind Turbine model.
2.27.1 Availability
This feature is available when the wind turbine is selected. The feature is activated using either the tool bar
or context menu, see Figure 26: Wind turbine component management location (see page 40).
Figure 26: Wind turbine component management location

The purpose of this feature is to modify the composition of the wind turbine by adding or removing
components from the wind turbine. Similar to the Wind Turbine Initialization (see page 53),
components of each type are proposed which can be selected to replace the current item.
2.27.3 Description
Running this feature will display a window similar to that of Figure 27: Manage components window (see
page 41).
Figure 27: Manage components window
The window is composed of a few tool bar buttons, a main box split into two panes and a drop down menu.
Tool bar
This feature allows you to add a wind turbine
Add/remove wind turbine component
component which is not a standard type of
component (tower, bedplate, gearbox, etc).
The following types of components can be
added:
Samcef Field models
Super elements
or you can import a saved component.
Add a new component by clicking on the
button. A component can be removed by
clicking the
Folder selection for component scanning
button.
The
button permits you to manage the
directories which SWT uses for locating your
components. Click this button will open the
Figure 36: Wind Turbine component paths
dialog (see page 55) window.
Wind turbine components

The window is separated into a left and right pane. A number of things are apparent in the left pane. First,
components which are used have a white background. That which is selected has a blue background.
Components which are not used have an orange background.
In the right pane, we see the list of available gearboxes (in this example). The gearbox currently used is has
a
icon and (current) is appended to its name.
Connectivity schema
You can also change the default connectivity schema used for the wind turbine on this screen.
For more information on Connections refer to the SWT User Guide.

2.27.3.1 User families
The Export... (a component) (see page 30) command explains how you can save a component that
has been built and modified. This enables you to have directories, which can be considered as sets of user
components which can be scanned by SWT in order to propose the components for selection.
The
button gives access to a panel, in which the user can define the directories to scan.
Figure 28: Wind Turbine component paths dialog
In the panel, some directories can be added. To be taken into account, directories have also to be selected
(check box). The system makes it possible to avoid taking directories into account, without having to
remove them from the list (just by deselecting the check box).
If you Save the status, it will be stored in your preferences, so that the whole list will be automatically
scanned when opening the WT initialization panel.
If you want modifications in the directories to be taken into account after a modification, you have to
rescan all directories, by using the
button.
2.27.4 Remarks
Note: Changes in this window are immediate.
Clicking on components selects them automatically
for use in the wind turbine. The window can simply
be closed when you are happy with your changes.
2.28 Migrate CP file...

Transforms a component saved in SWTV2.2 for use in the current version.
2.28.1 Availability
Always available through the menu SWT > Advanced > Compatibility > Version 2.2 > Migrate CP
file... , this command modifies component files and does not depend on the current model.
2.28.2 Description
For components saved or exported in Version 2.2 of SWT, this task loads the file and converts it for use
in this version of the software. Since this process modifies the file, a back-up of your file is made before
initiating the migration process. This back-up file is saved in the same directory as the original file, but
with __CSMV5 appended to the file name.

Migrate a wind turbine component from version 2.2 of the software for use with the current version. Since
this modifies the file, this operation need only be performed once per file.
Activating this process via the menu listed above will present you with an input window requesting a file
name, see Figure 29: Prompt for component file to migrate. (see page 43). Using the button, navigate
to the file requiring migration, then click OK to start or Cancel to abandon the process.
Figure 29: Prompt for component file to migrate.
2.29 Open temporary directory...

Opens the current document's temporary directory in a file browser.
This command opens a file browser to the temporary directory. This directory is used for temporary
storage while Caesam is running for various tasks and analyses.
2.30 Pack & Go

Packages a Caesam document for transfer to another computer.
2.30.1 Availability
Always available. Command does not depend on any currently selected object.
Accessed via the SWT > Advanced menu entry with the
icon.
2.30.2 Description
Packages the Caesam document for transfer to another computer. Similar to a "Save As...", a copy of the
document is saved, including reference files. SamcefField, super-element and controller DLLs are external
reference files. As opposed to simply saving the document, packaging copies any files which are on your
computer which are not part of SWT into a new Document.caesamexternalfiles directory. This
directory, along with the Document.czm file, are saved in the directory you specify.
The caesamexternalfiles directory and czm file are all that you need to use the Caesam document
on another computer.
2.30.3 When to use

Use this task any time you transfer a Caesam document to another computer.
2.30.4 Remarks
Whether using the
or filling in the path manually, the path should specify a directory which does
not exist.
The directory name should be specified in a url format. This formatting is performed automatically
when browsing for a file:
Figure 30: Dialog box with URL path
The directory name (MyPackNGoDocument in the figure Figure 30: Dialog box with URL path (see
page 44)) will be used for the new Caesam document name and the external files directory. In this
case:
MyPackNGoDocument.czm
MyPackNGoDocument.caesamexternalfiles
2.31 Refresh orientations

Reloads the available orientations for the Wind Turbine
Availability
The command is available in the pop-up menu of the Wind Turbine Orientations in the Property View as
well as directly in the Orientations editor via the
button.
In some cases, an error will occur when refreshing using the button4. This is a known limitation of the
software. When this occurs, the pop-up menu of the Orientations is the preferred manner to refresh the
orientations.
Description
This command reconstructs the orientations attached to the Wind Turbine, updating the origin and axes
directions based on information derived from the current Wind Turbine model.
Under normal conditions, this command is always safe. Previously imported, and modifications made to
the orientations are preserved during the updating process.
2.32 Run Analysis

Starts the processing of selected analyses
This command allows you to launch the selected analyses (foreground, background or remote modes).
2.32.1 Availability
The error message appears in the console as:
in the Analyses Tab

in the main tool bar
in the menu bar
Analysis
Run analysis
The run analysis is launched through the button. The button is available if you have at least one analysis
selected. You can also run a calculation in the right click menu when an analysis is selected.
2.32.2 Description
This command is used to run calculation on selected analysis. When you run an analysis, you get the
following dialog box:
You have three possibilities (modes) to run the calculation:

Foreground mode
Background mode
Job mode
If the Job mode is selected, you have the possibility to change the number of jobs:
Figure 32: Job mode parameters
The job mode is used to submit calculation on several computers (must be configured with Condor). It is
advised to put as many jobs as you have analysis. There is no interest to use it with only 1 job.
Note: You do not have to change anything in other
parameters.
Before to launch the calculation, SWT creates automatically a global Bacon file which is the assembly
of each element of your model. Then the calculation is run and results data are created. If an error occurs
during the process the console windows appears with the corresponding error.
2.33 Run python file

Executes a python file on the current model.
This task can be used to launch a python file on the current SWT model.
2.33.1 Availability
This feature can be launched through the imenus SWT / Advanced /
Run Python File .

This feature has to be used only on recommendation of Samtech hotline. It gives indeed the possibility to
run specific code, which would be helpful e.g. to examine or even repair some models in case of problem.
2.33.3 Description
According to what has to be done, the task can be launched with or without selection in the tree.
When launched, it will display an input panel, where you will select the python file to run.
When you click on the OK button, the python file is executed.
2.33.4 Remarks
Use this feature only on recommandation of the hotline.
2.34 SamcefField Postprocessing

Post processes a selected item.
Launch the Post-processing on the selected item.
2.34.1 Availability
in theAnalyses tab.
in the Results tab.
in the menu bar SWT SamcefField Post Processing
when a transient or a modal analysis is selected.
The Post-processing is launched through the
button.
Note that these finite element results are available only if you have requested to keep the SAMCEF Field
Animation Files in the Analysis Parameters (Option property)

This command is used after a calculation. It allows you to see and eventually edit your selected item in
Samcef Field (as for the Pre-Processing command) but the main goal is to have access to detailed results in
SamcefField (and particularly, to make animations).
2.34.3 Description
2.34.3.1 Use in Analyses or Results tabs
When running the post-processing of an analysis, you will have an access to the Finite Element model of
your Wind Turbine, and to the F.E. results for the selected analysis.
Note: It is not possible to do the Post-Processing on
a multi-selection. It can be done only on one single
Analysis.
Note: See Pre-Processing command for the editing
possibilities in SamcefField mode.
The first time the Post-processing button is activated on an analysis, the SamcefField model is created and
saved in the result folder. Afterwards, as long as you do not run your analysis again, this file is saved in the
directory and all modifications you make and save will be kept.
Initially, just after its creation, nothing is displayed in the SamcefField Interface. You can go in Display
Show All for a complete display or select yourself the items of interest and select Show in the popup
menu. These modification in the display can be saved like any other modification by saving your SAMCEF
Field document. Consequently if you launch again the Post-processing you will be able to see these
modifications. One interest is for instance to add a background to your model after a calculation: during a
presentation of your results if you show the Post-processing this background will be visible. Furthermore
the SamcefField model is already created and then must no be re-built - which is an operation that can take
time.
2.35 SamcefField Preprocessing

Launches the pre-processing of a selected item
Launch the Pre-processing on the selected item.
2.35.1 Availability
in the Model tab.
in theAnalyses tab.
in the menu bar SWT SamcefField Pre Processing
The Pre-processing is launched through the button.

This command allows you to see and eventually edit (only for Samcef field element) your selected item in
Samcef Field.
2.35.3 Description
2.35.3.1 Use in Model tab
If Caesam is selected, it not possible to do the Pre-processing. If the Wind Turbine Assembly is selected,
you will see all your model in SamcefField. If a SEA is selected, you will see this SEA in SamcefField but
it is not possible to see a single SE in SamcefField.
Note: It is not possible to do the Pre-Processing on
a multi-selection. It can be done only on one SEA,
even if the 'Wind Turbine Assembly' is finally a set
of SEA.
Behaviour of the button is different in function of the selected item. If the item is a parametric model
Bacon files are created and assembled to get a global Bacon model. This model is then opened by
SamcefField. Initially nothing is displayed in the SamcefField Interface, you must go in Display
Show All. If you change something in the model in SamcefField, it will not be saved! Indeed before the
calculation the global bacon model is built again, but this 'building' is based on parametric values defined,
and not on modification(s) you could have done in SamcefField!
With Bacon elements, the behaviour is the same: changes in the Pre-processing environment has no impact
on the calculation.
If you are working directly on SamcefField elements, you can edit your model with this Pre-proccessing
button.
If an Analysis is selected, you can do the Pre-processing: you will have your whole model in SamcefField.
Inside the analysis, you can also select the Wind Turbine Assembly or SEA and do the Pre-Processing - as
it is done in the Model tab.
Note: It is not possible to do the Pre-Processing on
a multi-selection. It can be done only on the Analysis
or a SEA
2.36 Shaded / Wireframe

Switches between shaded and wireframe views
These commands allow you to change the view of the selected item(s) in shaded/wireframe mode.
2.36.1 Availability
These commands are always available:
in the field Options Display on each SE. You can choose between following modes: Exact - Quick Shaded - Wireframe
in the Model tab in the right click menu if you select an item.
The Wireframe mode is launched through the Wireframe button that can be found in the right click
menu when SEA or SE is (are) selected. You can also used the shortcut CTRL-W.
The Shaded mode is launched through the Shaded button that can be found in the right click menu when
SEA or SE is (are) selected. You can also used the shortcut CTRL+SHIFT-W.
Note: Exact and Quick mode have no impact in
SWT
2.36.2 Description
By default the view of the model is set on Shaded mode. Sometimes it could be interesting to switch in the
wire frame view to do not hide other components. The wire frame mode is very interesting if you want to
see the connectors position inside your component.
Note: In the Shaded mode you can play on the
Transparency if you also want to see inside your
object - see Options Display of your SE (not SEA)
2.37 Show / hide 3D view labels

Shows or hides the textual annotations in the 3D view for supported objects.
Availability
This switch is always available. Its effect is noticeable only when there are annotations for the visible
objects.
This command can be accessed in the SWT menu under Show/hide 3D View labels.
Description
This command acts like a toggle switch for changing the visibility of selected annotations for some 3D
objects in the 3D view. Running this command will change the visibility of the texts such that if they were
hidden they will be shown, or shown if they were hidden.
2.38 Show/Hide console

Show or hide message console
This command switches the presence of the message console.
2.38.1 Availability
This feature is always available.
2.38.2 When to use?

Click the button to show or hide the message console window. The console can also be closed by clicking
on any of the other buttons highlighted in Message console show/hide buttons.
Note: The message console cannot be shown or
hidden during an analysis. Messages, however, are
constantly updated behind the scenes, and stored
whether or not the console window itself is visible.
Figure 33: Message console show/hide buttons
2.39 Super-Element Conversion

2.39.1 Availability
in the Menu Bar > SWT > Super-Element Conversion

This command has to be used when you want to use in SWT a super-element which has been built in
NASTRAN or in ANSYS .
2.39.3 Description
Where super-elements can be used, SWT expects a SAMCEF super-element. If your super-element has
another format, you have first to translate it into a SAMCEF one. This way of working leads to a saving of
time, because the translation has to be done once for all.
When you launch the task, you are prompted with a panel, where you have to specify
the super-element format (Ansys or Nastran)
the path to the super-element file, which has to be translated.
The result of that task will be a SAMCEF super element (set of several files). You have to keep all of them
together. In the GUI of SWT, when you are requested to enter a super-element file, always select the .sdb
one.
2.40 Swap component...

Exchanges one component for another of the same type in the Wind Turbine.
Use this command as a quick way to replace a Wind Turbine component with another one.
2.40.1 Availability
This command is available when a WT component is selected.
Access to this command can be found in the context menu when a Wind Turbine component is selected
(see Figure 34: Accessing the Swap command (see page 51)
Figure 34: Accessing the Swap command

You can use this command whenever you want to swap out one Wind Turbine component for another of
the same type.
2.40.3 Description
The swap command is a way to access to the Management of Wind Turbine components command from a
component. See that command for a complete description.
2.41 Update 3D View

Refreshes the 3D View
Refresh the WT 3D display.
2.41.1 Availability
in the global tool bar

in the tool bar of the Model tab
in the SWT menu
through the
button.

You have to use this command when you have made modifications that have an influence on the WT
aspect, dimensions, etc:
modification of some component dimensions
modifications in connectivity tables
definition or modifications of SAMCEF Field models or super-elements,
etc.
Important: It is important to note that the refreshing
the display is never automatic, mainly because
the redrawing of some components (SAMCEF
Field, super-elements, gearboxes) can take some
considerable time. It is thus more efficient to make
all your modifications before making a single refresh
operation.
It is important to note that the redisplay is never automatic, mainly because the redrawing of some
components (SAMCEF Field, super-elements, gearboxes) can sometimes take time. It is thus faster to
make first all modifications and then redisplay once for all.
2.41.3 Description
This command has two main effects:
1. It recomputes the global Wind Turbine connectivity table (i.e. it recomputes the position of all the
components
2. it rebuilds the drawing of all components
2.42 Update Connectors

Updates connector locations
Computes the connector locations.
2.42.1 Availability
This feature in the pop-up menu associated with the items of the WT component tree (Caesam SEA or SE).
The associated icon is

This command has to be called on SAMCEF Field or Super-Element components when their connector
locations are either not known or because they have changed.
The determination of these locations needs to open the associated SAMCEF Field model or to reload the
associated Super-Element, which can take some time. It is for this reason why, that operation is always
done on demand only.
2.42.3 Description
2.42.3.1 SAMCEF Field models
In SAMCEF Field models, connectors are defined internally as selections. The command retrieves their
positions in the following way:
1.
2.
3.
4.
Open the SAMCEF Field model

Get all the selections with one single selection
Retrieve the corresponding positions
Use the selection names and positions to rebuild the complete list of the connectors.
Note: It is important to note that for SAMCEF Field
models, the connector list is completely directed by
the model.
2.42.3.2 Super-Element models

In Super-element models, the SE connectors are defined by the list of the retained nodes. The link between
the SEA and the SE connectors are defined in a standard way through the connection tables. The update of
the SE connectors is done in the following way:
1. Reload the super element
2. Get the positions of all declared retained nodes
3. Use these data to update the connector table.
Note: It is important to note that for Super-Element
models, the connector list is directed by the retained
nodes declared in SWT.
2.42.4 Remarks
In SAMCEF Field components, the connector list is really shared between the SEA and the SE. It is
therefore absolutely equivalent to select either of them for the Update Connectors command.
In Super-Element components, if you update the connectors of the SEA, it will first update those of the
SE, and then update those of the SEA according to the connection tables. If you update the connectors
of the SE, only those will be updated by the command. The SEA connectors - which are standard ones will be automatically updated in the standard way at the next update.
2.43 Wind Turbine Initialization

Initialises the Wind Turbine model with a selected set of components
Build a wind turbine assembly from scratch.
2.43.1 Availability
This feature can be used when you have an empty model (when you have just launched SWT, or after a
New Document action).
Its is launched through the
icon in the tool bar of the Model tab.

It is the first step of the creation of a new model.
2.43.3 Description
The initialization command opens the following dialog.
Figure 35: Wind Turbine Initialization
2.43.3.1 Selection of components

The panel proposes a list of predefined components with, for each of them, the choice between several
implementation. Those implementation corresponds to the following families:
parametric models (detailed or simple ones)
SAMCEF Field models
Super-element models
BACON advanced models
user's families (see hereunder)
Selecting globally a family will select for each type of component the first one corresponding to the chosen
family.
Note: It is also possible to add Additional
Components (i.e. component that do not match any
predefined one) by using the
button of the panel.
2.43.3.2 Selection of a connectivity schema

You (the user) must select choose the connectivity pattern to be used (at least as a starting one: it is still
possible to edit it later).
The user must also choose the connectivity pattern he wants to use (at least as a starting one: it is still
possible to edit it later).
A default connectivity pattern is selected. This is done according to the family choice for families that
define their own connectivity patterns.
2.43.3.3 User families
The Export... (a component) (see page 30) command explains how you can save a component that
has been built and modified. This enables you to have directories, which can be considered as sets of user
components which can be scanned by SWT in order to propose the components for selection.
The
button gives access to a panel, in which the user can define the directories to scan.
Figure 36: Wind Turbine component paths dialog
In the panel, some directories can be added. To be taken into account, directories have also to be selected
(check box). The system makes it possible to avoid taking directories into account, without having to
remove them from the list (just by deselecting the check box).
If you Save the status, it will be stored in your preferences, so that the whole list will be automatically
scanned when opening the WT initialization panel.
If you want modifications in the directories to be taken into account after a modification, you have to
rescan all directories, by using the
button.
2.43.4 Remarks
Most features of the WT Initialization panel are identical to those of the WT Component Management
command.
56 | Samcef Wind Turbines | 3 Connectors and outstanding nodes
3 Connectors and outstanding nodes

This chapter describes all special nodes that can exist in a model.
Among all outstanding nodes, the connectors are the mostly visible. They are indeed widely used in the
GUI in order to connect components or sub-components with each others.
There are however other kind of oustanding nodes:
the control nodes are also very useful. They can be considered as sensors, or measurements. Most of
them are attached to hinges and measure the angles.
Some other special nodes can be available and could be used.
The main places where such nodes can be used are listed below:
connector list and connection tables
user load definitions
controlled items in the controller (control nodes only)
reference nodes
sensor definitions (curve selection)
It is worth pointing out that the node names are defined within the models. This chapter presents the
names used in the predefined models. In external (SAMCEF Field) models, the user can choose its own
naming. Obviously, if he uses the same names as those defined in the predefined models, he will also be
able to use directly the predefined connection tables, or the controller sensor definitions. If he prefers using
its own namings, he will simply have to modify or redefine the latter.
Table 1: Connectors by components
Component
Tower connectors
Bedplate connectors
Mainshaft connectors
Rotor connectors
Gearbox connectors
Coupling Shaft (HSCS) connectors
Generator connectors
Nacelle connectors
Support connectors
3.1 List of connectors

Table 2: Alphabetic list of connectors
Connector
Component
BEDPL_GENO_iXjY_LINK_NODE
BEDPL_MNSH_MB1_LINK_NODE
BEDPL_MNSH_MB2_LINK_NODE
Bedplate
Bedplate
Bedplate
Samcef Wind Turbines | 3 Connectors and outstanding nodes | 57
Connector
Component
BEDPL_YOKES_kY_LINK_NODE
BLADEi_ROOT_LINK_NODE
BLADEi_SEC_NODE_j
BLADES_HUB_BLDi_LINK_NODE
BLADES_HUB_LINK_NODE
GBOX_HSCS_BRAKE_LINK_NODE
GBOX_HSCS_LINK_NODE
GBOX_MNSH_LINK_NODE
GBOX_YOKE_NEGY_LINK_NODE
GBOX_YOKE_POSY_LINK_NODE
GENO_BEDPL_iXjY_LINK_NODE
GENO_CONTROL_NODE
GENO_HSCS_LINK_NODE
HSCS_BRAKE_CONTROL_NODE
HSCS_BRAKE_PRESSURE_NODE
HSCS_ELCPL_INPUT_NODE
HSCS_GBOX_LINK_NODE
HSCS_GBOX_BRAKE_LINK_NODE
HSCS_GENO_LINK_NODE
HSCS_SLIP_CONTROL_NODE
MNSH_BEDPL_MB1_LINK_NODE
MNSH_BEDPL_MB2_LINK_NODE
MNSH_BLADES_BLDi_LINK_NODE
MNSH_BLADES_LINK_NODE
MNSH_GBOX_LINK_NODE
MNSH_MB1_CONTROL_NODE
PITCHi_CONTROL_NODE
TOWER_FIXED_NODE
TOWER_FOUNDATION_LINK_NODE
YAW_BEDPL_LINK_NODE
YAW_CONTROL_NODE
YAW_OLNK_NODE
YOKE_GBOX_kY_LINK_NODE
Bedplate
Rotor
Rotor
Rotor
Rotor
Gearbox
Gearbox
Gearbox
Gearbox
Gearbox
Generator
Generator
Generator
HSCS
HSCS
HSCS
HSCS
HSCS
HSCS
HSCS
Mainshaft
Mainshaft
Mainshaft
Mainshaft
Mainshaft
Mainshaft
Rotor
Tower
Tower
Tower
Tower
Tower
Bedplate
3.2 Tower outstanding points and sensors

List of the connectors and other external nodes related to the predefined towers. It is advised - although
not compulsory - to use the same names in user defined components, excepted for the ones defined as
compulsory. In the latter case, the point/sensor must be defined somewhere in the model.
3.2.1 TOWER_FOUNDATION_LINK_NODE
Description
This connector usually represents the lowest point of the tower. When a foundation
bushing is modeled, this point is located above the foundation (it moves)
Use
This connector is used
by the standard assembling table, when a support component has been selected
(connection between the tower and the support)
by the standard and simple parametric components (case of a tower clamp, possibly
with a foundation bushing)
3.2.2 YAW_BEDPL_LINK_NODE
Compulsory
This connector is compulsory if the tower shadow effect is requested in the aerodynamic
loads.
Description
This connector usually represents the highest point of the tower, above the yaw hinge. This
point rotates with the nacelle.
Use
by the standard assembling table (connection between the tower and the bedplate)
by the aerodynamic loads, in order to locate the tower for the computation of the tower
shadow.
3.2.3 YAW_CONTROL_NODE
Compulsory
This control node (or an equivalent one) is compulsory if the wind turbine has a controller.
Description
This control node holds the rotation of the yaw.
Use
This control node is used
by the controller (yaw controlled or driven)
by the loadcase (yaw imposed or driven)
as a sensor support to measure the yaw angle, rotation speed etc.
3.2.4 YAW_OLNK_NODE
Description
This connector usually represents the highest point of the tower, under the yaw hinge. This
point does not rotate with the nacelle.
Use
This connector not used
3.2.5 TOWER_FIXED_NODE
Description
This connector represents the clamped point of the tower. When a foundation bushing is
modeled, this point is located under the foundation bushing (it does not move). When the
tower base is left free, this point does not exist, and may not be used
Use
This point is used
in the predefined models to set the tower base clamp
in the sensor definition to get the reactions
3.3 Bedplate outstanding points and sensors

List of the connectors and other external nodes related to the predefined bedplate, mainframe or rearframe.
It is advised - although not compulsory - to use the same names in user defined components, excepted
for the ones defined as compulsory. In the latter case, the point/sensor must be defined somewhere in the
model.
3.3.1 BEDPL_MNSH_MB1_LINK_NODE
Description
This connector represents the bedplate point that supports the main bearing 1 ("rotor side"
main bearing). Since the main bearing belong to the mainshaft component, this point does
not rotate with the shaft.
Use
by the standard assembling table (connection between the bedplate and the mainshaft)
3.3.2 BEDPL_MNSH_MB2_LINK_NODE
Description
This connector represents the bedplate point that supports the main bearing 2 ("generator
side" main bearing). Since the main bearing belong to the mainshaft component, this point
does not rotate with the shaft. Note that this connector does not exist when there is only 1
main bearing.
Use
3.3.3 BEDPL_GENO_iXjY_LINK_NODE
Description
These connectors represent the 4 bedplate points that support the generator:
Table 3:
Connector
Location
BEDPL_GENO_NXNY_LINK_NODE
Negative-X Negative-Y
point
Negative-X Positive-Y
point
Positive-X Negative-Y
point
Positive-X Positive-Y
point
BEDPL_GENO_NXPY_LINK_NODE
BEDPL_GENO_PXNY_LINK_NODE
BEDPL_GENO_PXPY_LINK_NODE
Use
These connectors are used
by the standard assembling table (connections between the bedplate and the generator)
3.3.4 YOKE_GBOX_kY_LINK_NODE
Description
These connectors represent the 2 bedplate points that support the gearbox:
Table 4:
YOKE_GBOX_NEGY_LINK_NODE
YOKE_GBOX_POSY_LINK_NODE
Negative-Y
Positive-Y
For detailed bedplates (standard or super-element ones), which are made of 2 separate subcomponents (Bedplate body and yokes), they are located on the gearbox side of the yokes.
Use
by the standard assembling table (connections between the bedplate and the gearbox)
3.3.5 BEDPL_YOKES_kY_LINK_NODE
Description
These connectors represent the 2 bedplate body points that support the yokes:
Table 5:
BEDPL_YOKES_NEGY_LINK_NODE
BEDPL_YOKES_POSY_LINK_NODE
Negative-Y
Positive-Y
They exist only for detailed bedplates (standard or super-element ones), which are made of
2 separate sub-components (Bedplate body and yokes). They are located on the bedplate
side of the yokes.
Use
These connectors are not used
3.4 Mainshaft outstanding points and sensors

List of the connectors and other external nodes related to the predefined bedplate, mainframe or rearframe.
It is advised - although not compulsory - to use the same names in user defined components, excepted
for the ones defined as compulsory. In the latter case, the point/sensor must be defined somewhere in the
model.
3.4.1 MNSH_BEDPL_MB1_LINK_NODE
Description
This connector represents the main bearing 1 fixed point ("rotor side" main bearing). This
point does not rotate with the shaft (it is located on the hinge bedplate side).
Use
3.4.2 MNSH_BEDPL_MB2_LINK_NODE
Description
This connector represents the main bearing 2 fixed point ("generator side" main bearing).
This point does not rotate with the shaft (it is located on the hinge bedplate side). Note that
this connector does not exist when there is only 1 main bearing.
Use

3.4.3 MNSH_GBOX_LINK_NODE
Description
This connector represents the output point of the mainshaft, i.e. the point that is connected
to the gearbox (when the WT has a gearbox).
Use
by the standard assembling table (connection between the mainshaft and the gearbox
3.4.4 HUB_BLADES_LINK_NODE
Description
This connector represents the location on the mainshaft that is at the center of the
rotor (projection of the blade root points on the shaft axis, using a projection direction
perpendicular to that axis).
Use
by the standard assembling table (connection between the mainshaft and the rotor). This
connector has to be the first one between the mainshaft and the rotor in order to ensure
a perfect centering of the rotor, and to avoid in that way any numeric imbalance.
in the sensor definition, to gather in one locations all forces flowing from the rotor to
the mainshaft.
3.4.5 HUB_CENTER_NODE
Description
This connector represents a node on the hub which does not rotate with it. Although the
connector does not follow the main rotations of the hub, it does follow displacements and
secondary rotations.
Use
This connector defines the origin node for the reference frame fixed_hub.
3.4.6 HUB_BLADES_BLDi_LINK_NODE
Description
These connectors represent the points where the blades are connected to the hub. Since the
pitch mechanism belong to the blades, these points rotate with the hub (around the rotor
axis) but not with the blades (around the blade axes).
Use
by the standard assembling table (connections between the mainshaft and the rotor)
in the sensor definition, to hold the forces flowing from each blade to the hub.
3.4.7 MNSH_MB1_CONTROL_NODE
Description
This sensors holds the mainshaft rotation dof at the main bearing 1 ("rotor side" MB).
Use
by the controller (rotor speed measure)
as a sensor support to measure the rotor angle, speed or acceleration
3.4.8 MNSH_MB2_CONTROL_NODE
Description
This sensors holds the mainshaft rotation dof at the main bearing 2 ("genetor side" MB).
Use
This connector is not used
3.5 Gearbox outstanding points and sensors

List of the connectors and other external nodes related to the predefined gearboxes. It is advised - although
3.5.1 GBOX_MNSH_LINK_NODE
Description
This connector represents the input node of the gearbox. It exists in all prametric gearbox
models. This node rotates with the input shaft.
Use
by the standard assembling table (connection between the mainshaft and the gearbox)
3.5.2 GBOX_HSCS_LINK_NODE
Description
This connector representsthe the ourput node of the gearbox. It exists in all parametric
gearbox models.This node rotates with the output shaft.
Use
by the standard assembling table (connection between the bedplate and the high speed
shaft)
3.5.3 GBOX_YOKE_NEGY_LINK_NODE
Description
This connector represents the gearbox support node on the negative Y side. It exists in all
parametric gearbox models. This node belongs to the casing part of the gearbox.
Use
by the standard assembling table (connection between the gearbox and the bedplate)
3.5.4 GBOX_YOKE_POSY_LINK_NODE
Description
This connector represents the gearbox support node on the positive Y side. It exists in all
parametric gearbox models. This node belongs to the casing part of the gearbox.
Use
by the standard assembling table (connection between the gearbox and the bedplate)
3.5.5 GBOX_HSCS_BRAKE_LINK_NODE
Description
This connector represents the location on the gearbox where the brake pad is fixed.
It exists in all parametric gearbox models. This node belongs to the casing part of the
gearbox.
Use
by the standard assembling table (connection between the bedplate and the high speed
shaft)
3.6 Rotor outstanding points and sensors

List of the connectors and other external nodes related to the predefined rotor (blades).
3.6.1 BLADES_HUB_LINK_NODE
Description
This connector represents the (virtual) center of the rotor. This point does not hold any
degree of freedom, but is used to center correctly the rotor on the hub, avoiding any
"preference" (hence any desequilibrium) among the blades (as long as it is used in the first
connection between the rotor and the mainshaft).
Use
by the standard assembling table (connection between the rotor and the mainshaft)
3.6.2 BLADES_HUB_BLDi_LINK_NODE
Description
These connectors represent the blade extremities, attached to the mainshaft (1 for each
blade: BLADES_HUB_BLD1_LINK_NODE, BLADES_HUB_BLD2_LINK_NODE,
etc). Since the pitch hinges are considered as part of the blades, they rotate with the hub,
but not with the blades.
Use
by the standard assembling table (connection between the rotor and the mainshaft)
3.6.3 PITCHi_CONTROL_NODE
Description
These sensors hold the blade rotation dof (1 for each blade: PITCH1_CONTROL_NODE,
PITCH2_CONTROL_NODE, etc)
The blade numbers range from 1 to the number of blades.

Use
These sensors are used
by the controller (blade pitches controlled or driven)
by the loadcase (blade pitches imposed or driven)
as a sensor support to measure the pitch angles, rotation speed etc.
3.6.4 BLADEi_ROOT_LINK_NODE
Description
These connectors represent the "physical" blade extremities, i.e. on the bladeside of the pitch hinge (1 for each blade: BLADE1_ROOT_LINK_NODE,
BLADE2_ROOT_LINK_NODE, etc). They rotate with the hub and with the blades.
Use
These connectors are not used.
3.6.5 BLADEi_SEC_NODE_j
Description
These points represent the extremities of the (aero) blade sections. (1 for each aero
section of each blade: BLADE1_SEC_NODE_1, BLADE1_SEC_NODE_2, ... ,
BLADE2_SEC_NODE_1, BLADE2_SEC_NODE_2, ... , etc). They rotate with the hub
and with the blades.
The station numbers range from 1 to the number of station, considering that
for the Bladed-like rotor, the first station is located at the blade root and the last one at
the blade tip (# stations = # sections + 1)
for the other rotors, there is no station at the blade root (# stations = # sections)
Note also that, in case of a beam rotor model, the connectors correspond to the F.E. nodes
that belong to the beam after the station.
Use
These sensors are used
by the loadcase: support of the aerodynamic forces (AERO elements)
3.7 HSCS outstanding points and sensors

List of the connectors and other external nodes related to the predefined HSCS (Coupling Shaft).
3.7.1 HSCS_GBOX_LINK_NODE
Description
This connector represents the HSCS point that is normally linked to the gearbox output.
Use
by the standard assembling table (connection between the gearbox and the HSCS)
3.7.2 HSCS_GENO_LINK_NODE
Description
This connector represents the HSCS point that is normally linked to the generator input.
Use
by the standard assembling table (connection between the HSCS and the generator)
3.7.3 HSCS_GBOX_BRAKE_LINK_NODE
Description
This connector represents the HSCS point on the brake pad. In the standard connection
table, this point is linked to the gearbox casing.
Use
by the standard assembling table (brake connection between the HSCS and the gearbox)
3.7.4 HSCS_BRAKE_CONTROL_NODE
Description
This conrol node holds the HSCS disk brake rotation, and is submitted to the braking
torque when the brake is activated.
Use
This control node is used internally by the HSCS brake model.
3.7.5 HSCS_BRAKE_PRESSURE_NODE
Compulsory
This control node (or an equivalent) is compulsory if the wind turbine has a controller able
to manage the brake or if the brake has to be activated by the loadcase.
Description
This control node represents the brake state: when its position x=0, the brake is inactive;
as soon as x=1, the brake is activated, using the brake activation function defined in the
HSCS.
Use
by the controller, when it is able to manage the brake
3.7.6 HSCS_SLIP_CONTROL_NODE
Description
This control node holds the HSCS slip coupling rotation and the associated torque limiter.
Use
This control node is used internally by the HSCS slip coupling model.
3.7.7 HSCS_ELCPL_INPUT_NODE
Description
This connector is located on the HSCS just before the generator coupling. It is seperated
from HSCS_GENO_LINK_NODE just by the coupling bushing (generalized stiffness and
damping properties)
Use
This conector is not used (node used internally).
3.8 Generator outstanding points and sensors

List of the connectors and other external nodes related to the predefined generator. It is advised - although
3.8.1 GENO_HSCS_LINK_NODE
Description
This connector usually represents the input point of the generator. In standard models, it is
linked to the HSCS after the elastic coupling.
Use
by the standard assembling table (connection between the HSCS and the generator)
3.8.2 GENO_CONTROL_NODE
Compulsory
This control node (or an equivalent one) is compulsory if the wind turbine has a controller.
Description
This control node holds the rotation of the generator. It receives the generator resisting
torque from the controller (or possibly from the loadcase).
Use
by the controller (generator controlled)
by the loadcase (additional torque)
as a sensor support to measure the generator angle, rotation speed etc.
3.8.3 GENO_BEDPL_iXjY_LINK_NODE
Description
These connectors represent the 4 generator points that linked to the bedplate or rearframe:
Table 6:
Connector
Location
GENO_BEDPL_NXNY_LINK_NODE
Negative-X Negative-Y
point
Negative-X Positive-Y
point
Positive-X Negative-Y
point
GENO_BEDPL_NXPY_LINK_NODE
GENO_BEDPL_PXNY_LINK_NODE
Connector
Location
GENO_BEDPL_PXPY_LINK_NODE
Positive-X Positive-Y
point
Use
by the standard assembling table (connections between the bedplate and the generator)
68 | Samcef Wind Turbines | 4 SWT error Messages
4 SWT error Messages

In SWT each message are composed of an ID and a reference Class.
The format of the error/warning message will always be:
ERROR["ClassName": ID ]
Description of the error message
and
WARNING["ClassName": ID ]
Description of the warning message
Notice that we can also have:
PROGERROR["ClassName": ID ]
Description of the programming error message
But these programming errors should normally never occur for the user and are not related to bad
parameters in the model.
In the following list, you can find tables with all error messages created for this specification. A solution
to solve the problem is also given only when the description of the problem is not clear enough. No
comment is given for the programming errors.
4.1 Messages related to ConnectorUtil

These messages are related to the Class ConnectorUtil
ID
Description
This message occurs when there is an incomplete line in the connection

table. It is highly recommended to correct the problem to avoid a
connection table which is not valid.
ID 1 - ConnectorUtil
Type: Warning
Description of the message: This message occurs when there is an incomplete line in the
connection table. It is highly recommended to correct the problem to avoid a connection
table which is not valid.
Comments/Solution:
The connection table can be corrected either by removing the row from the table using the
button or by completing the required columns in the table.
Samcef Wind Turbines | 4 SWT error Messages | 69
4.2 Messages related to AbstractMasher

These messages are related to the Class AbstractMasher
ID
Description
1
2
Different messages are possible depending on the context

Object type mismatch: expected an object of type PMabstractMasher
( found object of type 'typename'."
No URL found for CsmType: key Skipping type.
3
4
5
6
7
8
9
10
11
ID 1 - AbstractMasher
Type: Error
Description of the message: Different messages are possible depending on the context
Comments/Solution:
Such errors occur when launching a SAMCEF execution when a necessary data is
not found. This is a low level error, which can be repeated in a more explicit way in
subsequent messages coming from a higher level.
Type: Error
Description of the message: Object type mismatch: expected an object of type
PMabstractMasher ( found object of type 'typename'."
Comments/Solution:
Such errors occur when launching a SAMCEF execution when a data is not what the
program expects. This is a low level error, which whose origin cab be found in a more
explicit way in subsequent messages coming from a higher level.
Type: Error
Comments/Solution:
An error has occurred during the operation 'Export to Neutral'. The message explains what
error occured.
Type: Warning
Comments/Solution:
Problems have occured during the copy of dependency file from their original location to
the computation temporary directory.
Type: Warning
Description of the message: No URL found for CsmType: key Skipping type.
Comments/Solution:
None
Type: Error
Comments/Solution:
This message comes from FemPad.
Type: Error
Comments/Solution:
The reported error occurred during the creation of a file by FEMWORD (generation of a
file by merging a template and the parameters).
Type: Error
Comments/Solution:
The reported error occurred during the creation of a bank file by FEMWORD (generation
of a bank file by merging a template and the parameters).
Type: Error
Comments/Solution:
The reported error occurred during the execution of Samcef.
Type: Error
Comments/Solution:
None
Type: Error
Comments/Solution:
The reported error occurred during the export of the bank file from a CAD system.
4.3 Messages related to AnalyseAddedMethods

These messages are related to the Class AnalyseAddedMethods
ID
Description
1
2
3
4
Different messages are possible under this number

No loadcase set defined in the Analyse 'name'
The analyse is neither a S4WTloadcaseV2 nor a S4WTloadcaseV3 type
The analyse ('name') duration cannot be greater than the load case
('name') end time
The MECANO maximum time step (advanced MECANO parameters)
should be lower or equal to the Controller Time Step (analysis 'name')
No loadcase selected in the Analyse 'name'
5
6
ID 1 - AnalyseAddedMethods
Type: Programming Error
Description of the message: Different messages are possible under this number
Comments/Solution:
Such message appear when an expected data cannot be found.
Refer To Samtech headquarters
Description of the message: No loadcase set defined in the Analyse 'name'
Comments/Solution:
Such message appear when an expected data cannot be found.
Refer To Samtech headquarters
Type: Error
Description of the message: The analyse is neither a S4WTloadcaseV2 nor a
S4WTloadcaseV3 type
Comments/Solution:
You have selected in your analysis a loadcase that has not been created in the LoadCase
tab (e.g. generic loadcase object created in the Shared Worspace tab).
Use loadcase created in the LoadCase tab only
Type: Error
Description of the message: The analyse ('name') duration cannot be greater than the load
case ('name') end time
Comments/Solution:
The functions which describe the loadcase are then not defined over a sufficiently long
period of time, which would lead to problems during the computation.
Modify the Duration of the specified analyse to avoid problems in Mecano.
Type: Warning
Description of the message: The MECANO maximum time step (advanced MECANO
parameters) should be lower or equal to the Controller Time Step (analysis 'name')
Comments/Solution:
To ensure that the controller is called according to its time step, you must prevent
MECANO to step over those times and define the Mecano maximum time step with a
compatible value (MECANO maximum time step < controller time step).
The controller Time Step: you can find it in the Controller properties in the tab
'Implementation'. The value is given in the field 'Control updating time'.
The Maximim Time Step (advanced MECANO parameters): you can find it in the field
'Solver Data' of the analysis in Advanced Parameters in the field 'Maximum Step'
Type: Error
Description of the message: No loadcase selected in the Analyse 'name'
Comments/Solution:
The analysis contains no loadcase. This does normally not appear when you create
the analysis in the standard SWT way, by the operation of the button
applied on a
loadcase. In that case indeed, the loadcase is automatically selected in the created analysis.
However, when you create a transient analysis in the standard CAESAM way (popup
menu on the Wind Turbine, then Create Analysis, then selection of Transient Analysis) ,
there is no automatic selected loadcase. You have thus to select it yourself:
select the loadcase set (Applied Load)
click on the Edit button
select the suited loadcase (transfer it in the right column). Take 1 single loadcase only.
If you select more than 1 loadcase, the following ones will be ignored.
Note that the current error sould also be obtained by using this loadcase set editor and
removing the selected loadcase.
4.4 Messages related to AnalysisBuilder

These messages are related to the Class AnalysisBuilder
ID
Description
File 'sensorInfo.csm' not found! Run the script 'sensorInfoExport.ccl'

in the initial model to export the file. If not you will get problems to
postprocess the analysis.
ID 1 - AnalysisBuilder
Type: Warning
Description of the message: File 'sensorInfo.csm' not found! Run the script
'sensorInfoExport.ccl' in the initial model to export the file. If not you will get problems to
postprocess the analysis.
Comments/Solution:
If you want to post-process the linked analysis you need a file named 'sensorinfo.csm'
that must be in the caesam external files folder of the original Transient Analysis. This
file contains the information related to the sensors of the initial Transient Analysis. This
file is not generated by default in the result folder. To create it open the czm where the
initial Transient Analysis is located and open the ccl script 'sensorInfoExport.ccl' - you can
find it in the CCL folder at the root of SWT. Edit in the script the name of the Transient
Analysis to correspond to the analysis you want to export. Run the script to generate the
file. After that the command 'Link Transient Analysis' can be used on another analysis to
link it towards this initial Transient Analysis.
If the command is used related to an analysis that does not have the file 'sensorinfo.csm'
the command will work but you cannot use this analysis to create a Fatigue/ELA/VL
Durability analysis.
4.5 Messages related to AnalyseExplorer

These messages are related to the Class AnalyseExplorer
ID
Description
1
2
Can not save this object in Csv format

Unable to open the object 'name'
ID 1 - AnalyseExplorer
Type: Warning
Description of the message: Can not save this object in Csv format
Comments/Solution:
It is not possible to export this king of object in a csv format.
ID 2 - AnalyseExplorer
Type: Error
Description of the message: Unable to open the object 'name'

Comments/Solution:
Before to save the object in csv format, we try to load it. An error occurs during the
loading: check the log for further information about the problem.
4.6 Messages related to BladeStationTableEditor

ID
Description
1
2
BladeStationTable contains special col type

BladeStationTable is Null
ID 1 - BladeStationTableEditor
Description of the message: BladeStationTable contains special col type
Comments/Solution:
Refer to Samtech Headquarter.
ID 2 - BladeStationTableEditor
Type: Error
Description of the message: BladeStationTable is Null
Comments/Solution:
Check that the Table with all data of the Bladed rotor exists.
4.7 Messages related to BuildAnalysesFromResults

These messages are related to the Class BuildAnalysesFromResults
ID
Description
Directory (name) not found, skipping.
ID 1 - BuildAnalysesFromResults
Type: Warning
Description of the message: Directory (name) not found, skipping.
Comments/Solution:
None
4.8 Messages related to CatiaWorker

These messages are related to the Class CatiaWorker
ID
Description
1
2
Message can be different depending on the context

ID
Description
3
4
CDV file name not specified

Object type mismatch: expected PMcatiaMasher
ID 1 - CatiaWorker
Type: Error
Description of the message: Message can be different depending on the context
Comments/Solution:
An error occurred during the Post Processing in Catia
ID 2 - CatiaWorker
Type: Error
Comments/Solution:
An error occurred during the export of the bank file.
ID 3 - CatiaWorker
Type: Error
Description of the message: CDV file name not specified
Comments/Solution:
None
ID 4 - CatiaWorker
Type: Error
Description of the message: Object type mismatch: expected PMcatiaMasher
Comments/Solution:
None
4.9 Messages related to ConnectorList

These messages are related to the Class ConnectorList
ID
Description
Unable to get CaesamStd_Model: EditorData.getCaesamApiObject

returned null.
ID 1 - ConnectorList
Type: Warning
Description of the message: Unable to get CaesamStd_Model:
EditorData.getCaesamApiObject returned null.
Comments/Solution:
None.
4.10 Messages related to ConnectorUtil

These messages are related to the Class ConnectorUtil
ID
Description
com.samcef.s4wt.util.connectors.ConnectorUtil Row #num contained

null elements, pattern not exported.
ID 1 - ConnectorUtil
Type: Warning
Description of the message: com.samcef.s4wt.util.connectors.ConnectorUtil Row #num
contained null elements, pattern not exported.
Comments/Solution:
This message appears when you try to export the pattern of a connection table (using
button
) whilst that table is not completely defined (you have some red rows)
4.11 Messages related to CsvFunctionReader

These messages are related to the Class CsvFunctionReader
ID
Description
1
2
Some values are missing in the curve 'curve name'

In a csv HISTOGRAM curve (curve name) three points must be defined
for each line
ID 1 - CsvFunctionReader
Type: Warning
Description of the message: Some values are missing in the curve 'curve name'
Comments/Solution:
This curve is defined in a csv File. In such file we can define several Y curves for a single
X curve. After the tag 'FUNC_DATA' in the Csv file data are given: the X value followed
by the Y points - each value being separated by a semi-colon. Normally each row must
have the same number of points. This message appears because the number of point is
different for at least two rows.
ID 2 - CsvFunctionReader
Type: Warning
Description of the message: In a csv HISTOGRAM curve (curve name) three points must
be defined for each line
Comments/Solution:
This curve is defined in a csv File. In such file we can define a histogram curve. After
the tag 'FUNC_DATA' in the Csv file data are given: the minimum X value of the bin
followed by the maximum X Value. Finally we get the height of the bar itself - each value
being separated by a semi-colon. Consequently each row must have three points.
4.12 Messages related to CURVcombinator

These messages are related to the Class CURVcombinator
ID
Description
1
2
3
No recombination style specified

Unknown recombination style
Conversion from (x,y) to (r,th) requires two sections, only num were
found
Conversion from (x,y) to (r,th) requires two sections, only num output
sections were found
SFR curve 'x' (or 'y') was NULL
Number of points in x not equal to number of points in y
4
5
6
ID 1 - CURVcombinator
Description of the message: No recombination style specified
Comments/Solution: None
Description of the message: Unknown recombination style
Description of the message: Conversion from (x,y) to (r,th) requires two sections, only
num were found
Description of the message: Conversion from (x,y) to (r,th) requires two sections, only
num output sections were found
Description of the message: SFR curve 'x' (or 'y') was NULL
Description of the message: Number of points in x not equal to number of points in y

4.13 Messages related to CURVsfrConverterV

These messages are related to the Class CURVsfrConverterV
ID
Description
Invalid CURVfileFormat ("format")...
returning null
ID 1 - CURVsfrConverterV
Type: Error
Description of the message: Invalid CURVfileFormat ("format")...
returning null
4.14 Messages related to CURVsfrToCrv

These messages are related to the Class CURVsfrToCrv
ID
Description
1
2
3
5
No files to convert (path="name")

invalid CURVprecision enum value
Exception caught: exception
%%%ERROR(CURVsfrToCrv::convert) SRsfrCurve, errors reading
file: " filename
Unable to recombine curve, missing component id, curvename
Unable to recombine curve, looking for section index id in
sfrcurve.sections list with only numItems
6
7
ID 1 - CURVsfrToCrv
Type: Error
Description of the message: No files to convert (path="name")
ID 2 - CURVsfrToCrv
Description of the message: invalid CURVprecision enum value
ID 3 - CURVsfrToCrv
Description of the message: Exception caught: exception
ID 5 - CURVsfrToCrv
Type: Error
Description of the message: %%%ERROR(CURVsfrToCrv::convert) SRsfrCurve, errors
reading file: " filename
ID 6 - CURVsfrToCrv
Type: Warning
Description of the message: Unable to recombine curve, missing component id,
curvename
ID 7 - CURVsfrToCrv
Description of the message: Unable to recombine curve, looking for section index id in
sfrcurve.sections list with only numItems
4.15 Messages related to CURVsfrToFlex5

These messages are related to the Class CURVsfrToFlex5
ID
Description
1
2
Unable to open output file 'filename'

In file="filename": nt="id" different from firstNt="id"
ID 1 - CURVsfrToFlex5
Type: Error
Description of the message: Unable to open output file 'filename'
ID 2 - CURVsfrToFlex5
Type: Error
Description of the message: In file="filename": nt="id" different from firstNt="id"
4.16 Messages related to DataTranslator

These messages are related to the Class DataTranslator
ID
Description
Error when decoding WaveLoad results: ZONE not found. File

corrupted
Unable to open (reload) WaveLoads results file
ID 1 - DataTranslator
Type: Error
Description of the message: Error when decoding WaveLoad results: ZONE not found.
File corrupted
ID 2 - DataTranslator
Type: Error
Description of the message: Unable to open (reload) WaveLoads results file
4.17 Messages related to DefaultAddedMethods

These messages are related to the Class DefaultAddedMethods
ID
Description
1
2
3
4
5
6
7
8
9
S4WTwindTurbineSEA_Check: inst is NULL

Component #id of the WT is null
Component #id of the WT is not a SEA
Component #id of the WT is not a SEA
Wrong object type ' name': expected a S4WTtransientAnalysis.
No dataset in the SWT analysis
No 'utilities' EO found in data set (S4WTtransientPost)
sensInfo member is not a SKTSsensorGlossaryData
Connector table and pattern table have different sizes:
#connectors=nconnections #patterns=npatterns
The origin, x-, y- or z-axis definitions contain errors for the following
orientations: List of orientations
10
ID 1 - DefaultAddedMethods
Description of the message: S4WTwindTurbineSEA_Check: inst is NULL
Type: Warning
Description of the message: Component #id of the WT is null
Description of the message: Component #id of the WT is not a SEA
Description of the message: Component #id of the WT is not a SEA

Description of the message: Wrong object type ' name': expected a
S4WTtransientAnalysis.
Description of the message: No dataset in the SWT analysis
Description of the message: No 'utilities' EO found in data set (S4WTtransientPost)
Description of the message: sensInfo member is not a SKTSsensorGlossaryData
Description of the message: Connector table and pattern table have different sizes:
#connectors=nconnections #patterns=npatterns
Type: Warning
Description of the message: The origin, x-, y- or z-axis definitions contain errors for the
following orientations: List of orientations
4.18 Messages related to DeleteOrientationAction

These messages are related to the Class DeleteOrientationAction
ID
Description
Cannot delete built-in orientations: List of orientations
ID 1 - DeleteOrientationAction
Type: Information
Description of the message: Cannot delete built-in orientations: List of orientations
4.19 Messages related to DependencyFileMethods

These messages are related to the Class DependencyFileMethods
ID
Description
Dependency not found: location='path
ID 1 - DependencyFileMethods
Type: Error
Description of the message: Dependency not found: location='path
Comments/Solution:
A dependency file has not been found, although it was not declared as an optional one. It is
reminded that a dependency file is a file declared in the system as (possibly) necessary for
the execution. Some interesting flags are:
optional: if true, means that in some cases, the execution do ne use it; if false, means
that all execution will need it. In that latter case, if the file does not exist, this error
message is issued
forceCopy: if true, means that the file will be copied into the temporary computation
directory; if false, means that the file can remain at its location and will be used there.
Note SWT uses several dependency files (hidden to the user, and for which the flags are
imposed by the system), but the end user can define some also (especially in the analysis
Solver Data properties.
4.20 Messages related to FEMWPexecutionMethods

These messages are related to the Class FEMWPexecutionMethods
ID
Description
FEMWORD Script file not found. Looking for: femword_script
ID 1 - FEMWPexecutionMethods
Type: Error
Description of the message: FEMWORD Script file not found. Looking for:
femword_script
Comments/Solution: A part of the installation is missing.
4.21 Messages related to FemwpSamcefWorker

These messages are related to the Class FemwpSamcefWorker
ID
Description
1
2
3
4
5

Object type mismatch: expected PMfemwpSamcefMasher
No SKTsfieldDependency found at 'key_name'. Value was NULL.
Errors converting SFIELD to Samcef BANK: List of error messages
ID 1 - FemwpSamcefWorker
Type: Error
Comments/Solution:
None
Type: Error
Comments/Solution:
An error occurred during the Post Process operation.
Type: Error
Description of the message: Object type mismatch: expected PMfemwpSamcefMasher
Comments/Solution:
None
Type: Error
Description of the message: No SKTsfieldDependency found at 'key_name'. Value was
NULL.
Comments/Solution:
There is no dependency file for the key specified.
Type: Error
Description of the message: Errors converting SFIELD to Samcef BANK: List of error
messages
Comments/Solution:
None
4.22 Messages related to FunctionEditor

These messages are related to the Class FunctionEditor
ID
Description
Impossible to get the function. Check the path you have defined
ID 1 - FunctionEditor
Type: Error
Description of the message: Impossible to get the function. Check the path you have
defined
Comments/Solution:
None
4.23 Messages related to FunctionFileExport

These messages are related to the Class FunctionFileExport
ID
Description
1
2
Cannot save this object in Csv format

Cannot export to csv function 'Function_name' and 'Function_name'
in the same file because they do not have the same number of points
(value and value)
ID 1 - FunctionFileExport
Type: Warning
Description of the message: Cannot save this object in Csv format
Comments/Solution:
This object has not the possibility to be exported in csv format.
ID 2 - FunctionFileExport
Type: Warning
Description of the message: Cannot export to csv function 'Function_name' and
'Function_name' in the same file because they do not have the same number of points
(value and value)
Comments/Solution:
You have selected several curves and tried to export them in a csv format. The multicurves export is done to save them in the same file: the first column is the X values, the
second the Y values of the first curve, the third the Y values of the second curve, etc. If the
different curves do not have the same number of points, it is not possible to do the export
in this format.
4.24 Messages related to InterpolatedCurves

ID
Description
Foil Section of the Blade Station 'name' does not contain an

Interpolation table
arrayY is null in method createCurveChart
ID 1 - InterpolatedCurves
Type: Error
Description of the message: Foil Section of the Blade Station 'name' does not contain an
Interpolation table
Comments/Solution:
The Foil Section must contain a non null Matrix.
ID 2 - InterpolatedCurves
Type: Error
Description of the message: arrayY is null in method createCurveChart
Comments/Solution:
Check that the Interpolation for the Bladed Rotor has been run. Check also if the Curves
used for the interpolation exists and are well defined.
4.25 Messages related to LoadcaseAddedMethods

These messages are related to the Class LoadcaseAddedMethods
ID
Description
1
2
3
4
5
6
8
9
No function defined for the mentioned item

Pitch, Generator, Brake or Yaw parameters are undefined
Aero parameters are undefined
Tab Aero Wind parameters are undefined
Tab Aero Wind Generator parameters are undefined
Design loadcase parameters are undefined
Starting time is greater than the Final Time
Tab Design Loadcase (Start time + Duration) is greater than the
Final Time
Tab Design Loadcase (Pitch Delay + Pitch Ramp Time) is greater
than the E-Stop duration
Tab Design Loadcase (Brake Delay + Brake Ramp Time) is greater
than the E-Stop duration
Unknown Design Load case Type
Tab Aero Path to Data File file is missing
Faults parameters are undefined
Tab Faults Start time (Grid Loss) is lower than the start time
defined in Design Loadcase
Tab Faults Start time + duration (Grid Loss) is greater than the
final time defined in Design Loadcase
10
11
12
13
14
15
16
ID
Description
17
Tab Faults Start time (Generator Torque Perturbation) is lower than

the start time defined in Design Loadcase
Tab Aero The rotor is not found in the Grid dimension specified
"Loadcase 'name': Aero -> Calculated Total Rotor height from ground
(height) (m)) should be equal to the specified Hub Height (tol 0.1 (m))
Tab Aero Starting time is greater than the Final Time defined in
Design Loadcase
Tab Aero Calculated Rotor diameter must be equal to the specified
one
Unknown loadcase type
Loadcase 'name': Tab Offshore Reference node reference does not
exist
'Object' does not containt the member 'member_name'
Tower Shadow Function in the 'Wind Turbine Assembly' none X
values in the function
Tower Shadow Function in the 'Wind Turbine Assembly': the maximum
X value cannot be lower than the Tower_Height: 'value'
Tower Shadow Function in the 'Wind Turbine Assembly': the minimum
X value cannot be greater than the Tower_Height - rotor Radius: 'value'
Unknown Rotor Type to calculate the Diameter
Tower Shadow Function in the 'Wind Turbine Assembly' No method
'GetFunction'
Unknown Rotor Shaft Type 'Type_name' to calculate the Hub Height
Unknown Bedplate Type 'Type_name' to calculate the Hub Height
Unknown Tower Type 'Type_name' to calculate the Hub Height
Unknown Support Type 'Type_name' to calculate the Hub Height
'Message can differ depending on the context'
Unable to assess the height of the support
Controller Parameter File not found
Rotor-name section num: Curve curve_name must be defined with
strictly increasing values
Rotor-name: section id : Curve name must be defined from -180 to
180
Rotor-name: section id : Curve name has no Xunit defined in the csv
file. Default Solver Units system will be used.
Loadcase 'name' - Tab Offshore: At least one group should be defined
Loadcase 'name' has no 'initialValues'
The argument is not the Wind Turbine SEA
Controller SE(A) could not be found
Controller has no 'Data' or 'Parameters' member
Controller data has no 'Curves' member
Reference node 'node' has not been found
SEA has not been initialized. No adaptation performed
18
19
20
21
23
24
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
ID 1 - LoadcaseAddedMethods
Type: Error
Description of the message: No function defined for the mentioned item
Comments/Solution:
This error is related to the Advanced Load case: Related to the tab Pitch, Generator, Brake
or Yaw. Check that each function is correctly defined.
The test is done only for the "Controller behavior" different than Controlled
Description of the message: Pitch, Generator, Brake or Yaw parameters are undefined
Comments/Solution:
This error is related to the Advanced Load case: Related to the tab Pitch, Generator, Brake
or Yaw. Refer to Samtech Headquarter.
Description of the message: Aero parameters are undefined
Comments/Solution: Refer to Samtech Headquarter.
Description of the message: Tab Aero
Wind parameters are undefined

Wind
Generator parameters are undefined

Description of the message: Design loadcase parameters are undefined
Type: Error
Description of the message: Starting time is greater than the Final Time
Comments/Solution: Incoherence in the time definition.
Type: Error
Description of the message: Tab Design Loadcase
than the Final Time
(Start time + Duration) is greater
Comments/Solution:
Incoherence in the time definition (only for Normal shutdown or Start-up).
Type: Warning
is greater than the E-Stop duration
(Pitch Delay + Pitch Ramp Time)
Comments/Solution:
Incoherence in the time definition (only for Emergency Stop)
Type: Warning
Time) is greater than the E-Stop duration
(Brake Delay + Brake Ramp
Comments/Solution:
Incoherence in the time definition (only for Emergency Stop)
Description of the message: Unknown Design Load case Type
Type: Error
Path to Data File file is missing
Comments/Solution: You have selected a turbulent wind defined by a wind file, but either
you have not selected any file, or the selected file does not exist.
Description of the message: Faults parameters are undefined
Type: Warning
Description of the message: Tab Faults
time defined in Design Loadcase
Start time (Grid Loss) is lower than the start
Comments/Solution: Incoherence in the time definition

Type: Warning
Description of the message: Tab Faults Start time + duration (Grid Loss) is greater
than the final time defined in Design Loadcase

Type: Warning
Description of the message: Tab Faults Start time (Generator Torque Perturbation) is
lower than the start time defined in Design Loadcase
Type: Error
specified
The rotor is not found in the Grid dimension
Comments/Solution:
TurbSim: The grid height must be at least equal to twice the rotor radius (= length of a
blade + radius of the rotor)
Test done only for parametric models and when the check is done on the Analysis (not on
the load case)
Type: Error
Description of the message: "Loadcase 'name': Aero -> Calculated Total Rotor height
from ground (height) (m)) should be equal to the specified Hub Height (tol 0.1 (m))
Comments/Solution:
This test is done only for non offshore load cases.
Type: Error
defined in Design Loadcase
Starting time is greater than the Final Time
Comments/Solution:
Incoherence in the time definition (only for not Advanced load case)
Type: Error
specified one
Calculated Rotor diameter must be equal to the
Comments/Solution:
where (Calculated Rotor diameter) = 2*(length of a blade) + (diameter of the hub) .
The data entered in the loadcase do not match the dimensions of your model
Test done only for parametric models and when the check is done on the Analysis (not on
the load case)
Description of the message: Unknown loadcase type
Comments/Solution:
The type is neither OffshoreDesignLoadcase, OffshoreAdvancedLoadcase,
S4WTloadcaseV2 or S4WTloadcaseV3. Refer to Samtech Headquarter.
Type: Error
Description of the message: Loadcase 'name': Tab Offshore
does not exist
Reference node reference
Comments/Solution:
Test done only when the check is done on the Analysis (not on the load case). The
reference node specified in the offshore tab has not been found in the connectors declared
in the model.
Description of the message: 'Object' does not containt the member 'member_name'
Comments/Solution:
The LC data organization is not as expected. Refer to Samtech Headquarter.
Type: Error
Description of the message: Tower Shadow Function in the 'Wind Turbine Assembly'
none X values in the function
Comments/Solution:
You have choose to use a given 'Tower Shadow Function' in the field 'Parameters' of the
Wind turbine Assembly but you have probably badly defined the function. If you do not
want to specify a user function, uncheck the box 'Use Tower shadow Function'.
Type: Error
Description of the message: Tower Shadow Function in the 'Wind Turbine Assembly': the
maximum X value cannot be lower than the Tower_Height: 'value'
Comments/Solution:
To avoid problems in Mecano, the Tower Shadow Function must be defined in a certain
range to cover all aero elements. Modify your Function to have a maximum X value
greater than the value specified in the error message.
Type: Error
Description of the message: Tower Shadow Function in the 'Wind Turbine Assembly': the
minimum X value cannot be greater than the Tower_Height - rotor Radius: 'value'
Comments/Solution:
To avoid problems in Mecano, the Tower Shadow Function must be defined in a certain
range to cover all aero elements. Modify your Function to have a minimum X value lower
than the value specified in the error message.
Description of the message: Unknown Rotor Type to calculate the Diameter
Comments/Solution:
The rotor component type is not recognized. It is thus not possible to compute its diameter.
Type: Error
Description of the message: Tower Shadow Function in the 'Wind Turbine Assembly'
No method 'GetFunction'
Comments/Solution:
You have choose to use a given 'Tower Shadow Function' in the field 'Parameters' of the
Wind turbine Assembly but you have probably badly defined the function. If you do not
want to specify a user function, uncheck the box 'Use Tower shadow Function'.
Description of the message: Unknown Rotor Shaft Type 'Type_name' to calculate the Hub
Height
Comments/Solution:
The rotorshaft component type is not recognized. It is thus not possible to compute the hub
height. Refer to Samtech Headquarter.
Description of the message: Unknown Bedplate Type 'Type_name' to calculate the Hub
Height
Comments/Solution:
The bedplate component type is not recognized. It is thus not possible to compute the hub
Description of the message: Unknown Tower Type 'Type_name' to calculate the Hub
Height
Comments/Solution:
The tower component type is not recognized. It is thus not possible to compute the hub
Description of the message: Unknown Support Type 'Type_name' to calculate the Hub
Height
Comments/Solution:
The support component type is not recognized. It is thus not possible to compute the hub
Type: Warning
Description of the message: 'Message can differ depending on the context'
Comments/Solution:
The position of the Hub height from the ground is automatically calculated to check
coherency of the load case. It is calculated from parameters defined by the user in the
Wind Turbine itself, but also in the Support (if it exists), the Tower, the Bedplate, the
Rotor Shaft and the Rotor. However it could happen that one of these component are not
parametric but modelled with a Samcef (or Bacon, or Super element) component. In this
case it is not possible to run an automatic calculation of the hub height. Consequently
automatic checks related to the hub height cannot be done. To summarize this message
informs you that all checks have not been done, but it does not mean necessary that your
data are bad.
Description of the message: Unable to assess the height of the support
Comments/Solution:
A support is used but the related SE is not defined. Refer to Samtech Headquarter.
Type: Error
Description of the message: Controller Parameter File not found

Comments/Solution:
This error occures when you want to define a controller specific parameter file associated
to the loadcase (e.g. because the loadcase is directly managed by a SCADA controller).
You have ticked the corresponding option in the loadcase Miscellaneous tab, but you have
selected no file, or the selected file does not exist.
Type: Error
Description of the message: Rotor-name section num: Curve curve_name must be defined
with strictly increasing values
Comments/Solution:
This error is related to the Rotor section curves. Such functions must be defined with
scrictly increasing abscissas..
The specified curve does not fulfil that rule. Check your csv file values.
Type: Error
Description of the message: Rotor-name: section id : Curve name must be defined from
-180 to 180
Comments/Solution:
This error is related to the Rotor section curves. It is imperative that such curve range all
possible attack angles, from -180 to +180.
The specified curve does not fulfil that rule. Check your csv file and the abscissa factor
(values and units).
Type: Warning
Description of the message: Rotor-name: section id : Curve name has no Xunit defined in
the csv file. Default Solver Units system will be used.
Comments/Solution:
This warning is related to the Rotor section curves. Since no unit is defined, the Solver
Unit System will be considered. This can lead to problems if your csv file values do not
correspond to radians. It is advise to change your csv file or to adapt your xfactor.
Type: Warning
Description of the message: Loadcase 'name' - Tab Offshore: At least one group should
be defined
Comments/Solution:
If you use an Offshore loadcase you should specify on which group offshore loads will
be calculated. Select a pre-defined group or create at least one in the table 'User Defined
Selection'.
Description of the message: Loadcase 'name' has no 'initialValues'
Comments/Solution:
Description of the message: The argument is not the Wind Turbine SEA
Comments/Solution:
Description of the message: Controller SE(A) could not be found
Comments/Solution:
Description of the message: Controller has no 'Data' or 'Parameters' member
Comments/Solution:
Description of the message: Controller data has no 'Curves' member
Comments/Solution:
Type: Error
Description of the message: Reference node 'node' has not been found
Comments/Solution: In an offshore load case the reference node given is not part of the
model. Correct your data.
Type: Error
Description of the message: SEA has not been initialized. No adaptation performed
Comments/Solution:
4.26 Messages related to LoadcaseTranslationMethods

These messages are related to the Class LoadcaseTranslationMethods
ID
Description
Translation of S4WTloadcaseV3 is not correct due to a change in class

S4WTbladeAeroLoad
ID 1 - LoadcaseTranslationMethods
Type: Warning
Description of the message: Translation of S4WTloadcaseV3 is not correct due to a
change in class S4WTbladeAeroLoad
Comments/Solution:
This message could appear when loading an old model and a problem has been detected
during the translation method of the load case. Check that parameters of your load case are
correct - especially the option 'With Tower Shadow', 'User Tower Height' and 'Advanced
Options'. These parameters are related to aerodynamic elements.
4.27 Messages related to MasherBuilder

These messages are related to the Class MasherBuilder
ID
Description
1
2
3
4
Parameter must be a CaesamStd_DataSet.

SField component 'key' does not specify a location.
Resolving url 'name' without context
Too many (or none) sfieldDependencies found in name': Don't know
which to use.
ID 1 - MasherBuilder
Type: Error
Description of the message: Parameter must be a CaesamStd_DataSet.
Comments/Solution:
None
Description of the message: SField component 'key' does not specify a location.
Comments/Solution:
None
Type: Warning
Description of the message: Resolving url 'name' without context
Comments/Solution:
None
Description of the message: Too many (or none) sfieldDependencies found in name':
Don't know which to use.
Comments/Solution:
None
4.28 Messages related to MatrixUtilities

These messages are related to the Class MatrixUtilities
ID
Description
Two nodes are located at the same place: li=0
ID 1 - MatrixUtilities
Type: Error
Description of the message: Two nodes are located at the same place: li=0
4.29 Messages related to MonopileDisplayDriver

These messages are related to the Class MonopileDisplayDriver
ID
Description
Incoherency in external/internal diameters
ID 1 - MonopileDisplayDriver
Type: Error
Description of the message: Incoherency in external/internal diameters
Comments/Solution:
None
4.30 Messages related to OffshoreHydroCurveProcessor

These messages are related to the Class OffshoreHydroCurveProcessor
ID
Description
1
2
3
4
7
8
9
10
11
12
The context is not defined

The existing curve file is not defined
The curve file to create is not defined
The mesh neutral file is not defined
The mesh neutral file 'name' could not be opened
The neutral file 'filepath' does not contain a 'elnames' variable
The first curve could not be retrieved from the crv file
No abscissa is associated to the first curve of the crv file
No ordinate is associated to the first curve of the crv file
The node map is empty
ID 1 - OffshoreHydroCurveProcessor
Description of the message: The context is not defined
Comments/Solution:
None
Description of the message: The existing curve file is not defined
Comments/Solution:
None
Description of the message: The curve file to create is not defined
Comments/Solution:
None
Description of the message: The mesh neutral file is not defined
Comments/Solution:
None
Type: Error
Description of the message: The mesh neutral file 'name' could not be opened
Comments/Solution:
None
Type: Error
Description of the message: The neutral file 'filepath' does not contain a 'elnames'
variable
Comments/Solution:
None
Description of the message: The first curve could not be retrieved from the crv file
Comments/Solution:
None
Description of the message: No abscissa is associated to the first curve of the crv file
Comments/Solution:
None
Description of the message: No ordinate is associated to the first curve of the crv file
Comments/Solution:
None
Description of the message: The node map is empty
Comments/Solution:
None
4.31 Messages related to OffshoreLoadComputerForMecano

These messages are related to the Class OffshoreLoadComputerForMecano
ID
Description
6
7
8
Unable to open bank file 'filename'

Offshore -> Group Name 'groupName' not found
Node not found in the node map (node=noID element=elId
group=[groupName]) Skipped...
Reference node 'reference' not found
The parameter 'cm' (or 'cd') of the pseudo mesh (row index) must be
constant. Default value used is 1.
9
10
ID 6 - OffshoreLoadComputerForMecano
Type: Error
Description of the message: Unable to open bank file 'filename'
Type: Error
Description of the message: Offshore -> Group Name 'groupName' not found
Description of the message: Node not found in the node map (node=noID element=elId
group=[groupName]) Skipped...
Comments/Solution:
Type: Error
Description of the message: Reference node 'reference' not found
Type: Warning
Description of the message: The parameter 'cm' (or 'cd') of the pseudo mesh (row index)
must be constant. Default value used is 1.
Comments/Solution: You cannot use function to define cm (or cd) for hydrodynamic
element. Use a constant value.
4.32 Messages related to OffshoreWLcomputer

These messages are related to the Class OffshoreWLcomputer
ID
Description
Could not load WaveLoad DLL at path 'path'. Check Waveload is

correctly installed and if the dll is referenced in SWT environment.
variable
Error when running WaveLoad
Error No WaveLoad data
Unable to open bank file 'path'
Offshore Group Name 'name' not found
Node not found in the node map (node=id element=elID
group=[name])\nSkipped...
Reference node 'name' not found
Waveload results could not be found or reloaded
Caution: using the stream flow computed by WaveLoad...
Caution: using the stream flow without stream shear...
No analysis/loadcase/WL simulation duration can be found...
2
5
6
7
8
9
10
11
12
13
ID 1 - OffshoreWLcomputer
Type: Error
Description of the message: Could not load WaveLoad DLL at path 'path'. Check
Waveload is correctly installed and if the dll is referenced in SWT environment. variable
Comments/Solution:
SWT cannot find the file wl2.dll - related to Waveload. Possible reasons are:
You do not have an offshore licence
The path of the dll must be referenced in the SWT environment variables.
Type: Error
Description of the message: Error when running WaveLoad
Description of the message: Error No WaveLoad data
Type: Error
Description of the message: Unable to open bank file 'path'
Type: Error
Description of the message: Offshore
Group Name 'name' not found
Comments/Solution:
In the tab Offshore of the load case, the Group Name specified does not exist. For
parametric model, following names exist (depending on what you have selected for your
model):
BEDPLATE_ALL_ELEMENTS
HSCS_ALL_ELEMENTS
GENERATOR_ALL_ELEMENTS
ROTOR_ALL_ELEMENTS
MNSH_ALL_ELEMENTS
TOWER_ALL_ELEMENTS
SUPPORT_ALL_ELEMENTS
GBOX_ALL_ELEMENTS
NACELLE_ALL_ELEMENTS
If you have created your own Samcef model, you can use your own defined groups.
Rem.: this check is done only during a calculation and not when you click on the Check
button.
Description of the message: Node not found in the node map (node=id element=elID
group=[name])\nSkipped...
Type: Error
Description of the message: Reference node 'name' not found
Comments/Solution:
In the tab Offshore, you must define a reference node. The specified one seems not exist.
Check the spelling of the node.
Type: Error
Description of the message: Waveload results could not be found or reloaded
Comments/Solution:
None
Type: Warning
Description of the message: Caution: using the stream flow computed by WaveLoad...
Comments/Solution:
none
Type: Warning
Description of the message: Caution: using the stream flow without stream shear...
Comments/Solution:
None
Type: Error
Description of the message: No analysis/loadcase/WL simulation duration can be found...
Comments/Solution:
None
4.33 Messages related to PMsamcefStarterMethods

These messages are related to the Class PMsamcefStarterMethods
ID
Description
Unable to locate SAMCEF installation.
ID 1 - PMsamcefStarterMethods
Type: Error
Description of the message: Unable to locate SAMCEF installation.
4.34 Messages related to PMsfieldStarter

These messages are related to the Class PMsfieldStarter
ID
Description
Unable to locate SamcefField executable. Specified path was: path
ID 1 - PMsfieldStarter
Type: Error
Description of the message: Unable to locate SamcefField executable. Specified path
was: path
Comments/Solution:
None
4.35 Messages related to S4WTaeroLoadGenerator

These messages are related to the Class S4WTaeroLoadGenerator
ID
Description
1
2
3
4
5
7
8
Other Aero Group Name 'GroupName' not found

Output level is unknown
Connector node 'name' not found
Characteristic Length not well defined: value
Nacelle Length not well defined: value
Unexpected type for a SKTGlobalFunction: type
Problem to get topology for node1 id1 ; node 2 id2
ID 1 - S4WTaeroLoadGenerator
Type: Warning
Description of the message: Other Aero
Group Name 'GroupName' not found
Comments/Solution:
In the tab Other Aero of the load case, the Group Name specified does not exist. For
model):
HSCS_ALL_ELEMENTS
ROTOR_ALL_ELEMENTS
MNSH_ALL_ELEMENTS
TOWER_ALL_ELEMENTS
GBOX_ALL_ELEMENTS
button.
Description of the message: Output level is unknown
Comments/Solution:
None
Type: Error
Description of the message: Connector node 'name' not found
Comments/Solution:
In the load case in the tab Aerodynamic Supports a valid application point must be
specifided for the nacelle. The application selected has not been found in the model.
Type: Error
Description of the message: Characteristic Length not well defined: value
Comments/Solution:
In the load case in the tab Aerodynamic Supports aerodynamic elements have been
selected for the nacelle. The nacelle height has been badly defined. The value must be
strictly positive.
Type: Error
Description of the message: Nacelle Length not well defined: value
Comments/Solution:
In the load case in the tab Aerodynamic Supports aerodynamic elements have been
selected for the nacelle. The nacelle length has been badly defined. The value must be
strictly positive.
Description of the message: Unexpected type for a SKTGlobalFunction: type
Comments/Solution:
Allowed types are: CST or FCT.
Type: Warning
Description of the message: Problem to get topology for node1 id1 ; node 2 id2
Comments/Solution:
Problem to find the nodes inside the mesh.
4.36 Messages related to S4WTaeroLoadGenerator_0

These messages are related to the Class S4WTaeroLoadGenerator_0
ID
Description
1
2
3
Other Aero Group Name 'GroupName' not found

Output level is unknown
Aero Loads Translation: in previous version the 'nacelle' was
defined by: selection; diameter; cd; Now it is defined by: connector;
characteristicLength, lift, drag, moment
ID 1 - S4WTaeroLoadGenerator_0
Type: Warning
Description of the message: Other Aero
Group Name 'GroupName' not found
Comments/Solution:
In the tab Other Aero of the load case, the Group Name specified does not exist. For
model):
HSCS_ALL_ELEMENTS
ROTOR_ALL_ELEMENTS
MNSH_ALL_ELEMENTS
TOWER_ALL_ELEMENTS
GBOX_ALL_ELEMENTS
button.
Description of the message: Output level is unknown
Comments/Solution:
None
Type: Warning
Description of the message: Aero Loads Translation: in previous version the 'nacelle' was
defined by: selection; diameter; cd; Now it is defined by: connector; characteristicLength,
lift, drag, moment
Comments/Solution:
This message occurs if we load an old model where the aero elements have been selected
for the nacelle. The way these elements are generated has now change. Consequently
results can now be different that those obtained on a previous version.
4.37 Messages related to S4WTCaesamTableComposer

These messages are related to the Class S4WTCaesamTableComposer
ID
Description
Unable to get CaesamStd_Model: EditorData.getCaesamApiObject

returned null.
ID 1 - S4WTCaesamTableComposer
Type: Warning
Description of the message: Unable to get CaesamStd_Model:

EditorData.getCaesamApiObject returned null.
Comments/Solution:
None.
4.38 Messages related to S4WTcreateELA

These messages are related to the Class S4WTcreateELA
ID
Description
1
2
3
4
5
6
7
Parameter is not a Caesam_ObjectMap

Parameter has no key 'Selection'
Selection was not a CaesamStd_ItemArray
Please select one or more analyses or flag analyses for ELA
Operation at index id is ignored because it's not an operation
Unable to load result data. Invalid analysis type: 'type', analysis name:
'name'
No results found for analysis: 'name'
NULL parameter resdata_ to buildELA
No analyses present
8
9
10
11
ID 1 - S4WTcreateELA
Description of the message: Parameter is not a Caesam_ObjectMap
Description of the message: Parameter has no key 'Selection'
Description of the message: Selection was not a CaesamStd_ItemArray
Type: Error
Description of the message: Please select one or more analyses or flag analyses for ELA
Comments/Solution:
This message occurs if you select Caesam (in the tree) and then click on the button 'Create
Extreme Load Analysis' without any load case selected with the flag 'Ultimate Load case'.
Check for each load case (related to the analysis that you have created) if in the Tab Type,
you have at least one 'Ultimate Load Case' selected. If not, it is impossible to create an
Extreme Load Analysis.
Type: Warning
Description of the message:
Type: Error
Description of the message: Operation at index id is ignored because it's not an operation
Type: Error
Description of the message: Unable to load result data. Invalid analysis type: 'type',
analysis name: 'name'
Type: Error
Description of the message: No results found for analysis: 'name'
Type: Error
Description of the message: NULL parameter resdata_ to buildELA
Type: Warning
Description of the message: No analyses present
4.39 Messages related to S4WTcreateFatigue

These messages are related to the Class S4WTcreateFatigue
ID
Description
1
2
3
4
5
6
7

Please select one or more analyses or flag analyses for Fatigue
None
'name'
NULL parameter resdata_ to build FATIGUE
No analyses present
8
9
10
11
12
ID 1 - S4WTcreateFatigue
Type: Error
Description of the message: Please select one or more analyses or flag analyses for
Fatigue
Comments/Solution:
Fatigue Analysis' without any load case selected with the flag 'Fatigue Load case'. Check
for each load case (related to the analysis that you have created) if in the Tab Type, you
have at least one 'Fatigue Load Case' selected. If not, it is impossible to create a Fatigue
Analysis.
Type: Warning
Description of the message: None
Type: Error
Type: Error
Type: Error
Type: Error
Description of the message: NULL parameter resdata_ to build FATIGUE
Type: Warning
Type: Error
S4WTloadcaseV3 type
Comments/Solution: The analyse selected to do the Fatigue analyse has an inappropriate

type.
4.40 Messages related to S4WTcreateRsup

These messages are related to the Class S4WTcreateRsup
ID
Description
1
2
3
4
5
Parameter is not a Caesam_ObjectMap.

Parameter has no key 'Selection'.
Selection was not a CaesamStd_ItemArray.
Please select one or more analyses or flag analyses for Rsup.
The following analyses cannot be used for an Extreme Load analysis
name
ID 1 - S4WTcreateRsup
Description of the message: Parameter is not a Caesam_ObjectMap.
Comments/Solution:
None
Description of the message: Parameter has no key 'Selection'.
Comments/Solution:
None
Description of the message: Selection was not a CaesamStd_ItemArray.
Comments/Solution:
None
Type: Error
Description of the message: Please select one or more analyses or flag analyses for Rsup.
Comments/Solution:
None
Type: Warning
Description of the message: The following analyses cannot be used for an Extreme Load
analysis name
Comments/Solution:
None
4.41 Messages related to S4WTcreateVLDurability

These messages are related to the Class S4WTcreateVLDurability
ID
Description
1
2
3
4
5
6
7

Please select one or more analyses or flag analyses for VL Durablity
None
'name'
NULL parameter resdata_ to build VL Durability
No analyses present
8
9
10
ID 1 - S4WTcreateVLDurability
Type: Error
Description of the message: Please select one or more analyses or flag analyses for VL
Durablity
Comments/Solution:
VL Durability Analysis' without any load case selected with the flag 'VL Durability Load
case'. Check for each load case (related to the analysis that you have created) if in the Tab
Type, you have at least one 'VL Durability Load Case' selected. If not, it is impossible to
create a VL Durability Analysis.
Type: Warning
Description of the message: None
Type: Error
Type: Error
Description of the message: NULL parameter resdata_ to build VL Durability
Type: Warning
Type: Error
S4WTloadcaseV3 type
Comments/Solution: The analyse selected to do the VL Durability analyse has an
inappropriate type.
4.42 Messages related to S4WTcrvTool

These messages are related to the Class S4WTcrvTool
ID
Description
xseries not found in crv crv_name
ID 1 - S4WTcrvTool
Type: Error
Description of the message: xseries not found in crv crv_name

Comments/Solution:
The crv has no xseries. Check that the analysis has correctly been run.
4.43 Messages related to S4WTextremeLoadAnalysis

These messages are related to the Class S4WTextremeLoadAnalysis
ID
Description
1
2
3
4
5
7
8
9
10
11
15
Model files not found in any dependent analysis.

Analysis not present in analysis data.
No results found for analysis: \name\.
Unable to find analysis from dataset.
No utilities found for analysis: \name\.
Copying file \filename\ into \pathname\
Unable to copy \filename\: file doesn't exist.
Waiting for file name to be copied
No resultsRootDir found for analysis: \name\.
No manifest file found for extreme load analysis \ name\.
Unable to obtain result data for \name\. Please refer to analysis for more
details.
No sensors selected. (Nothing to do.)
Not yet implemented, returning NULL
16
99
ID 1 - S4WTextremeLoadAnalysis
Type: Error
Description of the message: Model files not found in any dependent analysis.
Description of the message: Analysis not present in analysis data.
Type: Error
Description of the message: No results found for analysis: \name\.
Type: Warning
Description of the message: Unable to find analysis from dataset.
Type: Error
Description of the message: No utilities found for analysis: \name\.
Type: Info
Description of the message: Copying file \filename\ into \pathname\
Type: Error
Description of the message: Unable to copy \filename\: file doesn't exist.
Type: Log
Description of the message: Waiting for file name to be copied
Type: Error
Description of the message: No resultsRootDir found for analysis: \name\.
Type: Error
Description of the message: No manifest file found for extreme load analysis \ name\.
Comments/Solution: This is probably caused by errors in that analysis. Please run it again
and check closely for any errors that may have occurred.
Type: Warning
Description of the message: Unable to obtain result data for \name\. Please refer to
analysis for more details.
Type: Warning
Description of the message: No sensors selected. (Nothing to do.)
Description of the message: Not yet implemented, returning NULL
4.44 Messages related to S4WTfatigueAnalysis

These messages are related to the Class S4WTfatigueAnalysis
ID
Description
1
2

ID 1 - S4WTfatigueAnalysis
Comments/Solution:
The fatigue analysis does not contain any reference to transient analysis. This should not
appear since a fatigue analysis is built from a set of transient analysis. Refer to Samtech
Headquarter.
ID 2 - S4WTfatigueAnalysis
Type: Error
Comments/Solution:
Run first the indicated Transient analysis before to run the fatigue analysis.
4.45 Messages related to S4WTinterpolFoilSections

ID
Description
1
2
'Object_name' does not contain any member 'name'

Interpolation table of the Aerofoil Section 'name' must contain at least
one Aerofoil Data
Aerofoil Data 'name': the column num contains values with different
Reynolds number
The Function 'name' defined in the Foil Section 'name' must have the
dimension PLANE ANGLE for the X Dimension
Column 'num' of the Interpolation Table: Aerofoil Data 'name' has a
thickness already defined in another Aerofoil Data of the Foil Section
'name'
Interpolation table of the Foil Section ' name' for the Blade Station num:
Column 'num_i' and column 'num_j' have the same Reynolds number
Blade Station Table is null
Blade Property EO is null
3
4
5
6
7
8
ID 1 - S4WTinterpolFoilSections

Description of the message: 'Object_name' does not contain any member 'name'
Comments/Solution:
The message can differ depending on the context. Refer to Samtech Headquarter.
Type: Error
Description of the message: Interpolation table of the Aerofoil Section 'name' must
contain at least one Aerofoil Data
Comments/Solution:
Check that the specified Aerofoil Section is well defined.
Type: Error
Description of the message: Aerofoil Data 'name': the column num contains values with
different Reynolds number
Comments/Solution:
The Aerofoil Data contains a matrix. A column correspond to a unique Reynolds number.
Consequently you can not have different Reynolds number used in the same column.
Correct your data to avoid problems during the interpolation of the Lift, Drag, and Moment
coefficient curves. Notice that for the version SWT 3.2, you cannot use different columns.
Only one Reynolds number must be defined - so only one column must exist.
Type: Error
Description of the message: The Function 'name' defined in the Foil Section 'name' must
have the dimension PLANE ANGLE for the X Dimension
Comments/Solution:
The specified function gives coefficient values in function of the attack angle.
Consequently the X dimension must be PLANE ANGLE. Correct your data to avoid
problems during the interpolation of the Lift, Drag, and Moment coefficient curves
Type: Error
Description of the message: Column 'num' of the Interpolation Table: Aerofoil Data
'name' has a thickness already defined in another Aerofoil Data of the Foil Section 'name'
Comments/Solution:
In a column we must have different thicknesses defined because for each column, an
interpolation is done based on the thickness. Consequently is not authorized to find the
same thickness for a given column. Notice that for the version SWT 3.2, you cannot use
different columns. Only one Reynolds number must be defined - so only one column must
exist.
Type: Error
Description of the message: Interpolation table of the Foil Section ' name' for the Blade
Station num: Column 'num_i' and column 'num_j' have the same Reynolds number
Comments/Solution:
Consequently is not authorized to find the same Reynolds value in different columns.
Notice that for the version SWT 3.2, you cannot use different columns. Only one Reynolds
number must be defined - so only one column must exist.
Type: Error
Description of the message: Blade Station Table is null
Comments/Solution:
None.
Type: Error
Description of the message: Blade Property EO is null
Comments/Solution:
None.
4.46 Messages related to S4WTliftDragMomCoeff

ID
Description
1
2
3
4
liftDragMomCoeff has an unknown format

Method GetFunction should return a CaesamPrm_DiscreteFunction
Object 'Name' is Null
Unknown function name
ID 1 - S4WTliftDragMomCoeff
Description of the message: liftDragMomCoeff has an unknown format
Comments/Solution:
To define the Lift, Drag, and Moment curves, different format can be defined (one file
by curve, or all curves in the same files). The specified format seems unknown. Refer to
Samtech Headquarter.
Description of the message: Method GetFunction should return a

CaesamPrm_DiscreteFunction
Comments/Solution:
Description of the message: Object 'Name' is Null
Comments/Solution:
Description of the message: Unknown function name
Comments/Solution:
4.47 Messages related to S4WTlinkAnalysis

These messages are related to the Class S4WTlinkAnalysis
ID
Description
Expected a WindTurbineSEA for analysis support, found a 'Type'
ID 1 - S4WTlinkAnalysis
Type: Info
Description of the message: Expected a WindTurbineSEA for analysis support, found a
'Type'
4.48 Messages related to S4WTloadGenerator

These messages are related to the Class S4WTloadGenerator
ID
Description
1
2
3
4
5
6
7
8
9
10
Declaration of a null analysis

The Wind Turbine attached to the analysis 'name' is null
The context attached to the analysis 'name' is null
No analysis is attached to the load generator
One or several errors occurred when preparing the load generation
One or several errors occurred when retrieving the mesh
The dataset is null
The loadcaseset is null
The loadcase is null
Some errors occurred when running BACON: message
ID
Description
11
12
13
14
15
16
17
Declaration of a null dataset

The Wind Turbine attached to the dataset 'name' is null
The context attached to the dataset 'name' is null
Problem to find the 'super' SE related to superElementName
Impossible to find the EO 'super' in superElementName
Impossible to find the EO 'pseudoMesh' in superElementName
Problem to find the superSEMemberName related to
superElementName
ID 1 - S4WTloadGenerator
Description of the message: Declaration of a null analysis
Description of the message: The Wind Turbine attached to the analysis 'name' is null
Description of the message: The context attached to the analysis 'name' is null
Description of the message: No analysis is attached to the load generator
Type: Error
Description of the message: One or several errors occurred when preparing the load
generation
Type: Error
Description of the message: One or several errors occurred when retrieving the mesh
Description of the message: The dataset is null

Description of the message: The loadcaseset is null
Type: Error
Description of the message: The loadcase is null
Type: Error
Description of the message: Some errors occurred when running BACON: message
Description of the message: Declaration of a null dataset
Description of the message: The Wind Turbine attached to the dataset 'name' is null
Description of the message: The context attached to the dataset 'name' is null
Type: Error
Description of the message: Problem to find the 'super' SE related to superElementName
Comments/Solution:
In the load case in the tab Aerodynamic Supports a Super Element SE Name has been
entered in the related table. This name is not found in the model. Enter a coherent name if
you want to use aerodynamic elements on a super element.
Type: Error
Description of the message: Impossible to find the EO 'super' in superElementName
Comments/Solution:
entered in the related table. The name entered doesn't correspond to a super element. Enter
a coherent name if you want to use aerodynamic elements on a super element.
Type: Error
Description of the message: Impossible to find the EO 'pseudoMesh' in
superElementName
Comments/Solution:
entered in the related table. The name entered correspond to a element which doesn't have
an EO 'Pseudo Mesh'. Enter a coherent name if you want to use aerodynamic elements on a
super element.
Description of the message: Problem to find the superSEMemberName related to
superElementName
4.49 Messages related to S4WTmodelChecker

These messages are related to the Class S4WTmodelChecker
ID
Description
1
2
3
4
5
6
7
8
9
11
12
13
14
15
16
17
dataset is null...
item is NULL...
context associated to the item 'item name' is NULL...
No map returned by the url finder...
No keys found in the url map...
object associated to 'key' is not an url or is null...
the following path is left blank : 'key'
the following file does not exist: 'filename found at path='key'
No map returned by the EO finder...
No keys found in the EO map...
object associated to 'key' is not an EO or is null...
class associated to EO 'name' (type 'type') is null...
the class associated to EO 'name' (type 'type') has no members...
in EO 'key' (type 'type'): the member 'name' is not defined
SEA is NULL...
the SEA 'name' has no connection table
ID
Description
18
19
20
21
22
23
24
25
26
27
28
in SEA 'name': CP #id is null

CP 'name' has no connector
in CP 'name': connector #id is null
Connection line #id is null
Connection line #id: CP component 1 is null
Connection line #id: CP component 2 is null
Connection line #id: connector 1 is null
Connection line #id: connector 2 is null
Connection line #id: CP component 1 has no associated topological data
Connection line #id: CP component 2 has no associated topological data
Connection line #id: distance between connector (distance) is larger
than the allowed tolerance (tolerance)
Connection line #id: connector 1 does not actually exist!
Connection line #id: connector 2 does not actually exist!
unusedConnectors - connector is null...
unusedConnectors - CP is null...
Blade connector 'name' is not used. Probable mismatch between rotor
and mainshaft topology
Hub connector 'name' is not used. Probable mismatch between rotor and
mainshaft topology
Tower connector 'name' is not used nor fixed...
Tower connector 'name' is not used. Check that it is fixed...
Connector 'name' of component 'name' is not used...
Connection Table: cpName of the row#id must be at least once in the
Right part in upper rows
LoadCaseSet is null...
Connection Table: Connector name is found twice in the Connection
Table
Monopile connector 'name' is not used nor fixed...
Monopile connector 'name' is not used. Check that it is fixed...
Jacket connector 'name' is not used nor fixed...
Jacket connector 'name' is not used. Check that it is fixed...
No Loadcase...
in SEA 'seaName': CP #number 'cpName' is not attached
Component #id of the sea name is null
Direct drive component must have at least one bearing
Number of bearings in the Frame (id1) must be equal to number of
bearings in the Hub (id2)
Bearing Frame - Generator: Incoherence for the 'Front' bearing
Bearing Frame - Generator: Incoherence for the 'Back' bearing
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
ID 1 - S4WTmodelChecker
Description of the message: dataset is null...
Description of the message: item is NULL...
Type: Warning
Description of the message: context associated to the item 'item name' is NULL...
Description of the message: No map returned by the url finder...
Description of the message: No keys found in the url map...
Description of the message: object associated to 'key' is not an url or is null...
Type: Warning
Description of the message: the following path is left blank : 'key'
Type: Warning
Description of the message: the following file does not exist: 'filename found at path='key'
Description of the message: No map returned by the EO finder...
Description of the message: No keys found in the EO map...
Description of the message: object associated to 'key' is not an EO or is null...
Description of the message: class associated to EO 'name' (type 'type') is null...
Description of the message: the class associated to EO 'name' (type 'type') has no
members...
Type: Error
Description of the message: in EO 'key' (type 'type'): the member 'name' is not defined
Description of the message: SEA is NULL...
Type: Warning
Description of the message: the SEA 'name' has no connection table
Description of the message: in SEA 'name': CP #id is null
Type: Warning
Description of the message: CP 'name' has no connector
Description of the message: in CP 'name': connector #id is null
Type: Error
Description of the message: Connection line #id is null
Type: Error
Description of the message: Connection line #id: CP component 1 is null
Type: Error
Description of the message: Connection line #id: CP component 2 is null
Type: Error
Description of the message: Connection line #id: connector 1 is null
Type: Error
Description of the message: Connection line #id: connector 2 is null
Type: Warning
Description of the message: Connection line #id: CP component 1 has no associated
topological data
Type: Warning
Description of the message: Connection line #id: CP component 2 has no associated

topological data
Type: Warning
Description of the message: Connection line #id: distance between connector (distance) is
larger than the allowed tolerance (tolerance)
Comments/Solution:
Try to modify distances/parameters of related SEA to solve the problem. Eventually you
can also increase the tolerance if it is acceptable.
Type: Error
Description of the message: Connection line #id: connector 1 does not actually exist!
Type: Error
Description of the message: Connection line #id: connector 2 does not actually exist!
Description of the message: unusedConnectors - connector is null...
Description of the message: unusedConnectors - CP is null...
Type: Error
Description of the message: Blade connector 'name' is not used. Probable mismatch
between rotor and mainshaft topology
Type: Error
Description of the message: Hub connector 'name' is not used. Probable mismatch
between rotor and mainshaft topology
Type: Error
Description of the message: Tower connector 'name' is not used nor fixed...
Type: Warning
Description of the message: Tower connector 'name' is not used. Check that it is fixed...
Type: Warning
Description of the message: Connector 'name' of component 'name' is not used...
Type: Error
Description of the message: Connection Table: cpName of the row#id must be at least
once in the Right part in upper rows
Comments/Solution:
The order of rows in Connection Table is very important to build the model. The starting
point to build the model is the Left part specified in the first row. The Right part is linked
to this element. For below lines, you must check that the Left Part element must be found
in previous line in the Right Part column. If needed, insert new rows in the Connection
Table or inverse side of rows with the button
Description of the message: LoadCaseSet is null...
Type: Error
Description of the message: Connection Table: Connector name is found twice in the
Connection Table
Comments/Solution:
You can only have one connector in the Connection Table to avoid incoherency in the
Connection Table.
Type: Error
Description of the message: Monopile connector 'name' is not used nor fixed...
Comments/Solution:
None.
Type: Warning
Description of the message: Monopile connector 'name' is not used. Check that it is
fixed...
Comments/Solution:
None.
Type: Error
Description of the message: Jacket connector 'name' is not used nor fixed...
Comments/Solution:
None.
Type: Warning
Description of the message: Jacket connector 'name' is not used. Check that it is fixed...
Comments/Solution:
None.
Type: Error
Description of the message: No Loadcase...
Comments/Solution:
None.
Type: Error
Description of the message: in SEA 'seaName': CP #number 'cpName' is not attached
Comments/Solution:
None.
Type: Warning
Description of the message: Component #id of the sea name is null
Comments/Solution:
None.
Type: Error
Description of the message: Direct drive component must have at least one bearing
Comments/Solution:
Select at least one bearing for the direct drive component.
Type: Error
Description of the message: Number of bearings in the Frame (id1) must be equal to
number of bearings in the Hub (id2)
Comments/Solution:
Check coherence for number of bearings between Direct Frame and Direct Hub.
Type: Error
Description of the message: Bearing Frame - Generator: Incoherence for the 'Front'
bearing
Comments/Solution:
Check coherence for number of bearings between Direct Frame and Direct Generator Front side.
Type: Error
Description of the message: Bearing Frame - Generator: Incoherence for the 'Back'
bearing
Comments/Solution:
Check coherence for number of bearings between Direct Frame and Direct Generator Back side.
4.50 Messages related to S4WTorientationCollection

These messages are related to the Class S4WTorientationCollection
ID
Description
Undefined orientation 'orientation_name' is used by sensor

sensor_name
Unable to generate key-defined orientations: WindTurbine (arg) was
NULL.
ID 1 - S4WTorientationCollection
Type: Error
Description of the message: Undefined orientation 'orientation_name' is used by sensor
sensor_name
ID 2 - S4WTorientationCollection
Type: Error
Description of the message: Unable to generate key-defined orientations: WindTurbine
(arg) was NULL.
4.51 Messages related to S4WTPostProcessAnalysisV

These messages are related to the Class S4WTPostProcessAnalysisV
ID
Description
1
3
4

Unable to find the analysis from dataset.
Unable to obtain result data for 'name' Please refer to analysis for more
details.
No sensors selected. (Nothing to do.)
Not implemented yet, returning NULL
5
6
ID 1 - S4WTPostProcessAnalysisV
Type: Error
Comments/Solution:
The analysis does not contain any reference to transient analysis. This should not appear
since that kind of analysis is built from a set of transient analysis.
Type: Warning
Description of the message: Unable to find the analysis from dataset.
Comments/Solution:
None
Type: Error
Description of the message: Unable to obtain result data for 'name' Please refer to
analysis for more details.
Comments/Solution:
Some transient analysis have no result. Check that they have been successfully run.
Type: Warning
Description of the message: No sensors selected. (Nothing to do.)
Comments/Solution:
You must select at least one sensor before to run the analysis.
Description of the message: Not implemented yet, returning NULL
Comments/Solution:
4.52 Messages related to S4WTrsupData

These messages are related to the Class S4WTrsupData
ID
Description
1
2
3
4
5
No transient analyses found.

The associated transient analyses has no result directory.
No time neutral file found in the associated transient analyses.
Could not open the No time neutral file 'name'
Number of time steps and number of times are different in neutral file
'name'
No time step found in the given range
Bad step value (must be positive)
Bad time interval (tmin must be lower than tmax)
No Wind Turbine SEA found.
No Wind Turbine SEA found.
The selected component is not of a 'Super-Element' type
'FEdata' member is null
The super-element id is not well defined
6
7
8
9
10
11
12
13
ID 1 - S4WTrsupData
Type: Error
Description of the message: No transient analyses found.
Comments/Solution:
None
ID 2 - S4WTrsupData
Type: Error
Description of the message: The associated transient analyses has no result directory.
Comments/Solution:
None
ID 3 - S4WTrsupData
Type: Error
Description of the message: No time neutral file found in the associated transient
analyses.
Comments/Solution:
None
ID 4 - S4WTrsupData
Type: Error
Description of the message: Could not open the No time neutral file 'name'
Comments/Solution:
None
ID 5 - S4WTrsupData
Type: Error
Description of the message: Number of time steps and number of times are different in
neutral file 'name'
Comments/Solution:
None
ID 6 - S4WTrsupData
Type: Error
Description of the message: No time step found in the given range
Comments/Solution:
None
ID 7 - S4WTrsupData
Type: Error
Description of the message: Bad step value (must be positive)
Comments/Solution:
None
ID 8 - S4WTrsupData
Type: Error
Description of the message: Bad time interval (tmin must be lower than tmax)
Comments/Solution:
None
ID 9 - S4WTrsupData
Type: Error
Description of the message: No Wind Turbine SEA found.
Comments/Solution:
None
ID 10 - S4WTrsupData
Type: Error
Description of the message: No Wind Turbine SEA found.
Comments/Solution:
None
Type: Error
Description of the message: The selected component is not of a 'Super-Element' type
Comments/Solution:
None
Description of the message: 'FEdata' member is null
Comments/Solution:
None
Type: Error
Description of the message: The super-element id is not well defined
Comments/Solution:
none
4.53 Messages related to S4WTserver

These messages are related to the Class S4WTserver
ID
Description
1
2
3
4
No wind turbine SEA

Component #num of the sea_name is null
No tower connector can be found
No rotor connector can be found
ID 1 - S4WTserver
Type: Error
Description of the message: No wind turbine SEA
Comments/Solution:
None
ID 2 - S4WTserver
Type: Warning
Description of the message: Component #num of the sea_name is null
Comments/Solution:
None
ID 3 - S4WTserver
Type: Error
Description of the message: No tower connector can be found
Comments/Solution:
The connectors TOWER_FOUNDATION_LINK_NODE and
YAW_BEDPL_LINK_NODE seems not exist.
ID 4 - S4WTserver
Type: Error
Description of the message: No rotor connector can be found
Comments/Solution:
The connectors MNSH_MB1_LINK_NODE and HUB_BLADES_LINK_NODE seems
not exist.
4.54 Messages related to S4WTtransientPost

These messages are related to the Class S4WTtransientPost
ID
Description
Error updating sensor definitions: message
ID
Description
Error selecting sensors: message
ID 1 - S4WTtransientPost
Type: Warning
Description of the message: Error updating sensor definitions: message
Comments/Solution:
A serious error has occured during a step which tries to connect sensors with the finite
element model nodes and elements. This can happens e.g. if the F.E. analysis has failed
early and no result file can be found. This error usually results from a former one.
ID 2 - S4WTtransientPost
Type: Error
Description of the message: Error selecting sensors: message
Comments/Solution:
A serious error has occured during a step which tries to retrieve the selected sensors of the
analysis.
4.55 Messages related to S4WTVLDurabilityAnalysis

These messages are related to the Class S4WTVLDurabilityAnalysis
ID
Description
1
2

ID 1 - S4WTVLDurabilityAnalysis
Comments/Solution:
The VL Durability analysis does not contain any reference to transient analysis. This
should not appear since a VL Durability analysis is built from a set of transient analysis.
ID 2 - S4WTVLDurabilityAnalysis
Type: Error
Comments/Solution:
Run first the indicated Transient analysis before to run the VL Durability analysis.
4.56 Messages related to SEALibraryModel

These messages are related to the Class SEALibraryModel
ID
Description
1
2
3
4
5
6
7
The path 'name' does not specify a directory

The path 'name' does not exist
User component at 'name' contains errors: 'error messages'
File 'name' contains errors: 'error messages'
File 'name' does not exist
An error occurs during reading line 'line' in file 'name'
The following file 'name' contains errors. Please see the log for details.
ID 1 - SEALibraryModel
Type: Error
Description of the message: The path 'name' does not specify a directory
Comments/Solution:
None.
Type: Error
Description of the message: The path 'name' does not exist
Comments/Solution:
None.
Type: Warning
Description of the message: User component at 'name' contains errors: 'error messages'
Comments/Solution:
See error message(s) for further information.
Type: Warning
Description of the message: File 'name' contains errors: 'error messages'
Comments/Solution:
See error message(s) for further information.
Type: Warning
Description of the message: File 'name' does not exist
Comments/Solution:
None.
Type: Warning
Description of the message: An error occurs during reading line 'line' in file 'name'
Comments/Solution:
None.
Type: Warning
Description of the message: The following file 'name' contains errors. Please see the log
for details.
Comments/Solution:
None.
4.57 Messages related to SensorGlossarySelectionEditor

These messages are related to the Class SensorGlossarySelectionEditor
ID
Description
1
2
The sensor file selected 'filename' does not have the ccl extension
Unable to load the sensor file 'filename'
ID 1 - SensorGlossarySelectionEditor
Type: Warning
Description of the message: The sensor file selected 'filename' does not have the ccl
extension
Comments/Solution:
To add user sensor(s), it is recommended to use a file with the extension ccl. Notice that
other kind of file can work but they must respect the same syntax than a ccl file.
ID 2 - SensorGlossarySelectionEditor
Type: Error
Description of the message: Unable to load the sensor file 'filename'
Comments/Solution:
Check than the syntax inside your file is correct.
4.58 Messages related to SFieldComponentWorker

These messages are related to the Class SFieldComponentWorker
ID
Description
ID
Description
2
3
4
5
Error in GetAssemblyBankFileName: List of error messages

Object type mismatch: expected PMsfieldComponentMasher
Resolving url 'url name' without context
ID 1 - SFieldComponentWorker
Type: Error
Comments/Solution:
None
Type: Error
Description of the message: Error in GetAssemblyBankFileName: List of error messages
Comments/Solution:
An error occurred when we try to get the name of the bank file.
Type: Error
Comments/Solution:
An error has occurred during the Post Process Operation.
Type: Error
Description of the message: Object type mismatch: expected PMsfieldComponentMasher
Comments/Solution:
None
Type: Warning
Description of the message: Resolving url 'url name' without context
Comments/Solution:
None
4.59 Messages related to SfieldSamcefWorker

These messages are related to the Class SfieldSamcefWorker
ID
Description
1
2
3
4
5
Object type mismatch: expected PMsfieldSamcefMasher

Dependency not found: path
Error reported by FEMWPexecution.CreateFile: List of error messages
ID 1 - SfieldSamcefWorker
Description of the message: Object type mismatch: expected PMsfieldSamcefMasher
Comments/Solution:
None
Type: Error
Comments/Solution:
None
Type: Error
Description of the message: Dependency not found: path
Comments/Solution:
None
Type: Error
Description of the message: Error reported by FEMWPexecution.CreateFile: List of error
messages
Comments/Solution:
An error occurred during the creation of a file with FemWord
Type: Error
Comments/Solution:
None
4.60 Messages related to SKTEelaWorker

These messages are related to the Class SKTEelaWorker
ID
Description
1
2
Nothing to do, no analysis results present.

Treating 'n' analyses.
ID 1 - SKTEelaWorker
Type: Warning
Description of the message: Nothing to do, no analysis results present.
ID 2 - SKTEelaWorker
Type:
Info
Description of the message: Treating 'n' analyses.
4.61 Messages related to SKTEresultDataExplorerV

These messages are related to the Class SKTEresultDataExplorerV
ID
Description
Duplicate sensor \label\ found in sensor list, ignoring.
ID 1 - SKTEresultDataExplorerV
Type: Warning
Description of the message: Duplicate sensor \label\ found in sensor list, ignoring.
4.62 Messages related to SKTFcrvData

These messages are related to the Class SKTFcrvData
ID
Description
Fatigue parameter End Time must be null or strictly greater than Tstart.
The crv duration is maybe lower than Tstart.
Analysis duration must be null or strictly greater than Tstart
ID 1 - SKTFcrvData
Type: Error
Description of the message: Fatigue parameter End Time must be null or strictly greater
than Tstart. The crv duration is maybe lower than Tstart.
Comments/Solution:
Check that your crv length is greater than TStart. Check that Tstart is lower than End
Time.
ID 2 - SKTFcrvData
Type: Error
Description of the message: Analysis duration must be null or strictly greater than Tstart
Comments/Solution:
Check your crv length. It cannot be lower than Tstart. Check also analysis duration.
4.63 Messages related to SKTFcsvTableWriter

These messages are related to the Class SKTFcsvTableWriter
ID
Description
File path too long (path_length); Windows limitation 256 characters) Select a shorter working directory: path
ID 1 - SKTFcsvTableWriter
Type: Error
Description of the message: File path too long (path_length); Windows limitation 256
characters) - Select a shorter working directory: path
Comments/Solution:Some results are saved in csv files on the computer. However on
Windows the maximum path length is 256 characters. Csv paths created can be long
and sometimes reach this limitation. To avoid this you should work in a shorter working
directory - for example c:/tmp/
4.64 Messages related to SKTFfatigueWorker

These messages are related to the Class SKTFfatigueWorker
ID
Description
1
2
5

Treating 'x' analyses.
S4WTfatigueRange does not contain the enumeration
'RangeChoiceValue'
No sensor selected
Problem to open a CRV file
6
7
ID 1 - SKTFfatigueWorker
Type: Error
Comments/Solution: Check that the analysis exists and has been run.
Type: Info
Description of the message: Treating 'x' analyses.

Comments/Solution:
Just for your information: how many transient analyses are processes by the fatigue
analysis
Type: Error
Description of the message: S4WTfatigueRange does not contain the enumeration
'RangeChoiceValue'
Comments/Solution:
By now the enumeration value should be 'range' or 'amplitude'.
Type: Warning
Description of the message: No sensor selected
Comments/Solution:
Select at least one sensor before to run the fatigue analysis.
Type: Error
Description of the message: Problem to open a CRV file
Comments/Solution:
This probably occurs because at least one transient analysis used in the fatigue analysis
has been deleted - and consequently the corresponding main.crv curve file no longer
exists.
4.65 Messages related to SKTUtools

These messages are related to the Class SKTUtools
ID
Description
Impossible to get super Translation method for class classname
ID 1 - SKTUtools
Type: Error
Description of the message: Impossible to get super Translation method for class
classname
Comments/Solution:
4.66 Messages related to SKTVLExtract3dxml

These messages are related to the Class SKTVLExtract3dxml
ID
Description
1
2
Impossible to find the file 'file'. 3DXML file will not be created.
Impossible to find the 3DXML OLE object in the Excel File 'file'.
3DXML file will not be created.
Impossible to find the legend (png image) in the Excel File 'file'
Impossible to extract the 3DXML OLE object from the Excel File 'file'.
3DXML file will not be created.
Impossible to extract the legend (png image) from the Excel File 'file'.
Impossible to delete the Excel File 'file'.
The following path 'file' cannot be translated in a valid URL. Correct
your 'Durability Analysis Name' or your 'Combine Events Case name'
3
4
5
6
7
ID 1 - SKTVLExtract3dxml
Type: Error
Description of the message: Impossible to find the file 'file'. 3DXML file will not be
created.
Comments/Solution: To extract 3DXML from Virtual.Lab it is necessary to create an
Excel file to copy/paste the 3DXML file inside. Then the 3DXML can be extracted and
viewed in SWT. This problem can occur when we cannot open the Excel file. Possible
reasons:
The xlsx file has not been created due to an error in Virtual.Lab
The file is already opened by another process
Check if some Excel processes are not running on your machine. Close all of them before
to re-run a VL Durability Analysis.
Description of the message: Impossible to find the 3DXML OLE object in the Excel File
'file'. 3DXML file will not be created.
viewed in SWT. This problem can occur when we cannot find the 3DXML object inside
the Excel file. Possible reasons:
The Excel version is not compatible for the 3DXML export operation;
The file is already opened by another process.
Check if some Excel processes are not running on your machine. Close all of them
before to re-run a VL Durability Analysis. Check that you have Excel 2010 installed on
your computer. If it still doesn't work, de-select the option 'Export 3DXML file' in VL
Durability analysis. If you want to get results images, open the output .CATanalysis file
with Virtual.Lab and do the post-processing manually.
Type: Error
Description of the message: Impossible to find the legend (png image) in the Excel File
'file'
Comments/Solution:
To extract 3DXML from Virtual.Lab it is necessary to create an Excel file to copy/
paste the 3DXML file inside. Then the 3DXML can be extracted and viewed in SWT.
However the legend can not be exported inside the 3DXML file. This legend is thus
extracted like the 3DXML object inside a temporary Excel file. This error appears if the
legend cannot be found in the Excel file. If this message is recurrent, de-select the option
'Export 3DXML file' in VL Durability analysis. If you want to get results images, open the
output .CATanalysis file with Virtual.Lab and do the post-processing manually.
Type: Error
Description of the message: Impossible to extract the 3DXML OLE object from the Excel
File 'file'. 3DXML file will not be created.
viewed in SWT. This error appears if it is not possible to extract the 3DXML object from
the Excel file. Be sure the file is not hold by another process: close all Excel processes
on your machine. Eventually close also each SWT process - the file could be hold by
another VL Durability analysis. If this message is recurrent, de-select the option 'Export
3DXML file' in VL Durability analysis. If you want to get results images, open the
output .CATanalysis file with Virtual.Lab and do the post-processing manually.
Type: Error
Description of the message: Impossible to extract the legend (png image) from the Excel
File 'file'.
viewed in SWT. However the legend can not be exported inside the 3DXML file. This
legend is thus extracted like the 3DXML object inside a temporary Excel file. This error
appears if the legend cannot be extracted from the Excel file. Be sure the file is not hold
by another process: close all Excel processes on your machine. Eventually close also each
SWT process - the file could be hold by another VL Durability analysis. If this message is
recurrent, de-select the option 'Export 3DXML file' in VL Durability analysis. If you want
to get results images, open the output .CATanalysis file with Virtual.Lab and do the postprocessing manually.
Type: Error
Description of the message: Impossible to delete the Excel File 'file'.
viewed in SWT. After the export of the 3DXML file, this temporary Excel file is deleted.
This message appears if it is not possible to delete the Excel File. Be sure the file is not
hold by another process: close all Excel processes on your machine. Eventually close
also each SWT process - the file could be hold by another VL Durability analysis. If this
message is recurrent, de-select the option 'Export 3DXML file' in VL Durability analysis.
If you want to get results images, open the output .CATanalysis file with Virtual.Lab and
do the post-processing manually.
Description of the message: The following path 'file' cannot be translated in a valid URL.
Correct your 'Durability Analysis Name' or your 'Combine Events Case name'
Comments/Solution: Check names chosen for each durability analysis - see 'Analyses
Data' in your VL Durability analysis. The name is used to create a folder that will contain
3DXML files. In the names avoid characters not authorised in Windows path. The
Combine Events Case name (in EO 'VL Parameters') must also follow the same rules.
4.67 Messages related to SKTVLLogParser

These messages are related to the Class SKTVLLogParser
ID
Description
Impossible to find the log file 'file'. Check you have closed all Virtual
Lab windows before to run the analysis.
Message variable
Message variable
Number of sensors selected 'i' and number of matching elements 'j' in
VL are different! Sensor names are maybe bad chosen.
End of VL script has not been reached. An unknown error occurred
during the VL batch mode.
Number of sensors selected 'i' and number of matching elements '0' in
VL are different! Sensor names are maybe bad chosen. You MUST at
least have one matching.
2
3
4
5
6
ID 1 - SKTVLLogParser
Type: Error
Description of the message: Impossible to find the log file 'file'. Check you have closed
all Virtual Lab windows before to run the analysis.
Comments/Solution: During the VL Durability analysis a log file is created to register
all warnings/errors that could occur during the batch run. This error appears if the log file
has not been created. Check you have closed all Virtual Lab windows before to run the
analysis.
Type: Warning
Description of the message: Message variable
Comments/Solution: A warning occurs during the run of Virtual.Lab in batch mode. The
message should be explicit enough to inform the user about the problem.
Type: Error
Description of the message: Message variable
Comments/Solution:
An error occurs during the run of Virtual.Lab in batch mode. The message should be
explicit enough to inform the user about the problem.
Type: Warning
Description of the message: Number of sensors selected 'i' and number of matching
elements 'j' in VL are different! Sensor names are maybe bad chosen.
Comments/Solution: In your VL Durability Analysis the number of selected sensors is
different than the number of matching elements in the 'Load - FE Assignment'. The names
of the unitary load cases in the Finite Element model do not correspond to the names of the
sensors. Check the names of the sensors in the 'Load - FE Assignment' window. Change
the name of the unitary load case in your input .CATanalysis file - in the 'Mode Set' object,
in Modal Editing.
Type: Error
Description of the message: End of VL script has not been reached. An unknown error
occurred during the VL batch mode.
Comments/Solution: To run Virtual.Lab durability in batch mode, a VBscript is created
and then executed by Virtual.Lab. This message appears if an exception has been raised
during the batch process. Before to run the VL Durability analysis, closes all Virtual.Lab
processes. Check Virtual.Lab Durability is correctly installed on your machine. Check you
have an available license to use Virtual.Lab Durability. Check you use at least the version
"LMS Virtual.Lab 11-SL2".
Type: Error
Description of the message: Number of sensors selected 'i' and number of matching
elements '0' in VL are different! Sensor names are maybe bad chosen. You MUST at least
have one matching.
Comments/Solution: In your VL Durability Analysis the number of selected sensors is
different than the number of matching elements in the 'Load - FE Assignment'. The names
of the unitary load cases in the Finite Element model do not correspond to the names of the
sensors. Check the names of the sensors in the 'Load - FE Assignment' window. Change
the name of the unitary load case in your input .CATanalysis file - in the 'Mode Set' object,
in Modal Editing. To run a VL Durability analysis you must at least have one matching.
4.68 Messages related to SKTVLScript

These messages are related to the Class SKTVLScript
ID
Description
1
2
3
An error occurred when running LMS Virtual Lab: [error_message]

The environment variable 'VIRTUAL_LAB' has not been found
The environment variable 'VIRTUAL_LAB' doesn't refer to a folder
that contains the file 'VLStart.bat'. Ensure you have correctly set the
variable and correctly installed Virtual Lab.
Impossible to find the run command line in file 'VLStart.bat'. The file
has been corrupted or the Virtual Lab Version is not supported.
ID 1 - SKTVLScript
Type: Error
Description of the message: An error occurred when running LMS Virtual Lab:
[error_message]
Comments/Solution: During the VL Durability analysis Virtual.Lab is run in batch mode.
An error has been raised during the execution. The error message should highlight you on
the problem.
ID 2 - SKTVLScript
Type: Error
Description of the message: The environment variable 'VIRTUAL_LAB' has not been
found
Comments/Solution: To run Virtual.Lab in batch mode the environment variable
'VIRTUAL_LAB' has to be correctly set. The variable must point to the folder that
contains the script 'VlStart.bat'.
ID 3 - SKTVLScript
Type: Error
Description of the message: The environment variable 'VIRTUAL_LAB' doesn't refer to
a folder that contains the file 'VLStart.bat'. Ensure you have correctly set the variable and
correctly installed Virtual Lab.
Comments/Solution:
To run Virtual.Lab in batch mode the environment variable 'VIRTUAL_LAB' has to be
correctly set. The variable must point to the folder that contains the script 'VlStart.bat'. The
environment variable exists but is not set to the correct path. Check Virtual.Lab is correctly
installed on your machine.
ID 4 - SKTVLScript
Type: Error
Description of the message: Impossible to find the run command line in file 'VLStart.bat'.
The file has been corrupted or the Virtual Lab Version is not supported.
Comments/Solution: Check Virtual.Lab is correctly installed on your machine. Check the

Virtual.Lab version is supported by SWT.
4.69 Messages related to SKTVLWorker

These messages are related to the Class SKTVLWorker
ID
Description
1
2
3

Treating 'x' analyses.
VL Durability parameter End Time must be null or strictly greater than
Tstart
Analyse duration must be null or strictly greater than Tstart
No sensor selected
Problem to open a CRV file
Output .CAtAnalysis File must have an existing parent directory.
Errors encountered during run of Virtual Lab Durability calculation:
[Error_List]
Could not find the crv curve - Code - Type - Id - Component - Frame
4
6
7
8
ID 1 - SKTVLWorker
Type: Error
Comments/Solution: Check that the analysis exists and has been run.
ID 2 - SKTVLWorker
Type: Info
Description of the message: Treating 'x' analyses.
Comments/Solution:
Information message: how many transient analyses are processes by the VL Durability
analysis
ID 3 - SKTVLWorker
Type: Error
Description of the message: VL Durability parameter End Time must be null or strictly
greater than Tstart
Comments/Solution:
If the End Time is null, it means we take the time defined in the Analysis. It is thus
authorized. But if a positive value is given, this value will be used and must be greater than
the Tstart.
ID 4 - SKTVLWorker
Type: Error
Description of the message: Analyse duration must be null or strictly greater than Tstart
Comments/Solution:
The TStart (time from which the VL Durability analysis will consider the time history)
must be greater than the value defined for the analysis Duration (final time of the transient
analysis). Indeed, this means you want to consider times which have not been computed.
The only exception is if the Analyse duration is zero - which means that the real duration
of the analysis is fixed by the times defined in the corresponding load case.
ID 6 - SKTVLWorker
Type: Warning
Description of the message: No sensor selected
Comments/Solution:
Select at least one sensor before to run the VL Durability analysis.
ID 7 - SKTVLWorker
Type: Error
Description of the message: Problem to open a CRV file
Comments/Solution:
This probably occurs because at least one transient analysis used in the VL Durability
analysis has been deleted - and consequently the corresponding main.crv curve file no
longer exists.
ID 8 - SKTVLWorker
Type: Error
Description of the message: Output .CAtAnalysis File must have an existing parent
directory. Errors encountered during run of Virtual Lab Durability calculation: [Error_List]
Comments/Solution:
The parent directory of the output .CATAnalysis file must exist. Create the folder before to
run the VL Durability Analysis.
ID 9 - SKTVLWorker
Type: Error
Description of the message: Could not find the crv curve - Code - Type - Id - Component
- Frame
Comments/Solution:
The connector has not been found in the crv file.
Note: If the sensor selected is a
'connection sensor' - i.e. sensor selected
in the Connection Table - the message
could appear if the two connectors are
not coincident. The tolerance is 10e-6
(m) so if the distance between the two
nodes is greater than that you can get
this error message. This 'bug' will be
removed in future release
4.70 Messages related to StandardHscsDisplayDriver

These messages are related to the Class StandardHscsDisplayDriver
ID
Description
XXX dimension is invalid (must be strictly positive)
ID 1 - StandardHscsDisplayDriver
Type: Error
Description of the message: XXX dimension is invalid (must be strictly positive)
Comments/Solution:
None
4.71 Messages related to StandardFunctionViewer

These messages are related to the Class StandardFunctionViewer
ID
Description
The file filename cannot be found.
ID 1 - StandardFunctionViewer
Type: Warning
Description of the message: The file filename cannot be found.
Comments/Solution: The function viewer retrieves the curve values from one or several
files, whose paths are located in the analysis model (or at least, whose paths can be built
from information stored in the analysis model). This message informs you that such a file
does not exist. Among possible reasons:
the analysis could not complete successfully and the curve file was not created
the file had been created correctly, but has been deleted afterwards
Such files are normally stored in the analysis directory, within the document
caesamexternalfiles directory.
4.72 Messages related to StdModelsAddedMethod

These messages are related to the Class StdModelsAddedMethod
ID
Description
1
2
3
4
5
The tower segment #id is undefined

Tower segment #id: the geometry is undefined
Tower segment #id: the flange is undefined
Tower segment #id: invalid length L=value
Tower segment #id: upper position: external diameter # internal one
[upperExtDiam # upperIntDiam]
Tower segment #id: invalid flange thickness TH=value
Tower segment #id: lower position: external diameter # flange internal
one [lowerExtDiam # flIntDiam]
6
7
ID
Description
SE SE_Name: Recalculated connector ctor1Name and connector

ctor2Name are at the same location (tol 10e-6 m)
Bedplate: the distances are undefined
Bedplate: Generator Frame is undefined
Bedplate: Bearings are undefined
Bedplate: Levels are undefined
BedPlate: X-Distance between Generator Supports is negative
Y-Distance between Generator Supports is negative
BedPlate: X-Distance between main bearings mid-points is negative
BedPlate: X-Distance between Tower and Generator Support (rotor
side) is negative
BedPlate: X-Distance between yokes and Generator Support is negative
BedPlate: Y-Distance between yokes is negative
BedPlate: Number of bearings must be 1 or 2
BedPlate: Rotor Axis Level is below the Yaw Level
BedPlate: Yokes Level is below the Yaw Level
Inertia parameters are undefined
Inertia Super Element Display file not found
Inertia Super Element Database file not found
General Data parameters are undefined
Distances are undefined
Teeth parameters are undefined
Reduction parameters are undefined
Diameters are undefined
Bearings parameters are undefined
PlanetCarrier parameters are undefined
Bearings The Planet Carrier (Rotor Side) is undefined
Bearings The Planet Carrier (Generator Side) is undefined
Bearings The Planet Bearing is undefined
Number of planets must be 3 or 4
Min distance between input wheel and bearings (rotor side) not
respected
Min distance between input wheel and bearings (generator side) not
respected
Gear center to output shaft coupling should be greater than Planet
Carrier Bearing (gen side) to Gear center
Planet Carrier Coupling to Gear center should be greater than Planet
Carrier Bearing (rot side) to Gear center
Distance Planet Carrier Bearing (rotor side) to Gear center is negative
Distance Planet Carrier Bearing (generator side) to Gear center is
negative
Teeth The Gear Width must be strictly positive
Diameters The Sun Shaft Internal Diameter is negative
Diameters The Sun Shaft External Diameter must be strictly positive
Diameters The Pin Internal Diameter is negative
Diameters The Pin External Diameter must be strictly positive
Reduction Number of teeth must be at least 3
Bad number of teeth - We must have Nf=2Np+Ns - Change Nf to
Indicated_Number
Diameters Pin Internal Diameter must be lower than the Pin External
Diameter
9
10
11
12
13
14
15
16
17
18
19
20
21
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
ID
Description
51
The Sun Internal Diameter should be equal to the Sun Shaft Internal
Diameter (tol 10e-6 m)
The Planet Internal Diameter must be larger than the Pin External
Diameter
Diameters The Sun Shaft Internal Diameter must be lower than the
Sun Shaft External Diameter
Diameters Teeth diameter of the Sun should be greater than the Sun
Shaft External Diameter
Diameters Teeth diameter of the Sun must be greater than the Sun
Internal Diameter
Diameters Teeth diameter of the Planet must be greater than the
Planet Internal Diameter
Pin Length of the planet must be greater than the Gear Width
Bearings The number of bearings for the planet must be at least
equal to 2
Bearings The number of bearings for the planet must be at least
equal to 1
Bearings Distance between rows must be strictly positive
Bearings
Pin length must be long enough for the bearings
(composed eventually of several rows)
Planet Carrier Super Element file not found
Planet Carrier Display file not found
Position parameters are undefined
Xdistances parameters are undefined
Reduction parameters are undefined
Teeth parameters are undefined
Diameters parameters are undefined
Bearings parameters are undefined
bearings Input Shaft Rotor Side bearing parameters are undefined
bearings Input Shaft Generator Side bearing parameters are
undefined
bearings Output Shaft Rotor Side bearing parameters are undefined
bearings Output Shaft Generator Side bearing parameters are
undefined
XDistances Gear mid-point / Input Shaft (RS Bearing) is negative
XDistances Gear mid-point / Input Shaft (GS Bearing) is negative
XDistances Gear mid-point / Output Shaft (RS Bearing) is negative
XDistances Gear mid-point / Output Shaft (GS Bearing) is negative
XDistances Input Shaft Coupling / Gear mid-point is negative
XDistances Input Shaft Coupling / Gear mid-point is negative
Teeth Gear Width must be strictly positive
Diameters The Input Shaft External Diameter must be strictly
positive
Diameters The Input Shaft Internal Diameter is negative
Diameters The Output Shaft External Diameter must be strictly
positive
Diameters The Output Shaft Internal Diameter is negative
X-Distance: Gear mid-point / Output Shaft (GS Bearing) must be lower
than X-Distance: Output Shaft Coupling / Gear mid-point
X-Distance: Gear mid-point / Input Shaft (RS Bearing) - (Width of the
Input Shaft Rotor Side Bearing) must be lower than Gear Width/2
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
86
87
ID
Description
88
X-Distance: Gear mid-point / Input Shaft GS Bearing - (Width of the

Input Shaft Generator Side Bearing)) must be lower than Gear Width/2
X-Distance: Gear mid-point / Output Shaft (RS Bearing) - (Width of the
Output Shaft Rotor Side Bearing) must be lower than Gear Width/2
X-Distance: Gear mid-point / Output Shaft (GS Bearing) - (Width of the
Output Shaft Generator Side Bearing) must be lower than Gear Width/2
The Input Shaft External Diameter should be lower than the input
Wheel diameter
The Input Shaft Internal Diameter must be lower than the input Wheel
diameter
The Output Shaft External Diameter should be lower than the output
Wheel' diameter
The Output Shaft Internal Diameter must be lower than the output
Wheel' diameter
The Input Shaft Internal Diameter must be lower than the Input Shaft
External Diameter
The Output Shaft Internal Diameter must be lower than the Output
Shaft External Diameter
Input shaft (rotor side) of the second helical stage overlaps the wheel of
the planetary stage
Intersection between the output shaft of the second helical stage and the
fixed wheel of the planetary stage
Overlap between the Planetary Wheel and the Input wheel of the second
helical stage
Overlap between the Planetary Wheel and the Output wheel of the
second helical stage
Distance between Planetary stage bearing (gen side) and Helical bearing
(rotor side) is negative
Planetary Wheel overlaps first helical Output Shaft (rotor side)
Sun shaft External Diameter is not equal to the Input Internal Diameter
of the first helical stage (tol 10e-3 m)
Distance between bearing (gen side) of the first planetary stage and
bearing (rotor side) of the second planetary stage must be positive
Sun shaft Internal Diameter of the first planetary stage is greater than
the Sun shaft External Diameter of the second planetary stage (tol 10e-3
m)
Output Internal Diameter of the first helical stage must be equal to the
Input Internal Diameter of the second helical stage
Output External Diameter of the first helical stage must be equal to the
Input External Diameter of the second helical stage
Input shaft of the first helical stage overlaps input wheel of the second
helical stage
Output shaft of the second helical stage overlaps input wheel of the first
helical stage
Output shaft of the second helical stage overlaps input shaft of the first
helical stage
Output Wheel of the second helical stage overlaps input shaft of the
first helical stage
GearBox type unknown
Function checkHousing: bad Input parameter
Function checkPlanetaryStage: bad Input parameter
Function checkHelicalStage: bad Input parameter
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
107
108
109
110
111
112
113
114
115
116
ID
Description
117
BedPlate: X-Distance between MB1 (or MB2) and Generator support is

negative
Rotor-name: Super Element file 'path' not found
Rotor-name: Display file 'path' not found
Rotor-name: Position of section id must be greater than the previous
one
Rotor-name: Position of section id may not exceed the blade length
Controller - 'name': the Member 'Data' does not exist
Controller - 'name': the Member 'Implementation' in the EO 'Data' does
not exist
Controller - 'name': the Member 'DLLpath' in the EO 'Implementation'
does not exist
Controller - 'name': Parameter file 'name' not found
Controller - 'name': the Member 'datafile' in the EO 'Implementation'
does not exist
Controller - 'name': DLL file 'name' not found
Rotor - 'name': Section 'id' in tab Mass and Stiffness MassByUnitLength must be greater than 0
Rotor - 'name': Section 'id' in tab Mass and Stiffness - FlapStiffness
must be greater than 0
Rotor - 'name': Section 'id' in tab Mass and Stiffness - EdgeStiffness
must be greater than 0
Rotor - 'name': Distance from root must be null for the first station
118
119
120
121
126
127
128
129
130
131
132
133
134
135
ID 1 - StdModelsAddedMethod
Description of the message: The tower segment #id is undefined
Comments/Solution:
This error is related to the Tower. Refer to Samtech Headquarter.
Description of the message: Tower segment #id: the geometry is undefined
Comments/Solution:
This error is related to the Standard Tower. An error occured and the geometry of the
specified segment could not be built or disappeared. The tower can no longer be used and
must be replaced by a new one (using the Edit Wind Turbine Assembly command)
Description of the message: Tower segment #id: the flange is undefined
Comments/Solution:
This error is related to the Standard Tower. An error occured and the flange of the
specified segment could not be built or disappeared. The tower can no longer be used and
must be replaced by a new one (using the Edit Wind Turbine Assembly command)
Type: Error
Description of the message: Tower segment #id: invalid length L=value
Comments/Solution:
This error is related to the Standard Tower. Segment length must be positive. Correct the
length of the specified segment.
Type: Error
Description of the message: Tower segment #id: upper position: external diameter #
internal one [upperExtDiam # upperIntDiam]
Comments/Solution:
This error is related to the Standard Tower. Correct the upper position diameters of the
specified segment.
Type: Error
Description of the message: Tower segment #id: invalid flange thickness TH=value
Comments/Solution:
This error is related to the Tower
Type: Error
Description of the message: Tower segment #id: lower position: external diameter #
flange internal one [lowerExtDiam # flIntDiam]
Comments/Solution:
This error is related to the Tower
Type: Warning
Description of the message: SE SE_Name: Recalculated connector ctor1Name and
connector ctor2Name are at the same location (tol 10e-6 m)
Comments/Solution:
Two connectors cannot have the same location.
To solve this problem, change a geometrical parameter relative to one of the concerned
connector.
Description of the message: Bedplate: the distances are undefined

Comments/Solution:
This error is related to the Bedplate. Refer to Samtech Headquarter.
Description of the message: Bedplate: Generator Frame is undefined
Comments/Solution:
Description of the message: Bedplate: Bearings are undefined
Comments/Solution:
Description of the message: Bedplate: Levels are undefined
Comments/Solution:
Type: Error
Description of the message: BedPlate: X-Distance between Generator Supports is
negative
Comments/Solution:
This error is related to the Bedplate
Type: Error
Description of the message: Y-Distance between Generator Supports is negative
Comments/Solution:
Type: Error
Description of the message: BedPlate: X-Distance between main bearings mid-points is
negative
Comments/Solution:
Type: Error
Description of the message: BedPlate: X-Distance between Tower and Generator Support
(rotor side) is negative
Comments/Solution:
Type: Error
Description of the message: BedPlate: X-Distance between yokes and Generator Support
is negative
Comments/Solution:
Type: Error
Description of the message: BedPlate: Y-Distance between yokes is negative
Comments/Solution:
Type: Error
Description of the message: BedPlate: Number of bearings must be 1 or 2
Comments/Solution:
Type: Error
Description of the message: BedPlate: Rotor Axis Level is below the Yaw Level
Comments/Solution:
Type: Error
Description of the message: BedPlate: Yokes Level is below the Yaw Level
Comments/Solution:

Description of the message: Inertia parameters are undefined
Comments/Solution:
Type: Error
Description of the message: Inertia
Super Element Display file not found
Comments/Solution:
The file should have the extension *.sdb
Type: Error
Description of the message: Inertia
Super Element Database file not found
Comments/Solution:
This error is related to the Housing of the GearBox.
Type: Warning
Description of the message: General Data parameters are undefined
Comments/Solution:
This warning is related to the GearBox.
Description of the message: Distances are undefined
Comments/Solution:
This error is related to the GearBox. Refer to Samtech Headquarter.
Description of the message: Teeth parameters are undefined
Comments/Solution:

Description of the message: Reduction parameters are undefined
Comments/Solution:
Description of the message: Diameters are undefined
Comments/Solution:
Description of the message: Bearings parameters are undefined
Comments/Solution:
Description of the message: PlanetCarrier parameters are undefined
Comments/Solution:
Description of the message: Bearings
The Planet Carrier (Rotor Side) is undefined
Comments/Solution:
The Planet Carrier (Generator Side) is undefined
Comments/Solution:
The Planet Bearing is undefined
Comments/Solution:
Type: Warning
Description of the message: Number of planets must be 3 or 4
Comments/Solution:
This warning is related to Planetary Stage of the GearBox.
Type: Error
Description of the message: Min distance between input wheel and bearings (rotor side)
not respected
Comments/Solution:
This error is related to Planetary Stage of the GearBox.
Decrease the Gear width or increase the Planet Carrier Bearing (rotor side) to Gear Center.
Type: Error
Description of the message: Min distance between input wheel and bearings (generator
side) not respected
Comments/Solution:
Decrease the Gear width or increase the Planet Carrier Bearing (generator side) to Gear
Center.
Type: Warning
Description of the message: Gear center to output shaft coupling should be greater than
Planet Carrier Bearing (gen side) to Gear center
Comments/Solution:
Type: Warning
Description of the message: Planet Carrier Coupling to Gear center should be greater than
Planet Carrier Bearing (rot side) to Gear center
Comments/Solution:
Type: Error
Description of the message: Distance Planet Carrier Bearing (rotor side) to Gear center is
negative
Comments/Solution:
Type: Error
Description of the message: Distance Planet Carrier Bearing (generator side) to Gear
center is negative
Comments/Solution:
Type: Error
Description of the message: Teeth
The Gear Width must be strictly positive
Comments/Solution:
Type: Error
Description of the message: Diameters
The Sun Shaft Internal Diameter is negative
Comments/Solution:
Type: Error
strictly positive
The Sun Shaft External Diameter must be
Comments/Solution:
Type: Error
The Pin Internal Diameter is negative
Comments/Solution:
Type: Error
positive
The Pin External Diameter must be strictly
Comments/Solution:
Type: Error
Description of the message: Reduction
Number of teeth must be at least 3
Comments/Solution:
This message could be relative to the Sun, the Planet or the Fixed Wheel.
Type: Warning
Description of the message: Bad number of teeth - We must have Nf=2Np+Ns - Change
Nf to Indicated_Number
Comments/Solution: This warning is related to Planetary Stage of the GearBox.
Nf is the teeth number of the Fixed Wheel.
Np is the teeth number of the Planet.
Ns is the teeth number of the Sun.
Type: Error
Pin External Diameter
Pin Internal Diameter must be lower than the
Comments/Solution:
Type: Warning
Description of the message: The Sun Internal Diameter should be equal to the Sun Shaft
Internal Diameter (tol 10e-6 m)
Comments/Solution:
Type: Error
Description of the message: The Planet Internal Diameter must be larger than the Pin
External Diameter
Comments/Solution:
Type: Error
than the Sun Shaft External Diameter
The Sun Shaft Internal Diameter must be lower
Comments/Solution:
Type: Warning
than the Sun Shaft External Diameter
Teeth diameter of the Sun should be greater
Comments/Solution:
The Teeth diameter of the Sun is automatically calculated and is linked to the Center
Distance and to the number of teeth of Sun and of the Planet.
Type: Error
than the Sun Internal Diameter
Teeth diameter of the Sun must be greater
Comments/Solution:
Type: Error
than the Planet Internal Diameter
Teeth diameter of the Planet must be greater
Comments/Solution:
Type: Error
Description of the message: Pin Length of the planet must be greater than the Gear Width
Comments/Solution:
Type: Error
least equal to 2
The number of bearings for the planet must be at
Comments/Solution:
Type: Error
least equal to 1
The number of bearings for the planet must be at
Comments/Solution:
Type: Error
Distance between rows must be strictly positive
Comments/Solution:
Rem.: this test is done only if the number of rows is greater than 1.
Type: Error
Pin length must be long enough for the
bearings (composed eventually of several rows)
Comments/Solution:
The minimum distance needed depends on the number of rows, number of bearings,
distance between rows and distance between bearings.
Type: Error
Description of the message: Planet Carrier
Super Element file not found
Comments/Solution:
The file must have the extension *.sdb
Type: Warning
Description of the message: Planet Carrier
Display file not found
Comments/Solution:
The file must should the extension *.brep
Description of the message: Position parameters are undefined
Comments/Solution: This error is related to the GearBox. Refer to Samtech Headquarter.
Description of the message: Xdistances parameters are undefined
Description of the message: Reduction parameters are undefined
Description of the message: Teeth parameters are undefined
Description of the message: Diameters parameters are undefined
Description of the message: Bearings parameters are undefined

Description of the message: bearings
undefined
Input Shaft Rotor Side bearing parameters are

are undefined
Input Shaft Generator Side bearing parameters

undefined
Output Shaft Rotor Side bearing parameters are

are undefined
Output Shaft Generator Side bearing parameters

Type: Error
Description of the message: XDistances
negative
Gear mid-point / Input Shaft (RS Bearing) is
Comments/Solution:
This error is related to the Helical Stage of the GearBox.
Type: Error
negative
Gear mid-point / Input Shaft (GS Bearing) is
Comments/Solution:
Type: Error

negative
Gear mid-point / Output Shaft (RS Bearing) is
Comments/Solution:
Type: Error
negative
Gear mid-point / Output Shaft (GS Bearing) is
Comments/Solution:
Type: Error
negative
Input Shaft Coupling / Gear mid-point is
Comments/Solution:
Type: Error
negative
Input Shaft Coupling / Gear mid-point is
Comments/Solution:
Type: Error
Description of the message: Teeth
Gear Width must be strictly positive
Comments/Solution:
Type: Error
strictly positive
The Input Shaft External Diameter must be
Comments/Solution:
Type: Error
The Input Shaft Internal Diameter is negative
Comments/Solution:
Type: Error
strictly positive
The Output Shaft External Diameter must be
Comments/Solution:
Type: Error
The Output Shaft Internal Diameter is negative
Comments/Solution:
Type: Error
Description of the message: X-Distance: Gear mid-point / Output Shaft (GS Bearing)
must be lower than X-Distance: Output Shaft Coupling / Gear mid-point
Comments/Solution:
Rem.: this point is not checked if the helical stage has no bearing in Output Generator side.
Type: Error
Description of the message: X-Distance: Gear mid-point / Input Shaft (RS Bearing) (Width of the Input Shaft Rotor Side Bearing) must be lower than Gear Width/2
Comments/Solution:
Rem.: this point is not checked if the helical stage has no bearing in Input Rotor side.
Type: Error
Description of the message: X-Distance: Gear mid-point / Input Shaft GS Bearing (Width of the Input Shaft Generator Side Bearing)) must be lower than Gear Width/2
Comments/Solution:
Rem.: this point is not checked if the helical stage has no bearing in Input Generator side.
Type: Error
Description of the message: X-Distance: Gear mid-point / Output Shaft (RS Bearing) (Width of the Output Shaft Rotor Side Bearing) must be lower than Gear Width/2
Comments/Solution:
Rem.: this point is not checked if the helical stage has no bearing in Output Rotor side.
Type: Error
Description of the message: X-Distance: Gear mid-point / Output Shaft (GS Bearing) (Width of the Output Shaft Generator Side Bearing) must be lower than Gear Width/2
Comments/Solution:
Rem.: this point is not checked if the helical stage has no bearing in Output Generator side.
Type: Warning
Description of the message: The Input Shaft External Diameter should be lower than the
input Wheel diameter
Comments/Solution:
This warning is related to the Helical Stage of the GearBox.
The input Wheel diameter is automatically calculated and is linked to the Center Distance
and to the number of teeth of the input and output wheel.
Type: Error
Description of the message: The Input Shaft Internal Diameter must be lower than the
input Wheel diameter
Comments/Solution:
The input Wheel diameter is automatically calculated and is linked to the Center Distance
and to the number of teeth of the input and output wheel.
Type: Error
Description of the message: The Output Shaft External Diameter should be lower than the
output Wheel' diameter
Comments/Solution:
The output Wheel diameter is automatically calculated and is linked to the Center
Distance and to the number of teeth of the input and output wheel.
Type: Error
Description of the message: The Output Shaft Internal Diameter must be lower than the
output Wheel' diameter
Comments/Solution:
The output Wheel diameter is automatically calculated and is linked to the Center
Distance and to the number of teeth of the input and output wheel.
Type: Error
Description of the message: The Input Shaft Internal Diameter must be lower than the
Input Shaft External Diameter
Comments/Solution:
Type: Error
Description of the message: The Output Shaft Internal Diameter must be lower than the
Output Shaft External Diameter
Comments/Solution:
Type: Error
Description of the message: Input shaft (rotor side) of the second helical stage overlaps
the wheel of the planetary stage
Comments/Solution:
This error is related to the Link Planetary stage Helical Stage for the Gear Box 1 Plan 2
Hel type A
To solve this problem, decrease the Gear Width or change a distance. The easiest way is
to increase the Gear center to output shaft coupling of the Planetary stage, but it is also
possible to decrease some shaft lengths. Another solution is to increase the Center distance
of the first helical stage.
Type: Error
Description of the message: Intersection between the output shaft of the second helical
stage and the fixed wheel of the planetary stage
Comments/Solution:
Hel type A
To solve this problem, decrease the Gear Width or change a distance. The easiest way
is to increase the Gear center to output shaft coupling of the Planetary stage, but it is
also possible to decrease some shaft lengths. Another possibility is to change the Angle
between Z axis and center distances of the first and/or the second helical stage.
Type: Error
Description of the message: Overlap between the Planetary Wheel and the Input wheel of
the second helical stage
Comments/Solution:
Hel type A
Type: Error
Description of the message: Overlap between the Planetary Wheel and the Output wheel
of the second helical stage
Comments/Solution:
Hel type A
Type: Error
Description of the message: Distance between Planetary stage bearing (gen side) and
Helical bearing (rotor side) is negative
Comments/Solution:
This error is related to the Link Planetary stage Helical Stage
Increase the Gear center to output shaft coupling of the Planetary stage
Type: Error
Description of the message: Planetary Wheel overlaps first helical Output Shaft (rotor
side)
Comments/Solution:
To solve this problem, decrease the Gear Width or change a distance. The easiest way is
to increase the Gear center to output shaft coupling of the Planetary stage, but it is also
possible to decrease some shaft lengths. Another solution is to increase the Center distance
of the first helical stage.
Type: Error
Description of the message: Sun shaft External Diameter is not equal to the Input Internal
Diameter of the first helical stage (tol 10e-3 m)
Comments/Solution:
Type: Error
Description of the message: Distance between bearing (gen side) of the first planetary
stage and bearing (rotor side) of the second planetary stage must be positive
Comments/Solution:
Type: Warning
Description of the message: Sun shaft Internal Diameter of the first planetary stage is
greater than the Sun shaft External Diameter of the second planetary stage (tol 10e-3 m)
Comments/Solution:
This warning is related to the Link Planetary stage Helical Stage
Type: Error
Description of the message: Output Internal Diameter of the first helical stage must be
equal to the Input Internal Diameter of the second helical stage
Comments/Solution:
This error is related to the Link Helical stage Helical Stage
Type: Error
Description of the message: Output External Diameter of the first helical stage must be
equal to the Input External Diameter of the second helical stage
Comments/Solution:
Type: Error
Description of the message: Input shaft of the first helical stage overlaps input wheel of
the second helical stage
Comments/Solution:
Distance of the shafts can be changed or the Angle between Z axis and center distances
of the first and/or the second helical stage.
Type: Error
Description of the message: Output shaft of the second helical stage overlaps input wheel
of the first helical stage
Comments/Solution:
Type: Error
Description of the message: Output shaft of the second helical stage overlaps input shaft
Comments/Solution:
Type: Error
Description of the message: Output Wheel of the second helical stage overlaps input shaft
Comments/Solution:
Description of the message: GearBox type unknown
Comments/Solution:
This error is related to the Gear box. Refer to Samtech Headquarter.
Description of the message: Function checkHousing: bad Input parameter
Comments/Solution:
Description of the message: Function checkPlanetaryStage: bad Input parameter
Comments/Solution:
Description of the message: Function checkHelicalStage: bad Input parameter
Comments/Solution:
Type: Error
Description of the message: BedPlate: X-Distance between MB1 (or MB2) and Generator
support is negative
Comments/Solution:
Type: Error
Description of the message: Rotor-name: Super Element file 'path' not found
Comments/Solution:
This error is related to the Rotor
The file must have the extension .sdb
Type: Warning
Description of the message: Rotor-name: Display file 'path' not found
Comments/Solution:
The file should have the extension .stp
Type: Error
Description of the message: Rotor-name: Position of section id must be greater than the
previous one
Comments/Solution:
Type: Error
Description of the message: Rotor-name: Position of section id may not exceed the blade
length
Comments/Solution:
Description of the message: Controller - 'name': the Member 'Data' does not exist
Comments/Solution:
Description of the message: Controller - 'name': the Member 'Implementation' in the EO
'Data' does not exist
Comments/Solution:
Description of the message: Controller - 'name': the Member 'DLLpath' in the EO
'Implementation' does not exist
Comments/Solution:
Type: Error
Description of the message: Controller - 'name': Parameter file 'name' not found
Comments/Solution:
The file specified for the controller in the field 'Parameter File' does not exist. A valid file
must be specified.
Description of the message: Controller - 'name': the Member 'datafile' in the EO
'Implementation' does not exist
Comments/Solution:
Type: Error
Description of the message: Controller - 'name': DLL file 'name' not found
Comments/Solution:
The file specified for the controller in the field 'DLL File' does not exist. A valid file must
be specified.
Type: Error
Description of the message: Rotor - 'name': Section 'id' in tab Mass and Stiffness MassByUnitLength must be greater than 0
Comments/Solution:
In the Rotor select the EO 'Blade Properties'. In the tab 'Mass and Stiffness' of the table
check than the value of MassByUnitLength is strictly positive.
Type: Error
Description of the message: Rotor - 'name': Section 'id' in tab Mass and Stiffness FlapStiffness must be greater than 0
Comments/Solution:
check than the value of FlapStiffness is strictly positive.
Type: Error
Description of the message: Rotor - 'name': Section 'id' in tab Mass and Stiffness EdgeStiffness must be greater than 0
Comments/Solution:
check than the value of EdgeStiffness is strictly positive.
Type: Fatal Error
Description of the message: Rotor - 'name': Distance from root must be null for the first
station
Comments/Solution:
In the Rotor select the EO 'Blade Properties'. In the tab 'Blade Geometry' the parameter
DistanceFromRoot must be null for the first station.
4.73 Messages related to WindAddedMethods

These messages are related to the Class WindAddedMethods
ID
Description
1
3
GetInitialWind is called on a NULL instance.

GetInitialWind argument is not a loadcase. Unable to take wind
misalignment nor yaw orientation into account
The loadcase has no 'initialValues' member
GetInitialWind is not implemented for analytical functions
The turbulent wind has no translated file url member
Unable to open turbulent file 'filename'
GetInitialWind argument is not an item. The url is resolved without
context
4
5
6
7
8
ID 1 - WindAddedMethods
Description of the message: GetInitialWind is called on a NULL instance.
Comments/Solution:
Description of the message: GetInitialWind argument is not a loadcase. Unable to take

wind misalignment nor yaw orientation into account
Comments/Solution:
Type: Warning
Description of the message: The loadcase has no 'initialValues' member
Comments/Solution:
Description of the message: GetInitialWind is not implemented for analytical functions
Comments/Solution:
Description of the message: The turbulent wind has no translated file url member
Comments/Solution:
Description of the message: Unable to open turbulent file 'filename'
Comments/Solution:
Description of the message: GetInitialWind argument is not an item. The url is resolved
without context
Comments/Solution:
4.74 Messages related to WindGenerator

These messages are related to the Class WindGenerator
ID
Description
The file 'filename' does not exist... Should have been created by the
wind generator...
TurbSim - Error: message coming from TurbSim log
ID 1 - WindGenerator
Type: Error
Description of the message: The file 'filename' does not exist... Should have been created
by the wind generator...
Comments/Solution:
An error occurred in Turbsim. This error message should normally be followed by another
message more explicit.
ID 2 - WindGenerator
Type: Error
Description of the message: TurbSim - Error: message coming from TurbSim log
Comments/Solution:
An error occurred in Turbsim. This is the same error that you can find in the file
gwinddata.sum. Normally the error message should be explicit.
4.75 Messages related to WindTurbineInitializationCommand

These messages are related to the Class WindTurbineInitializationCommand
ID
Description
Cannot create Wind Turbine: Only one wind turbine allowed per
document.
ID 1 - WindTurbineInitializationCommand
Type: Error
Description of the message: Cannot create Wind Turbine: Only one wind turbine allowed
per document.
Comments/Solution:SWT is not design to manage several wind turbines in one single
document. If your purpose is to modify the current WT, you have to use the Edit a Wind
Turbine Assembly command.
180 | Samcef Wind Turbines | 5 Function types
5 Function types
The following types of functions can be defined :
Function defined by points.
Function defined in a csv file.
Constant function.
Analytic function.
Analytic multi range function.
Step function.
Function defined by points
This type of function is defined by a series of pairs of values.
To create a function defined by points:
1. Select 'Function defined by points' in the 'Type of function' list.
2. Choose the name of function. You can select several functions if you want to create more than one
function.
3. In the definition panel select the required dimensions for the X and the Y axes.
4. Default units are selected for any dimension, which may require the application of a multiplicative
factor. You can adapt the units and the factor if required.
5. In the Points section right click to bring up the pop up menu. Then insert the number of rows required to
create the function.

6. Enter the required values of X and the corresponding values of Y.
The function can be edited using the options available from the pop up menu shown above.
Insert item above - this will insert a row the table above the currently selected row. Both the X and the Y
values for the corresponding point must be defined.
Insert item below - this will insert a row the table below the currently selected row. Both the X and the Y
values for the corresponding point must be defined.
Insert multiple items - this will insert a number of rows below the currently selected row.
Removed selected items - this will remove row(s) containing the currently selected cell(s).
Copy - this copies the selected cell value. Multiple selections are possible.
Paste - this pastes the copied value in to the selected cell. Multiple selections are possible.
Samcef Wind Turbines | 5 Function types | 181
Function defined in a csv file

A csv function is one in which the abscissa and ordinate values are defined by a set of comma separated
values contained in a .csv file. A csv file can be created from an Excel file and can be imported into Excel.
The csv file must contain at least value pairs must be separated by a semicolon (;) value X1;value Y1 value
X2;value Y2; ... It may also contain header values that define the units used.
A csv function can also be used to defined histogram curves.
To create a function defined in a csv file :
1. Select 'Function defined in a csv file' in the 'Type of function' list.
function.
3. In the definition panel, click in the File field, then on the [...] button to browse for the csv file.
4. Click [Open] to select it.
5. If the csv file contains just the values, then you can select the required dimensions for the X and the Y
axes in the definition panel.
6. Enter any multiplicative factors for these axes if required.
Constant function
A constant function is created with a defined ordinate value. This constant value will be applied for the
period of the analysis.
To create a constant function:
1. Select 'Constant Function' in the 'Type of function' list.
function.
4. Insert the value of your constant function. You can change the unit depending on the Y-axis dimension
you have selected.
Analytic function
Analytic functions are those that can be defined using a mathematical formula. The function definition
must be based on the independent variable $u.
Examples: sin($u*0.05)+2
Lower bound - the lowest value taken by $u
Upper bound - the highest value taken by $u.
X-axis units - the type of unit for the x-axis
Y-axis units - the type of unit for the y-axis
X factor - multiplicative factor in the x-direction
Y factor - multiplicative factor in the y-direction
To create an analytic function
1. Select 'Analytic Function' in the 'Type of function' list.
function.
4. Enter any multiplicative factors for these axes if required and adapt the units if necessary.
5. Enter the analytic formula in the input field.

6. Enter the lowest value taken by $u in the boundmin field.
7. Enter the highest value taken by $u in the boundmax field.
The screen shots below show an analytical function definition and the corresponding graphical
representation.
Analytic multi range function

Analytic multi range functions are equivalent to analytic functions but you can define different functions in
several intervals. You do not have only one formula and one boundmin and boundmax: you can define as
many intervals as you want. Right click on the definition table and insert several rows if you want several
intervals. In each formula you can use the independent variable $u. Notice you cannot have x overlaps in
your definition.
If the function name appears in red it means the definition of the function is not correct. Put your mouse on
the name and a tool tip will describe the problem.
To create an analytic multi range function
1. Select 'Analytic Multi Ranges Function' in the 'Type of function' list.
function.
5. Enter the analytic formula in the first row of the input field.
6. Enter the lowest value taken by $u in the boundmin field of the first row.
7. Enter the highest value taken by $u in the boundmax field of the first row.
8. Right click on the table and select 'Insert item below' if you wan to add a new interval.
9. Fill this new row and add as many rows as you want.
Example:
Row 1: Formula = sin($u); boundmin = 0; boundmax = 3
Row 2: Formula = 1; boundmin = 5; boundmax = 8
Row 3: Formula = cos($u); boundmin = 10; boundmax = 12
Samcef Wind Turbines | 5 Function types | 183
The function is supposed to be null for non defined intervals.

Step function
A step function is defined as a series of (Y) values that are applied between two X values ("from" and
"to"). Between a "to" value and the next "from" value the (Y) value reverts to the defined default value.
Right click on the definition table and insert several rows if you want several intervals.
To create a step function
1. Select 'Step Function' in the 'Type of function' list.
function.
5. Enter the 'from', 'to' and 'value' parameters.
6. Right click on the table and select 'Insert item below' if you want to add a new interval.
7. Fill this new row and add as many rows as you want.
Example:
Row 1: from = 4; to = 5; value = 2
Row 2: from = 8; to = 9; value = 5
The function is supposed to be null for non defined intervals.
Samcef Wind Turbines | 6 Predefined Frames | 185
6 Predefined Frames
The following frames are predefined and used in sensors.
6.1 Model frame

Key: model
Name: Default model system
Origin: (depending on the model)
This frame is the finite element model frame. Its origin depends on the assembling table and the model
origin choice. The axes are the conventional SWT axes:
the X axis is parallel to the rotor axis (pointing upwind to downwind)
the Z axis in the plane [Rotor axis, tower axis], perpendicular to the rotor axis (pointing towards the
sky)
the Y axis is perpendicular to the 2 other ones
186 | Samcef Wind Turbines | 6 Predefined Frames
6.2 Tower frame
Key: tower_foundation
Name: Tower foundation system
Origin: TOWER_FOUNDATION_LINK_NODE
This frame is attached to the tower foundation. The axes are parallel to the "ground" axes:
the X axis is parallel to the (supposed to be horizontal) ground, in the same plane as the (initial) rotor
axis (pointing upwind to downwind)
the Z axis is the "real world" vertical axis (pointing towards the sky)
6.3 Bedplate frame
Key: bedplate_yaw
Name: Bedplate system
Origin: BEDPL_YAW_LINK_NODE
This frame is attached to the bedplate, at its connection to the tower. The axes are parallel to the tower axes
(thus to the "ground" axes):
the X axis is parallel to the (supposed to be horizontal) ground, in the same plane as the (initial) rotor
axis (pointing upwind to downwind)
the Z axis is the "real world" vertical axis (pointing towards the sky)
6.4 Hub frame
Key: fixed_hub
Name: Hub fixed system
Origin: HUB_BLADES_LINK_NODE
This frame is attached to the hub center. The axes are parallel to the computation axes:
the Z axis is the (computation) vertical axis, i.e. perpendicular to the rotor axis, in the plane [rotor axis,
tower axis] (pointing towards the sky)
6.5 Rotor frame
Key: rotor
Name: Rotor system
Origin: HUB_BLADES_LINK_NODE
This frame is attached to the rotor:
the Z axis is perpendicular to the rotor axis, in the plane [rotor axis, blade 1 axis (pointing from the
blade root towards the blade tip)]
6.6 Blade frames
Key: hub_bladei
Name: Blade i system
Origin: HUB_BLADES_BLDi_LINK_NODE
These frames are attached to the corresponding blade roots. The axes are oriented in this way:
the Z axis is perpendicular to the rotor axis, in the plane [rotor axis, blade i axis (pointing from the
blade root towards the blade tip)]
6.7 Pitch axis frames
Key: pitch_axisi
Name: Pitch axis i system
Origin: BLADES_HUB_BLDi_LINK_NODE
These frames are attached to the corresponding blade roots. The axes are oriented in this way:
the Z axis is parallel to the pitch axis (taking thus into account the conicity)
the X axis is in the plane [rotor axis, pitch i axis (pointing upwind to downwind)
6.8 Blade Section frames
Key: bladei_sectionj
Name: Blade i system
Origin: BLADEi_SEC_NODE_j
These frames are attached to the blade sections. he axes are oriented in this way:
the Z axis is parallel to the blade axis (pointing from the blade root towards the blade tip)
the Y axis is parallel to the section chord, orientated to blade trailing edge
the X axis is perpendicular to the 2 other ones

Samtec Wind Turbines Reference

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Samtec Wind Turbines Reference

Uploaded by

Copyright:

Available Formats

Samcef Wind Turbines Reference Guide

2 | Samcef Wind Turbines | TOC

Samcef Wind Turbines | TOC | 3

2.18 Display Bacon Model.....................................................................................................................29

4 | Samcef Wind Turbines | TOC

Samcef Wind Turbines | TOC | 5

6 | Samcef Wind Turbines | TOC

4.26 Messages related to LoadcaseTranslationMethods........................................................................ 95

Samcef Wind Turbines | TOC | 7

Rotor frame.................................................................................................................................... 189

8 | Samcef Wind Turbines | 1 Reference Guide

Samcef Wind Turbines | 2 SWT Command Reference | 9

2 SWT Command Reference

Edit (see page 12)

Open a new editor for the selection

Add orientations from file (see page 16)

Browse result files (see page 16)

Convert LC (on/off-shore) (see page 20)

Create new functions (see page 23)

Create a new function in the Shared

10 | Samcef Wind Turbines | 2 SWT Command Reference

Export Engineering Object (see page 30)

Export the selection items in a .csm file

Export... (a component) (see page 30)

Export a component into a file for reuse

Generate load cases... (see page 31)

Extend the selected load case by parameter

Import Engineering Object (see page 35)

Import selection items from a .csm file

Import results... (see page 35)

Import Transient Analysis results into the

Link Transient analysis (see page 37)

Show / hide 3D view labels (see page 48)

Solve a compatibility issue between V2 and

Samcef Wind Turbines | 2 SWT Command Reference | 11

Wind Turbine Initialization (see page 53)

Creates a new wind turbine from scratch

2.1 Caesam Standard Commands

12 | Samcef Wind Turbines | 2 SWT Command Reference

Samcef Wind Turbines | 2 SWT Command Reference | 13

2.1.2.19 Save as XML

2.2 Adapt wind data to Wind Turbine

14 | Samcef Wind Turbines | 2 SWT Command Reference

2.3 Add Engineering Object in Shared Workspace

Figure 2: Creating Engineering Object(s)

Samcef Wind Turbines | 2 SWT Command Reference | 15

2.4 Add missing sensors

2.4.3 When and how to use

Figure 3: Component without sensors

16 | Samcef Wind Turbines | 2 SWT Command Reference

Figure 4: Component with sensors

2.5 Add orientations from file

2.6 Bacon Postprocessor

2.6.2 When is it used?

2.7 Browse result files

Samcef Wind Turbines | 2 SWT Command Reference | 17

Browse result files, in the popup menu displayed by right-clicking on the

2.7.2 When is it used?

2.8 Build sensor CCL file

Figure 5: Build sensor CCL menu

2.9 Check Model

18 | Samcef Wind Turbines | 2 SWT Command Reference

2.9.2 When is it used?