Tedds Developer Tutorials
Tedds Developer Tutorials
Training Manual
Disclaimer iii (130)
Disclaimer
© 2017 Trimble Solutions Corporation and its licensors. All rights reserved.
This Software Manual has been developed for use with the referenced Software. Use of the Software, and use of this
Software Manual are governed by a License Agreement. Among other provisions, the License Agreement sets certain
warranties for the Software and this Manual, disclaims other warranties, limits recoverable damages, defines permitted
uses of the Software, and determines whether you are an authorized user of the Software. All information set forth in this
manual is provided with the warranty set forth in the License Agreement. Please refer to the License Agreement for
important obligations and applicable limitations and restrictions on your rights. Trimble does not guarantee that the text is
free of technical inaccuracies or typographical errors. Trimble reserves the right to make changes and additions to this
manual due to changes in the software or otherwise.
In addition, this Software Manual is protected by copyright law and by international treaties. Unauthorized reproduction,
display, modification, or distribution of this Manual, or any portion of it, may result in severe civil and criminal penalties,
and will be prosecuted to the full extent permitted by law.
Tekla, Tekla Structures, Tekla Structural Designer, Tekla BIMsight, BIMsight, Tekla Civil, Tedds, Solve, Fastrak and Orion are
either registered trademarks or trademarks of Trimble Solutions Corporation in the European Union, the United States,
and/or other countries. More about Trimble Solutions trademarks: External link: http://www. tekla. com/tekla-
trademarks. Trimble is a registered trademark or trademark of Trimble Inc. in the European Union, in the United States
and/or other countries. More about Trimble trademarks: External link: http://www. trimble. com/trademarks. aspx.
Other product and company names mentioned in this Manual are or may be trademarks of their respective owners. By
referring to a third-party product or brand, Trimble does not intend to suggest an affiliation with or endorsement by such
third party and disclaims any such affiliation or endorsement, except where otherwise expressly stated.
D-Cubed 2D DCM © 2010 Siemens Industry Software Limited. All rights reserved.
EPM toolkit © 1995-2006 Jotne EPM Technology a. s. , Oslo, Norway. All rights reserved. Open Cascade Express Mesh ©
2015 OPEN CASCADE S. A. S. All rights reserved.
PolyBoolean C++ Library © 2001-2012 Complex A5 Co. Ltd. All rights reserved. FLY SDK - CAD SDK © 2012
VisualIntegrity™. All rights reserved.
Teigha © 2002-2016 Open Design Alliance. All rights reserved. CADhatch. com © 2017. All rights reserved.
This product contains proprietary and confidential technology, information and creative works owned by Flexera Software
LLC and its licensors, if any. Any use, copying, publication, distribution, display, modification, or transmission of such
technology in whole or in part in any form or by any means without the prior express written permission of Flexera
Software LLC is strictly prohibited. Except where expressly provided by Flexera Software LLC in writing, possession of this
technology shall not be construed to confer any license or rights under any Flexera Software LLC intellectual property
rights, whether by estoppel, implication, or otherwise.
The elements of the software described in this Manual are protected by several patents and possibly pending patent
applications in the United States and/or other countries. For more information go to page External link: http://www. tekla.
com/tekla-patents.
Table of Contents
Typographical conventions .................................................................................................................... 11
Note boxes ............................................................................................................................................. 11
Header Usage
Bold Any text that you see in the user interface appears in bold. This
font is used, for example, for window and dialog box titles, box
and button names, and list items.
Italic bold New terms are in italic bold when they appear in the current
context for the first time.
Monospace Extracts of program code, HTML, or other material that you
would normally edit in a text editor, appear in monospaced
font. This font is also used for file names and folder paths, and
for any text that you should type yourself.
Note boxes
You should always read very important notes and warnings, like
this one. They will help you avoid making serious mistakes, or
wasting your time.
Tedds
Developer
Training
The best way to become familiar with these applications is to run through the various Lessons in this document.
The steps shown in the lessons are the same as those used by the Tedds Development Team to create the Tedds
Engineering Library. We recommend that you familiarise yourself with some of the library calculations to see
examples of what can be achieved.
The Developer Tools allow you to build on your existing Tedds for Word calculation writing skills to create more
professional calculations. A good understanding of how to write Tedds calculations is essential before you start
using the Developer tools.
First Steps:
1. Plan and specify the scope and requirements for your calculation. Planning the calculation before you
start developing is extremely important. Try to break down the overall design solution into smaller,
simpler components that are easier to design and implement. If you plan your solution well you will save
time throughout the development of your calculation.
2. Write the calculation components that perform the required calculations that you specified in your design
plan, save these components as Calc Items to a Calculation Library.
Using the Tedds Calc Designer:
3. Create a Flowchart to link the Calc Items using the required logic to determine which components are
calculated.
4. Create a User Interface to prompt the end user for the required calculation data.
2 Glossary of Terms:
AutoCalc A complete calculation solution.
Calc Library A file containing Calc Items (has . lbr file extension).
Calc Item Field Tedds ‘Field’ that runs an AutoCalc when calculated.
Calc Module A Flowchart that has been saved in a Calc Library as a Calc Item
.cdd file The file used for saving Calc Designer Flowcharts
.tid file The file used for saving Interface Designer information
Tedds
Calc
Designer
An outline of the procedure that you will use in the Calc Designer is as follows:
Standard Toolbar
Flowchart
Window
Zoom Toolbar
Properties
Window
Library Access
Standard Launch the Library Access System
System
Calc Objects represent the various elements of the Calc Module and can be divided into five types:
Terminators
Decisions
Processes
Perform an operation
Connectors
Allow the Flowchart to be laid out in a more logical and presentable way.
External Process
To place a Calc Object, click on the required Calc Object in the Calc Objects Window and then click on the
Flowchart window. To reposition any Calc Object click the Select button on the Diagram Toolbar and then click
and drag the Calc Object. Use Edit > Select All or click and drag the mouse to select multiple Calc Objects within a
rectangle, click on an empty space on the Flowchart window to clear the current selection.
Double-click on each Calc Object and enter the required properties. The properties can also be entered using the
Properties Window.
PROPERTY FUNCTION
There is an alternative way to place Evaluate Lib Item Calc Objects, which also defines the Object Properties in
the same operation. Launch the Library Access System using the icon on the Standard toolbar and check that you
have drag and drop enabled, via Tools > Options > General. Open the Set that contains the required Calc Item,
then simply drag and drop it onto the Flowchart window.
Click on the Link command on the Diagram toolbar, click on the ‘node’ at the beginning of the Link and then the
‘node’ at the end of the link. To draw a Link with multiple nodes simply click on grid points between the start and
end nodes. To add a node press the Ctrl key and click on the Link, click and drag to move a node. To delete a
node, press the Ctrl key and click on the node to delete.
3.8.1 Properties
The Calc Module must be stored in a Calc Library as a Calc Item and it is the Calc Item that can be Executed from
the Library Access System to actually run and evaluate the full calculation. Select File > Properties and specify the
Library File and Item Name for saving the Calc Module. You can use the dialog buttons to select an existing Calc
Library or type the new details into the dialog.
3.8.2 Building
Click on the Build Module command on the Standard toolbar to convert the Flowchart into a Calc Module. The
Calc Module will be saved in the specified library as the Calc Item specified in the calc module properties above.
You can also save the Flowchart itself so that you can modify and enhance your design at a later time. Click the
Save command and enter a new file name (<filename>.cdd).
In Tedds for Word, select Tedds > Insert > Tedds Field and select the Calc Item tab. Using the dialog buttons select
the relevant Calc Library and Calc Item then confirm your selection by clicking OK. Now calculate the document.
Tedds
Interface
Designer
An outline of the procedure that you will use in the Interface Designer is as follows:
• Choose a page layout.
• Define information that will appear on each page
• Build the completed Interface to a Calc Library
Main Toolbar
Preview window
Tree view
4.3 Basics
There are four main components that can be created within the Interface Designer:
4.3.1 Controls
Controls are the basic parts of an interface which allow the user to enter information:
CONTROL FUNCTION
LAYOUT CONTROLS
4.3.2 Groups
Groups allow Controls to be ‘grouped’ together. This provides two main benefits 1) the Controls are displayed
together in a visible area in the interface, with a title and 2) logic as to whether the Controls are enabled or not
can be set at the Group level.
4.3.3 Pages
Pages represent actual pages of the interface. A Page can contain multiple Groups and controls. Logic can be used
to define whether a Page is enabled or not.
Page Groups are the highest level component that can be created in the Interface Designer. A Page Group may
contain one or more Pages and is used to set the layout and other properties of these Pages. For example, if an
interface should have a sketch on the first and second page, and none on the third and fourth, then two different
Page Groups would be used to set these different properties. Logic can be used to define whether a page group is
enabled. Notes and sketches items are also controlled at the Page Group level.
4.4 General
The following capabilities are available across the different types of components.
• Condition as to whether the component is included in the interface.
• Condition as to whether the component is enabled in the interface.
• Validation for the data entry with messages displayed if the validation is not met.
• For Pages and Controls only – Additional information to be displayed at the top of the interface.
Click on the Build command on the toolbar to build the Interface. The Interface will be saved in the specified
library using the interface name specified in the interface properties.
You can also save the Interface file itself so that you can modify and enhance your interface ata later time. Click
the Save command and enter a new file name (<filename>.tid).
Lessons
5 Lessons - Components
These lessons use some simple pre-written calculations that can be used to calculate the moment, shear and
deflection of a simply supported beam with either full or partial udl loading.
wu k N /m
A B
L s
w u k N /m
A B
L a L b L c
L s
L x 1
The calculation has been divided up into its basic ‘components’ and stored as Calc Items in a Calc Library. In the
lesson examples we will show you how to use the Tedds Calc Designer to link these components together and the
Tedds Interface Designer to create the prompts for information.
All calc items can be previewed using the Tedds library access syetm
via File/Open > Tedds Developer. las and then using the preview
button
5.1 Installation
Before you start you need to make sure that you have all the necessary training files available.
5.1.1 Files
If you have not already installed the developer training files open Tedds for Word, on the Ribbon select the Tedds
Tab, in the Tools group select Help and then select Install Developer Tutorial Files. Unless you have changed the
Tedds default locations for your user sets and libraries the training files will be installed to the following
directories
<My Documents\Tedds\Calc Libraries>
Tedds Developer. lbr
Tedds Developer Completed. lbr
<My Documents\Tedds\Calc Sets\>
TeddsDeveloper. las
Tedds Developer Completed. las
The ‘Completed’ Calc Set, Calc Library, Calc Designer and Interface Designer files are included so that you can
compare your implementation with the completed versions. Each of the Lessons builds on the work carried out in
the previous exercise and if you want to use the completed files instead of continuing with your own then you can
select the appropriate file from:
<My Documents\Tedds\AutoCalcs\Developer Training\Completed>
Calc Designer:
Lesson 1.cdd
Lesson 2.cdd
Lesson 4.cdd
Lesson 5.cdd
Lesson 6.cdd
Lesson 7.cdd
Lesson 8 Calc Module.cdd
Lesson 8. AutoCalc Module.cdd
Interface Designer:
Lesson 3.tid
Lesson 5.tid
Lesson 6.tid
Lesson 7.tid
Lesson 8.tid
Lesson 1
These Calc Items have already been written and saved in the Tedds Developer Calc Library.
Step 6. Place a Start Module and an Evaluate Lib Item Calc Object onto the Flowchart - by clicking on the
desired Calc Object in the Calc Object Window and then clicking on the relevant place on the
Flowchart Window. An Evaluate Lib Item Calc Object specifies which of the stored Calc Items will be
run at this stage of the calculation.
Step 7. Double-click on the Evaluate Lib Item Calc Object and use the dialog buttons to select the Full UDL
Beam Details Calc Item from the Tedds Developer. lbr Calc Library.
Step 8. Place two more Evaluate Lib Item Calc Objects and an End Module directly below the first Evaluate
Lib Item.
Step 9. Use the same procedure for each of these new Evaluate Lib Item Calc Objects and set:
Second
Step 10. Draw Links between the Calc Objects - by selecting the Link command and then clicking the
white circle at the bottom of one Calc Object and then the black circle at the top of the next Calc
Object.
Data Preview – The Data Preview window will display the contents of
the Calc Item associated with the selected Evaluate Lib Item. If the
Data Preview Window is not visible you can select it from the View
menu or by clicking the command on the Standard toolbar.
Step 11. Click the Build Module command to build the Calc Module and to save it in the Calc Library,
using the Calc Item name Lesson 1
Step 12. Select File > Save to save the completed Flowchart file as "Lesson 1.cdd".
In the next lesson you will continue using the Calc Designer and this time create a more powerful flowchart that
uses logic to decide which Calc Items to evaluate.
Lesson 2
These Calc Items have already been written and saved in the Tedds Developer Calc Library.
Below is a preview of the flowchart that you will create in this lesson.
In order to calculate the appropriate Calc Items the Calc Module needs to know which type of load is to be
applied to the beam and whether a sketch is required . To achieve this you will use a Variable "_UDLType" to
control whether the loading is full or partial and a Variable "_ShowSketch" to set whether or not to include a
sketch of the beam in the output.
Step 1. Open the Tedds Calc Designer, or select File > New if it is already open.
Step 2. Select File > Properties and use the dialog button to select the Tedds Developer. lbr for the Calc
Library and then enter Lesson 2 for the Calc Item.
Step 3. Save the Flowchart as Lesson 2.cdd, in <My Documents\Tedds\AutoCalcs\ Developer Training\>.
Step 4. Place a Start Module and a decision Expression Calc Object on the flowchart.
Step 5. Double-click on the Expression Calc Object and define the following Expression:
_UDLType == "Partial"
If the Variable _UDLType equals "Partial" your Flowchart will branch out to the right, if _UDLType does NOT equal
"Partial" (i. e. "Full") then the Flowchart will continue below.
Expressions – The Calc Designer and the Interface Designer use the
same rules for writing expressions as Tedds for Word so all the
techniques you have learnt to write calculations in Tedds for Word
can be reused.
Variable names are case sensitive and must match the names used
in the Interface Designer and/or the calculation components.
Mismatched Variable names are the most likely cause of errors in
both the Calc Designer and Interface Designer.
The quotes round the value are also important parts of the
expression as they are required when defining text Values.
Now, you will complete the design of the "Full UDL" calculation, the first step is to include the option to show the
sketch:
Step 6. Place another Decision Expression Calc Object directly below the existing Calc Objects, right-click
over it and select Properties. Define the following expression, remembering to use case sensitive
Variable names and double ==:
_ShowSketch == "yes"
If _ShowSketch equals "yes" your Flowchart will branch out to the right but if _ShowSketch does NOT equal "yes"
(i. e. "no") then the Flowchart will continue below.
You will use an alternative method to place the three Evaluate Lib Item Calc Objects required for the Full Loading
calculation.
Step 7. Open the Library Access System using the icon on the Standard toolbar and check via Tools >
Options > General that you have drag and drop enabled.
Step 8. Open the Tedds Developer. las Set, select the "Full UDL Beam Details" Calc Item and drag and drop
it directly below the existing Calc Objects.
Step 9. Repeat this procedure for "Loading Details" and "Full UDL Design Forces".
Step 10. Place an End Module below the last Calc Object.
Step 11. Place another Evaluate Lib item Calc Object by dragging the "Full UDL Sketch" Calc Item from the
Tedds Developer Library and dropping alongside the _ShowSketch == "yes" Expression Calc Object.
Step 12. Draw Links to connect the Calc Objects as shown below:
Links - A Link must start and finish at a Calc Object – not simply at
another Link. To make your Flowcharts easier to follow you can draw
Links that overlap.
You now want to include the design elements of the "Partial UDL" calculation. You can either repeat these steps
and place a new set of Calc Objects to suit partial loading or alternatively you can copy and edit the existing Calc
Objects. As the two routes through the calculation are similar copying and editing is probably the quickest
solution.
Step 13. Click the Select command and then drag a window that encompasses all but the Start Module and
first Expression Calc Objects. You should find that all the other Calc Objects and the Links will now
be ‘selected’.
Step 14. Select Edit > Copy from the main menu, click into the space to the right of the selected Objects and
then select Edit > Paste. A duplicate set of Calc Objects should now exist and whilst they are all still
selected you can click & drag them into a more suitable position.
Step 15. Double-click or right click on each of the new Calc Objects to change them to:
Second no change
Step 16. Draw a Link from the first Expression Calc Object (_UDLType=="Partial") to the new
_ShowSketch=="yes" Expression.
Step 17. Click the Build Module command to build the Calc Module and to save it to the Calc Library, using
the Calc Item name Lesson 2
Step 18. Save the completed Flowchart file as Lesson 2.cdd.
Word Options– When you type variables names that start with an ‘_’
character you may find that the underscore characters suddenly
disappear and your text is formatted in italic. This is a feature of Word
that is not desirable when writing Tedds calculations, if you type an
underscore character then some text and then another underscore
character Word automatically formats the text you have typed in
italics.
We would recommend that you disable this Word feature. Select File
> Options > Proofing > AutoCorrect Options. Select the tab
AutoFormat. Make sure that the option *Bold* and _italic_ with real
formatting is not checked and confirm you settings by clicking OK.
Step 21. Insert a call to the Calc Module using a Tedds Calc Item Field in the same way as you did for Lesson
1 except this time select the Calc Item Lesson 2.
Step 22. Calculate the document and you should have the Partial loading calculation with a sketch.
Step 23. Change the ‘control’ Variables to "Full" and "no" and re-calculate. You should now have the Full
loading calculation without a sketch.
In the next lesson you will create an Interface for this Calc Module that will prompt you for the analysis data as
well as allowing you to select the loading type and whether or not to include the sketch.
Lesson 3
in the following lessons you will be using the various options and
properties available in the Interface Designer. In each subsequent
step we have only described the data that you need to change or
have not seen before. If a property is not described then it should
be left as the default value or blank.
You need to enter the following information in order to complete your simple beam analysis:
Analysis Options – the loading type and whether or not to include a sketch
Partial UDL Loading – the beam span, partial udl position and values
To achieve this you will design three interface pages, the selection made on the analysis options page will
determine which of the two loading pages will be displayed:
Controls – define an item in the interface which does one or more of accepting input from the user,
executing expressions or showing output to the user.
Interface Name Simple Beam Analysis text for the Interface title bar.
Step 3. Select File > Save and save the Interface Designer file as Lesson 3.tid, in <My
Documents\Tedds\AutoCalcs\Developer Training\>.
Page Groups are used to define the overall layout and properties of the interface. First you will choose the page
‘style’ and specify the notes and sketches to display with the interface:
$(UserLbrDir)Tedds
File Name
Developer. lbr
$(UserLbrDir)Tedds
File Name
Developer. lbr
Show Control
True
Descriptions
Comment Leave blank Design time notes for you the developer
Now you will define the details of the first Page within this Page Group. Pages represent actual pages of the
interface.
Scope: Calculation of
maximum moment, shear
force and reactions for a Additional information which is helpful to
Information
simple beam under full or the end user
partial uniformly distributed
loads.
Comment Leave blank Design time notes for you the developer
You can now add a Group to the first Page that will contain your analysis options – load type and sketch. Groups
allow Controls to be ‘grouped’ together.
Title Beam Analysis Options Text shown at run time on the interface
Comment Leave blank Design time notes for you the developer
8.6 Controls
Controls are the basic parts of an interface that allow the user to enter information. The first Control will decide
which type of loading is to be applied to your beam:
Text in Drop Down Lists – By adding the choice as Full="Full" the drop
down list on the interface will show the text without quotes but
Tedds will store the value as a string.
The second control will decide whether or not a sketch is included with the calculation:
Although the Interface is not yet complete you can make sure that everything that you have specified so far is
working correctly and you can do this without actually linking it to the Calc Designer or any calculations!
Step 10. Click the Export command to send the Interface Designer information to the Tedds
document. You can view the information by clicking Show Field Codes
Step 11. Calculate the document and you should see the following interface:
Step 12. Click the Notes and Sketch commands in the interface toolbar to check that the correct notes and
sketches are displayed.
Step 13. Select a Load Type, select whether to include a Sketch and then click Next. The interface will close
but no calculations will be displayed as you have yet to add the Interface Calc Item to the Calc
Module.
Step 14. In Tedds for Word, click the Variables command to see if the ‘control’ Variables have been defined
correctly:
Although there are no further pages and the calculation has not run, your first Interface is working well. You will
now create the interface Pages for the two loading conditions
Step 15. Return to the Interface Designer.
Now you will choose the page ‘style’ to suit both loading types:
Step 16. Click on the first page Group "Simple Beam 1" and then double-click the Page Group command to
add a second Page Group and specify the following:
$(UserLbrDir)Tedds
File Name
Developer. lbr
$(UserLbrDir)Tedds
File Name
Developer. lbr
Now you will define the details of the first Page within this Page Group and use the horizontal sketch window to
display a picture of the beam. The choice of Calc Item for the sketch is not fixed but depends upon the Variable
_UDLType so you will use an "expression" to select the correct sketch:
Step 17. Double-click the Page command to add a new Page and specify the following:
Buttons Back Finish Cancel Last page of the interface so show Finish button
$(UserLibDir)Tedds
Library
Developer. lbr
8.11 Groups
You will create different Groups for the full and partially loaded beam span details and then use the Include If
setting to control which Group (and associated Controls) is displayed. Note: the Controls required for the dead
and live loads are the same for both load types.
Step 18. Double-click the Group command to add new Group and specify the following:
Name Fully Loaded Span Text shown at design time in the tree
Step 19. Double-click the Group command to add another Group and specify the following:
Name Partially Loaded Span Text shown at design time in the tree
Step 20. Double-click the Group command to add a third Group and specify the following:
8.12 Controls
As the overall beam span Control will be the same regardless of whether the beam is fully or partially loaded you
can copy the previous Control into the Partially Loaded Span Group. Note: You can copy and paste Controls,
Groups, Pages and Page Groups.
Step 23. Right-click over the L_{s} Edit Control within the Fully Loaded Span Group and select Copy.
Step 24. Right-click on the Partially Loaded Span Group and select Paste.
Now you can add more Controls to the Partially Loaded Span Group that define the length and position of the
loading. You can either copy and amend the first Control or add new Controls.
Step 25. Click the Edit Control command to add a new Control and specify the following:
Description Length to start of UDL Text shown at run time on the interface
Step 26. Copy and Paste the L_{a} Control and amend it to the following:
Step 29. Copy and Paste the w_{D} Control and amend it to the following
Make sure that everything that you have specified so far is working correctly before you actually link it to the Calc
Designer or any calculations:
Step 30. Export the Interface Designer information to a Tedds for Word document.
Step 31. Calculate the document and select a Load Type, select whether to include a sketch and then click
Next.
Step 32. Depending on your choices you should see an Interface similar to this:
Step 33. Enter some values and check all the routes through the calculation, view the Variables that are
defined in each case. Note when you choose a partially loaded beam the associated Controls do no
all fit on one interface so Tedds automatically displays an additional page.
Step 34. Click the Build Interface command to create the Interface and save it in the library.
Step 35. Save the Interface Designer file as Lesson 3.tid file.
In the next lesson you will combine the Interface and Calc Module from Lessons 2 and 3 to create an AutoCalc.
Lesson 4
Each of the lessons builds on the work carried out in the previous exercise. In order to allow you to go back over
previous lessons you will rename the Calc Designer and Interface Designer files rather than overwriting them. You
will also use different Calc Item names for the Calc Modules and Interfaces for the same reason. If you wish to use
our CDD and/or TID files instead of continuing with your own then you can select the appropriate file from <My
Documents\Tedds\AutoCalcs\Developer Training\Completed\".
Step 1. Launch the Tedds Calc Designer and Open your Lesson 2.cdd file.
Step 2. Select File > Properties and change the Calc Item to Lesson 4
Step 3. Select File > Save As and save the file as Lesson 4.cdd.
Step 4. Delete the Link between the Start Module and the first Expression Calc Object, and then move the
Start Module Object up or the rest of the Objects down so that there is room for another Calc
Object.
Interface Calc Items - Because user Interfaces are saved as Calc Items
you add them to a Flowchart in exactly the same way as you do for
any other Calc Item.
Step 5. Place an Evaluate Lib Item Calc Object in the gap and use the dialog buttons to set the Properties as
Property Value
Step 6. Draw the Links to link the new Evaluate Lib Item Calc Object to the Calc Designer Flowchart.
Step 7. Click the Build Module command to build the Calc Module and to save it in the library.
Step 8. Save the completed Flowchart file, Lesson 4.cdd.
You now have a Calc Item called Lesson 4, that will run the Logic Example Interface, calculate the appropriate
components as laid in the Flowchart and then display the completed calculation. To check your combined
calculation:
Step 9. In Tedds for Word, add a call to the Calc Item Lesson 4 using a Tedds Calc Item Field in the same
way as you did for Lesson 1.
Step 10. Check all the various routes through the beam analysis.
The final step is to save the Call Item Field in the Calc Library as an AutoCalc.
Step 11. Close any open Tedds for Word documents.
Step 12. Insert a call to the Calc Item Lesson 4 using a Tedds Calc Item Field, but do not calculate it.
Step 13. Highlight the Calc Item Field that you have just inserted into the document
In the next lesson you will learn more Calc Designer features such as Sub Modules and more Interface Designer
features such as SetVar and Button Controls. You will use these to add a deflection check to your beam analysis.
Lesson 5
In the second part of this lesson you will add the deflection check Controls to an Interface called Lesson 5
Interface, but first you will set up the Calc Designer Flowchart to run this new interface.
Step 1. Launch the Tedds Calc Designer and open your Lesson 4.cdd file
Step 2. Select File > Properties and change the Calc Item to Lesson 5.
Step 3. Select File > Save As and save the file as Lesson 5.cdd.
Step 4. Double click on the "Lesson 3 Interface" Evaluate Lib Item Calc Object and change the Item Name to
"Lesson 5 Interface"
You will now add the deflection checks to new pages in the Flowchart and use a new control Variable
"_CalcDeflection" to determine whether or not a deflection calculation is required. To keep the Flowchart
connected but also use the new pages you will use Sub Module, Start Sub Module and End Sub Module Objects.
Although there is still plenty of space on the current Flowchart managing complex calculations is much easier if
you keep the separate parts of the calculation on distinct pages. At the bottom of the Calc Designer are scroll bar
commands that allow you to add, delete and move between pages:
Step 5. Right click over the text for Page 1, select Rename and call the page Main.
Step 6. Click the + symbol to the right of the scroll bar to add a new page.
Step 7. Rename this page to Deflection Full UDL.
Step 8. Repeat these steps to create a page called Deflection Partial UDL.
Sub Modules allow you to divide flowcharts in to smaller more manageable parts. You add a Sub Module Process
Calc Object to the main Flowchart to specify the name of the Sub Module that is to be used and begin the Sub
Module Flowchart with a Start Sub Module Terminator Calc Object with the same name. All branches of a Sub
Module Flowchart must finish at the same End Sub Module Calc Object.
Start & End Sub Module Calc Objects – All Sub Modules must begin
with a Start Sub Module and all branches of a Sub Module must finish
at the same End Sub Module.
The Sub Module Name is case sensitive and cannot include spaces.
It is good practice to create a new page for each Sub Module and to
give the page and Sub Module the same name.
Step 9. Use the page navigate buttons to return to the Main page
Step 10. Delete the Link between the "Full UDL Design Forces" and the End Module Calc Objects, and then
move the End Module Calc Object down so that there is room for another Calc Object.
Step 11. Place a Decision Expression Calc Object in the gap and set the Expression property to:
_CalcDeflection == "yes"
Step 12. Place a Sub Module Calc Object alongside this Expression and set the Sub Module Name property
to:
DeflectionFullUDL
Step 13. Draw Links to connect the new Expression and End Module Calc Object to the rest of the Flowchart:
Step 14. Change to the Deflection Full UDL page and place a Start Sub Module Calc Object at the top of the
Flowchart.
Step 15. Set the Start Sub Module Calc Object Name to:
DeflectionFullUDL
Step 16. Below this Start Sub Module Calc Object, place an Evaluate Lib Item Calc Object for Full UDL
Deflection by either dragging and dropping from the Tedds Developer Set or by browsing to the
correct Calc Library and Calc Item.
Step 17. Below this, place an End Sub Module Calc Object and draw Links to connect all three Objects.
Step 18. Repeat the above steps for the Partial UDL Loading part of the Flowchart. Set the Sub Module and
Start Sub Module Properties to something suitable, e. g. DeflectionPartialUDL.
Step 19. Check the new Calc Objects and make sure that you have been consistent with the Expressions and
Properties.
Step 20. Click the Build Module command to build the Calc Module and to save it in the library.
Step 21. Save the completed Flowchart file, Lesson 5.cdd.
You cannot test this Calc Module until you have completed the Lesson 5 Interface. So now you will open the
Interface Designer and do just that.
To include the deflection calculation you will amend the Interface created in Lesson 3 to:
You will add new control Variables (_DesignCode and _SteelDataList) so that once the design code has been
chosen the interface can set the appropriate Data List and value of Young’s Modulus (E), using SetVar Controls.
Here’s what your ‘advanced’ interface will look like when you're finished:
Step 22. Launch the Interface Designer and open your existing Lesson 3.tid file.
Step 23. Select the Properties command and change the Calc Item to Lesson 5 Interface.
Step 24. Save the file as Lesson 5.tid.
10.10 Controls
You will add a Checkbox Control so that the engineer can specify whether or not a deflection calculation is
required.
Step 25. Expand the Wizard to show the contents of the Analysis Options\Options Group.
Step 26. Copy and Paste the _ShowSketch Control to create a duplicate within the Options Group.
Step 27. Amend the copy to the following:
10.11 Groups
You will now create a new Group that will contain all the Controls related to the deflection calculation. You will
use the Enable If property to make this Group, and all its Controls, either ‘enabled’ or to leave them visible but
‘disabled’ depending upon whether the deflection calculation is required or not.
Step 28. Return to the Analysis Options Page, add another Group and specify the following:
10.12 Controls
You will add a Drop List Control to choose a steel design code from: British BS5950, Canadian S16. 1 or American
LRFD.
Step 29. Select the Deflection Group, add a new Control and specify the following:
Description Select steel design code Text shown at run time on the interface
British (BS5950)="BS5950"
Canada (S16. 1)="S161" Values for the drop list, click on the dialog
Choices
USA (LRFD)="LRFD" button to access the Choices Editor
Australia (AS400)="AS4100"
Each of these design codes uses a slightly different value of Young’s Modulus and these values all exist as the
following Tedds System Variables: BS5950 = ES5950, S16. 1 = ES161, and LRFD = ESLRFD. You can use the Variable
_DesignCode in an expression to select the appropriate value of Young’s Modulus.
Step 30. Add a new Set Variable Control and specify the following:
Select(_DesignCode,
"BS5950", E_{S5950},
Value "S161", E_{S161}, "LRFD",
E_{SLRFD}, "AS4100",
E_{S4100}, "Not Specified")
Value - Make sure that you include all the commas and quotes and
that you type the case sensitive Variable names correctly e. g.
E_{S5950} not e_{5950}. If you are not familiar with the select
function see the notes below.
Example
Colour= "blue"
select(Colour,"red",0,"blue",1,"black",2,3) = 1
The number '3' at the end is a fall through result and is returned if no
match is made. Use this function only if values will match exactly, for
numeric comparisons, where the values will not always be exactly
equal, use nested 'if' statements or the ‘ifelseif’ function.
You can use _DesignCode in another expression to select the correct Data List. For each design code there is a
different Tedds Data List for the standard steel sections. In these lessons you are using metric (SI) units so the
Data Lists required are: BS5950 = euro. dls, S16. 1 = caciscsi. dls and LRFD = aiscsi. dls.
Step 31. Copy and Paste the E Set Variable Control and amend the copy to the following:
Select(_DesignCode,
"BS5950", "euro. dls",
"S161", "caciscsi. dls",
Value
"LRFD", " aiscusus. dls",
"AS4100", "auall. dls", "Not
selected")
A Button Control can be used for a variety of ‘commands’ such as displaying a Data List or Data Table. For this
interface you want to be able to click the button to display the Data List that matches the Variable _SteelDataList,
set by the SetVar Control above.
Step 32. Add a new Button Control and specify the following:
Description Select a steel section Text shown at run time on the interface
Select an I or H shaped
Information
section.
Step 33. For the Command property click the dialog button and select the Data List tab in the Command
Builder
Step 34. Choose the euro. dls Data List. The other options on this dialog can be used to specify which section
is initially selected and other properties of the Data List and returned Variables. You will not be
using these options for these lessons so just click OK.
This would be sufficient if only one Data List was required but you need a different Data List for each design code.
Step 35. Click the dialog button and select the Expression page.
Step 36. Replace "EURO. dls" with _SteelDataList. _SteelDataList is case sensitive and no quotes required.
Now, when the Select Section button on the interface is clicked, the Data List displayed will suit the current
design code. For example, if _DesignCode = "LRFD" then _SteelDataList = "aiscsusus. dls" and the button will run
DListSelectUI( "aiscusus. dls" ) and therefore display the standard US steel sections.
It would be very helpful if the name of the current section were displayed on the interface. This can be achieved
by using a Label Control that includes a string to report the section size. You can use the Enable If and Hide if
disabled features so that the section size is only displayed if the engineer chooses to run a deflection calculation.
Step 37. Select the Deflection Group, add Label Control and specify the following:
= StrFormat("Current
section: [1]",
Description Text shown at run time on the interface
GetVar("Name", "Not yet
selected"))
Step 38. Click the Build command to create the Lesson 5 Interface Calc Item
Step 39. Save Lesson 5.tid.
Because you have already built the Calc Module that includes the Lesson 5 Interface all you need to do now is test
this Calc Module and save the AutoCalc Calc Item. You might prefer to test the Lesson 5 Interface separately
before checking it in combination with the calculations or you might be confident enough to save the AutoCalc
and test everything in one go.
Step 41. Insert a call to the Calc Module using a Tedds Calc Item Field in the same way as you did for the
previous lessons except this time select the Calc Item Lesson 5.
Step 42. Check all the different routes through the calculations.
Step 43. Follow the same step as you did at the end of Lesson 4, to save the AutoCalc as a Calc Item.
In the Interface Designer part of this lesson you have learnt how to:
In the next lesson you will create an option to choose either summary or full results.
Lesson 6
Step 1. Launch the Tedds Calc Designer and open Lesson 5.cdd.
Step 2. Save the file as Lesson 6.cdd.
Step 3. Change the Flowchart Properties Item Name to Lesson 6.
Step 4. Change the interface Evaluate Lib Item Item Name to Lesson 6 Interface.
Step 5. In the same Edit Properties dialog, change the Output property to Discard.
Append and Discard – The Properties of each Evaluate Lib Item Calc
Object can be set so that the associated calc component is either
calculated and included in the final output document (Append) or
simply calculated and not included (Discard). The choice between
Append and Discard can also be controlled using an expression.
Step 6. Double click on the "Full UDL Beam Details" Evaluate Lib Item Calc Item, which currently has the
default Output Property of Append. Change this property to:
if(_Results=="Full", Append, Discard)
If the Variable _Results does equal "Full" then the component will be evaluated and included in the output
(Append). If _Results does NOT equal "Full" (i. e. "Summary") then the component will simply be evaluated and
NOT included (Discard).
You need to make the same change to the Output property of the other Calc Objects. You could either edit each
one separately or use the Replace feature:
Step 7. Select Edit > Replace and specify the following, then click the Replace button:
Replace – Will search all the properties of all the Calc Objects and
replace any occurrence of the ‘Find what:’ entry with the text in
‘Replace with:’. You can use Replace on all the Calc Objects in one go
by clicking Replace All, however unless you are sure that this is
appropriate we recommend that you make the changes individually
by using the Find Next and Replace buttons.
Step 8. Use a combination of the Find Next and Replace buttons to change the Output property of all the
Evaluate Lib Item Calc Objects except for Lesson 6 Interface and the two Sketches. Don’t forget the
Deflection pages.
Step 9. Check that the Output property has been changed for all eight Calc Objects using the Properties
Window.
You now need to add the component for the Summary output to the Flowchart and set its’ Output property to be
Append only if _Results does NOT equal "Full". You will use the techniques that you learnt in lesson 5 to add a
new page for the output and to link this page to the rest of the Flowchart as a Sub Module. The same Sub Module
can be used for both the Full UDL and Partial UDL routes through the design.
Step 10. Delete both the End Module Calc Objects on the Main page.
Step 11. Add a Sub Module and an End Module at the bottom-middle of the Flowchart.
Step 12. Set the Sub Module name Results.
Step 13. Draw the Links to connect the Sub Module and End Module Calc Objects to the Flowchart.
Step 14. Add a new page using the scroll bar and rename it Results.
Step 15. On the Results page place a Start Sub Module, an Evaluate Lib Item and an End Sub Module Calc
Object and connect them together.
Step 16. Set the Property of the Start Sub Module as Results.
Step 17. Set the Evaluate Lib Item Properties as
Property Value
Step 18. Click the Build Module command to build the Calc Module and to save it in the library.
Step 19. Save the completed Flowchart file, Lesson 6.cdd.
You cannot test this Calc Module until you have completed the Lesson 6 Interface. So now you will open the
Interface Designer and do just that.
The Calc Module is now complete but you need to use the Interface Designer to define the Variable _Results and
build the Lesson 6 Interface.
Step 20. Launch the Interface Designer and open Lesson 5.tid.
11.7 Group
There is plenty of room on the initial Analysis Options Page to add another Group for selecting the output detail
required so:
Step 23. Expand the Wizard to show the Analysis Options Page.
Step 24. Add a new Group and specify the following:
11.8 Control
Step 25. Add a new Drop List Control and specify the following:
Summary="Summary",Full=
Choices
"Full"
Step 26. Click the Build Interface command to create the Interface Calc Item.
Step 27. Save Lesson 6 Interface.tid.
Step 31. Check all the different routes through the calculations.
Step 32. Follow the same step as you did at the end of Lesson 4, to save the AutoCalc as a Calc Item.
In the next lesson you will refine your AutoCalc even further by adding input ‘validation’ to the user Interface to
prevent invalid values being accidentally entered, for example the beam span in metres when the AutoCalc is
expecting it in millimetres.
Lesson 7
12.2 Validation
You will enter a validation check so that a message is displayed if the engineer enters a beam span dimension that
is less than 100 mm.
Step 4. Expand the Wizard and in the Fully Loaded Span Group highlight the L_{s} Control.
Step 5. In the Expression field, within the Validation area, specify a minimum value that must be entered to
avoid the validation message being displayed. Make sure you include units:
Min value 100 mm
Step 6. In the Message field type the message that you wish to be displayed if this condition is NOT met:
Beam span, Ls, must be at least 100 mm.
Step 7. Add similar validation for the L_{s} Control, in the Partially Loaded Span Group.
If you leave the message field empty Tedds will create a default message
The values for w_{D} and w_{L} should all be positive i. e. minimum value of 0 kN/m.
Step 8. Enter appropriate conditions in the Min value Expression field and add messages to inform the
engineer to only use positive values. Don’t forget to specify units in the expressions.
Min value: 0 kN/m
Step 9. The Variable L_{a} should be positive and less than L_{s}, enter the following Validation Expression
and add an appropriate Validation Message.
Min value: 0 mm
Max value: L_{s}
The Variable L_{b} should be greater than 0 mm but also no greater than L_{s} – L_{a}, or the load will be located
off the end of the beam.
Step 10. Enter the following Validation Expression and add an appropriate Validation Message.
Min value: 0 mm
Max value: L_{s} – L_{a}
If the engineer chooses to perform a deflection calculation they must select a steel section from a Data List. In the
current calculation it is possible to proceed through the interfaces without choosing a section size but an error
will occur during the calculations, to prevent this:
Step 11. Highlight the Select Section Control, in the Deflection Group.
Step 12. Enter the following Validation Expression. A Variable called Name will only exist if a section has
been selected:
VarExists("Name")
Step 13. Add an appropriate Validation Message; such as "Select a steel section".
Step 14. Click the Build Interface command to create the Interface
Step 15. Save Lesson 7.tid.
Step 16. Launch the Tedds Calc Designer and open the Lesson 6.cdd.
Step 17. Select File > Save As and save the file as Lesson 7.cdd.
Step 18. Change the Flowchart Properties Item Name to Lesson 7
Step 19. Double click over the Output Example Interface Evaluate Lib Item Calc Object and change the Item
Name to Lesson 7 Interface.
Step 20. Click the Build Module command to build the Calc Module and to save it in the library.
Step 21. Save the completed Flowchart file, Lesson 7.cdd.
Step 25. Follow the same step as you did at the end of Lesson 4, to save the AutoCalc as a Calc Item.
In the next lesson you will add a Preview to the interfaces that will allow you to see key results before accepting
the data and returning the calculation output to the document.
Lesson 8
1. The full design is run with the interfaces displayed but without generating any output
3. When the Finish button is clicked, the full design will be repeated without the user interface and the
output will be created.
You will create a separate Calc Module that displays the interface, runs your existing Calc Module (whilst the
interface is still open allowing you to see the Preview) and then re-runs the calculation and returns the output to
the document. To begin with you need to amend the existing Calc Module.
Step 1. Launch the Tedds Calc Designer and open Lesson 7.cdd.
Step 2. Change the Flowchart Properties Item Name to Lesson 8 Calc Module.
Step 3. Save the file as Lesson 8 Calc Module.cdd.
Step 9. Place a new Sub Module alongside the Results Sub Module.
Step 10. Double-click on the new Sub Module and define the following name:
Preview_Results
13.4 Preview_Results
Add new Links to connect the Preview_Results Sub Module to the right of the _Output==0 Expression.
Step 14. Add Calc Objects for a Start Sub Module, two Evaluate Lib items, an Expression and an End Sub
Module and link them together as shown below:
Step 15. Change the name of the Start Sub Module to Preview_Results
Step 16. Double click on the first Evaluate Lib item Calc Object and amend its Properties to:
Property Value
Output _Output == 0
Step 17. Double click on the second Evaluate Lib Item Calc Object and amend its Properties to:
Property Value
Output _Output==0
Step 18. Double click on the Expression Calc Object and specify the following expression:
Step 19. Select Edit > Replace and specify the following:
Find what: if(_Results=="Full", Append, Discard)
Replace with: and(_Results=="Full", _Output)
Step 20. Click the Replace All button to change the Output properties of all the Evaluate Lib Item Calc
Objects.
Step 21. Click the Build Module command to build the Calc Module and to save it in the library.
Step 22. Save the completed Flowchart file, Lesson 8 Calc Module.cdd.
is equvalent to
if(_Results == "Full", Append, Discard)
If _Results does = "Full" the Output will have a value of 1 and hence
Append.
If _Results does not = "Full" the Output will have a value of 0 and
hence Discard.
Step 23. Launch the Interface Designer and open Lesson 7.tid.
Step 24. Save the file as Lesson 8.tid.
Step 25. Select Properties and change the Calc Item to Lesson 8 Interface.
Currently the button on the bottom of the Analysis Options page of the interface is set to be displayed as Finish
but you are going to add another page so will change this back to the default of Back Next Cancel.
Step 26. Select the Analysis Data Page within the Simple Beam 2 Page Group
Step 27. Change the Buttons property from Back Finich Cancel to Back Next Nancel.
Step 28. Add a new Page Group and specify the following:
The Calc Item for the key results can now be run from the interface.
Step 29. Add a new Page and specify the following:
$(UserLibDir)Tedds
Library
Developer. lbr
Step 30. Click the Build command to create the Lesson 8 Interface Calc Item
Step 31. Save Lesson 8.tid.
Now you will create the separate Calc Module that will display the interface with the Preview, run the Calc
Module that you have just edited and then return the results to the document.
Step 32. Select File > New to open a new blank Flowchart
Step 33. Set the properties as:
Property Value
Step 35. Place and Link a Start Module, a Set Variable Value, an Evaluate Lib Item, another Set Variable
Value, a Calc Module and finally an End Module, one directly after another.
$(UserLbrDir)Tedds
Library file
Developer.lbr"
Output Discard
$(UserLbrDir)Tedds
Library file
Developer. lbr"
Item name Lesson 8 Calc Module Run the lesson 8 Calc Module
Step 37. Click the Build Module command to build the Calc Module and to save it in the library.
Step 38. Save the completed Flowchart file, Lesson 8 AutoCalc Module.cdd.
You have completed this training course but as you can see there is plenty more to learn and almost unlimited
ways to enhance your calculations.