Documente Academic
Documente Profesional
Documente Cultură
V6.2
User Manual
Last Updated: June 4, 2014
Crystal Palace Tower, London
The front cover features Britain’s tallest unguyed steel tower. It was checked for structural
adequacy using MStower.
Contents
1:Introduction 1
General ............................................................................................................................... 1
Responsibility...................................................................................................................... 4
2:Getting Started 5
Downloads and Support ....................................................................................................... 5
MStower and Design Codes ................................................................................................. 6
Product Licensing Considerations ........................................................................................ 7
Starting MStower .............................................................................................................. 10
Commands ........................................................................................................................ 11
Right-Clicking Away from Any Part of the Tower ............................................................. 11
Configuration .................................................................................................................... 13
Printing in MStower .......................................................................................................... 14
Print and Print Preview Commands ...................................................................... 14
The Windows Print Dialog Box ............................................................................ 14
The Page Setup Dialog Box.................................................................................. 15
Configurable User Graphic................................................................................... 17
Steel Section Libraries ....................................................................................................... 17
Data from Earlier Versions ................................................................................................ 18
Technical Support.............................................................................................................. 18
4:Operation 37
Data Files .......................................................................................................................... 37
Units .................................................................................................................... 38
Coordinate Systems .............................................................................................. 38
Sections ............................................................................................................... 39
Member Checking ................................................................................................ 39
Export to Microstran Archive File......................................................................... 39
Errors ................................................................................................................................ 39
5:Tower Data 41
General .............................................................................................................................. 41
The Tower Data (TD) File .................................................................................................. 42
Title Block ........................................................................................................... 43
Component Block................................................................................................. 43
Profile Block ........................................................................................................ 44
Supports Block ..................................................................................................... 51
Guys Block .......................................................................................................... 52
Sections Block ..................................................................................................... 53
Material Block ..................................................................................................... 56
Bolt Data Block .................................................................................................... 56
Guy Library ....................................................................................................................... 59
Steel Poles ......................................................................................................................... 60
TD File Examples .............................................................................................................. 63
Example 1 ............................................................................................................ 63
Example 2 ............................................................................................................ 64
Example 3 ............................................................................................................ 65
Example 4 ............................................................................................................ 66
Example 5 (Plan Bracing) ..................................................................................... 68
6:Standard Panels 69
General .............................................................................................................................. 69
Index – Face Panels............................................................................................................ 70
Index – Plan Bracing .......................................................................................................... 74
Index – Hip Bracing & Cross-Arms.................................................................................... 75
D & V Face Panels............................................................................................................. 76
X Face Panels .................................................................................................................... 77
11:Analysis 193
General ........................................................................................................................... 193
Method .............................................................................................................. 194
Consistency Check............................................................................................. 194
Accuracy ........................................................................................................... 194
Linear Elastic Analysis .................................................................................................... 195
Non-Linear Analysis........................................................................................................ 195
Second-Order Effects ......................................................................................... 196
Running a Non-Linear Analysis ......................................................................... 198
Troubleshooting Non-Linear Analysis ................................................................ 201
Elastic Critical Load Analysis .......................................................................................... 202
Selecting Load Cases for ECL Analysis.............................................................. 203
Analysis Control Parameters .............................................................................. 203
Why ECL Analysis May Give High k Factors .................................................... 204
Dynamic Analysis ........................................................................................................... 205
Analysis Control Parameters .............................................................................. 205
Dynamic Modes ................................................................................................. 206
Response Spectrum Analysis ........................................................................................... 207
Defining Load Cases .......................................................................................... 207
Running a Response Spectrum Analysis ............................................................. 207
Response Spectrum Curves ................................................................................ 210
Errors .............................................................................................................................. 211
14:Reports 237
Report Types ................................................................................................................... 237
Display and Printing of Files ............................................................................................ 238
Input/Analysis Report ...................................................................................................... 238
Error Report ..................................................................................................................... 239
Static Log ........................................................................................................................ 239
Dynamic Log ................................................................................................................... 239
Design Summary.............................................................................................................. 239
Detailed Design Report .................................................................................................... 240
Reaction Report ............................................................................................................... 240
Rotation Report................................................................................................................ 240
15:Examples 241
General ............................................................................................................................ 241
TWEX1 ........................................................................................................................... 244
General
MStower is a specialized program that assists in the analysis and
checking of latticed steel communication and power transmission towers
and guyed masts and steel monopoles. MStower contains options for
defining the geometry, loading, analysis, plotting of input, results, and
member checking.
Loading may be computed in accordance with:
• BS 8100 Part 1 1986
• BS 8100 Part 4 1995
• AS 3995-1994
• AS/NZS 1170.2:2011
• Malaysian Electricity Supply Regulations 1990
• EIA/TIA-222-F-1996.
• TIA-222-G-2005.
• Institution of Lighting Engineers Technical Report No. 7 –
High Masts for Lighting and CCTV – 2000 Edition.
• IS 875 (Part 3):1987
• BNBC 93 – Bangladesh National Building Code
• ANSI/ASCE 7-95
• NSCP C101-01 – Philippines National Building Code
To configure and activate an MStower licence, use the File > Manage
Licensing command. Note that this dialog will appear automatically
after the first launch of MStower following installation.
This provides a very convenient alternative to the main menu for many
commands. In effect, you can perform some operations in three different
ways. For example, you can display the section number on all members
by clicking a button on the Display toolbar, by selecting the View >
Display Options command, or by right-clicking and then selecting
Section Numbers.
Text Size
The text size, in points, for both reports and graphical output. There are
72 points to the inch. The default value is 8.
DEFAULT GRAPHIC
Note: The Windows drivers for some printers do not support the
printing of bitmaps.
Technical Support
Click the Check Version Microstran technical support is available by telephone, fax, and e-mail.
button in the Help About Use the Help > About MStower command to display the serial number,
MStower dialog box to the version number, and licence details for your software. This
determine whether your information is required when you ask for technical support. The Help
software needs updating.
About dialog box contains links to the MStower website, where you may
submit a support request or update your software.
Layout
The diagram below shows the layout of the MStower screen. Commands
may be initiated from the main menu, any toolbar, or a context (pop-up)
menu. The main menu comprises a menu bar, each item of which gives
access to a drop-down menu. Some items on drop-down menus lead to
sub-menus. Each toolbar button usually corresponds to a command
accessible from the main menu. Context menus, which appear when you
click the right mouse button, contain a selection of commands from the
main menu. This chapter lists all the commands available on the main
menu and all toolbars.
FILE MENU
Command Action
New Creates a new job.
Open Opens an existing job.
Close Closes the current job.
Save Saves the current job using the same file name.
Save As Saves the current job to a specified file name and changes
the name of the current job accordingly.
Save Copy As Saves a copy of the current job to a specified file name.
Delete Deletes job files, optionally keeping source files.
List/Edit File Opens the selected file with the MsEdit text editor for
viewing or editing.
Page Setup Change the printing options.
Print Preview Displays the selected file on the screen, as it would appear
printed.
Print File Prints the selected file.
Import Reads data into MStower from a file (e.g. Microstran
Archive file or CAD DXF). This command is only available
when editing a UDP.
Export Writes MStower data to a file. File types include MStower
archive file, results file, CAD DXF, and SDNF detailing
file.
Configure Configuration of program capacity, section library, material
library, colors, intermediate file folder, and timed backup
interval. Also used for editing of section and material
VIEW MENU
Command Action
Toolbars Shows or hides the toolbars.
Status Bar Shows or hides the status bar.
Redraw Redraws the current view.
Viewpoint Change the orientation of the structure in the view by
selecting a new viewpoint.
Zoom Change the scale of the view or select a rectangular part of
the view to fill the display window.
Pan Displace the view by the selected distance.
Limit Select a part of the structure by one of several available
methods. Unselected parts are shown in light grey or
hidden.
Full Redraws the current view so that it fills the window.
Copy Copy view to Windows clipboard in EMF format.
Print Preview Displays the view as it would appear printed
Print View Prints the view.
Display Options Select options for displaying node numbers, member
numbers, etc.
Ancillary Sort Specify whether ancillaries will be sorted by serial number
Order or height.
TOWER MENU
Command Action
Build Tower Opens the tower data (TD) file for editing and
processing. Includes graphical creation of user-defined
panels.
Load Tower Opens the tower loading (TWR) file for editing and
processing.
Analyse Analyses the tower.
Gust Factor Applies BS 8100 gust factoring to wind forces in tower
members.
Build/Load/Analyse Runs all the previous items sequentially.
Command Action
BS 8100 Part 3 Checks members to the rules of BS 8100 Part 3.
BS 449 Checks member to the rules of BS 449.
ASCE 10-90 Checks member to the rules of ASCE 10-90.
ASCE 10-97 Checks member to the rules of ASCE 10-97.
EIA-222-F Checks member to the rules of EIA-222-F.
TIA-222-G Checks member to the rules of TIA-222-G.
AS 3995 Checks member to the rules of AS 3995.
IS 802 Checks member to the rules of IS 802.
ILE Tech. Report 7 Checks poles to the rules of ILE Tech. Report.
ASCE Manual 72 Checks poles to the rules of ASCE Manual 72.
BS 5950 Checks poles to the rules of BS 5950.
AS 4100 Checks poles to the rules of AS 4100.
EIA-222-F Checks poles to the rules of EIA-222-F.
TIA-222-G Checks poles to the rules of TIA-222-G.
STRUCTURE MENU
Command Action
Draw Members Draw members or input node coordinates.
Erase Members Erase selected members.
Select All Selects all members, including any that may not be
visible.
Drawing Settings Snap modes for drawing members, grid spacing etc.
ANALYSE MENU
Command Action
Check Input Check structure and load data (normally automatic).
Linear Perform linear analysis (first-order).
Non-Linear Perform non-linear analysis (second-order).
Elastic Critical Load Determine frame buckling load factors and buckling
mode shapes.
Dynamic Determine natural frequencies and mode shapes.
Response Spectrum Add response spectrum and static analysis results.
RESULTS MENU
Command Action
Select Load Cases Select load cases for display of loads or results.
Select Natural Modes Select modes for display of vibration mode shapes.
Select Buckling Modes Select modes for display of buckling mode shapes.
Undisplaced Shape Display structure in undisplaced position.
Member Actions Display bending moment, shear force, axial force,
torque, or displaced shape.
Natural Modes Display vibration mode shapes.
Animate Modes Show each currently displayed mode (natural or
buckling) in alternate extreme positions. Press the
space bar to show the next mode, Esc to cancel.
Buckling Modes Display buckling mode shapes.
Design Ratios Display results of member design check with colors
representing range of design ratios. The legend in the
Output window shows the range of values
represented by each color.
REPORTS MENU
Command Action
Input/Analysis Create report on structure and current analysis results.
SHOW MENU
Command Action
Section Highlight members with specified section number.
Material Highlight members with specified material number.
Member Type Highlight members of specified type (tension-only etc.).
Member Class Highlight members of specified classes such as legs,
braces, etc.
Members Highlight specified members.
Panels Highlight members in a panel.
Wind Panels Highlight members to show how tower is sub-divided for
wind load calculations.
Nodes Highlight members connected to specified nodes.
Master Nodes Show master nodes.
Slave Nodes Show slave nodes.
Node Masses Show all nodes with non-zero added mass.
Design Members Show all defined design members.
Cancel Cancel current “Show” selection.
QUERY MENU
Command Action
Node Data List data for selected node (coordinates etc.).
Node Displacements List displacements for selected node.
Support Reactions List reactions for selected (support) node.
Master Node List slave nodes for selected master node.
Slave Node List constraints for selected slave node.
Member Data List member data for selected member.
Member Displacements List displacements for selected member.
Member Forces List member forces for selected member.
Node Loads List loads for selected node.
Member Loads List loads for selected member.
Design Member Highlight design member containing selected
member.
Linear Ancillary List properties of linear ancillary.
Large Ancillary List properties of large ancillary.
Ancillary Group List properties of ancillary group.
WINDOW MENU
The Window menu offers the following commands, which enable you to
arrange multiple views in the application window:
Command Action
Cascade Arranges windows in an overlapped fashion.
Tile Horizontally Arranges windows side-by-side.
Tile Vertically Arranges windows above and below.
Output Window Show or hide the Output window.
Window All open windows are listed. Clicking one of these will
move the focus to the selected window.
HELP MENU
Command Action
MStower Help Topics Display the Help Topics dialog box. This has three
tabs, Contents, Index, and Find, so you can easily
find help topics.
What’s This? Display help for clicked buttons, menus, and
windows.
Tip of the Day Show Tip of the Day.
About MStower Display details about this copy of MStower and
system resources. Also contains links to Internet.
MAIN TOOLBAR
VIEW TOOLBAR
DISPLAY TOOLBAR
HELP TOOLBAR
DRAW TOOLBAR
ATTRIBUTES TOOLBAR
RESULTS TOOLBAR
OK/CANCEL TOOLBAR
Any toolbar that has been customized may be reset to the original
configuration by selecting it and then clicking the Reset button.
CUSTOMIZING TOOLBARS
Data Files
The tower is described in data files by the minimum number of key
dimensions and a description of the types of panel in the tower. Panel
types are described by mnemonics of one to four characters. Panels may
be selected from a set of built-in face, plan, hip, and cross-arm patterns
or may be defined by the user.
The following data files are used:
• Job.td
The tower data file.
• Job.udp
An optional file containing the description of non-standard or user-
defined panels.
• Job.twr
The tower loading file.
When a job is saved the above files and others associated with the job
are copied into the job.mst file.
It may be convenient to copy the data files from an existing MStower job
and edit these, rather than creating them from the beginning. This may
be done by opening the existing job and selecting the File > Save Copy
As command to create the new job.
The data files are text files, usually created and edited with the built-in
text editor, MsEdit. Data is set out in blocks identified by keywords.
Blank lines may be used as required to improve the readability of the
file. The “$” character may be used to introduce comments; the “$”
character and all text following on that line are ignored as input data.
Individual items of data may be separated by one or more blank spaces.
Each line of data must be no longer than 80 characters.
Units
MStower accepts two sets of units:
• Metric – using meters, kilonewtons, tonnes, and degrees Celsius,
with some data items being input and/or reported in the more
customary units of mm and kg.
• US – using feet, kips, kip.sec2/ft, and degrees Fahrenheit, with some
data items being input and/or reported in the more customary units
of inches and pounds.
Entries in the ancillary and guy libraries are required in metric units.
Coordinate Systems
The vertical axis of the tower is parallel to the global Z axis. The X and
Y axis of the tower lie in the horizontal plane and do not need to be
aligned with the geographic north. The X axis is always normal (in plan)
to one face of the tower.
Each member in MStower has its own set of member or local axes. The
local x axis is aligned along the member while the local y and z axes
correspond to the rectangular section axes. The reference node or axis
defines the plane of the local y axis.
Member Checking
You must ensure that wind velocities and other factors used to compute
loads are consistent with the code method chosen to check member
strengths.
BS 8100 Part 3, AS 3995, ASCE10, TIA-222-G, and IS-802 are limit
states codes, whereas EIA/TIA-222-F uses permissible stresses.
Errors
After assembly of the tower, MStower checks for the following
conditions:
Overlaid Members and Unconnected Nodes
These occur when a node is coincident with a member but not connected
to it. When this occurs it is usually at the junction between panels and
happens either because a horizontal has not been deleted or because of
an incompatibility between panels. For example if a PL1 plan brace is
used with an X face brace the PB1 member will overlay the H1 member.
The duplicated member will not be detected by the assembly process
because of the mid-side node in PB1. A list of such members will be
displayed.
Floating Members
These are members that are not connected to the structure. If not
removed they will result in errors during analysis. They can result if
members are deleted; for example if PL1 plan bracing is used with XO
face bracing and the PB1 member is deleted, the internal plan bracing
members will not be connected to the tower. A list of such members will
be displayed.
You may readily locate overlaid and floating members using MStower
screen plots. Select the Show > Members command and then enter the
list of offending members. The full tower will now be displayed with the
listed members highlighted. You may zoom to inspect the members
more closely and determine the reason for the error. The TD or UDP file
should be modified as necessary.
General
Data describing the tower geometry is entered into a free-format text file
called Job.td, where “Job” is the job name. A prototype tower data file
may be generated by selecting the Tower > Build Tower > Make
Tower Data File command. The dialog box shown below appears for
you to enter the basic geometric parameters.
You may then enter details for each panel in this dialog box.
The resulting tower data file is shown below. It must now be customized
for the particular tower you are modelling. The file will be displayed in
the MsEdit text editor when you select the File > List/Edit File
command and then choose “TD”.
PROFILE
FACES 4
WBASE 4.0000
RLBAS 0.0000
END
SECTIONS
LIBR P:UK IFACT 0.1 $ 1.00
1 EA200X200X16
2 EA150X150X10
3 EA100X100X8
4 EA70X70X6
END
BOLTDATA
$ TODO - bolt data goes here - format of bolt data:
$ [ X x Y y Z z NSP nsp LJ lj ]
END
END
Title Block
TITL1 titl1
TITL2 titl2
UNITS units
where:
TITL1 Keyword.
titl1 First line of job title.
TITL2 Keyword.
titl2 Second line of job title.
UNITS Keyword.
units Integer value indicating system of units being used – 1 or 4.
1 = SI units.
4 = US units.
Component Block
Although MStower provides a comprehensive range of panel types, there
may be times when you wish to define additional panel types. This block
allows you to reference a file containing panel data to be included in the
tower.
COMPONENT
udp [file]
..
END
where:
udp Name (1-8 characters) of a user-defined panel.
file Name of file containing the user-defined panel. It must have the
file name extension “udp”. The file must be specified only if
the UDP file is not named after the job. UDP files may be
referenced by multiple jobs but unless named after the job will
not be saved in the MST file. The file may contain more than
one user-defined panel.
PANEL Keyword.
nn Panel number.
HT Keyword.
hpanl Panel height.
TW Keyword.
tw Width at top of panel, for the face normal to the X axis. If not
given, this value will be interpolated.
TD Keyword, optional, used for rectangular towers.
tw Width of the top of the panel, for the face normal to the Y axis.
If not given, it will be interpolated.
scale Optional keyword pertaining to variable dimensions F1 and F2:
FR
F1 and F2 are factors; the actual dimensions are obtained by
multiplying a length as shown on the panel diagram.
LE
F1 and F2 are lengths.
If omitted, fractional scaling, FR is assumed.
BOLT Keyword.
class Member class, one of the following member types:
LEG
Leg members.
BR BR1..BR4
Bracing in the face.
H H1 H2
Horizontal in the face.
R R1..R9
Face redundant.
PB PB1..PB10
Plan bracing.
HP HP1..HP10
Hip bracing.
CR CR1..CR10
Cross-arm members.
If a mnemonic without a numeric suffix is used, all members of
the class will have the number of bolts specified.
nbolt The number of bolts in the end connection of the member –
zero for welded connections.
You may use as many class/nbolt pairs as are necessary.
FACE Keyword.
ftype Face bracing pattern type. User-defined panels must have their
names prefixed with the “@” character; e.g. @XYZ refers to a
user-defined panel XYZ. UDPs may have names with a
maximum of 8 characters and must have been referenced in the
COMPONENT block.
SPACE Keyword.
s1..sn List of spacings for XM, DM, DLM, DRM, DMH, KXM, and
XDM type face bracing.
ns@sm Shorthand way of indicating that a multiple panel has a number
of identical spacings:
ns
Number of identical spacings.
@
Keyword.
sm
Value of identical spacing.
F1,F2 Keywords.
f1,f2 Factors used to locate nodes for some bracing types. The use of
these factors is shown on the individual bracing diagrams.
NTR,ND Keywords.
ntr,nd Number of levels of triangle and diagonal braces, respectively,
in some face and hip brace patterns.
NPL Keyword.
npl Bracing pattern in part of a portal or cranked K face.
D Keyword – used with XDM bracing.
LEFT Keyword – used with DM bracing.
INV Keyword, used with KB, KBP, KM, KMA, KMG, KMGA,
KMGD, KMH, KMHA, KMV, KVH3, and KVS3, indicating
that the panel is to be inverted.
LEG Keyword.
leg Section property number for leg members.
BRn Keyword.
brn Section property number for brace members, type n, where n is
a digit from 1 to 3.
Hn Keyword.
MCAP Keyword.
class Member class, as described above under BOLT.
c1,c2,c3 User defined member capacity, kN or kips.
c1 Capacity of member in compression.
c2 Capacity of member in tension.
c3 Capacity of joint.
All three capacities must be given. Code rules will be used to
compute the capacity if any of “c1 c2 c3” is entered as zero.
For monopoles, c1, c2 and c3 are the compressive, flexural and
torsional capacities respectively.
If members are to be checked to BS 8100 or ILETR7, a partial
safety factor for material of unity should be used when
determining user defined capacities.
HIP Keyword.
htype Hip bracing pattern type.
NTR, ND Keywords.
ntr, nd Number of levels of triangle and diagonal braces, respectively,
in some hip brace patterns.
HPn Keyword.
hpn Property number for hip bracing, type n. The property
numbers for all hip braces will be set to this value if the
numeric suffix is omitted from the keyword.
NORST Keyword.
list List of integers, 1–10, giving the suffix number of members
CROSS Keyword.
ctype Cross-bracing pattern type.
X,Y Keywords indicating that the cross-arms are to be attached to
the X or Y faces of the tower. If not specified the cross-arms
will be attached to the Y faces; i.e. they will project to the left
and right when viewed from the direction of the X axis.
SPAN Keyword.
span Total span of symmetrical cross-arm. If the cross-arm is not
symmetrical, separate left-hand and right-hand “half” spans
must be specified.
SL Keyword.
sl Left-hand “half” span of the cross-arm. Viewed from the
positive X axis direction if attached to the Y faces, or viewed
from the positive Y axis direction if attached to the X faces.
SR Keyword.
sr Right-hand “half” span of the cross-arm.
RL Keyword.
rl Rise of left-hand “half” span of the cross-arm when viewed as
described above.
RR Keyword.
rr Rise of right-hand “half” span of the cross-arm.
CRn Keyword.
crn Section property number for cross-arm member, type n, where
n is a value from 1 to 10. The property numbers for all cross-
arm members will be set to this value if the numeric suffix is
omitted from the keyword.
Each panel must have one set of face braces and optionally one set of hip
bracing and one or two sets of plan and/or cross-arm braces.
Redundant members are pin-ended. All other members are assumed to
be rigidly connected.
Any member assigned a property number of zero will be deleted. For
example an “X” face panel with H1 = 0 is identical to an “X0” panel.
You must ensure that the deletion of members does not result in an
unstable structure.
When inverting panels, it may be necessary to delete the horizontal
member in either the inverted panel or the panel on which it is mounted,
if the two horizontals are not sub-divided in identical fashion.
“C” nodes (reference nodes), which define member orientation, are
allocated in the plane of the face or hip for all members except H1 and
H2 type members, where the “C” node is in the direction of the global
The first guy in the group will span between (xb, yb, zb) and (xt, yt, zt),
and if no is greater than 1, additional cables will be automatically
generated at an angular increment of angl anti-clockwise about the
vertical axis of the mast. Guys can be generated only where they are
radially symmetrical about the vertical axis of the mast. For example,
guys that have their anchor points at different levels because of a sloping
site have to be input singly.
Usually, guys are input as single members. A guy may also be input as a
number of segments to accommodate changes in properties or to allow
an insulator to be positioned along its length. In this case, you should
input the segments of guy sequentially, commencing at the anchor point
and working up to the mast shaft with the coordinates of the lower end
of one segment being set equal to those of the upper end of the preceding
segment. The segments of guy may be generated as described above.
Sections Block
This block specifies the section library and nominates the section to be
used for each section property number.
SECTIONS
LIBR libr IFACT fact
n sname [X|Y] [CONNECT con] [BH bh] [FY fy] [FU fu]
..
END
where:
LIBR Keyword.
libr Name of library containing section data. It is assumed that the
library is located in the data folder unless the name is prefixed
with “P:” or “L:”. “P:” indicates that the library is in the
program folder and “L:” indicates that it is in the library folder.
IFACT Keyword.
fact Factor by which the section Ixx and Iyy will be multiplied on
extraction from the library. When you specify a low value the
tower will approach the condition of a space truss with pin-
ended members. This is convenient for analysing as a space
frame, with sufficient continuity across the joints to avoid
mathematical instabilities due to coplanar nodes, but without
generating significant bending moments.
n Section property number.
sname Name of library section.
X Y Keywords used to indicate the orientation of the section with
respect to the member y axis:
X The section XX axis is aligned with the member y axis.
Y The section YY axis is aligned with the member y axis.
Use of these keywords will allow you to correctly orient
The orientation of the section is the cross-section axis (XX or YY) that is
coincident with the member y axis (see diagram below).
ORIENTATION OF SECTION
Note: Material properties for guys are obtained from the specified guy
library.
Note: Not all pole shapes available in MStower are covered by the
various codes that deal with poles.
In the next dialog box, data is input for each panel starting at the top of
the pole. You may change panel heights, plate thicknesses, and yield
strengths. Diameters have to be entered for the top of the pole and at
bend points only. All other diameters are interpolated by MStower.
UNITS 1
PROFILE
FACES 1
WBASE 0.600
RLBAS 0.000
PANEL 1 HT 0.6000 TW 0.6000
FACE SH1 LEG 1 R1 22
PANEL 2 HT 0.6000 TW 0.6000
FACE SH1 LEG 2 R1 22
PANEL 3 HT 0.6000 TW 0.6000
FACE SH1 LEG 3 R1 22
PANEL 4 HT 0.6000 TW 0.6000
FACE SH1 LEG 4 R1 22
PANEL 5 HT 0.6000 TW 0.6000
FACE SH1 LEG 5 R1 22
PANEL 6 HT 0.6000 TW 0.6000
FACE SH1 LEG 6 R1 22
PANEL 7 HT 0.6000 TW 0.6000
FACE SH1 LEG 7 R1 22
PANEL 8 HT 0.6000 TW 0.6000
FACE SH1 LEG 8 R1 22
PANEL 9 HT 0.6000 TW 0.6000
FACE SH1 LEG 9 R1 22
PANEL 10 HT 0.6000 TW 0.6000
FACE SH1 LEG 10 R1 22
PANEL 11 HT 0.6000 TW 0.6000
FACE SH1 LEG 11 R1 22
PANEL 12 HT 0.6000 TW 0.6000
FACE SH1 LEG 12 R1 22
PANEL 13 HT 0.6000 TW 0.6000
FACE SH1 LEG 13 R1 22
PANEL 14 HT 0.6000 TW 0.6000
FACE SH1 LEG 14 R1 22
PANEL 15 HT 0.6000 TW 0.6000
FACE SH1 LEG 15 R1 22
PANEL 16 HT 0.6000 TW 0.6000
FACE SH1 LEG 16 R1 22
PANEL 17 HT 0.6000 TW 0.6000
FACE SH1 LEG 17 R1 22
PANEL 18 HT 0.6000 TW 0.6000
FACE SH1 LEG 18 R1 22
PANEL 19 HT 0.6000 TW 0.6000
SUPPORT
COORD 0.0 0.0 0.0 FIXED
END
EOF
TD File Examples
Example 1
The example below shows the TD file statements required to generate a
pyramidal face panel with two sets of cross-arms.
PANEL 1 HT 1.372 TW 0
FACE X0 LEG 1 H1 0 BR1 0
CROSS CT SPAN 6 RISE 7 CR1 10 CR2 12
CROSS CT SPAN 8
PANEL 3 HT 1.575
FACE XDM SPACE .788 .787 D
CROSS CT1 SPAN 8.32 CR1 10 CR2 12 CR3 15 CR4 16
PROFILE
FACES 4
WBASE 4.0
RLBAS 0.0
PANEL 1 HT 3.5 TW 3
FACE K1
FACEY K2
END
PROFILE
FACES 4
WBASE 4.0
DBASE 3.0
RLBAS 0.0
PROFILE
FACES 4
WBASE 8.0
DBASE 8.0
RLBAS 0.0
This example shows part of a tower with plan bracing at the top and at
the level of the X bracing intersection points. Only the members forming
the plan bracing are rendered.
PROFILE
FACES 4
WBASE 4.0
DBASE 4.0
RLBAS 0.0
General
This chapter shows the standard panels available in MStower. Many of
these have been included to assist in modelling existing towers or to give
the starting geometry for making a UDP. The inclusion of any particular
panel pattern should not be construed as a recommendation for its use.
General
While MStower has an extensive set of standard panels, there will be
times when some variant will be required to model a particular panel.
MStower allows you to create your own panels – user-defined panels, or
UDPs, for just this purpose. Unlike standard panels, which are scaled to
the dimensions specified in the tower data file, UDPs once created are of
fixed size.
Although data for the UDP is contained in a text file which may be
edited, the most expeditious way of creating a UDP is to start by
building a tower with standard panels that are as close to the final
configuration as possible, and then to extract and graphically edit a panel
as required. MStower has facilities (see “8:Graphics Input for UDPs”
on page 125) that allow UDPs to be created and manipulated using a
CAD-like interface. For most UDPs you will never need to edit the text
file.
UDPs
Select the UDP File to Graphics command and the dialog box below
will be shown. Select the UDP to be edited and proceed as if part way
through making a UDP.
Note: Any Microstran job from which you want to create a UDP must
be compatible with the basic assumptions in MStower: the Z axis is
vertical and forms the central axis of the tower and there is a face normal
to the positive X axis. It is not difficult to adjust a job in Microstran that
does not meet these requirements.
Step 1
* Have MStower job (TOWR for example) and Microstran job (MICRO
for example) in the same data folder. Do not use the same name for both
jobs.
Step 2
* Open the Microstran job in Microstran.
* Export an archive file using the name of the MStower job
(TOWR for example).
* Close the Microstran job.
Step 3
* Edit the archive file in Microstran and change the name of the
Microstran library to that of the MStower library, e.g. change “Ukw.lib”
to “Uk.lib”.
Step 4
* Open the MStower job in MStower.
Step 5
* Select the command:
Tower >
Build Tower >
User Defined Panels >
Graphical Edit
* Select the command:
Files >
Import >
Archive File
to import the Towr.arc file.
* Delete members not in the UDP.
* Define member classes.
* Select the command:
Tower >
Build Tower >
User Defined Panels >
Graphics to UDP File
* Check that UDP file name is Towr.udp.
* Input the UDP name and UDP type.
COMPONENT
UDP1
UDP2
..
END
Here, the name of the file containing the UDPs is omitted and MStower
assumes them to be in a file named Job.udp, where “Job” is the name of
the job. When the job is saved the UDP file will be saved automatically
with it. Also, if the job is renamed in a Save As operation the UDP file
will be renamed.
It is not mandatory for the UDP file to be named after the job. For
example, if you have a number of towers all with a particular panel that
is a UDP you may place the UDP in a file not named after the job and it
may then be referenced by any number of jobs. The main advantage of
this is that the UDP needs to be created only once. Any changes to the
UDP will apply to all jobs that use the panel when those jobs are rebuilt.
If the changes are not required for all towers referencing the UDP you
must make the changes in a copy of the UDP file and change the
references in the COMPONENT block of each tower that is to use the
modified UDP.
Note: Only UDPs in a file named after the job are automatically saved
when the job is saved.
General
Graphics Input is the most efficient input method of inputting a user-
defined panel. It involves “drawing” a structure on the screen using the
mouse or keyboard, and it includes many simple graphical operations,
such as copying, moving, rotating, sub-dividing, and erasing. More
powerful graphical operations include intersection, extrusion, and
transforming coordinates. In effect, MStower’s graphical input capability
is an intelligent CAD system customized for the task of entering structure
data.
GRAPHICS INPUT
You may find that the few hours required to become proficient at
graphical input will be well rewarded by much increased productivity in
creating and editing UDPs.
Basic Drawing
Graphics Input is started by selecting Tower > Build Tower > User-
Defined Panels > Graphics Edit. You will also be in Graphics Input
mode when you import an existing UDP by selecting Tower > Build
Tower > User-Defined Panels > UDP To Graphics.
To start drawing a UDP, click on the toolbar button. This is the same
as selecting the Structure > Draw Members command from the main
menu. Notice the tooltip “Draw Members” that appears when the mouse
cursor crosses this button.
As you initiate the Draw command several things happen:
1. The toolbar button displays in the depressed state, indicating that
MStower is in DRAW mode.
2. “DRAW” is displayed in the status bar at the bottom of the
MStower window.
3. The prompt area of the status bar (on the left) displays the
instruction “Click on first point or enter coordinates”.
4. The cursor becomes a cross.
You may now click anywhere in the main window or enter coordinates
from the keyboard to locate the “A” node of the first member. Notice
that once the first point is specified the prompt changes to “Click on end
point or enter coordinates; press SPACE BAR to break line”. Select
another point and you will have drawn the first member. This point is the
“B” node of the first member and the “A” node of the next member. You
may continue selecting points to define new members.
Coordinate Systems
You may input coordinates in rectangular, cylindrical, or spherical
coordinate systems, using standard syntax or AutoCAD syntax. The
format of the coordinate string is described below for each syntax.
STANDARD SYNTAX
• Rectangular coordinates
“X Y Z”, where “X”, “Y”, and “Z” are respectively, the X, Y, and Z
coordinates of the point.
• Cylindrical coordinates
“C radius theta h”, where “radius”, “theta”, and “h” are respectively,
the radius, horizontal angle, and height of the point.
• Spherical coordinates
“S radius theta phi”, where “radius”, “theta”, and “phi” are
respectively, the radius, horizontal angle, and vertical angle of the
point.
Trailing zero coordinates do not have to be entered. For example, the
point (3,0,0) may be entered as “3”. Coordinates must be separated by a
space or a comma. Coordinates relative to the last point are preceded by
“R” or “r”. No separator is required after the “R” or “r”.
AUTOCAD SYNTAX
• Rectangular coordinates
“X Y Z”, where “X”, “Y”, and “Z” are respectively, the X, Y, and Z
coordinates of the point.
• Cylindrical coordinates
“radius < theta h”, where “radius”, “theta”, and “h” are respectively,
the radius, horizontal angle, and height of the point. The last two
values must be separated by a space or a comma.
• Spherical coordinates
“radius < theta < phi”, where “radius”, “theta”, and “phi” are
respectively, the radius, horizontal angle, and vertical angle of the
point.
Coordinates relative to the last point are preceded by “@”. No separator
is required after the “@”.
Breaking the Line
Press the space bar or right-click and choose Break Line on the context
menu. Notice that the cursor, the status bar, and the button show that
MStower is still in Draw mode. You may now click a new node that is
not connected to the last by a member.
Shortcut Command
Ctrl+C Copy
Ctrl+X Cut
Ctrl+V Paste
Ctrl+Z Undo
Ctrl+Y Redo
F5 Redraw
Ctrl+A Select All
Delete Erase Members
Home Zoom Extents/Limits
Viewpoint Left
Viewpoint Right
Viewpoint Up
Viewpoint Down
Space Break Line
The OK button in this dialog box is disabled. You may use the dialog
box to check properties but you will not be able to change them.
The OK button in this dialog box is disabled. You may use the dialog
box to check properties but you will not be able to change them.
Extrusion
There is a check box for “Extrude nodes” in each of the Linear Copy,
Polar Copy, and Reflect dialog boxes. When you perform a copy
Key concept. operation you may “extrude” each copied node into a series of members
– in other words, there will be a string of new members lying on the path
traced out by each node involved in the copy operation. The member x
axis is aligned with the direction of extrusion.
Interrupting Commands
The diagram below shows the View toolbar, normally docked at the top
of the MStower window.
VIEW TOOLBAR
DRAW TOOLBAR
Firstly, a member is added to represent the stretch vector. All the nodes
to be transformed are highlighted. Node 2 is selected as the fixed node.
Nodes 12 and 13 are selected to define the stretch vector. The diagram
below shows the truss on completion of the command.
If you inadvertently click on the wrong node when selecting the fixed
node or the start of the stretch vector, you can abort the command by
selecting the start of the stretch vector as the end point also.
The Stretch command could be used to input tower cross-arms as a
parallel chord truss, which is later tapered, as in the example above.
The commands on the View > Limit menu allow you to restrict activity
to a selected part of the structure. The rest of the structure may be greyed
out or hidden from view. This has the advantage that the view you are
working on is uncluttered by irrelevant detail and the rest of the structure
is inaccessible while Limit is in effect.
The Limit > Window command, , was used to select one segment of
the tower in the diagram below. To hide the rest of the structure right-
click and uncheck Show Outside Limits.
* Check the box to provide a skeleton block for UDPs and remove
checks from all other options. The tower width must be defined at bend
points only. In this case, input a top width of 2m for the first panel and
zero for the remaining panels. MStower interpolates all intermediate
widths.
COMPONENT
$ TODO - udp list goes here
END
PROFILE
FACES 4
WBASE 4.0000
RLBAS 0.0000
$ TODO:
$ Remove '$' and replace '?' with appropriate
$ section numbers in following PANEL blocks.
PANEL 2 HT 2.500
FACE X $ LEG ? BR1 ? H1 ?
PANEL 3 HT 4.000
FACE K $ LEG ? BR1 ? H1 ?
PANEL 4 HT 4.000
FACE K $ LEG ? BR1 ? H1 ?
END
END
BUILT TOWER
Note that the Draw and Attributes toolbars on the right of the screen are
disabled at this stage.
* Click the right mouse button to confirm the selection. Only the
members of panel 3 should now be displayed.
Note: If you are unsure about methods of selection and graphical input
you should review material at the beginning of this chapter.
PANEL 3 HT 4.000
$ FACE K $ LEG ? BR1 ? H1 ? R1 ?
FACE @P3
Here, the FACE K line has been commented out with the $ character but
retained in the file to indicate the panel type used as the basis for the
UDP.
* Save the edited TD file and close MsEdit.
* Rebuild the tower and inspect to ensure that the UDP is as required.
* If the UDP must be modified select the command
Tower > Build Tower > User Defined Panels > UDP File to Graphics
and select the UDP to be modified (P3 in this case).
* After making any necessary modification select the command
Tower > Build Tower > User Defined Panels > Graphics to UDP File
If the UDP file already exists a message box is displayed…
General
This chapter describes the operation of the MStower loading module in
computing loads on the tower and ancillaries in accordance with the
requirements of:
• BS 8100 Part 1 2005
• BS 8100 Part 4 1995
• BS 8100 Part 4 Amendment 1 2001
• AS 3995-1994
• AS 1170.2-2002
• Malaysian Electricity Supply Regulations 1990
• EIA/TIA-222-F-1991
• TIA-222-G-2005
• Institution of Lighting Engineers Technical Report No. 7 –
High Masts for Lighting and CCTV – 2000 Edition
• IS 875 (Part 3):1987
• ASCE 7-95
• BNBC 93 – Bangladesh National Building Code
Loading types include dead load, ice load (with and without wind), node
loads, wind loading on the structure, its ancillaries, feeders, and
attachments, and temperature loads.
Tower loading represented as node loads are computed for wind acting
at any angle to the tower, with and without icing of members, as well as
gravity loads due to self weight and icing. Additional node forces may
be specified for any primary load case. Combination load cases may also
be defined.
Code partial safety factors may be specified directly or as factors in
combination load cases.
Parameters Block
PARAMETERS
ANGN an
[CODE code]
where:
ANGN Keyword.
an The angle, in degrees, measured anti-clockwise from the X axis
to geographic north.
CODE Keyword.
code Character string indicating the code rules to be followed in
computing the wind and other loading:
BS8100
Use the rules of BS 8100 Part 1 with
Amendment 1 – May 2005.
BS8100A1
Use the rules of BS 8100 Part 4 with
Amendment 1 – April 2003.
BS6399
Use the rules of BS 6399.
MER
Use the rules of the Malaysian Electricity Supply Regulations
1990 – See note below.
AS3995
Use the rules of AS 3995.
AS1170
Use the rules of AS 1170.
EIA222
Use the rules of EIA/TIA-222-F.
TIA222G
Use the rules of TIA-222-G.
ILETR7
Use the rules of the Institution of Lighting Engineers
Technical Report No. 7.
Damping
British codes BS 8100, BS 6399, and ILE TR7 use the logarithmic
decrement of damping, δ. Other codes use the ratio of the actual
damping to the critical damping, ζ, where
δ = 2π ζ / √(1 – ζ2)
Basic Velocity
The definition of the basic velocity vb depends on the code being used.
AS 1170.2 VR, regional 3 second gust wind speed for required return
period, Fig. 3.1 and Table 3.1.
AS 3995 Vu, basic wind speed for ultimate limit state Fig. 2.2.
VR and VU are not the same.
BS 8100 Part 1 Hourly mean wind speed, Fig. 3.1.
BS 8100 Part 4 Hourly mean wind speed, Fig. 2.
BS 6399 Hourly mean, BS 6399 Part 2, Fig. 6.
ILETR7 Hourly mean, BS 6399 Part 2, Fig. 6.
ASCE 7-02 3-second gust wind speed, ASCE 7-02, Fig. 6-1.
3-second gust wind speed, NSCP C101-1, Fig. 207-1.
EIA-222-F Fastest mile wind speed.
TIA-222-G 3-second gust wind speed.
IS 875 Part 3 3-second gust wind speed, Fig. 1.
BNBC Fastest mile wind speed, Fig. 6.2.1.
It is important that the basic velocity used in the tower data file is
consistent with the specified code. The figures and tables referred to
above are in the particular code. Meteorological specialists may need to
be consulted for sites for sites in other locations.
It is also important that the wind speeds conform to the requirements of
the code being used. Non-standard descriptions of wind speeds such as
“operational”, “survival”, or “extreme” are not used in any code
Note: The table on p. 225 of TIA-222-G and Fig. A.1 of BS 8100 Part 1
may assist in the conversion of wind speeds.
Terrain Block
This block is used to specify the variation of terrain factor with wind
direction around the tower. The data required depends on the loading
code being used.
The TERRAIN block for BS 8100 Part 1 is as follows:
TERRAIN
ANGLE angle TCAT tcat [Kd kd] [KR kr] [HH hh]...
[BETAH betah] [XLEE xlee]
END
where:
ANGLE Keyword.
angle Wind angle in degrees east of north.
TCAT Keyword.
tcat Terrain category in Arabic numerals. Intermediate terrain
categories may be given as a decimal, e.g. 2.5.
KR Keyword.
kr Terrain roughness factor. Interpolated from BS 8100 Table 3.1
if not specified.
KD Keyword.
kd Wind direction factor. Interpolated from BS 8100 Fig. 3.2 if not
specified. If ice is present a maximum value of 0.85 will be
used.
HH Keyword.
hh Height of hill above general terrain, in m or ft. Assumed to be
zero if not specified.
BETAH Keyword.
betah Effective slope of hill , in degrees. Assumed to be zero if not
specified.
XLEE Keyword.
xlee Downwind distance from the crest of the hill to tower site, in m
or ft. Assumed to be zero if not specified.
ABT Keyword.
abt The altitude of the general terrain in this direction. If defined
this value will be used to apply an altitude correction to the
PVEL_GUY
ZF z VF vfact
..
END
If PVEL_MAST and PVEL_GUY blocks are defined a number of “patch”
load cases will be generated as described in this chapter.
A user defined velocity profile may be used where the terrain is more
complex than can be modelled adequately by the topographic models in
the code. Only a single user defined profile is allowed and will be used
for all wind directions.
Where the tower is mounted on top of a building, its elevation in the
wind stream may be modelled by setting the value of RLBAS in the
tower data file the distance of the tower base above ground level, as in
the following diagram. This does not take account of any change in the
velocity profile caused by the presence of the building.
VELOCITY PROFILE
The node list establishes node number aliases that may replace a node
number anywhere in the TWR file. The aliases may be useful where
modifications to the geometry results in node numbers changing, for
example, when the tower is being studied for strengthening or a number
of different bracing patterns are being considered. If a family of
transmission towers is being designed the node list could define the
loading points with only the ZREF parameter being changed as
extensions are added.
Note: You may obtain the member number for a guy from the data tip
that appears when the cursor is placed on it, with the Query > Member
Data command, or by double-clicking on it.
Any EXTERN factor defined with wind load data will take precedence
over factors defined in an EXTERNAL block.
Loads Block
This block describes the load cases that are to be computed. Each
primary load case consists of a CASE description, a specification for a
wind, dead, or ice load, and optionally, additional node loads that are to
form part of that load case. Combination load cases consist of a CASE
description and a number of load case references and factors.
All loads on the tower should be described in the LOADS block.
LOADS
CASE..
CASE..
Wind, dead, ice, earthquake, or miscellaneous load
Additional node loads
Additional member temperatures
..
CASE..
Combination load case
..
END
where:
ANGLX Keyword.
wangx Angle in degrees (anti-clockwise) from the global X axis. It is
recommended that wind direction be specified with respect to
the tower X axis rather than as a bearing (clockwise from
north). The latter is included for compatibility with prior
versions of MStower.
ANGLE Keyword.
wangn Angle in degrees (clockwise) from geographic north.
ICE Keyword indicating that ice is to be considered for this case.
NOICE Keyword indicating that ice is not to be considered for this
case.
BARE Keyword indicating that wind load is to be computed for the
bare tower, i.e., the tower without any ancillaries.
CROSS Keyword indicating that MStower is to generate sub-load cases
If the MEAN wind speed is being used the basic wind load case lcase
contains the loads due to the mean hourly wind applied to the equivalent
bare tower. This is followed by sequentially numbered sub-cases, the
first containing the fluctuating component of the wind load on the large
ancillaries, and the second the sum of the mean hourly loads on the
tower and ancillaries.
The CROSS wind load cases are required additional sub-cases containing
the loads due to cross-wind on the equivalent bare tower and the
fluctuating component of the cross-wind on the ancillaries are generated.
If the GUST wind speed is being used, the along-wind loads on the large
ancillaries are accumulated into the basic wind load case and no
additional sub-loads are formed. You must leave gaps in the numbering
of wind load cases to accommodate the sub-cases; a difference of 10
between successive cases is sufficient and convenient.
The SMEAR keyword used in previous versions to compute the uniform
load on guys for BS 8100 Part 4 patch load cases is no longer required.
The optional data item ZGUST z1 .. GFACT gf may be used to:
• Modify the wind loads over a section of the tower when dealing
with a tower that is Eiffelized.
• Model the variation of the gust response factor with height for
dynamically sensitive towers when computing wind loads to
AS 3995 or AS 1170.
• Model patch load cases for masts when using TIA-222-G.
Dead Loads
DL [BARE] [GUYS]
where:
DL Keyword signifying a dead load case. The weight of all
ancillaries will be included in the load case.
BARE Keyword. If present, the dead load is computed for the tower
structure only, without ancillaries.
GUYS Keyword. If present, the dead load of the guys only will be
computed. For use with TIA-222-G, where different load
factors are applied to the guys and shaft of the mast.
Ice Loads
ICE DENS dens {WIND|NOWIND} [BARE] [UNICE list]
where:
ICE Keyword signifying a gravity load due to icing of the tower.
The weight of ice coating structural members and ancillaries
will be taken into account.
DENS Keyword.
dens Specific weight of ice, in kN/m3 or lb/ft3.
WIND Keyword indicating presence of wind.
Miscellaneous Loads
Load cases not falling into one of the above categories may be included
as miscellaneous loads. These could include construction, maintenance,
or similar loads.
MI
NDLD list FX fx FY fy FZ fz
..
where:
MI Keyword.
NDLD See “Additional Node Loads”, below.
Uniform Acceleration
EQ {ACCEL|GACCEL} X x Y y Z z
where:
EQ Keyword.
ACCEL Keyword indicating that acceleration values are in absolute
units of either m/sec2 or ft/sec2.
GACCEL Keyword indicating that acceleration values are to be
multiplied by “g”, the acceleration due to gravity.
X Keyword.
x Acceleration in the global X direction.
Y Keyword.
y Acceleration in the global Y direction.
Z Keyword.
z Acceleration in the global Z direction.
The total seismic shear, Vs, is obtained as the product of vsm and the
weight of the structure.
The seismic force at the top of the structure is (ft × Vs) with the
remainder of the seismic force being distributed over the height of the
structure according to the formula:
Fsz = wz hz ke / Sum (wi hi ke ) × Vs (1 – ft)
The equivalent modal analysis procedure uses the equations of Cl. 2.7.8
of EIA-222-G.5.
Each earthquake load case will normally be used in at least two
combination load cases with positive and negative factors.
Panel Block
The panels into which the tower is divided are defined by listing nodes at
the panel boundaries in order from the top of the tower. The Z
coordinates of these nodes will be used when determining the panel to
which projected areas of member and ancillaries are allocated. The list of
nodes may extend over one or more lines. If the PANEL block is not
specified panel heights will be obtained from the Job.TWM file,
generated by the tower builder. The PANEL block is not usually
required.
ANCILLARIES
Linear Ancillaries
Linear ancillaries are items such as wave-guides, feeders and the like.
Usually they are either attached to the face of the tower or contained
within the body of the tower. The following data is required:
LINEAR LIB libr
name XB xb YB yb ZB zb [XT xt] [YT yt] ZT zt...
[SELF] LIB lname [FACT fact] [SHADE shade]...
[SHADY shady] ANG anga
..
where:
LINEAR Keyword.
LIB Keyword.
Face Ancillaries
These are ancillaries mounted on the faces of the tower and consisting of
small items whose wind resistances will be added to that of the panel of
the face to which they are attached.
FACE
name FACE flist ZA za MASS mass CN cn...
AREA area AICE aice {FLAT|CYL}
..
where:
FACE Keyword.
name Identifier for the ancillary – 1-16 characters, not recognizable
as a number.
FACE Keyword.
flist List of faces to which ancillaries of this type are attached, as a
concatenated string of the digits 1, 2, 3, and 4, with no
embedded spaces, e.g. 13 means the ancillaries are on faces 1
and 3.
ZA Keyword.
za Z coordinate of the mounted level of the ancillary, in m or ft.
MASS Keyword.
mass Mass of the ancillary, in kg or lb.
CN Keyword.
cn Drag coefficient for wind normal to the face to which the
ancillary is attached.
AREA Keyword.
area Projected area of the ancillary on the face of the tower, in m2 or
ft2.
AICE Keyword.
aice Surface area that can be coated with ice, in m2 or ft2. The
volume of ice is obtained by multiplying this area by the
thickness of ice.
FLAT Keyword indicating that the ancillary is to be considered as
sharp edged.
CYL Keyword indicating that the ancillary is to be considered as
cylindrical.
Resistances
Resistance, either additive or total, may be used to model the loading on
sections of the tower. For example if a section of a tower is completely
clad in panels, it may be more accurate to use an overall resistance for
this section that to use a sum of the loads on individual panels and
section of the tower. The data required is:
RESISTANCE
name ZB zb ZT zt [ARES|TRES|BRES] res
..
where:
Insulators
These may be used to separate sections of a multi-segment guy. They are
described as:
INSULATORS
name NODE node AREA area AICE aice...
MASS mass CN cn
..
where:
INSULATORS Keyword.
name Identifier for the insulator – 1-16 characters, not
recognizable as a number.
NODE Keyword.
node Node number at which the insulator is located.
AREA Keyword.
area Projected area of the insulator, in m2 or ft2. It is assumed that
the projected area is the same for all angles of wind
incidence.
Note: You may obtain the node number for an insulator from the data
tip that appears when the cursor is placed on it, with the Query > Node
Data command, or by double-clicking on it.
Output
The following tables of intermediate results computed by the loading
module are written to a loading log file and may be viewed by selecting
the File > List/Edit > Loading Log command or printed by selecting
the File > Print > Loading Log command.
Velocity Table
The input and computed parameters used in computing the velocity
profile and the variation of velocity with height above the base of the
tower are reported.
Member/Face Table
Each member is allocated to a tower face and its projected length in the
face is reported. Leg members will belong to two faces while internal
members, such as hip and plan bracing, will not belong to any face. The
length of bracing members that intersect leg members is adjusted for the
overlap between the IP and the edge of the leg member if the overlap
flag in the PARAMETERS block is set to 1.
Face Results
The area of each panel, its solidity ratio, and drag coefficient, the
resistance of ancillaries, shielding factor, Sf, and the normal resistance of
the face as a single frame are reported for each face.
Resistance Table
The effective resistance, Re1 and Re2, and the total wind resistance,
Rwt, for the specified wind angle are reported, along with the total mass
(structural and ancillary) of each panel. The factor determining whether
the equivalent static method is valid is also reported.
BS 8100
The velocity, VB, should be specified as MEAN.
MStower uses the general method of BS 8100 for computing the wind
resistance of towers. This method allows for towers with faces that are
asymmetrical, either structurally or due to their complement of
ancillaries. It also allows the resistance to be computed for any wind
incidence angle. When using the general method, the resistance of the
single frame comprised in each face is computed, along with shielding
factors and Kth. The resistance of the complete tower is built up from
these values. Methods of computing drag coefficients of panels made of
flat and circular sections (both sub-critical and super-critical) are also
given. BS 8100 also uses a simpler method for symmetrical towers,
whereby the resistance for the complete tower can be determined from
drag factors for the overall tower.
If a panel contains ancillaries, the projected area of the ancillary is used
when computing panel solidity ratios and single panel drag coefficients.
The wind forces on the ancillary are then computed using the drag
coefficients from the ancillary library and a statically equivalent set of
node loads is applied to the nodes to which the ancillary is attached.
Gust Factor Correction
If BS 8100 Part 1 is specified with a mean hourly wind speed, each wind
load case will consist of:
1. A load case containing forces on the equivalent bare tower due to
the mean wind.
2. A sub-load case containing forces on the large ancillaries due to the
mean wind multiplied by the gust factor appropriate to each
ancillary’s size and height above ground level.
3. A sub-load case containing the sum of the mean wind loads on the
tower and ancillaries.
AS 3995
When AS 3995 is specified MStower uses the general method as
described above but with single frame drag coefficients that give overall
drag coefficients equal to those in Table 2.2.8.2 of AS 3995. This allows
the program to maintain the ability to deal with towers that are
asymmetrical or composed of mixed section shapes. It also allows wind
forces to be computed for angles of incidence other than face and corner.
For a tower carrying large dishes, the critical wind may occur at some
other angle, which may vary from member to member.
AS 1170
When AS 1170 is specified wind forces are computed as the sum of the
wind load on the tower structure and that on the linear and large
ancillaries. The area of face ancillaries is added to that of panels in
computing solidity ratios. The drag force on ancillaries is multiplied by
an interference factor, KIN, whose magnitude depends on the solidity of
the tower and location and type of ancillary.
TIA-222-G
The wind velocity, VB, should be the 3-second gust wind speed. No
modifying keyword (MEAN or GUST) is required. MStower computes the
solidity of each face from the projected area of members and those linear
ancillaries that are within the face zone. The solidity of the most
windward faces is then used in computing the EPA (equivalent projected
area or resistance) of each panel of the tower.
All wind loads, including any NDLD forces specified in a WL case, are
multiplied by a gust response factor determined in accordance with Cl.
2.6.7.
BS 8100
Cl. 5.2.5 of BS 8100 Part 1 gives two serviceability criteria that may be
used. The gust-factoring process in MStower V6.2 modifies the
deflections for wind load cases and sub-load cases to provide deflections
that may be used in clauses (a) and (b) of Cl. 5.2.5. After gust-factoring
the deflections for towers are:
Base WL case (see 1 above):
[ (1 + GB) DTE + (1 + GA) DAW ] (SP / γV )2
Mean wind load case (see 3 above):
DMW (SP / γV)2
where:
GB Gust factor for leg loading at the base of the tower.
DTE Deflection for hourly mean wind on the equivalent bare tower.
GA Gust factor for ancillaries.
DAW Deflection for hourly mean wind on large ancillaries.
SP Probability factor computed from BS 6399 Part 2 Annex D for
serviceability return period. See RPSERV in Parameter block.
γV Partial safety factor on wind speed.
DMW Deflection for hourly mean wind on tower and ancillaries.
The gust-factored deflections from the base wind load case will be used
to update any combination load case that references a wind load case.
The gust-factored deflections are in a form that may be more readily
used in Cl. 3.3.2 of the code.
For masts, the gust-factored deflections are the deflections from the
analysis multiplied by the factor (SP / γV)2.
Other Codes
If the wind speed for serviceability differs from that used in member
checking, additional serviceability combinations will be required. In
these load cases the load factor applied to the wind load component must
be multiplied by the square of the ratio of the service wind speed to the
basic wind speed.
BS 8100
There is no codified method of taking dynamic effects into account. The
code recommends a spectral analysis if the equivalent static factor is
above 1.0. This type of analysis requires specialist knowledge and
experience. It is not available in Mstower. If necessary, such effects may
be accounted for by applying increased factors to wind loads in
combination load cases.
AS 3995
For towers, dynamic effects are taken into account by applying gust
response factors, GS, specified in Cl. 2.3.8 of the code, to the wind forces
obtained by applying the design mean wind speed. The gust response
factor varies over the height of the tower. A number of load cases may
be required for each wind direction to model the variation in gust
response factor. The codified method is not applicable to guyed masts.
The following data is required in the PARAMETERS block:
FREQ freq
TDAMP tdamp
The program computes the value of the gust response factor at the height
of each panel top and for each WL case outputs a table of these factors in
the loading log and also in the file Job.gfa, where “Job” is the job name.
To use them you will need to create sufficient WL cases for each wind
direction to model the variation of the gust response factor with height:
CASE n WL direction1
WL ANGLX ang1 .. ZGUST zgust1 GFACT gfact1
CASE n+1 WL direction1
WL ANGLX ang1 .. ZGUST zgust2 GFACT gfact2
CASE n+2 WL direction1
WL ANGLX ang1 .. ZGUST zgust3 GFACT gfact3
..
The program will multiply all wind forces above level zgust by
gfact.
Each combination load case that references a wind load will have to be
expanded in a similar fashion.
EIA-222-F
There is no codified method of taking account of the dynamic
amplification of wind loads. If necessary, such effects may be accounted
for by applying increased factors to wind loads in combination load
cases.
TIA-222-G
There is no codified method to take account of the dynamic
amplification of wind loads. If necessary, such effects may be accounted
for by applying increased factors to wind loads in combination load
cases. If the fundamental frequency and total damping are defined in the
PARAMETERS block, the gust effect factor will be computed in
accordance with 6.7.8 of SEI/ASCE 7-02.
ASCE 7
For towers, dynamic effects may be taken into account by applying a
gust effect factor, G, that allows for a resonant effect in the response as
IS 875
For towers, dynamic effects may be taken into account by applying a
gust factor, G, specified in Section 8, to the mean load. The codified
method is not applicable to guyed masts.
The following data is required in the PARAMETERS block:
FREQ freq
TDAMP tdamp
The program will compute and use a gust effect factor that takes account
of the dynamic effects.
BNBC
For towers, dynamic effects may be taken into account by applying a
gust factor, Gbar, specified in Section 8, to the load computed from the
fastest mile wind speed. The codified method is not applicable to guyed
masts.
The following data is required in the PARAMETERS block:
FREQ freq
TDAMP tdamp
The program will compute and use a gust effect factor that takes account
of the dynamic effects.
ILE TR7
The loads from the design wind are multiplied by a factor that is a
function of the pole natural frequency, height, and damping ratios.
The following data is required in the PARAMETERS block:
[FREQ freq]
SDAMP sdamp
[ADAMP adamp]
[TDAMP tdamp]
The program will compute and use a gust effect factor that takes account
of the dynamic effects. The parameters enclosed in square brackets are
optional; if not input they will be computed by the program.
The forces and moments at the origin of the antenna are given by:
Fx = 0.5 ρ × Cfx × Af × V2
Fy = 0.5 ρ × Cfy × Af × V2
Fz = 0.5 ρ × Cfz × Af × V2
Mx = 0.5 ρ × Cmx × a × Af × V2
My = 0.5 ρ × Cmy × a × Af × V2
Mz = 0.5 ρ × Cmz × a × Af × V2
where “a” is a lever-arm.
If necessary, the coefficients for the angle of wind incidence are
interpolated from the coefficients table. All dimensions and forces for an
antenna are measured in the ancillary axes, a set of right-handed
orthogonal axes (see diagram in “Ancillary Block” on page 169).
The forces and moments at the origin of the ancillary are given by:
FX = 0.5 ρ × Cfx × Af × V²
FY = 0.5 ρ × Cfy × Af × V²
If necessary, the coefficients for the angle of wind incidence are
interpolated from the coefficients table. All dimensions and forces for an
antenna are measured in the ancillary axes, a set of right-handed
orthogonal axes (see diagram in “Ancillary Block” on page 169).
General
The CAD interface is an integral part of MStower that offers the
capability of exporting 3-D data to a CAD system, forming the basis for
a CAD drawing. This function is selected with the File > Export > CAD
DXF command. Structure information is exchanged by means of an
AutoCAD DXF.
Note: You can use the Windows Paste command to transfer any part of
an MStower image into CAD.
GRADES
250L0 250
300 300
350 350
C250 C250
C350 C350
C450 C450
C450L0 C450L0
43 43A
50 50B
END
SECTIONS $ AS sections
$ MStower Xsteel
690UB140 UB690*140
690UB125 UB690*125
610UB125 UB610*125
610UB113 UB610*113
610UB101 UB610*101
530UB92.4 UB530*92
530UB82.0 UB530*82
460UB82.1 UB460*82
460UB74.6 UB460*74
460UB67.1 UB460*67
410UB59.7 UB410*60
410UB53.7 UB410*54
General
MStower offers a number of static and dynamic analysis options, each of
which employs exhaustive consistency checking and highly efficient
equation solution procedures. The analysis engines used in MStower are
derived from those used in Microstran, a widely-used and extremely
versatile program for analysing and designing structural frameworks in
steel and reinforced concrete.
Linear Elastic Analysis is a first-order elastic static analysis in which
non-linear effects are ignored and the stiffness equations are solved for
only the primary load cases. Solutions for combination load cases are
obtained by superposition of the solutions for the primary load cases.
Non-Linear Analysis is a second-order elastic analysis, which enables
you to take into account the non-linear actions arising from the
displacement of loads (the P-∆ effect), the change in flexural stiffness of
members subjected to axial forces (the P-δ effect), and the shortening of
members subjected to bending (the flexural shortening effect). Non-
linear analysis is an iterative procedure in which the behaviour at each
step is controlled by a number of parameters. Each selected case,
whether a primary or combination load case, must be solved separately,
as superposition of results cannot be used. Members defined as tension-
only will be checked at each iteration and included or excluded
accordingly.
Elastic Critical Load Analysis calculates the frame buckling load
factor, λc, for selected load cases and computes the corresponding
member effective lengths for each load case.
Dynamic Analysis computes the natural vibration frequencies of the
structure and the associated mode shapes. The dynamic loads on the
structure due to earthquake or other support acceleration may then be
assessed using the response spectrum method.
The Profile Optimizer is used in all analyses to minimize analysis time
and storage requirements. Nodes and members can therefore be
numbered for maximum convenience in data generation and
interpretation of results.
Consistency Check
MStower performs an automatic check of all input data prior to analysis.
The consistency check will detect a range of modelling problems related
to geometry and loading. Data errors and warnings are shown in the
Output window and are also written to the error report, which can be
listed and printed using options on the File menu.
Accuracy
All analyses use double-precision arithmetic to minimize the loss of
precision inherent in the many arithmetic operations required for solving
large, complex structural models. After the decomposition of the [K]
matrix MStower reports the maximum condition number, a measure of
the loss of precision that has occurred during the solution. For “well-
conditioned” structural models (those in which little numerical precision
is lost) the condition number will be less than 104. If the condition
number exceeds this value you should treat the results with caution and
look for evidence of “ill-conditioning”. For example, the large
displacement of a node or group of nodes may indicate that the structure
is acting, to some extent, as a mechanism, and the results could be
meaningless.
An important independent check on the accuracy of the solution is
provided by the node equilibrium check. At unrestrained nodes the sum
of all the member end actions is compared to the sum of external forces
acting on the node. Any difference is a force residual, the out-of-balance
force. The maximum residual is reported to the screen after the analysis.
The maximum residual should be considered in conjunction with the
magnitudes of the applied loads in assessing the adequacy of the
solution.
Note: A satisfactory equilibrium check, by itself, is not sufficient to
ensure an accurate solution – the condition number must also be
satisfactory.
Non-Linear Analysis
Non-Linear analysis (also called second-order analysis) performs an
elastic analysis in which second-order effects may be considered. The
different second-order effects are described below.
Non-linear analysis uses a multi-step procedure that commences with a
linear elastic analysis. The load residuals, computed for the structure in
its displaced position and with the stiffness of members modified, are
applied as a new load vector to compute corrections to the initial
solution. Further corrections are computed until convergence occurs.
There is no single method of iterative non-linear analysis for which
convergence is guaranteed. It may therefore be necessary to adjust the
analysis control parameters in order to obtain a satisfactory solution.
The solution may not converge if the structure is subject to gross
deformation or if it is highly non-linear. This may be the case as the
elastic critical load is approached.
Note: You should not attempt to use non-linear analysis to determine
elastic critical loads. Results of non-linear analysis should be treated
with caution whenever the loading is close to the elastic critical load.
Node Axial
Coordinate Force Analysis Type
Update Effects
NO NO Linear elastic analysis with tension-only or
compression-only members taken into
account. This can be achieved for any load
case by selecting linear analysis
YES NO Analysis includes the effects of
displacement due to sidesway but not
changes in member flexural stiffness due to
axial force. These settings will usually yield
satisfactory results for pin-jointed
structures.
NO YES Full account is taken of the effects of axial
force on member flexural stiffness while
the effects of node displacement are
approximated by a sidesway correction in
the stability function formulation. These
settings normally give minimum solution
time with second-order effects taken into
account.
YES YES This is the default analysis type, which
provides the most rigorous solution for all
structure types.
.
NON-LINEAR ANALYSIS PARAMETERS
Instability
Instability detected during linear analysis is usually due to modelling
problems and some of the common causes of these are discussed
elsewhere.
Because a non-linear analysis considers the effects of axial force on
member stiffness it is able to detect a range of instability that linear
analysis cannot. For example, non-linear analysis may detect buckling of
individual members or of the whole frame. The manner in which a
structure is modelled and the analysis parameters used can have some
Dynamic Analysis
Dynamic analysis computes the frequencies and mode shapes of the
natural vibration modes of the structural model. Only the mass and
stiffness of the model are considered in computing natural frequencies
and mode shapes. Static load cases are ignored. The frame mass is
computed automatically and modelled as node masses. Member masses
are computed automatically as the product of the cross-sectional area and
the mass density. The masses of ancillary equipment are taken into
account by masses lumped at attachment nodes.
Select the Analyse > Dynamic command to start dynamic analysis.
Dynamic Modes
After completing a dynamic analysis it is important to check the mode
shapes to ensure that you have the required dynamic modes. MStower
computes all dynamic modes, including torsional modes. The easiest
way to examine the results is to display an animated view of the
computed mode shapes.
The diagram below shows the mode shape computed for the first mode
in dynamic analysis of the TWEX5 example.
2. Select dynamic analysis, set the number of modes, and check Verify
eigenvalues and Response spectrum analysis.
3. Select the first RSA primary case (105 in the above example).
5. For each earthquake load case damping ratios are specified. The
“Complete Quadratic Combination” method (CQC) for combining
modal responses is used to determine the peak response. This is
equivalent to the “Square Root of the Sum of Squares” (SRSS)
method if all modal damping ratios are zero.
7. After Steps 3-6 have been completed for each earthquake case, the
dynamic analysis proceeds. On completion, select the Analyse >
Response Spectrum command to scale the computed actions and
combine them with the static analysis results (note that this item is
greyed out on the menu until all the necessary preconditions for
response spectrum analysis have been completed). The total
reactions (base shears) are displayed for each earthquake case and
you now enter scale factors for each case. The spreadsheets referred
to above will assist you in computing scale factors to comply with
code requirements.
MStower now adds the results from the response spectrum analysis to
the static analysis results. Earthquake load cases may now be treated as
any other load case for the display and reporting of results and for
design.
If loads are computed to BS 8100, select Tower > Gust Factor to apply
gust factors to wind loads.
The complete procedure must be repeated if either the static or dynamic
analysis is re-run.
Note: The displaced shape represents the peak values of the
displacement during the earthquake event. There are no negative values.
Interpretation of the results should take this into account.
Note: After running response spectrum analysis you should look at the
dynamic analysis log file, which contains important data including mass
participation factors.
General
This chapter describes the MStower modules for checking the strength
of members in latticed towers and masts in accordance with the rules set
out in the following codes.
Towers and Masts
• BS 8100 Part 3
• BS 449
• ASCE 10-90
• ASCE 10-97
• EIA-222-F
• TIA-222-G
• AS 3995
• IS 802
Monopoles
• Institution of Lighting Engineers Technical Report 7 (ILETR7)
• ASCE Manual 72
• BS5950 Part 1
• AS 4100
• EIA-222-F
• TIA-222-G
The member checking modules use data generated by the tower builder,
loading modules, and the results of the static analysis.
Important Note:
Good engineering practice requires fully triangulated bracing in tower
structures. Non-triangulated bracing relies on the flexural stiffness of the
brace in one tower face to provide restraint to the brace in an adjacent
face. In some cases this may be satisfactory but in general it will not
provide the same degree of restraint offered by a fully triangulated
system; in particular, under corner winds the braces in adjacent faces can
have approximately equal compression forces and they will provide little
or no mutual restraint.
Operation
Start the code checking module by selecting the appropriate code from
the Member Check > Towers/Masts or Member Check > Poles
menus.
The report may be limited by selecting classes of members to be checked
and setting the report limit on the ratio of design load/capacity.
Two forms of report are produced, a summary report and a detailed
report. They may be viewed or printed by selecting File > List/Edit and
File > Print, respectively.
The utilization ratios may be displayed graphically by selecting
Results > Design Ratios.
Loading Parameters
It is of the greatest importance to use loading parameters that are
consistent with the code being used for checking the capacity of
members. Loading parameters required for each design code are listed
below. These lists are not exhaustive and should not be used as a
replacement for the relevant code.
BS 8100 Part 3
CODE BS8100 or BS8100P4 or BS8100A1
VB Mean hourly (MEAN)
PSF-V From Part 1 or Part 4 of BS 8100
PSF-M From Part 1 or Part 4 of BS 8100 or as amended in Part 3
Combination for compression:
γDL × DL + WL
BS 449
CODE BS8100
VB 3 sec. gust (GUST)
PSF-V 1.0
PSF-M 1.0
EIA-222-F
CODE EIA222
VB Fastest mile
Combination for compression:
DL + WL
TIA-222-G
CODE TIA222G
VB 3 sec. gust (GUST)
Combination for compression:
1.2×DL + 1.6×WL
AS 3995
CODE AS1170
VB 3 sec. gust (GUST)
Combination for compression:
DL + WL
IS 802
CODE IS875
VB 3 sec. gust (GUST)
Combination for compression:
DL + 1.5×WL
ILE TR7
CODE ILETR7
VB Mean hourly from BS 6399 Part 2
PSF-M 1.15
SDAMP Logarithmic decrement of damping for structure
Combination for compression:
DL + 1.25×WL
BS 5950
CODE BS6399
VB Mean hourly from BS 6399 Part 2
PSF-M 1.0
SDAMP Logarithmic decrement of damping for structure
Combination for compression:
1.2×DL + 1.4×WL
Wind loading will be computed using ILETR7 / BS 6399 methods. If the
pole is cantilevered, the wind loads will incorporate the response factor
and size factor from Figures 1 and 2 in ILETR7. If the pole is guyed,
these factors are not appropriate and any dynamic increase in loads must
be allowed for by increasing the factor applied to WL in the loading
combinations.
AS 4100
CODE AS1170
VB 3 sec. gust (GUST)
SDAMP Damping ratio for structure
Combination for compression:
1.2×DL + WL
Design Loads
Axial loads are taken from the results of the analysis (and any
subsequent gust-factoring) for legs, braces, and horizontals.
Secondary or redundant members are used to stabilize primary load
carrying members. Codes specify hypothetical forces that the redundant
system should be able to resist, usually as a percentage of the load
carried by the member being stabilized. The percentage may be fixed, or
it may be dependent on the slenderness of the stabilized member.
Previous versions of MStower checked all redundant members for the
full stabilizing force. For face members MStower V6.2 applies the
stabilizing force transversely to the member and distributes it through
the redundant systems using a truss analysis. No distribution is done for
redundants, such as hip and plan bracing that are not part of the tower
faces. Stabilizing forces are determined as follows:
BS 8100 Part 3
Two cases are considered, as described in Section 5.4 (a) and (b) of
Part 3.
The factors used to determine the stabilizing forces for face redundants
are printed in the detailed design report.
Steel Detailing
Information may be exported in SDNF format for transfer to third-party
steel detailing programs (e.g. Xsteel). Refer to “Exporting a Steel
Detailing Neutral File” on page 190.
General
MStower refers to one or more steel section libraries for information
required for analysis and checking of members. Section library files may
be in the program folder, the data folder, or in an optional designated
library folder. The library name is prefixed in TD files with P:, D:, and
L:, respectively, for these folders. The File > Configure > General >
Library File Folder command allows you to select the library folder.
You may edit any steel section library using the File > Configure >
Section Library Manager command or the File > Configure > Edit
Section Library command. New section libraries may also be created.
The File > Configure > Library Viewer command is convenient for
viewing library contents files, in addition to ancillary and guy library
files.
Section Library
MStower’s library files must have no more than 8 characters in their file
name and have the file name extension “lib” (e.g. As.lib, Uk.lib). They
cannot be listed, printed, or edited. For each library file there is a
corresponding source file, an ordinary text file having a file name
extension “asc”. Library source files may be manipulated by the Section
Library Manager or a text editor.
Section Name
Each section has a unique section name with up to 15 characters. Blanks
are not permitted. The section name must have one contiguous
alphabetic group between 1 and 4 characters long. This is the section
mnemonic.
Section Mnemonic
The section mnemonic is used in MStower for specifying sections to be
chosen automatically in design. It is embedded in the section name and,
apart from “X”, is the only part of the name that may be alphabetic. An
“X” character contiguous with the section mnemonic is part of the
section mnemonic. Apart from the section mnemonic, “X” characters
Steel Grades
MStower does not use steel grades. The library contains two yield stress
values for each section – if the second is not used it is input as zero.
Residual Stress Code
Some design codes (e.g. AS 4100) require information about the level of
residual stresses in a section. This is provided by the parameter
designated “f”. It is also used to distinguish between cold-form and hot-
rolled sections with the same design type (e.g. Schifflerized angles).
f Section Type
1 Stress relieved
2 Hot-rolled
3 Cold-formed
4 Lightly welded
5 Heavily welded
Compound Sections
Compound sections made up of angles or channels are available as
shown in the diagram below. Section Library Manager allows you to
change an angle or channel to a compound section. You may right-click
on any of these sections in the destination library and choose the
required compound section type in the pop-up menu.
COMPOUND SECTIONS
Then you enter the name of a new library in this folder or choose the
name of an existing library. Valid library source files have no more than
8 characters in the file name (excluding the .asc file name extension).
You may edit any library After you have selected the destination library, either an existing library
source file supplied but it is source file or a new one, the dialog box below is displayed. A tree view
preferable to copy it to a of the destination library, empty if new, is shown on the right while all
new library and edit that – available library source files are shown on the left. Each library may be
otherwise, you will lose your
expanded to show the sections contained.
changes when you next
update library files.
You may select any library or section on the left and click the arrow
button to send it to the destination library on the right. Double-clicking a
section on the right will display a dialog box in which you may alter any
value.
When the section library manager combines sections from existing
libraries units are automatically converted to those of the destination
library.
Example
In the following example an angle section from the UK library is added
to a pole library.
1. Start the section library manager and select the existing pole
library as the destination file.
2. Select the source library, Uk.asc, and expand to display section
names. Select the desired angle section, say EA100x100x8.
3. Click on the green arrow button to add the angle section to the
pole library.
4. Click OK to save and compile the library file.
Section property dialog boxes for some sections have an Ax, Ay button,
which computes shear areas. For an I section Ax is computed as the nett
web area and Ay is computed as 5/6 of the flange area. For SHS, RHS,
and box sections, Ax is the nett “web” area where the web is considered
to include both sides. Similarly, Ay is the nett area of the top and bottom
“flanges” – this does not include overhang in the case of the box section.
Note: Shear areas are usually set to zero, causing MStower to ignore
shear distortion.
The library compiler reads and interprets the library source file and
writes an MStower library file. The value of any section property value
input as zero is computed automatically provided sufficient dimensions
for the calculation have been input.
Note: You should be careful when directly editing a library source file
not to introduce errors. It is safer to use Section Library Manager.
LIBRARY VIEWER
Report Types
MStower can create report files at several stages during the building,
loading, analysis, and checking of a tower. Commands for printing or
displaying reports show the dialog box below, in which there is a button
for each available report. If the button is disabled it means that the report
file does not yet exist. Each report is discussed in this chapter. Input
files, such as the TD and TWR files may also be displayed or printed
from this dialog box.
Input/Analysis Report
The Input/Analysis report is obtained at any stage by selecting the
Reports > Input/Analysis command. The dialog below then allows you
to select the items you require in the report.
Static Log
The static log is a file created during linear or non-linear analysis that
lists several analysis parameters, including the condition number, a
measure of the numerical quality of the analysis.
Dynamic Log
The dynamic log is a file created during dynamic analysis that lists
several analysis parameters, including the natural vibration mode
frequencies.
Design Summary
The design summary report file contains a summary of the results of any
member checking operation including those performed by the
Member Check > Reactions and
Member Check > Ancillary Rotations commands.
It reports the critical load case and condition for the various member
classes in each panel. It also contains a table of quantities and may note
any geometric or other problems encountered during the checking
process. Where possible, symbols similar to those in the particular code
of practice to which the check is done are used in the report.
Reaction Report
The reaction report file is created by the
Member Check > Reactions command and appended to the Design
Summary report. It contains the reactions at the tower supports in the
global axes and also transformed into the direction of the individual leg
axes.
Rotation Report
The rotation report file is created by the
Member Check > Ancillary Rotations command and appended to the
Design Summary report. It is in two sections:
• A rotation envelope giving maximum rotations about the global axes
for the selected load cases. These rotations are computed by
considering the displacement of a plane through the leg nodes at the
top of each panel.
• The rotation of each large ancillary for each selected load case. The
rotations are computed by considering the displacement of a plane
through the first three attachment nodes and are given in the axes of
the ancillary.
The tabulated rotations are those due to deflection of the tower. They do
not account for any deflection in the ancillary mounting items.
General
Use the following procedure to run an MStower job:
1. Start MStower (see “Starting MStower” on page 10).
2. Select the File > Open command and in the dialog box browse to
the Examples folder. Choose one of the example jobs, say TWEX1,
and then click the Open button. The tower should now be displayed
– if not, select the Tower > Build Tower > Process Tower Data
File command
3. Select the Tower > Build/Load/Analyse command.
4. Close the analysis window when it displays “Linear analysis
completed”.
5. If checking to BS 8100 select the Tower > Gust Factor command.
6. Select the appropriate design code on the Member Check menu. If
checking to BS 8100, select only the first load case of each set of
combinations as the results of the gust factoring and square root of
the sum of the squares is written to this case.
7. Select the Results > Design Ratios command and the structure will
be displayed with overstressed members colored red.
8. To display the results of the member checking select the File >
List/Edit command and then click either the Summary or Detailed
button. The selected report file will now be displayed in the MsEdit
text editor. You may use the File > Print Preview command to see
each page of the report, exactly how it will appear when printed.
To run a mast job, proceed as set out above but when the Analysis Load
Cases dialog box appears select Case 100 and all combination load
cases. When the Non Linear Analysis Parameters dialog box is displayed
click OK to accept the default values. The non linear analysis required
for masts takes longer than linear analysis.
To run an existing MStower Version 4 job select the File > New
command, confirm the job file folder, enter the job name and then
proceed from Step 3, above.
TWEX1
PROFILE
FACES 4
WBASE 2.000
RLBAS 0.0000
$ Section 1 ------------------------------------------
PANEL 2 HT 1.000
FACE DL0 LEG 1 BR1 5
PANEL 3 HT 1.000
FACE DR LEG 1 BR1 6 H1 6
PLAN PL1A PB1 0 PB2 4 PB3 0
BOLT LEG 4 M16-8 BR 1 M16-8 H 1 M16-8 PB 1 M16-8
$ Section 2 ------------------------------------------
PANEL 4 HT 1.000
FACE DL LEG 2 BR1 6 H1 8
BOLT LEG 0
PANEL 5 HT 1.000
FACE DR LEG 2 BR1 6 H1 8
PLAN PL1A PB1 0 PB2 4 PB3 0
PANEL 6 HT 1.000
FACE DL LEG 2 BR1 6 H1 0
PANEL 7 HT 1.000
FACE DR LEG 2 BR1 6 H1 0
PANEL 8 HT 1.000
FACE DL LEG 3 BR1 7 H1 0
BOLT LEG 4 M16-8
$ Section 3 ------------------------------------------
PANEL 9 HT 1.500
FACE K LEG 3 BR1 5 H1 8
BOLT LEG 0
PANEL 10 HT 1.500
FACE K LEG 3 BR1 5 H1 8
PLAN PL1A PB1 0 PB2 4 PB3 0
PANEL 11 HT 2.000
FACE K LEG 3 BR1 7 H1 8
BOLT LEG 4 M20-82 $ Bolts in double shear
END
SECTIONS
$ BRACING
END
BOLTDATA
END
END
$ STATION
$ HEIGHT
$ NGR SP
$ MAP No
$ STRUCTURE
$ TYPE:-
$ MANUFACTURERS:-
$ ANCILLARIES Drg
$ Amendments
$
$ CAD REF
$ STRUCTURAL DRAWINGS :-
$
PARAMETERS
ANGN 45.0
CODE BS8100 $ Wind profile to this code
ICE RO 0.0 RW 0.0 $
ALTOP 0 $ Site + tower height
PSF-V 1.20 $
PSF-M 1.20 $
VB 30.0 MEAN $ Site wind speed - mean hourly for BS 8100
OVERLAP 1
END
TERRAIN
ANGLE 0 TCAT 2 $ HH 0.0 BETAH 0.0 XLEE 0.0
END
LOADS
CASE 100 Weight of tower plus ancillaries
DL
$ TODO - any additional NDLDs go here
END
ANCILLARIES
FACE
END
END
CTIDATA
CTIDATA generates a tower data (TD) file from a prototype TWR file
and Cti.csv database file.
To run CTIDATA from the main menu select the
Tower > Load Tower > Process Ancillary DB File command.
This command will not be available unless a tower geometry has been
built and the CSV file exists in the data folder.
The prototype TWR file, Ctistd.twr must be present in the data folder
and the geometry of the structure must have been created.
A tower loading file is output.
When CTIDATA is run a number of dialog boxes are presented for you
to choose codes and enter parameters that will be substituted into a copy
of the prototype TWR file.
A set of wind angle and load combinations is entered for generation of a
new LOADS block. All wind load directions are referred to the tower X
axis, simplifying the generation of face and corner winds. Any or all face
or corner wind directions may be chosen. In addition, for triangular
towers, winds parallel to faces may also be chosen.
Any large ancillary data in the prototype file is replaced with data
derived from the CSV file.
If the tower loading file exists before CTIDATA is run, only the large
ancillary data will be replaced. The PARAMETERS and LOADS blocks
will be unchanged and previously existing ancillary loads will be
commented out and remain in the file for possible future reference.
Arrangements may be made to customize this program to user
requirements.
I M
ICE keyword 148, 161, 164 M face panels 92
Ice loads 164 Main toolbar 29
Icon 185 Main window 19
Import MASS keyword 172, 176
Archive file 122 MATERIAL block 56
DXF 190 MCAP keyword 47
UDP 126 MEMB keyword 117
Input load case 19 Member axes 38
Input/Analysis report 238 Member checking 39
Instability 201 Member Checking menu 23
Insulators 169, 175 Member orientation 49
INSULATORS keyword 175 Member properties 133
Interruptible commands 130 Member/face table 176
Members
Non-Linear 198
J Menu bar 19
Job size 13 Menus 19
Joints 58 MI keyword 165
Miscellaneous loads 165
Modifying a UDP 121
K Monopole 102
K face panels 82 MsEdit 234
KXM face panel 101 MTMP keyword 166
KXM2 face panel 101 Multiple selection 134
L N
Lambda 202 NDLD keyword 165
Large ancillaries 169, 173 NODE keyword 117, 175
LARGE keyword 173 Node properties 133
LIB keyword 52, 170, 173 NODENAME block 158
LIBR keyword 53 NOICE keyword 161
Library Non-linear analysis 195
Ancillary 184 NOPATCH keyword 162
Section 227 NOWIND keyword 165
Library Viewer 235
Limit 136 O
Linear analysis 195
Linear ancillaries 169, 170 OK/Cancel toolbar 33
LINEAR keyword 170 Orientation 55
Loads Output 176
Additional member temperatures Output window 19, 35
165
Additional node 165 P
Dead 164
Guyed mast patch 163 Page Setup 15
Ice 164 PANEL block 168
Miscellaneous 165 PANEL keyword 45
U
UDP example 138
UDP file 37
UDP file names 123
UDP from Microstran 122
UDP keyword 116
Unequal leg length 121
UNICE keyword 162, 165
Units 38
V
VB keyword 148
VELOCITY block 157
Velocity table 176
View menu 21
View toolbar 30
W
W face panels 94
WIND keyword 164
Wind load cases 161
Wind resistance 177
Window 136
Window menu 28
X
X face panels 77
XDM face panel 97
XDMA face panel 97
XM face panel 96
XMA face panel 96
Xsteel 190, 226
Y
Yield stress 229
Z
ZF keyword 157
ZGUST keyword 162, 177
ZGUST2 keyword 162
ZREF keyword 159