Beruflich Dokumente
Kultur Dokumente
User Guide
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from
viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data
created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in
contract, tort (including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's
claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it
(including source code, object code, any data contained in it, the manual and any other documentation supplied
with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document
is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without
the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires
that this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is
made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this
publication may be incorporated into any third-party software, product, machine, or system without the prior written
permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms
and conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.
Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall
not be liable for any breach or infringement of a third party's intellectual property rights where such breach results
from a user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or
logo belongs to its respective owner.
Revision Sheet
Date
Version
Comments / Remarks
Angular Dimensions enhancements included.
Accessing Data from Design or Catalogue Databases,
Accessing Dimensioning Data and Array Indexing, new
functionality incorporated.
January 2012
Contents
Page
DRAFT
Introducing DRAFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
What does DRAFT do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
DRAFT Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Who Should Read this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Organisation of the DRAFT User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
2:3
2:3
2:4
2:4
12 Series
2:5
2:5
2:5
2:5
2:6
2:6
2:6
2:6
3:6
3:6
3:7
3:7
3:7
3:7
ii
12 Series
3:24
3:25
3:26
3:28
3:28
4:6
4:7
4:7
4:8
4:8
iii
12 Series
At Representation Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
At Representation Style . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
At Hatching Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
At Hatching Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4:12
4:12
4:13
4:14
5:11
5:11
5:11
5:11
5:12
5:12
5:12
5:12
5:13
5:13
iv
6:7
6:7
6:7
6:8
6:8
12 Series
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1
7:4
7:4
7:5
7:6
7:6
7:15
7:18
7:19
7:22
7:24
7:26
7:28
7:29
7:29
7:29
7:32
Guidelines for Importing DGN Files from DRAFT into MicroStation. . . . . . . . 7:32
Exporting DRAFT Drawings Containing TrueType Fonts. . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting DRAFT Drawings Containing AVEVA Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing AVEVA Fonts into MicroStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mapping the Installed Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AVEVA Font File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Colours
.............................................................
Line Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7:32
7:32
7:33
7:36
7:36
7:38
7:38
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
12 Series
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1
10:8
10:8
10:9
10:9
vi
12 Series
Layers
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2
Autoblanking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:3
Dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1
Dimension Element Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1
Linear Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:2
Linear Dimensions and How to Create Them . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:2
Multi-valued Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:6
Principal Attributes of Linear Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:8
Detail Attributes of Linear Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:12
12:24
12:24
12:30
12:31
12:32
12:32
vii
12:43
12:43
12:43
12:44
12:44
12 Series
12:45
12:45
12:46
12:47
12:47
12:48
12:49
12:50
Labelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1
Creating and Manipulating Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2
Creating Labels and Label Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2
Labelling Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:5
Positioning and Orienting Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:5
Label Frame Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:6
Hiding Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:7
Label Text Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:7
Leader Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:10
Varying the Leader Line Connection Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:13
Leader Line Gaps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:14
Modifying Labels through Graphical Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:14
13:15
13:16
13:16
13:17
Autotagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:18
Defining the Autotagging Hierarchy and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controlling Label Appearance and Elements to be Tagged. . . . . . . . . . . . . . . . . . . . . . .
Querying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Label Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tracking the Autotagging Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Label Editing and Copying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tag Rule Editing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DATAL Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Schedule Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13:19
13:20
13:21
13:21
13:22
13:23
13:23
13:23
13:24
viii
12 Series
13:27
13:28
13:28
13:28
13:29
13:29
13:30
13:31
13:31
13:31
13:32
Substrings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:11
String Definition by Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:11
Substring Definition by Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:11
ix
12 Series
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:20
14:20
14:21
14:22
14:22
14:22
14:22
14:22
14:23
14:23
14:23
14:23
14:24
14:24
14:24
14:25
12 Series
16:3
16:3
16:4
16:4
16:4
16:4
2D Drafting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:1
Where 2D Drafting is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:1
Backing and Overlay Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:1
Symbol Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:3
xi
18:36
18:36
18:37
18:37
12 Series
18:37
18:37
18:38
18:38
18:38
18:39
18:39
xii
12 Series
20:17
20:17
20:18
20:18
20:18
20:18
xiii
12 Series
xiv
12 Series
Introducing DRAFT
1.1
Graphics to provide backing and overlay sheets which will be common to a number of
drawings.
Graphics providing annotation, including not only dimensioning and text but also such
items as leader lines and label boxes.
All the graphic items exist as, or are defined by, elements in the DRAFT database.
1.2
DRAFT Database
The DRAFT Database (DB) contains a complete definition of a DRAFT drawing. The
database does not contain information describing the geometry of the graphics that make up
a drawing, but gives a description of how those graphics should be presented on a drawing.
From this database definition (together with the DESIGN and Catalogue databases which
describe the appropriate 3D model) a drawing is generated which reflects the state of the
design at that particular time. The drawing can be displayed on the screen and processed to
produce a hard copy plotfile.
1.3
1:1
12 Series
1.4
Drawing the Design, describes how to create a DRAFT picture without annotations. It
describes the part of the DRAFT database that stores the main administrative and
graphical elements and how to create them. It also describes Views, which are the
areas used to display Design elements, and how to define their content.
Graphical Representation, describes how Design elements are defined and drawn
using Representation Rules. It describes how Representation Rules are defined and
describes the part of the DRAFT database that stores the Representation Rules. It also
describes Hatching Rules, used for the automatic hatching of faces of Design
elements.
Section Planes, describes how you can construct sections through Design items, using
Planes in DRAFT, which can be displayed at VIEW level.
Using the Cursor with DRAFT Commands, describes how, with many DRAFT
commands, you can use the cursor to identify an element in the graphics window by
using the ID command followed by an @.
Plotting and Drawing Output, describes how you can generate, at any time during the
drawing process, a plotfile consisting of a single Sheet, View, or the content of an Area
View.
Colours and Styles, defines the attributes that are associated with pens and describes
how to set these attributes.
Reports, Circulation Lists and Revisions, describes how to create the drawing office
administrative elements; reports and circulation lists. It also describes how DRAFT
handles revision numbers.
Change Highlighting, describes how you use Change Rules to control how Design and
Annotation elements that have been changed are drawn on a DRAFT View. It
describes how Change Rules are defined and describes the part of the DRAFT
database that stores the Change Rules. It also describes the concept of Comparison
Dates and how these are used to determine whether Design and Annotation elements
have been changed
Introduction to Annotation, describes the part of the DRAFT database that stores
annotation elements.
Labelling, describes labels, how they are created and the part of the DRAFT database
that stores them.
Intelligent Text, describes the use of code words to automatically extract data from the
Design, Catalogue or Drawing databases.
Miscellaneous Text Facilities, describes how the following text parameters can be
manipulated in DRAFT; font selection, using multiple fonts within a text string, inserting
symbols using the alternative character set, editing text attributes, text quality,
character height.
Underlays and Overlays, describes the use of underlays and overlays on a Sheet to
add standard elements such as borders, title blocks, keyplans, etc.
1:2
12 Series
Point and Line Construction, describes how a drafting position can be defined by
reference to other positions rather than explicitly.
Picture File Naming Conventions, describes the structure of picture file names.
1:3
12 Series
1:4
12 Series
2.1
Saving
2.1.1
Example:
RECREATE /DS1
saves the display status in file /DS1.
2:1
12 Series
2.1.2
Saving Work
The command:
SAVEWORK
saves the current DRAFT additions or modifications without leaving DRAFT. It is good
practice to use this command on a regular basis during a long session to ensure maximum
data security.
2.1.3
2.2
Database Commands
2.2.1
Cross-Database Referencing
The functionality described in this section exists in order to minimise problems of crossdatabase referencing when Design databases are deleted and rebuilt from macros.
All DRAFT elements with DDNM, IDLN, or IDNM reference attributes also have system text
attributes DDNX, IDLX, and IDNX respectively. These three attributes can be queried but
not set by the user.
DRAFT will always use the DDNM, IDLN and IDNM attributes; values in DDNX, IDLX and
IDNX will be ignored. Setting a DDNM, IDLN or IDNM attribute will also cause the
associated system text attribute (i.e. DDNX, IDLX and IDNX respectively) to be set to the
name of the Design element referenced, so long as it is named.
The following UPDATE commands exist to aid updating of a DRAFT database following
rebuilding of an associated Design database:
UPDATE element_identifier REFS
UPDATE element_identifier NAMES
The first of these will change the DDNM, IDLN, and IDNM attributes of element_identifier,
and all elements below it in the DRAFT database hierarchy, to match the values obtained
from the associated text attributes. This means that if a DESIGN database is deleted and
rebuilt then, so long as those elements referenced from DRAFT databases are all named,
references in DRAFT databases can easily be kept up to date.
The second command will change the DDNX, IDLX, and IDNX attributes to match the
values obtained from the associated reference attributes. This option has been included
primarily to allow a full set of these new text attributes to be generated for existing DRAFT
databases. In each case no change will occur if a value cannot be obtained from the name/
reference encoding/decoding process. The element_identifier can be omitted, in which case
the current element will be assumed.
During the updating process warning messages will be output whenever an attribute is
changed or when DRAFT attempts to change an attribute but is unable to generate the
required name or reference to do so. These messages will be of the form:
2:2
12 Series
2.2.2
2.2.3
2.3
Miscellaneous Facilities
2.3.1
ALARM ON
sets the audible tone to be on.
ALARM OFF
suppresses the audible tone until it is turned on again.
2.3.2
2:3
12 Series
Example:
2.3.3
TRACE OFF
TRACE ON
ALPHA FILE will only record commands you give, not the system's responses.
2.3.4
WARNINGS ON
2.4
Summary of Commands
2.4.1
Entering DRAFT...
DRAFT
enters DRAFT
2.4.2
Leaving DRAFT...
QUIT
leaves DRAFT without saving database changes.
QUIT module_name
switches to named module, without saving database changes.
module_name
switches to named module, saving database changes.
2:4
12 Series
2.4.3
2.4.4
2.4.5
2.4.6
Database Switching
SW
switch Design/Drawing contexts
CONT DRAW
switch to Drawing context
CONT DES
switch to Design context
2:5
12 Series
2.4.7
2.4.8
2.4.9
2.4.10
2:6
12 Series
3.1
DRAWING
SHEET
VIEW
Figure 3:1.
The principal element is the Drawing (DRWG), which is the Database equivalent of the
traditional paper drawing. All the elements below DRWG in the hierarchy are used to store
the information required to completely define the Drawing.
A Drawing can own one or more Sheet (SHEE) elements, which correspond to the sheets of
a paper drawing (Sheet 1 of 3, Sheet 2 of 3 etc). A Drawing can consist of a single Sheet.
A Sheet is the highest-level element that may be displayed within a view.
A Sheet may own one or more VIEW elements. These are projections of parts of the Design
Database. A VIEW element has attributes that:
define the viewing parameters (looking direction, through point, scale, etc)
define the size, position and orientation of the region on the Sheet that the View
occupies
3:1
12 Series
refer to another DRAFT database element that contains a list of the Design (or
Catalogue) elements that make up the VIEW picture.
3.2
NEW
NEW
NEW
NEW
NEW
DEPT /PIPES
REGI /PIPREG
DRWG /PD101
SHEET /SHEET1
VIEW /PLAN
You can omit all commands except for NEW DRWG and NEW VIEW if there is only
Department, one Registry and one Sheet on the Drawing. If the administrative elements do
not exist they will be created automatically.
Departments (DEPT) and Registries (REGI) are administrative elements. Departments
own Registries, as shown in the following diagram.
WORLD
DEPT
REGI
DRWG
REPO
LIBY
SHEE
(or to a DESIGN
database element)
DLLB
DESIGN
Database
IDLI
ADDE
Figure 3:2.
VIEW
IDLN
REME
3:2
12 Series
Note: You can have several VIEWs on a Sheet. Each VIEW can contain a picture of a
different part of the Design model, or different views of the same part of the model.
See Changing the Picture by Changing VIEW Attributes for details of manipulating
the contents of a VIEW.
3.2.1
3.3
3.3.1
AUTOSCALE Command
The AUTOSCALE command is typically:
AUTOSCALE
AUTOSCALE /ZONE1
AUTOSCALE /IDLIST-STEAM-PIPEWORK
This command carries out the following operations:
The VIEWs IDLN (ID List Name) attribute is set to the name of the Design item or
IDList element to be drawn (/ZONE1 or /IDLIST-STEAM-PIPEWORK in our second
and third examples).
The VIEW's THPO (Through Position) attribute is set to the World coordinates
corresponding to the centre of interest of the Design items to be drawn.
The VIEW's VSCA (View Scale) attribute is set to a value calculated such that the
Design items to be drawn will fit within the View rectangle. The current values of the
VIEW's DIR and SIZE attributes are used (these define the 'looking direction' and the
size of the rectangle).
Note: The AUTOSCALE command only sets the IDLN attribute if it has not already been
set. A second AUTOSCALE command will not change the IDLN (but the specified
Design item or IDList will be used in the recalculation of the VSCA and THPO
attributes). An AUTOSCALE command by itself will use the existing IDLN setting to
recalculate VSCA and THPO.
3.3.2
AUTOSIZE Command
The AUTOSIZE command is typically:
AUTOSIZE
AUTOSIZE /150-A-3-Branch1
AUTOSIZE /Equipment-List
This command carries out the following operations:
3:3
12 Series
The VIEW's IDLN (ID List Name) attribute is set to the name of the Design item or
IDList element to be drawn (/150-A-3-Branch1 or /Equipment-List in our second and
third examples).
The VIEW's THPO (Through Position) attribute is set to the World coordinates
corresponding to the centre of interest of the Design items to be drawn.
The VIEW's SIZE (View Rectangle Size) attribute is set to a value calculated such that
the Design items to be drawn will fit within the View rectangle. The current values of the
VIEW's DIR and VSCA attributes are used (these define the 'looking direction' and
scale).
Note: The AUTOSIZE command only sets the IDLN attribute if it has not already been set.
A second AUTOSIZE command will not change the IDLN (but the specified Design
item or IDList will be used in the recalculation of the SIZE and THPO attributes). An
AUTOSIZE command by itself will use the existing IDLN setting to recalculate SIZE
and THPO.
3.3.3
3.4
3:4
12 Series
Library (LIBY) elements can appear at four positions in the hierarchy (see Appendix
A). They are administrative elements used to group together several types of sublibrary. The type of sub-library of interest here is the Drawing List Library (DLLB).
The Id List is constructed by using ADD and REMOVE commands as in the following
examples:
ADD /ZONE.PIPES2-1
ADD /ZONE.EQUI2-1
REMOVE /PIPE2-1-12
REM /PUMP2-1-12
ADD and REMOVE may be combined on a single line, for example:
NEW
ADD
ADD
REM
IDLI /LIST1
/ZONE1
/LIST2
/LIST3
Note: When evaluated individually both /LIST2 and /LIST3 must define a set of design
elements which are then added to/removed from /LIST1, respectively. In particular if /
LIST3 is being used to remove a number of Branches (say) from /LIST1 then it
should be defined as:
Sequence 2
ADD /ZONE.PIPES
ADD /ZONE.PIPES
ADD /PIPE1-1
REM /PIPE1
REM /PIPE1
ADD /PIPE1-1
In Sequence 1 the final command removes all branches owned by /PIPE1 - including /
PIPE1-1 which has been added by the second command (and implicitly by the first). In
Sequence 2 these commands have been reordered so that having removed all branches in
/PIPE1 (second command) the required Branch (/PIPE1-1) is added by the final command.
3:5
12 Series
Having created an Id List it can be used to define the contents of a VIEW by setting the
VIEW's IDLN attribute directly:
IDLI /ID1
or indirectly:
AUTO /ID1
as described in Defining Views Using the AUTO Commands.
Note: GRIDSYstem and GRIDAXis elements may be added to IDLists but may not be the
sole member of the IDList. When drawn their GRIDLNs will be considered to be of
infinite length and so will be extended to the VIEW boundary. AUTO commands
ignore these elements when calculating the VSCA, THPOS, and SIZE attributes of a
VIEW.
3.4.1
DESADD /ZONE.PIPES2-1
DESADD /ZONE.EQUI2-1
DESREMOVE /PIPE2-1-12
DESREM /PUMP2-1-12
This sequence of commands adds elements /ZONE.PIPES2-1 and /ZONE.EQUI2-1 to a 3D
View, and removes /PIPE2-1-12 and /PUMP2-1-12. This is normally activated by the
interface.
3.4.2
NEW ADDE
CRIT ALL BRAN WITH (PSPE EQ /RF300)
3:6
12 Series
3.4.3
Spatial Map
The ADD ... WITHIN variation of the ADD command uses the PDMS spatial map. The
spatial map is a simplified geometric representation of the design model. For example:
3.4.4
LIMITS @ TO @
Set limits as 3D coordinates using the cursor.
LIMITS ID @ ID @
Set limits as 3D coordinates via Design elements selected with the cursor.
3.4.5
Cleaning Up Id Lists
Id Lists may be purged of unknown references by the command:
DELETE NULL IDLIstmembers
This command scans down the database hierarchy from the current position and deletes all
ADDE and REME elements whose IDNM attribute is null or references an unknown
element.
3.4.6
Querying Id Lists
Q FOR /design_element_name
At an IDLI, or at a VIEW.
3:7
12 Series
3.5
3.5.1
VIEW Frame
LFRA controls the visibility of the VIEW frame. The frame will be drawn using the Views
NLSTYLE/NLCOLOUR attributes. See Colours and Styles for a description of colours and
styles.
LFRA TRUE (or FRAME ON)
turns the frame on,
LFRA FALSE (or FRAME OFF)
turns the frame off. The frame is OFF by default.
3.5.2
View Size
SIZE is the paper size of the VIEW rectangle. Changing the size by a command such as
3:8
12 Series
leaves the scale of the VIEW contents unaffected, but moves the point at the centre of the
picture to the centre of the new VIEW frame.
The SIZE attribute is also be changed by the VREGION command, which may be used to
resize and reposition the VIEW. For example:
Example:
VREGION FROM @ TO @
Opposite corners of VIEW defined by cursor
VREG AT @
Centre of VIEW defined by cursor
VREG corner AT @
Specified corner of VIEW defined by cursor:
TL top left
TR top right
BL bottom left
BR bottom right
C centre
The default size is that of the owning Sheet. The VREGION command also affects the
XYPS attribute (see View Centre).
The SIZE command can also be used at SHEE level to change the Sheet size.
3.5.3
View Centre
XYPS controls the position of the centre of the VIEW on its owning Sheet. This attribute
takes two numeric values, which are the coordinates of the centre of the VIEW relative to
the bottom left corner of the Sheet. The attribute can be set directly by commands such as
AT @
Nominate new XYPS with cursor
3:9
12 Series
Figure 3:3.
ONPOS is the position of the centre of the VIEW contents, relative to the centre of the
VIEW. VIEW contents are centred within the VIEW by default, so this attribute takes the
default values x0 y0. ONPOS is set directly, for example:
ONPO 45 -25
See Figure 3:4.: Changing VIEW ONPOS. Changing ONPOS will make the existing VIEW
graphics out-of-date, so an UPDATE DESIGN command must be given.
ONPO
Figure 3:4.
3.5.4
ONPO
View Scale
VSCA controls the scale of the VIEW contents. The scale will normally be set automatically
to a value which ensures that the VIEW contents fit comfortably within the VIEW boundary
(see the AUTO command), but can be changed if necessary, e.g.
VSCA 0.05
The larger the VSCA value, the larger are the displayed objects.
VIEW scale may be expressed in terms of a ratio using the VRAT (VIEW Ratio) attribute, for
example:
VRAT 1 TO 75
VRAT 1/16in TO 1ft
3:10
12 Series
Two positive values have to be specified but the TO may be omitted. Setting VRAT will
cause the existing VIEW scale (VSCA attribute) to be recalculated. Setting VSCA directly
causes VRAT to be unset. The AUTO command calculates and sets VSCA directly so this
will also cause VRAT to be unset.
Care should be taken when changing VSCA, as it is easy to move the VIEW contents over
the VIEW frame. The AUTO command takes the ONPOS value into consideration when it
calculates the VSCALE.
3.5.5
TURN 60
ADEG -120
A positive value results in an anticlockwise rotation. Figure 3:5.: Changing Orientation of
VIEW Contents illustrates the effect of changing ADEG.
ADEG 0
Figure 3:5.
ADEG 90
Note that the degree of rotation produced is relative to an ADEG value of 0, not to the last
value of ADEG.
Varying RCOD (rotation code) produces a similar effect to varying ADEG, except that the
VIEW is rotated as well. RCOD may be set to UP, DOWN, LEFT or RIGHT, corresponding to
the direction of the top of the VIEW region relative to the top of the screen. Default is UP.
3.5.6
Perspective
PERS (perspective) can be used to give a perspective projection, the value taken by the
PERS attribute being related to the view angle. The default value of 0 gives a parallel
projection, which would be the normal setting for drawings. If PERS is changed, an
UPDATE DESIGN command must be given to change the picture.
3:11
12 Series
3.5.7
3D View
A 3D View can be generated from a 2D View using the GENERATE MODEL command. This
view can be amended using the user interface. Elements can be added using the DESADD
command (see Adding Elements to 3D View).
3.5.8
Looking Direction
The Views line of sight is fully defined by any two of:
Looking Direction
From Point
Through Point
which are defined by the attributes DIR, THPO and FRPO. Setting one of these will unset
one of the other two, assuming they are both already set.
DIR (Direction) specifies the Looking Direction, down by default. This attribute is set by
commands such as
LOOK E
LOOK N45W
ISO3
PLAN
ELEVATION N
IR D
Note that the picture produced by changing the Looking Direction may not necessarily fit
into the VIEW frame.
The THPO (Through Point) attribute is set to the Design coordinates corresponding to the
centre of interest of the view. These will be calculated automatically from the VIEWs related
Id List by the AUTO command.
FRPO (the From Point) is the position (in Design coordinates) at which the observer is
deemed to be.
The Through Point and From Point may be set explicitly by commands such as:
LOOK
LOOK
FRPO
THPO
Changing the Direction, Through Point or From Point will make the existing VIEW graphics
out of date, so this must be updated by typing
UPDATE DESIGN
before any change in the picture will be seen.
The 3D view direction equivalent to 2D Sheet direction may be queried using
Query VIEWDIRection <sheet-dir>
where <sheet-dir>is Left, Right, Up or Down. This command gives an error when the
VIEW has Perspective or the current database position is not at or below a VIEW.
For example, in a plan VIEW with RCODE UP (the default), then the query
Q VIEWDIR LEFT
3:12
12 Series
would give:
Viewdirection Left W
However, for a plan VIEW with RCODE LEFT, the result would be:
Viewdirection Left N
and for a plan VIEW with ADEG 120 (and RCODE UP) the result would be:
Viewdirection Left E 30 N
3.5.9
3.5.10
3.5.11
3.5.12
Arc Tolerance
The ATOL attribute controls the Arc Tolerance (the difference between the true and the
facetted representation of curves) of the graphical output for the VIEW, being set in units of
hundredths of a millimetre on the drawing. (Default value 15.)
3.5.13
3.5.14
3.5.15
3:13
12 Series
3.6
3.7
Figure 3:6.
3:14
12 Series
Modelled Wireline representation gives slightly greater realism by blending the intersection
of primitives, but without incurring the computational overheads of removing hidden lines.
Figure 3:7.: Typical Modelled Wireline View shows a modelled wireline display.
Figure 3:7.
Wireline Hidden Line Removed representation produces a View where hidden lines are
removed from individual significant elements (EQUI, SUBS, etc) but not from items hidden
behind them. A typical View is shown in: Figure 3:9.: Typical Local Hidden Lines Removed
View.
Figure 3:8.
3:15
12 Series
Local Hidden Line representation gives a picture where hidden lines are removed from
individual significant elements (EQUI, SUBS etc), but not from items hidden behind them.
This gives a picture as shown in Figure 3:9.: Typical Local Hidden Lines Removed View.
This representation differs from Wireline Hidden Lines Removed because individual
significant elements are properly modelled so that intersections between primitives and
holes are correctly shown.
Figure 3:9.
Global Hidden Line representation gives a picture where all hidden lines are removed,
giving a picture as shown in Figure 3:10.: Typical Global Hidden Lines Removed View.
3:16
12 Series
Universal representation (see Figure 3:11.: UNIVERSAL VIEW Type) gives a picture where
all hidden lines are removed (as in Global HLR), but in addition intersection lines between
clashing significant elements (e.g. EQUI and STRU or SUBS and SUBS) are generated.
Whether you will need to use this View type will depend on the way in which you have
created the model. The need for VTYP UNIVERSAL will be greater if the model is
composed of a large number of significant elements each with a small number of primitives,
rather than vice versa. It is also more likely to be needed in non-orthogonal Views, where
missing intersection lines are most noticeable.
Figure 3:11.
3.8
VTYP WIRE
wireline (default)
VTYP MWIR
modelled wireline
VTYP WIREHL
VTYP LOCAL
VTYP GLOBAL
VTYP UNIV
2D Symbolic Representation
DRAFT allows design elements to be represented symbolically in a 2D View when the
UPDATE DESIGN command is executed. Symbolic representation may either replace or be
in addition to the normal geometric representation of the elements.
3:17
12 Series
3.8.1
3:18
12 Series
design element that it is intended to replace in the DRAFT View, regardless of the aspect
ratio of that design element.
3.8.2
3.9
Querying Commands
3.9.1
For example:
Specify a significant design element and request a list of all its primitives that are visible
in a View.
Q VSCAN design_id IN view_id
For example:
Q VSCAN /PIPE100-B-1-B1
For example:
3:19
12 Series
3.9.2
Q FIND /BRANCH-01
Possible answers are:
FOUND
MISSING
INVALID ELEMENT
Note: A significant Design element will not be found in a View if it only owns other
significant elements. It must own visible primitives. This affects EQUI, STRU and
FRMW elements; they will not be found unless they own visible primitives.
3.9.3
Q
Q
Q
Q
VSIDE
VSIDE
VSIDE
VSIDE
OF
OF
OF
OF
/VESS-99
PPO2 OF /VALVE-100
PPLINE TOS OF /SCTN-101 START
PPLINE MEML OF /SCTN-101 PROP 0.5
The ROTATED option allows the rotation (i.e. the VIEWs RCOD attribute) to be considered
if required.
The response will be the nearest and next-nearest sides, and also whether the item is inside
or outside the View. For example, Point 1 in Figure 3:12.: Querying the nearest side to an
item will be LEFT UP OUTSIDE.
3:20
12 Series
3.10
3.10.1
Prerequisites
Certain environment variable settings must be defined before the BPM can be used:
PDMSWK, since it contains the job XML file, the PDMS macro, the regenerated VIEW
files and the DRAFT log file. It also contains the BPM log file.
The project environment variables XXX000, XXXISO, XXXMAC and XXXPIC must be
defined for each project XXX to which the BPM is applied.
A batch file BPM.bat is supplied to enable the above environment variables automatically
and to start the BPM in much the same way as PDMS.bat enables to PDMS environment
variables.
3.10.2
DESIGN
NOWAIT
command,
normally
via
associated
4. The system then creates an entry in the BPM queue and returns immediately for the
next action.
5. Once started, the BPM reads the next entry in the queue and creates a hidden
DRAFT session running in the background to run the job. To avoid unlimited multiple
copies of DRAFT being initiated, a process only starts after the previous one has
finished. (How to start the BPM is described below.)
6. For each job the background DRAFT session performs a special UPDATE DESIGN
command that generates and stores each new VIEW in a separate intermediate view
file or IVF. This is a picture file prefixed with the letter X instead of the standard M.
3:21
12 Series
7. Once the process has finished, a notification is raised, which is signalled by an icon in
the Windows notification toolbar. Each background DRAFT session started by the BPM
writes a standard PDMS log file to the PDMSWK folder. The log file has the same name
as the initiating XML job file but with the .log extension.
8. You may then re-enter foreground DRAFT and navigate back to the original VIEW
(SHEET or DRAWING) to load the new picture. Each VIEW updated by the BPM will
generate its own IVF. This enables you to refresh selected VIEWs only (or a SHEET or
a DRAWING).
9. Issue an UPDATE REFRESH command to refresh the current VIEW (SHEET or
DRAWING).
10. If the refreshed VIEWs are acceptable, you may save them permanently using a
SAVEWORK, as usual.
Note: If a refreshed VIEW is unacceptable, you should NOT issue a SAVEWORK to save it
permanently. Instead, the original SHEET should be re-selected to re-load the old
contents.
Be careful to save any outstanding changes to other VIEWs in the same SHEET
before refreshing another VIEW.
To start and use the Background Process Manager:
1. Initiate the BPM by invoking the BPM.bat start-up file.
2. The Background Process Manager form then appears, which displays details of each
job together with its Status of Not Started or Finished and an exit code showing
success or failure. See Managing Jobs using the Background Process Manager Form
for details of the Background Process Manager form.
3. Processing of Not Started jobs is initiated from the Background Process Manager
form. The form shows the job currently running and provides facilities to start job
processing or stopping the current job, as required.
4. When one or more jobs appear in the job list, click on the Start manager hyperlink to
start the processing of jobs with Status Not Started. Note that the hyperlink changes to
Stop manager at this point. The Background Process Manager form may be
iconised at this point.
5. Once the process for a job has finished, the Background Process notification icon
appears in the notification area on the Windows task bar.
6. The Background Process Manager form may then be restored, if necessary, to view
the updated Status and Exit Codes. An exit code of Success means that the updated
VIEW (SHEET or DRAWING) can be refreshed into the foreground DRAFT session.
7. The Background Process Manager form can then be minimised and the Background
Process notification icon cleared by right-clicking on it and then selecting the Clear
Item option.
8. The next waiting job is then started automatically.
9. Once the BPM is in the Stopped state it may be exited using the File>Exit menu
selection.
A log file of the processing is saved to the PDMSWK folder and is called
BPM_ddmmyyyy_hhmmss.log
where: ddmmyyyy is the standard date and hhmmss is the standard time that the process
was started. The log file should contain a record of all processing in the Background
Process session, including errors.
3:22
12 Series
3.10.3
Tabbed Windows
The Manager log tabbed window contains the BPM log of jobs processed.
The Job tabbed window is used to display the log file of the finished job. To select a finished
job double-click on the appropriate row in the job list table or right-click on View log (see
below).
Cancel, Delete and Purge
Jobs may be managed collectively by using the File pull-down menu (see below) or
individually by selecting the job from the table of jobs and selecting from the right-mouse
button menu.
Managing Jobs Collectively
The File pull-down menu is used for this. The options are:
Start manager
starts the processing of the jobs currently listed - changes to Stop Manager.
Stop manager
stops the processing of the jobs currently listed - changes to Start Manager.
Refresh
refreshes the job list table, i.e. clears it and then repopulates it from scratch.
3:23
12 Series
Exit
exits the BPM.
View log
displays the log file of the selected job in the Manager log tabbed window.
Cancel job
cancels the selected job.
Restart job
restarts the selected job.
Delete job
deletes the selected job.
3.11
Summary of Commands
3.11.1
At Id List . . .
ADD design_element_identifier [design_element_identifier...]
adds Design element to Id List.
REM design_element_identifier [design_element_identifier...]
removes Design element from Id List
ADD ALL design_element_identifier FOR design_element_identifier
REM ALL design_element_identifier WITH ( selection_criteria ) FOR
design_element_identifier
DESADD design_element_identifier [design_element_identifier...]
adds Design element to 3D View.
DESREMOVE design_element_identifier [design_element_identifier...]
removes Design element from 3D View
ADD ALL design_element_identifier FOR design_element_identifier
LIMITS E value N value U value E value N value U value
removes Design elements from ID List that are not wholly or partially contained within
defined limits box.
LIMITS @ TO @
set limits as 3D coords with the cursor
LIMITS ID @ ID @
set limits as 3D coords via Design elements using the cursor
DELETE ENTRY number
3:24
12 Series
delete either an ADDE or REME from the Id List members - the number is the member
list number
DELETE ADD number
delete an Add item, number corresponding to number of the element out of the Adds
only
DELETE REM number
delete a Remove item, number corresponding to the number of the element out of the
Removes only
3.11.2
3:25
12 Series
Database changes will be shown in the manner defined by the View's Change Ruleset. For
more information see Change Highlighting. This option is only valid at View elements or
above, it cannot be used for a Layer, say.
UPDATE PICTURE
regenerates Sheet level picture. Updates annotation graphics (but not Design
graphics). Use only when the picture file is corrupted. DRAFT will prompt the user
when this is necessary. Use at Sheet level or equivalent.)
3.11.3
At VIEW . . .
SIZE xvalue yvalue
set VIEW size in mm with origin at default i.e. centre of Sheet. Min, Max, x,y values
are 1 mm, 3276 mm respectively.
SIZE paper_size
set VIEW size to a standard paper size, e.g. SIZE A2
VREGION @
set VIEW size and position using cursor
VREGION FROM X value Y value TO X value Y value
set VIEW size and position explicitly
VREGION corner
move VIEW using specified corner to position:
TL top left
TR top right
BL bottom left
BR bottom right
C centre
VREGION VERTICAL direction
set VIEW (vertical axis) orientation:
U up
D down
L left
R right
AT @
position VIEW origin in Sheet using cursor
AUTO design_element_identifier
set VIEW Scale and Through Point through design_element_identifier and scale to fit
AUTO idlist_name
set VIEW Scale, Through Point and Id List reference. If idlist_name is omitted the IDLI
relevant to the VIEW is assumed.
AUTO LIMITS OF /idlist_name
use limits box of Id List to define VIEW
AUTO FROM position TO position
3:26
12 Series
use specified limits box to define view. The VIEWs VSCA and THPO attributes are
calculated from the box defined by the two 3D co-ordinates specified by position.
(position includes cursor specification of a 3D point or p-point, explicit p-point
reference, origin of a named element, or an explicit 3D coord.)
VSCALE value
set Scale of VIEW
THPO E value N value U value
(or LOOK THROUGH ...)
set Through Point of VIEW in 3D coords
THPO ID @
(or LOOK THROUGH ...)
set Through Point as Design element p-point (converted to 3D coord)
FRPO E value N value U value
(or LOOK FROM ...)
set From Point of VIEW in 3D coords
FRPO @
(or LOOK FROM ...)
set From Point in 3D coords with cursor
FRPO ID @
(or LOOK FROM ...)
set From Point as Design element p-point (converted to 3D coord)
ONPO xvalue yvalue
position the Through Point relative to the VIEW origin
ONPO @
position the Through Point relative to the VIEW origin using the cursor
TURN value
(or ADEG value)
rotate VIEW anticlockwise
VTYP option
set VIEW type.
Options: WIRE, MWIR, LOCAL, GLOB, UNIV
LOOK value
(or DIR value)
set VIEW direction
ISO value
set isometric VIEW direction
PLAN
set plan VIEW direction
ELEV option
3:27
12 Series
3.11.4
Anywhere . . .
DELETE NULL IDLI
deletes all ADDE and REME elements whose IDNM attribute is null or which
references an unknown element
3.11.5
3:28
12 Series
3:29
12 Series
3:30
12 Series
Graphical Representation
Representation Rules control how Design elements are drawn. Each Rule can specify a
given type or types of element, or named elements. Representation Rules refer to Styles.
The attributes of a Style define a series of drawing styles and colours, for example, for
frontface, backface and centreline, and whether items such as p-lines and obstruction
volumes are shown. For more information about styles and colours see Colours and Styles.
Representation Rules also control which design elements are to be replaced by symbols
when a 2D View is created. For a description of 2D symbology, refer to 2D Symbolic
Representation.
Representation Rules can be created in a Library and be referred to from a VIEW, or they
can be owned directly by a VIEW, in which case they are known as local rules. Local Rules
override Library Rules. See Local Rules for more information about the order in which Rules
are applied.
Representation Rules (RRUL) are stored in Representation Rulesets (RRST), which in
turn are owned by Representation Libraries (RPLB).
RPLBs are also used to store STYLs. The reference from an RRUL to a STYL is made by
setting the STYF attribute of the RRUL. When a View references a RRST, the reference is
made by setting the RRSF attribute of the View.
Figure 4:1.
4:1
12 Series
This Section also describes Hatching Rules, which are used for automatic hatching of
faces of Design elements. See Automatic Hatching.
For details of how changes to design elements can be shown see Change Highlighting.
4.1
Representation Styles
The Representation Style (STYL) defines the appearance of the elements specified by a
RRUL that references it. The STYL attributes, with their defaults, are as follows:
Tube flag
TUBEF
OFF
Centreline flag
CLIN
ON
PSYM
ON
Obstruction flag
OBSTF
OFF
Insulation flag
INSU
OFF
Profile flag
PRFG
OFF
P-line flag
PLFG
ON
Drawing Level
DLEV
Frontface Style/Colour
FFSTYLE/FFCOLOUR
SOLID/1
Centreline Style/Colour
CLSTYLE/CLCOLOUR
CHAIN/1
Backface Style/Colour
BFSTYLE/BFCOLOUR
OFF
Obscured Style/Colour
OBSTYLE/OBCOLOUR
OFF
P-line Style/Colour
PLNSTYLE/PLNCOLOUR
LDASH/1
MLNSTYLE/MLNCOLOUR
OFF
TUBEF, CLIN, PRFG, PLFG, PSYM, OBSTF and DLEV are standard PDMS display
representation controls and are not described here. (See the DESIGN Reference Manual for
details.)
If INSU is ON, Piping Component Insulation will be drawn using the frontface style and
colour (FFSTYLE/FFCOLOUR). The outline of the piping Components will be hidden by the
insulation in hidden-line views. If insulation and Components are required to be displayed,
two similar views (that use different Styles) will need to be defined and superimposed.
The style/colour attributes allow different parts of chosen items to be drawn differently, and
are used as follows:
Frontface Style/Colour. In wireline VIEWs these attributes control the style and colour
to be used to represent all edges. All edges are shown, except for holes that will be
drawn with a dashed line of the same colour as the FFCOLOUR. Set directly, for
example:
FFSTYLE SOLID M
FFCOLOUR 1
4:2
12 Series
Centreline Style/Colour. These attributes control the style and colour to be used for
representing centrelines. They are also used for drawing GRIDLN and LINE elements
of Catalogue Components. When drawing pipework with TUBEF ON, CENTRELINE
ON, the centreline will not be obscured by the piping Components. (Unlike FFSTYLE, it
is not necessary to superimpose two VIEWs with different Styles.
DRAWI elements owned by EQUI, SUBE, STRU, SUBS, or PTRA will be drawn using the
centreline style/colour of the STYL specified. For these DRAWIs the setting of the STYLs
centreline flag (CLFG) will be ignored even though the centreline style/colour is used; the
LEVEL attribute should be used to control whether the DRAWI appears on the drawing. Set
directly, e.g.
CKSTYLE DASHED
CLCOLOUR 1
Backface Style/Colour. In hidden line VIEWs, these attributes control the style and
colour to be used to draw the rear edges of items (set to OFF by default). Set directly,
e.g.
BFSTYLE DOT
BFCOLOUR 1
BFSTYLE would normally be set OFF for hidden line VIEWs, but if required can be used to
set the style and colour to be used for drawing the rear edges of items. These attributes
have no effect in wireline views. See Figure 4:2.: Use of Backface Style/Colour (shown
dotted) for an example of the use of the Backface Style/Colour.
Figure 4:2.
4:3
12 Series
Obscured Style/Colour. In global hidden line VIEWs, these attributes control the style
and colour to be used to draw the front-facing edges of items that would otherwise be
obscured by other objects (set to OFF by default). Set directly, e.g.
OBSTYLE DOT
OBCOLOUR 1
These attributes have no effect in wireline and local hidden line VIEWs. See Figure 4:3.:
Use of the Obscured Style/Colour (shown dotted) for an example of the use of the Obscured
Style/Colour.
Figure 4:3.
P-line Style/Colour. This attribute controls the style and colour to be used to draw plines. Set directly, for example:
PLNSTYLE CHAINED
PLNCOLOUR 1
Member line Style/Colour. These attributes control the style and colour to be used to
draw SCTN and GENSEC member lines. Set directly, for example:
MLNSTYLE SOLIDT
MLNCOLOUR 1
4:4
12 Series
P-line and member line styles and colours apply only to drawing steelwork Section
elements.
See Colours and Styles for a description of colour and linestyle functionality.
4.2
Representation Rules
The Representation Ruleset owns a series of Representation Rules, each of which contains
a reference to a different Representation Style. A Ruleset can therefore be used to produce
several graphical representations of the same VIEW. An example of the commands for
setting up a Ruleset is:
- create Ruleset
- create Rule
When more than one Rule is created, the order of the command sequence is important.
Consider the command sequences:
Sequence 1
Sequence 2
Sequence 1 would result in Nozzles being drawn according to style /S1, sequence 2 would
give Nozzles in style /S2.
You can also assign a style reference to an individual named Design element or a series of
named elements, for example:
4:5
12 Series
Example:
OMIT /EQUIP99
The OMIT command sets the OMITFG attribute of the Rule, which automatically unsets the
STYF of the Rule.
DRAFT determines the style to use from a particular element by scanning through the list of
RRULs (in database order) until a selection criteria is matched. If DRAFT is unable to find a
relevant rule for a component the default style will be used. This is:
Tube Off
Centreline On
Profile Off
Pline On
Drawing Level 0
Ffstyle SOLID
Ffcolour 1
Clstyle CHAINED
Clcolour 1
Other drawing styles Off
4.2.1
4:6
12 Series
be shown, unobstructed by other items of the model. Users should note that to obtain this
functionality the RRUL should apply to GRIDSYstem or GRIDAXis elements and not to
GRIDLNs. Typically, the definition of the RRUL should therefore be:
4.2.2
4.2.3
WI (PSPE EQ /RF300
is equivalent to
WI /RF300 EQ PSPE
WI (ABORE GT 80)
is equivalent to
WI 80 LE ABORE
4:7
12 Series
Note: That it is possible to apply a selection criterion to a list of class types by enclosing
them in brackets, for example:
USE /ST1 FOR (ALL BRAN ALL SUBS) WI (ZONE EQ /ZONE.PIPES)
Without the brackets the selection criterion would only be applied to SUBS.
Selection criteria should not be used unnecessarily. For example, if you wish to draw
small-bore Branches in style /ST1 and the rest in style /ST2, it is only necessary to
say:
4.2.4
Local Rules
Local Rules may be set up as VIEW members in the same way as Library rules; the
resulting graphical representation is determined as follows:
Local Rules always have priority over Rules within Rulesets in Libraries.
A Rules priority is determined by its position in the list; the higher in list the higher its
priority, but a Local Rule will still have a higher priority than the top Ruleset Rule.
This means that you should always place the more specific rules earlier in the list.
4.2.5
4.3
Automatic Hatching
Model faces created by section planes, and surfaces of specified Design primitives can be
hatched automatically by defining and applying Hatching Rules. The hatching is carried out
automatically as part of the Update Design process. For more information on Section planes
see Section Planes.
The Hatching Rules (HRUL elements) define the faces to be hatched, and they reference
Hatching Styles (HSTYL elements). Hatching Styles define the styles and colours to be
used to draw the hatching. Hatching Rules are stored in Hatching Rulesets (HRST
elements).
Hatching Rules and Rulesets are similar to Representation Rules and Rulesets. Hatching
Styles and Rulesets are stored in RPLBs. Local Hatching Rules can be defined by creating
HRULs owned directly by Views. The Local Hatching Rules directly reference Hatching
Styles (HSTYL).
The hierarchy of database elements for hatching is similar to the Representation Rules, and
allows you to impose company or project drawing standards.
4:8
12 Series
Hatched areas can be auto-blanked to allow annotation placed on top of them to be legible.
See Autoblanking.
Figure 4:4.
4.3.1
Hatching Rules
Each Hatching Rule references a Hatch Style element that defines the hatch pattern to be
applied. For each Hatch Rule you can specify:
The orientation of the faces to be considered for hatching. There are three options:
All Directions, in which case the face will be hatched regardless of its orientation.
Specified Direction, in which case the face will only be hatched if its normal
matches a specified value. The normal of a face is the vector perpendicular to it and
pointing out of the solid primitive. Thus the normal of the uppermost horizontal
surface of a box is Up.
HSTYF
Face Code
FCODE
Sectioned-Faces
Direction Code
DCODE
All-Directions
Face Normal
NORM
unset
Selection Criteria
CRIT
unset
4:9
12 Series
Example:
HSTYF /HSTYL1
FCODE SECTionedfaces
FCODE PRIMitivefaces
DCODE ALL Directions
DCODE PERPendiculardirection
DCODE SPECifieddirection
NORM standard AVEVA direction syntax
CRIT standard AVEVA selection criteria syntax
As well as the usual NEW command, an HRUL can also be defined by:
4.3.2
4.3.3
Hatching Styles
Each Hatching Style defines two style/colour pairs, either style may be set OFF. The Fill
Style and Fill Colour (FSTYLE and FCOLOUR) attributes define the hatch pattern to be
applied to the selected faces. The Outline Style and Outline Colour (OLSTYLE and
OLCOLOUR) attributes define the lines that may be drawn around the edges of the faces.
For example, it is possible to emphasise an area by drawing a thick line around it without
actually hatching it. For more information about hatch-patterns see Hatching Rules.
The HSTYL attributes, with their defaults, are as follows:
Outline Style
OLSTYLE
Off
Outline Colour
OLCOLOUR
Colour 1
Fill Style
FSTYLE
SYSTEM PATTERN 1
Fill Colour
FCOLOUR
Colour 1
PIPESYM
TRUE
4:10
12 Series
By default, when a length of implied tubing or a DUCT or STRT (ducting straight) element is
cut and the resulting face is circular or rectangular, DRAFT will generate a typical sectioned
symbol rather than just apply the hatch pattern to the face:
Figure 4:5.
The PIPESYM attribute of Hatching Styles allows this functionality to be suppressed and
replaced by normal hatching.
4.3.4
4.4
Querying Commands
4.4.1
Q DESC
- at Ruleset or Rule
Q RRSF DESC
- at VIEW
- at VIEW or Ruleset
The last example returns the Style used for the specified design element, irrespective of the
element type specified at the RRUL. A list of design element identifiers may be entered,
optionally separated by commas.
4:11
12 Series
4.4.2
4.5
Summary of Commands
4.5.1
At Representation Rule . . .
USE SYMBOLOGY FOR crit
Causes the Design elements defined by crit to be represented by 2D symbology only
USE SYMBOLOGY AND stylename FOR crit
Causes the Design elements defined by crit to be represented by both 2D symbology
and 3D graphics.
USE stylename FOR crit
set drawing style for Design generic types, see above.
CRITeria crit
set the CRIT attribute for the current rule
OMIT elements
omits the elements specified, by name or type, which may be an expression, from the
representation
4.5.2
At Representation Style . . .
FFSTYLE integer/line_pattern, FFCOLOUR integer/colour_name
FFSTYLE OFF
set style and colour for drawing edges (modelled wireline VIEWs) or visible (front face)
edges (hidden-line VIEWs).
4:12
12 Series
4.5.3
At Hatching Rule . . .
USE hstylename FOR crit
set hatching style for Design generic types, see above.
CRITeria crit
set the CRIT attribute for the current HRUL.
FCODE SECTionedfaces
Sectioned faces will be hatched.
FCODE PRIMitivefaces
Primitive faces will be hatched.
DCODE ALLDirections
All faces will be hatched, regardless of direction
DCODE PERPendiculardirection
Faces perpendicular to the viewing direction will be hatched.
DCODE SPECifieddirection
Faces whose normals match the direction specified in the NORM attribute of the
HRUL will be hatched. The normal of a face is the vector perpendicular to it and
4:13
12 Series
pointing out of the solid primitive. Thus the normal of the uppermost horizontal surface
of a box is Up.
NORM direction
Standard direction syntax
4.5.4
At Hatching Style . . .
OLSTYLE integer/line_pattern, OLCOLOUR integer/colour_name
Set different style and colour for drawing outline of selected faces.
OLSTYLE OFF
Selected faces will not be outlined.
FSTYLE integer/hatch_pattern, FCOLOUR integer/colour_name
Set style and colour for hatching selected faces.
FSTYLE SOLidfilled
Selected faces will be filled with solid colour.
FSTYLE OFF
Selected faces will not be hatched.
PIPESYM TRUE
PIPESYM FALSE
Pipe end symbols (or HVAC duct end symbols) will be drawn instead of hatching.
PIPESYM TRUE
PIPESYM FALSE
Pipe ends (or HVAC duct ends) will be hatched.
4:14
12 Series
Section Planes
Note: There are extensive graphical facilities for creating and manipulating Section
Planes in DRAFTs Graphical User Interface. See the Drawing Production User
Guide for details.
DRAFT gives you the ability to construct sections through specified Design items, the
results of which can be displayed at VIEW level. All Planes are database items and can
therefore be used with more than one VIEW. There are three types of Plane element that
can be used to define four types of section plane, namely:
A Perpendicular Flat Plane passes through a specified point in the 3D design, being
oriented so as to be perpendicular to the current VIEW direction. The VIEW contents
that are discarded can be on either side of the plane. This type of plane would be used
as either a section or a backing plane.
A Flat Plane is similar to a perpendicular flat plane, but can be oriented to allow views
of the section from any angle.
A Stepped Plane is a folded plane (i.e. a series of non-intersecting straight line spans)
that extends to infinity in both directions along a specified axis. The shape is defined by
a series of points, the ends of the plane also extending to infinity. The simplest form of
stepped plane would be defined by two points and would be equivalent to a Flat Plane.
Any VIEW direction can be used and the VIEW contents on either side can be
discarded. Note that the two end spans must not intersect each other or an inner span.
A stepped plane is illustrated in Figure 5:1.: Stepped Plane.
An Enclosed Plane. This is a particular form of stepped plane in which the first and last
points that define it coincide to form a tube that is infinitely long along its axis. Any
VIEW direction can be used and either the inside or outside of the tube can be
removed. An enclosed plane is illustrated in Figure 5:2.: Enclosed Plane.
5:1
12 Series
Figure 5:1.
Stepped Plane
Figure 5:2.
Enclosed Plane
All Planes have a standard retain and discard side, depending on how the Plane is
defined in the database. The Plane can be used in either standard or reverse mode, which
effectively switches the Planes action without altering its definition. This allows the Plane to
be used in different VIEWs both as a section or backing plane. Planes can only be used with
modelled VIEWs, that is not with basic wireline views.
5:2
12 Series
5.1
LIBY
VIEW
PLLB
VSEC
PLRF
PPLA
FPLA
SPLA
WPOS
Figure 5:3.
To use a plane to produce a sectioned VIEW, you need to create a View Section (VSEC)
element under a VIEW; VSEC attributes are:
IDLN - an Id List name for the section to operate on. If left undefined this will default to
the World (i.e. /*). This means that all elements in the VIEWs Id List will be sectioned.
A single Design item name can be used.
PMOD - the mode in which the plane will be used to section the VIEW, i.e. the side to
be retained or discarded. The default is STANDARD, which is as the plane is set-up.
REVERSE switches the side to be retained or discarded. OFF switches the plane off.
CLMO (centreline mode) By default this is set to ON, which has no effect on
functionality. If it is set to OFF then the section will not be applied to line elements of
Piping Components. This allows you to remove Components and tubing by a section
plane, but leave the centreline to show the path of the Branch. All other non-solid
primitives are sectioned normally and are unaffected by the value of attribute CLMO.
SMOD (a View attribute) - the section mode attribute, which defines how small parts of
piping components and implied tube that are cut by the front and back sectioning
planes will be treated. This attribute only affects piping components and implied tube in
orthogonal, non-perspective Views.
If SMOD is set to STANDARD (the default), all elements will be sectioned in the usual
way. If SMOD is set to OMIT FRACtional PCOMponents, the following functionality will
apply when the design graphics of the View are updated:
All piping components whose origins (P0) lie outside the front and back sectioning
planes will be removed from the drawlist. All other piping components will be drawn
completely, even if they are cut by one of the sectioning planes.
All lengths of implied tube that lie outside the front and back sectioning planes will
be removed from the drawlist. In this case the test for lying outside the sectioning
planes will be based on the vector Parrive -> Pleave, and not on the actual volume
5:3
12 Series
occupied by the length of tube. Lengths of tube that lie within or cross the front or
back sectioning planes will be drawn completely.
Where an IDList is defined by a set of piping components (for example, ADD /VALVE1 /
VALVE2 /VALVE3) the functionality will not apply.
The names of the items omitted can be output by the command
SMODE MESSAGES ON
but this will include all those piping components in the Views IDList that fall outside the
clipping box and would therefore not be drawn in any case.
Several VSEC elements can be used to produce as complex a section as you require, but
the larger the number the slower the operation will be.
After setting up the VSEC it is just a matter of updating the design (with an UPDATE
DESIGN command), remembering that sectioning will only take place if the VIEW attribute
VTYPE is set for Local, Global or Universal hidden line removal, or Modelled wireline.
5.1.1
- create a PPLA
POS @
POS ID @
POS IDP @
Note: You can only input a 3D Design position on orthogonal VIEWs; the looking direction
of such a VIEW will determine which coordinate is returned as zero. For example, a
plan view will return U0, which you may need to alter to give the required section.
Figure 5:4.: Use of the Perpendicular Plane (PPLA) illustrates the use of a perpendicular
Plane, positioned at the pump coupling.
5:4
12 Series
Figure 5:4.
5.1.2
5:5
12 Series
The NORM direction can be any standard direction, e.g. N45W, ISO2, or can be by
reference to a Design element p-point, in which case the result will be stored as a 3D vector
and the reference will be lost. Figure 5:5.: Use of the Flat Plane (FPLA) illustrates the use of
a flat Plane, positioned at the pump coupling and with a NORM direction of N45W.
Figure 5:5.
5:6
12 Series
5.1.3
Figure 5:6.
The SPLA shown above would be created by a sequence of commands such as:
NEW SPLA
DIR U
GTYP OPEN
STEP @ @ @ @
The STEP command will invoke the cursor, which will enable 3D positions or Design ppoints to be identified, automatically creating WPOS elements. DRAFT imposes no limit on
the number of steps, but in practice only four points can be defined by a single STEP
5:7
12 Series
command due to command line length restrictions. If a plane with more than four steps is
required, further STEP commands will enable additional points to be appended to the
existing member list. The minimum number of points required to define an SPLA is 2, which
will have the effect of a Flat Plane.
WPOS elements can be created explicitly by command sequences such as:
NEW WPOS
POS E120500 N236785 U0
If this syntax is used you must leave the list of WPOS elements in the correct order for the
SPLA to function. Figure 5:7.: Use of the Stepped Plane (SPLA) illustrates some examples
of Stepped Planes.
Figure 5:7.
(The pictures in the left half of Figure 5:7.: Use of the Stepped Plane (SPLA) 7 illustrate the
use of the SKETCH PLANE facility - see Plane Querying.)
If the STEP command is used then once a series of points are entered a check is made to
ensure correct SPLANE definition; if satisfactory then a message of the form:
5:8
12 Series
Figure 5:8.
Plane Errors
If you have defined a plane that is unsatisfactory then it will have to be manipulated. In
examples A and B, the plane can be corrected by either reordering or repositioning one of
the points or by adding a new point. Alternatively the plane could be made an enclosing
type. In example C the plane can only be corrected by either reordering the points or by
repositioning one or more of them. How to move points is discussed in the next Section.
5.2
Altering Planes
If you wish to change which side of a plane is retained or discarded, you can do this by
reversing the planes orientation if it is an FPLA and by changing the DIR or reordering the
WPOS points for a SPLA. The CHANGE ACTION command, for example:
CHANGE ACTION
will do this for you by altering either the DIR or NORM attributes depending on the plane
type. A PPLA cannot have its action reversed since it does not have an orientation.
Of course, changing the PMOD of the appropriate VSEC element would have the same
apparent effect as a CHANGE ACTION operation in this case, but whereas the former
operation only changes the view section representation, the latter operation changes the
Plane database element itself.
The CHANGE ACTION command is valid at any Plane element, and at WPOS element
level in the case of a Stepped Plane.
5:9
12 Series
If you require a plane point to be moved, i.e. either a POS attribute for a PPLA or an FPLA,
and the POS attribute of a WPOS element for an SPLA, the BY command can be used. For
example:
BY N500
BY @
Move by the difference between two cursor hits on the same orthogonal
VIEW
For an SPLA, the BY command will move the complete plane, i.e. the POS attribute will be
changed for all of the SPLAs member WPOS elements.
You can delete individual WPOS elements in the normal way but you can also delete
several at once using the command:
DELETE STEP number number
where the number arguments define the list position range of the points to be deleted.
5.3
Plane Querying
Once a plane has been created, it can be queried in the following ways:
Q DESC
The plane referred to by the PLRF attribute of the VSEC can be queried by:
Q PLRF DESC
- at VSEC level
It is possible to query whether a given 3D point is on the retained or discarded side by using
the following:
Q SIDE @
- at plane level
Q SIDE /plane_identifier @
- from anywhere
- from anywhere
In the latter case, only two coordinates need to be given dependent on which orthogonal
view direction you are working on, e.g. for a Plan view only the Easting and Northing are
required.
You can make any plane visible in a suitable VIEW (i.e. one that is orthogonal to the axis of
the plane) by using the following commands:
SKETCH PLANE IN /view_identifier
- at Plane level
- at VIEW level
- from anywhere
Figure 5:7.: Use of the Stepped Plane (SPLA) shows the SKETCH PLANE command in use.
Once the plane has been sketched then it will always be visible, irrespective of VIEW or
area view manipulation. Only one plane at a time can be sketched. A plane can be erased
by either of the following commands:
5:10
12 Series
ERASE PLANE
- at VIEW level
- from anywhere
Note that the sketch facility is only a drafting aid and is not part of the VIEW annotation.
Any change made to a sketched Plane will not result in a corresponding change to the
displayed sketch - another SKETCH PLANE command will be needed.
5.4
Summary of Commands
5.4.1
5.4.2
5.4.3
5.4.4
POS @
POS IDP @
NORM direction
For SPLAs . . .
DIR value
STEP @ @ @ . . . .
NEW WPOS
5:11
12 Series
5.4.5
5.4.6
BY N500
BY @
5.4.7
NEW VSEC
PLRF name
IDLN name
- An Id list name for the section to operate on. If left undefined will
default to the Id list specified by the VIEW.
The Id list can only have Added items, any Removes will be
ignored. A single Design item name can also be used.
PMOD [STANdard |
REVerse | OFF]
5.4.8
- The Mode in which the plane will be used to section the view, i.e.
which side will be retained or discarded. The default is either
STANDARD, which is as the plane is set up, or REVERSE, which
switches which side is retained or discarded. For a SPLA or FPLA,
this has the same result as using the CHANGE ACTIONS
command.
Querying . . .
Planes
Q DESC
- At Plane level
Q PLRF DESC
Q SIDE @
- At plane level
Q SIDE /plane_name @
- From anywhere
5:12
12 Series
5.4.9
5.4.10
Plane Sketching . . .
- At Plane level
- At VIEW level
- From anywhere
Plane Erasing . . .
ERASE PLANE
- At VIEW level
- From anywhere
5:13
12 Series
5:14
12 Series
6.1
ID VALV @
ID VALV VTWA @
ID NOZZ @
ID NOZZ @
For example
ON IDP @
You can restrict items picked to be either DESIGN database elements or DRAFT database
elements by using the commands:
6:1
12 Series
ID DESEL @
ID PADEL @
ID DRAEL @
Picking an element with the cursor will make the item the current element (i.e. the current
position in the database will move to that item). If you select a DESIGN element (e.g. a
Cylinder primitive in a vessel) you will move to the DESIGN database; if you select a
Drawing element (e.g. the edge of a Sheet) you will move to that element within the DRAFT
database.
6.2
for positioning annotation at a particular point on a primitive, for example the end of a
cylinder axis
To identify a p-point, move the cursor across the VIEW display with the left-hand mouse
button held down (the cursor changes its appearance); as the cursor moves across (by
default) a significant element its p-points will become visible.
Moving the cursor over a p-point (with the left-hand mouse button still depressed) will cause
the p-point identifier to be displayed in the Status Form; also, the appearance of the cursor
will change.
Selecting a p-point is achieved by releasing the mouse button with the cursor over the
required point. The identifier, direction and position of the point will appear in the DRAFT
Command Input & Output form and the p-point display markers will disappear.
Releasing the left-hand mouse button without selecting a p-point will leave the current set
of p-points visible; you will be able to zoom or pan the view, or quit out of the command line
by clicking on Cancel on the Status Form.
Whether the p-points for the last significant element identified or for the last primitive
identified are made visible is controlled by the PPOINTS command:
PPOINTS SIG
PPOINTS PRIM
Q PPOINTS
In the latter case, identifying a length of implied tube will cause only the Branches Head and
Tail p-points to be made visible. Lines generated by a section plane (see Section Planes)
are assigned to the significant element and not to the primitive sectioned; picking on one of
these lines will cause all the p-points of the significant element to be made visible - even
when in Design primitives mode. P-points that lie outside the view rectangle will not be
shown.
6:2
12 Series
6.2.1
P-point Style
P-points will be drawn for Design elements in all VIEW types. They are shown as markers.
You can change their colour, style, and scale using the SETFEEDBACK command, see
Graphical Feedback Style and Colour.
6.3
IDPE/ND @
This will return syntax to the command line in the following form:
PPLINE word OF element_identifier
The IDPE/ND command will generate text such as:
Q IDPE @
will return the ENU position of the start or end point of the
identified p-line.
This syntax is used for querying and to identify a p-line for direction (note that it may not
appear at the beginning of a command line).
The command
IDPDistance @
will return the proportional distance along the identified p-line. For example a GLAB can be
positioned by either of:
ON IDPL @
ON IDPD @
Examples of text returned by these commands could be (respectively):
6:3
12 Series
6.4
(at/below a VIEW)
where sheet_position is a position on the Sheet. This position (which must be within the
VIEW rectangle) may be specified by cursor. This command returns the back-projection of
this position at Z=0 into the 3D world coordinate system of the current or specified VIEW, for
example:
W 15500 N 10020 U 0
The specified VIEW must be axonometric without perspective.
To derive a 2D position from 3D data use:
Q SHPOSITION OF position
(at/below a VIEW)
where position may be a 3D point or p-point, explicit p-point reference, origin of a named
element, or an explicit 3D coordinate. This position or item may be specified by cursor.
This command returns the projection of the explicit or implied 3D position onto the Sheet for
the current VIEW. For example.
X 574 Y 200
As with the ENUPOS query command, the specified VIEW must be axonometric without
perspective and the specified position must lie within the VIEW rectangle.
You can query the 3D origin in World coordinates of any Design element using the
command:
Q IDORI @
Q IDORI sheet_position
(at/below a VIEW)
6.5
SNAP ON
SNAP OFF
SNAP ON 10
6:4
12 Series
When the SNAP grid is ON, all 2D cursor hits (including the BY @ command) will be
snapped onto the nearest grid point. This does not affect graphics picking or pseudo-3D
cursor hits. Snapping only applies to cursor-generated positions; positions entered explicitly
from the keyboard or via a macro are not snapped. Cursor hits will be snapped on any
picture, whether or not the visible grid (see VGRID command below) is displayed.
By default, the SNAP grid origin is positioned at the bottom left-hand corner of the Sheet,
and is drawn parallel to the X, Y axes of the Sheet. This origin may be changed by
commands such as
SNAP AT @
SNAP settings apply to all Sheets (and Symbol Libraries, Overlay Sheets etc) when SNAP
is ON. The initial setting (on entry to DRAFT) is a square grid at the Sheet origin, with
snapping switched off, i.e.
Q SNAP
The same information will also be output to file by a RECREATE DISPLAY command.
Visible Grids
VGRID ON
Visible grids are not output to plotfiles.
The VGRID command uses the current settings of the SNAP grid. A visible grid will be
output on the current Sheet using some multiple (default 1) of the current SNAP grid. An
element identifier may be specified as part of the command, for example:
VGRID /VIEW1-2 ON
This command would turn the visible grid on for the picture element (i.e. the SHEE, LALB,
BACK, OVER, ISOLB or SYLB) owning the specified element.
The visible grid is not maintained with changes in SNAP settings, so it is advisable to reset
the grid (with another VGRID ON command) if the SNAP settings are changed.
The spacing of the visible grid may be changed by commands such as
VGRID SNAP 2
This command would give a less-cluttered grid display on the drawing. The default setting
may be returned to by giving the command
VGRID SNAP
The following would cause a visible grid to be erased from the current Sheet (or a specified
Sheet), where sheet identifier identifies a picture element or an owned element:
6:5
12 Series
Module switching
Entry to MDB mode
The snap multiple of the visible grid may be queried using the command:
Q VGRID
Details of the VGRID snap multiple will also be output to file by a RECREATE DISPLAY
command.
It is also possible to query whether a specified Sheet currently has a visible grid displayed,
using.
Q VGRID sheet_identifier
6.6
HIGHLIGHT
HIGHLIGHT IN /VIEW1-1
HIG IN ID VIEW @
HIG
HIG
HIG
HIG
HIG IN _f1_v1
HIG /1501B
Elements may also be highlighted simply by passing the cursor over them in the display with
the left-hand button held down.
Note: For the permanent highlighting of 2D Drafting primitives, see the ENHANCE
command in Enhancing Drafting Primitives.
6:6
12 Series
6.7
Summary of Commands
6.7.1
Cursor Identification/Selection . . .
ID @
ID element_type @
ID VALV @
ID VALV VTWA @
ID BEND ELBOW @
ON IDP @
ON IDPL @
ID NOZZ @
- identify a Nozzle
The following can only be used as part of a command. For example, ON IDP @:
6.7.2
IDP @
IDPL @
IDPE/ND @
ID DESEL @
ID PADEL @
ID DRAEL @
Querying . . .
Q ENUPOSition OF sheet_position
Q SHPOsition OF position
You can query the 3D origin in World coordinates of any Design element using:
Q IDORI @
Q IDORI sheet_position
6.7.3
P-point Visibility . . .
PPOINTS SIG
PPOINTS PRIM
6:7
12 Series
6.7.4
6.7.5
Highlighting Elements...
HIGHLIGHT
HIG IN _f1_v1
HIG /1501B
SNAP ON
SNAP ON 10
SNAP AT @
VGRID ON
VGRID SNAP
Q SNAP
Q VGRI
6:8
12 Series
7.1
General
Plotfiles are produced by the PLOT command, which takes the following alternative forms:
PLOT uuname filename [papersize] [OVERWRITE]
PLOT /sheet_name /filename [papersize] [OVERWRITE]
PLOT SHEE FILE /filename [papersize] [OVERWRITE]
PLOT VIEW FILE /filename [papersize] [OVERWRITE]
Example:
CUTMARKS. By default the rectangular limit of the plotfile will be shown; this can be
suppressed by CUTMARKS OFF.
The BORDER value option will cause a border to be left within the specified paper size.
The image size of the item being plotted will be reduced accordingly.
The FRAME option causes a frame to be drawn around the image; FRAME can only be
used in concert with the BORDER option and marks the inside edge of the border. It
does not control the frame around the edge of the plotfile (see CUTMARKS above).
7:1
12 Series
7.2
When printer output is used, a standard print form is displayed for the user to select a
printer and set preferences.
The specific options for printing cover: automatic adjustment of the drawing size to fit
size and orientation of the paper with the REDUCETOFIT, EXPANDTOFIT and
ROTATETOFIT options; special control of print form box for automatic drawing
production in batch operation with the ONEDIALOG and NODIALOG options.
Plotting a PDF file has the option to automatically launch the reader by selecting the
VIEW option. The option NOVIEW is also available and is the default.
The output of an image file is in one of the following standard formats: jpg,
uncompressed tif, tif with LZW compression, tif-G4, png, bmp and gif. A tif image can
contain a multiple pages.
The COLOUR option defines how colour is to be handled when the drawing is output.
The default setting in the options string would be 'COLOUR STANDARD', which will
use the defined colours of the drawing unchanged.
By setting the option to 'COLOUR BW' all of the colours are the set to black if the
background is white and white if the background is white. This ensures that there is the
best contrast in the output.
7:2
12 Series
The FRAME option draws a thin frame around the drawing using the specified colour
number. An example of this in an options string is 'FRAME 3'.
The BGCOL option sets the background colour to a specified colour number. The
default background colour of all of these output types is white. An example of this in an
options string is 'BGCOL 15'.
The ISOCOLOURS and DICTCOLOURS options select alternative colour tables and
are intended to be used in tty mode when the standard colour table in not available.
The following table summarises all of the keywords and arguments that are valid in option
strings. The command option strings are always specified in upper case and / is used to
indicate the minimum abbreviation of an option name:
Option Name and
Arguments
Description
Output
Types
F/RAME value
Draws a thin frame around the drawing using the specified all
colour number.
IMAGE JPG
IMAGE TIF
IMAGE TIF_LZW
IMAGE TIF_G4
IMAGE PNG
IMAGE BMP
IMAGE GIF
COL/OUR STANDARD
COL/OUR BW
COL/OUR GRAYSCALE
COL/OUR COLOURPLUS
image
VIEW
NOVIEW
REDUCE/TOFIT
When a drawing size is larger than the selected paper size print
and/or the page orientation is different, this option reduces
and/or rotates the drawing to fit within the current paper
size, as necessary.
7:3
12 Series
Description
Output
Types
EXPAND/TOFIT
When the drawing size is smaller than the paper and/or print
the page orientation is different this option will expand
and/or rotate the drawing to fill the current paper size, as
necessary.
ROTATE/TOFIT
When the drawing does not fit on the page because their print
orientation is different this option will rotate the drawing to
fit the fit within the current paper size. No expansion or
reduction is performed
ONEDIALOG
When this option is selected for printing, the normal dialog print
is displayed before the print job and no further dialog will
be displayed for subsequent jobs. The initial print settings
including paper selection are used for subsequent prints.
This is useful for automatic drawing production.
NODIALOG
ISOCOL/OURS
Use the Isodraft colour table instead of the default table. all
These colours may be used in tty mode when the standard
colour table is not available.
DICTCOL/OURS
Use the Dictionary colour table instead of the default table. all
These colours may be used in tty mode when the standard
colour table is not available.
BGCOL value
7.3
7.3.1
7.3.2
7:4
12 Series
The TABLES section defines all required text styles and line types. Two sets of text styles
are available corresponding to horizontal and vertical text (paths Right and Down), and both
assume the existence of font files fnnnnnnnnnn (where nnnnnnnnnn denotes a ten-digit
number) that correspond to the fonts used in a DRAFT session. The line types are the
standard DRAFT predefined set; they have been given names for AutoCAD use, which are
the DRAFT names, prefixed by GT, e.g. GTSOLID, GTDOT etc.
Lines are passed as POLYLINE entities consisting of two or more points. The available
linestyles have names prefixed by GT.
All text strings are passed as TEXT entities in the appropriate font. For example, text
in Font 21 is output in style HTX21. The corresponding set of font files is defined in the
TABLES section of the DXF file. Text height and shear are supported. All text is justified
to the bottom-left corner of the text string. Note that non-zero character spacing is not
supported in DXF output.
AutoCAD font files are provided as part of the AutoDRAFT software. Instructions for
installing these can be found in the PDMS and Associated Products Installation Guide.
Layers are assigned to entities according to their colour definition within DRAFT.
These layers are named GT_n, where n is a number that corresponds to a PDMS
colour.
Colours are maintained according to Layer (i.e. BYLAYER in AutoCAD). Note that the
Layer colour for all DRAFT layers is white.
The ENTITIES section then follows, and is normally closed by the standard AutoCAD EOF.
7.3.3
If no header type is specified, the brief AVEVA header is assumed. If the ACAD option is
used, then the DXF file produced will contain a header, which is defined in file acadxf.hdr in
the PDMS executable directory (as defined by global variable PDMSEXE).
File acadxf.hdr must contain, as a minimum, the following:
If the ZCOORD option is used, the DXF file produced will contain Z-coordinates of value
0.000 (i.e. code 30 entries) in the $EXTMIN and $EXTMAX parameters in the header
section, and in polyline vertices and TEXT entities.
7:5
12 Series
7.3.4
7.3.5
Scaling
The output written to the DXF file can be scaled using the SCALEUP command option. If
required, the scaling value should be specified after the Z coordinate requirements. For
example:
7.4
7.4.1
Configuration Datasets
It is possible to control the format of DXF and DWG output using configuration datasets.
The configuration dataset controls how the database information is to be mapped into DXF
format. It does the following:
Controls how DRAFT graphics are to be grouped as AutoCAD Block and Group
definitions.
The configurable DXF and DWG facility uses loadable image (LI) applications, usable at
Sheet level. The export application can be executed using the LIEXEC command (which
also loads the application if it has not already been loaded).
Configurable DXF Output
The following example command uses the configuration data set MyConfigData to control
the export of DXF information:
7:6
12 Series
full_dxf.mac
Defines a sample set of configuration settings to produce fully blocked, grouped and layered DXF files closely mapped to the
DRAFT Sheet exported.
Note: Blocking commands for Design graphics in this file are only
intended as an example, and may require modification to
suit your own requirements.
Layers can be created with all the properties and exported. New
switches can be added to create new layers for Design elements
and set their properties. These can be exported with all applied
properties to DXF and DWG format.
graphics_dxf.mac
The configuration options may be overridden by LIEXEC command line options; in particular
the Outputfilename switch would normally be overridden by an LIEXEC option. For
example:
R18
R21
for versions 2007, 2008, 2009 (R22 and R23 may also be used) for
these versions
7:7
12 Series
R24
DWGOUT
for a "default" DWG version, currently 2006, but this may change
for future releases
Configuration Datasets
A DRAFT Configuration Dataset is made up of a series of switches and Blocking rules. The
{configuration options} will contain the BLOCK and SWITCH syntax that control the content
of the DXF file produced. See Switches and BLOCK Rules to Control DXF and DWG Export
for a full list of the switches and their permissible and default values.
Example:
SWITCH GroupGLAB ON
Group GLABs into AutoCAD groups
DLICON
7:8
12 Series
7.4.2
Switch Name
Value (default)
Description
PrimitiveThickness
[ ON ]
OFF
PlineWidthFactor
ViewNumberPrefix
LayerZone
LayerSite
LayerBack
LayerOlay
LayerNote
[ OFF ]
ON
[ OFF ]
ON
[ OFF ]
ON
[ OFF ]
ON
[ OFF ]
ON
[ OFF ]
7:9
12 Series
Switch Name
Value (default)
Description
LayerLaye
ON
[ OFF ]
[ ON ]
OFF
UseLayerRules
LayerDEFAA
Layer
FontMapping
[ ON ]
OFF
[ ON ]
LinetypeMapping
ColourMapping
OFF
[ ON ]
OFF
7:10
12 Series
Switch Name
Value (default)
Description
IncludeZCoordinates
ON
[ OFF ]
ON
GraphicsOnlyDXF
EntityAcDbMarkers
[ OFF ]
ON
[ OFF ]
7:11
12 Series
Switch Name
Value (default)
Description
NestedBlocks
ON
[ OFF ]
ON
[ OFF ]
[ ON ]
OFF
ON
[ OFF ]
[ ON ]
OFF
ON
[ OFF ]
ON
[ OFF ]
ON
[ OFF ]
ON
[ OFF ]
ON
[ OFF ]
BlockBack
BlockOlay
BlockSymb
BlockFill
BlockGraphicFile
GroupDims
GroupNote
GroupVnot
GroupFrame
7:12
12 Series
Switch Name
Value (default)
Description
GroupGlab
ON
[ OFF ]
ON
[ OFF ]
ON
[ OFF ]
/search/path/
[ OFF ]
ON
OFF
GroupSlab
GroupBlocks
FontFilePath
UseShiftJISFonts
IncludeDXFHeaderEn ON
tities
[ OFF ]
HeaderFileName
[%PDMSEXE%/draft_dxf_li.dxf]
Specifies the DXF header file name, which
will be read into DRAFT and used as a
backbone template for generating the DXF
information. If a header file name is
specified, it must be a valid AutoCAD release
13 DXF file, based on the default
draft_dxf_li.dxf'
OutputFileName
[output.dxf]
7:13
12 Series
Switch Name
Value (default)
Description
IgnoreBlockRules
[ ON ]
OFF
Positive Real
No.
(default 1.0)
[ 1.0 ]
ScaleFactor
Note: The default values specified in this table are those set up by the configuration macro
default_dxf.mac, as supplied with the product. The supplied default values will
always be obtained when using the System Defaults for DXF Output option on the
Configurable DXF Output form in the standard graphical user interface.
7.4.3
A line thickness, in mm or inches. (This will be rounded to the nearest standard lineweight.)
A colour chosen from the following list: RED, YELLOW, GREEN, CYAN, BLUE,
MAGENTA, WHITE, GREY, BRIGHTRED, PINK, ORANGE, TURQUOISE, INDIGO,
MAUVE, VIOLET, BROWN. (Note that geometry in the file is not generally set to
colour-by-layer, so this colour may not be displayed)
A line pattern chosen from the following list: CONTINUOUS, DASHED, DOTTED,
CHAINED, LDASHED, DDASHED, DDOTTED, FDOTTED, DCHAINED, TCHAINED.
7:14
12 Series
Standard selection syntax is used to define Layer Rules. These specify how design
elements are to be organised onto AutoCAD Layers.
Example:
LEVEL
LEVEL
LEVEL
LEVEL
Rules are applied in order; therefore, if a rule has already been applied for a given element,
a later rule will not affect it.
Design elements which can have level rules include: SITE, ZONE, STRU, SUBS, FRMW,
SBFR, EQUI, SUBE, PIPE, BRAN, HVAC, REST, GRDM, PTRA, BOUN, DRAWI (when
owned by a SITE or ZONE) and all Piping Components.
7.4.4
Limitations
The following limitations apply:
DRAFT's intelligent blanking primitives are not exported to the DXF or DWG file as
there are no equivalent AutoCAD primitives to which to map them.
Many user-defined line styles (see Line Styles) created by adding Glyphs and pictures
are not supported. These are translated to equivalent AutoCAD linetypes. Those that
are not (such as those defined with a PATNAM rather than a PATDEF) assigned to a
fixed (dashed) linetype definition in the DXF or DWG file using the DRAFT line pattern
name as the AutoCAD linetype name. This definition can be redefined in AutoCAD to
provide the linestyle required.
User-defined glyphs and line pictures (see Line Styles) are ignored.
7.5
7.5.1
Configuration Datasets
DGN files (for use in MicroStation) may also be created from DRAFT Sheets. DGN is a
binary format, and has two main variants - the older version 7 format (as used by
MicroStation/J)and the current version 8 format (as used by MicroStation V8 and later
versions). Many of the configuration options were designed for the version 7 format, and
may not apply in quite the same way for a version 8 file. In future releases version 7 specific
behaviour may be removed or deprecated.
It is possible to control the format of DGN output using configuration datasets. The
configuration dataset controls how the database information is to be mapped into DGN
format. It does the following:
7:15
12 Series
The configurable DGN facility uses loadable image (LI) applications, usable at Sheet level.
The DGN export application can be executed using the LIEXEC command (which also
loads the application if it has not already been loaded).
The following example command uses the configuration dataset MyConfigData to control
the export of DGN information:
LIEXEC /Draft_DGN_LI
Here DGNOUT is an application feature, and is used to indicate the version of Microstation
for the exported file. This keyword may also take the values DGN7, DGN8.
This will create a DGN file with a name and format defined in the specified dataset for the
current Sheet element. Before giving the above command, the configuration dataset must
have been defined in DRAFT. This may be done either by typing in the configuration data at
the command line; by building up the required mappings using the DRAFT applicationware;
or by reading in a predefined macro file.
Other commands related to this facility are:
LILIST
DLICON name
A DRAFT Configuration Dataset is made up of a series of Switches, Group rules and Level
rules. The configuration_options will contain the GROUP, LEVEL and SWITCH syntax that
controls the content of the DGN file produced.
Example:
7:16
12 Series
dra-dgn-pdms.pmldat
dra-dgn-imperial.pmldat
7:17
12 Series
dra-dgn-nnnn.pmldat
dra-dgn-dddd.pmldat
dra-dgn-basicTT.pmldat
dra-dgn-pdmsTT.pmldat
Note: These configuration files may be converted to command-line macro files for batch
creation of DGN files, using the Plant applicationware as follows:
7.5.2
If the right-hand list has a single element, all values in the left-hand list are mapped to
the same value.
If the right-hand list has the same number of elements as the left-hand list, each
element in the left list is mapped to the corresponding element in the right list.
If the right-hand list contains integers with an 'R' option, each element of the right-hand
list is used in turn, the elements being repeated as necessary.
If the right-hand list contains integers with a 'D' option, each element of the right-hand
list is used in turn once only, then the default value is used for all further mappings as
necessary.
7:18
12 Series
Example:
'CHAINED:pdmsChained, DASHED:pdmsDashed, DDOTTED: pdmsDdotted'
'1-11:15,12-20:33-41'
'1-20:26-30R'
'20-29:1-3D6'
Quoted Strings
Strings within mappings may be quoted, if necessary, with ' or | characters. For example,
some MicroStation custom line-styles have names that include a comma or colon, such as
{dash, medium}. In order to map to this MicroStation custom line-style, you must use an
extra set of quotes to prevent the name being treated simply as {dash. You need outer
quotes to tell DRAFT where the option string ends, and inner ones to tell Draft_DGN_LI
where each line-style name ends, thus:
SWITCH
SWITCH
SWITCH
SWITCH
MapLineStyle
MapLineStyleA
MapLineStyleB
MapLineStyleC
|CHAINED:pdmsChained|
|DDOTTED:pdmsDdotted|
|DASHED:'{ dash, medium }'|
|LDASHED:'{ dash, long }'|
Note: Continuation switches can be used in DLICON configuration syntax. They cannot be
used in the LIEXEC command syntax.
7.5.3
7:19
12 Series
Sub-Units
Positional Units
These keywords are not case-sensitive, but the values of MASTNAME and SUBNAME are
case-sensitive. The most common scenarios will be:
The working units are set up in the seed file. In this case, the Units switch just contains
the size of a master unit in mm. For example, with an imperial seed file, with master
units inches, the Units switch should be:
7:20
12 Series
The working units in the configuration override those in the seed file: all Units options
are needed. (A minor exception is that if the MASTNAME setting is recognised as a
common value, MASTMM may be omitted.) For example, to set both the master and
sub-unit names to millimetres, with one sub-unit per master unit, and 1270 positional
units per sub-unit, the Units switch should be:
7:21
12 Series
ExcludeFill
If this switch is set to On, (the default is Off), no hatching (including solid fill) in the DRAFT
drawing is transferred to the DGN file. This may be useful for good performance in
MicroStation, since hatching is transferred as a set of lines.
ExcludeSolidFill
If this switch is set to On, (the default is Off), all solid fill is ignored and not transferred to the
DGN file. However, other Hatching is still transferred.
ExcludeArrowFill
If this switch is set to On, (the default is Off), any solid fill for terminators on dimension-lines
and label leader-lines is omitted from the transfer to the DGN file. Other solid fill and
hatching is transferred.
Note: More than one of these switches to Exclude Fill may apply to the same entity. If any
of these switches is true, then the entity will be excluded. For example, either
ExcludeSolidFill or ExcludeArrowFill could be used to exclude the fill for dimensionline arrowheads. However, ExcludeArrowFill is more specific.
7.5.4
Any ScaleFactor (see ScaleFactor) is applied to custom line-styles used in the DGN
file.
The following example maps DRAFTs named line-styles to their nearest equivalents in
MicroStations numbered styles. This is the default:
7:22
12 Series
SWITCH MapLineStyle'CHAINED:pdmsChained,DASHED:pdmsDashed
,DDOTTED:pdmsDdotted,DOTTED:pdmsDotted,LDASHED:pdmsDashed
,SOLID:0,TCHAINED:pdmsTChained'
Custom line-style names can include spaces and punctuation; for example, the default
MicroStation/J installation includes styles { -E- } and { Cable / Tele }. See Quoted Strings for
details of when you must quote the style-names. As this mapping can get long, (the
preceding example is a single line mapping), you may need to use the continuation facilities
described in Continuing Long Mappings.
MapLineStyleByPen
More complex line-styles can be set up by the combination of line-pattern, line picture, line
thickness and glyph. To map these combinations onto MicroStation line-styles, you must
map them by Pen Number. (Note that this is the pen number as stored in the database,
which is not the same as the pen number in the DRAFT Administrator User Defined Pen
Settings form.)
For example, you might have DRAFT pen numbers 217 and 222 set up as:
7:23
12 Series
MarkerSize
This option sets the size of a DRAFT marker in millimetres (at scale 1). The size of a marker
in the DGN file will be the product of this size, the scale of the relevant DRAFT pen, and the
overall ScaleFactor switch setting (see ScaleFactor). The default is 1.0.
7.5.5
DRAFT supports TrueType fonts and some configuration is required to match the text
metrics between the AVEVA product and a version of Microstation. This involves the
use of specific configuration parameters in AVEVA Plant and a matching fonts resource
file. The details are project specific. The pdmsSamFontTT.rsc file is provided with a
corresponding settings in TrueType configuration datasets. The TrueType fonts are
installed in the standard way required by the operating system.
The DRAFT fonts supplied with the AVEVA product must be set up in MicroStation
using a fonts resource file. The contents of this file are project-specific. A
pdmsSamFont.rsc file is provided, based on the fonts used in the SAM project supplied
with AVEVA Plant.
MapFont
This option maps from DRAFT's font numbers (11-16, 21-26, 31-36, 41-46) and the special
SYMBOL to MicroStation font numbers. DRAFT font numbers 1 and 10 are treated as
equivalent to 11, 2 and 20 as equivalent to 21, 3 and 30 as equivalent to 31, 4 and 40 as
equivalent to 41. For example:
Width Factor
Height Factor
Offset Up
Offset Right
7:24
12 Series
Underline separation
Examples
Arial Unicode MS
Trebuchet MS
Courier New
17
Comic Sans MS
18
Tahoma
19
Georgia
27
Swiss 721 BT
62
Note: Using the SYMBOL font will only produce good results if it is mapped to a font
containing suitable symbol-characters in the correct character positions. The
SYMBOL font is included in the MicroStation resource file pdmsSamFont.rsc
supplied with AVEVA Plant. When using the supplied resource file, the following font
mapping should be used:
7:25
12 Series
7.5.6
Level-Related Options
MicroStation/J supports a maximum of 63 levels (numbered 1-63). Each DGN graphical
element is on one and only one level. MicroStation also offers names for levels, but
Draft_DGN_LI always refers to levels by number. The additional levels possible in DGN8
are not yet supported.
LevelDefault
This switch sets the default level: i.e. the level that will be used if no other switches or rules
apply. The default value is 1.
Example:
7:26
12 Series
Level Rules
Standard selection syntax is used to define Level Rules. These specify how design
elements are to be organised onto DGN Levels.
Example:
ALL BRAN
ALL EQUI
( /C1101
ALL LAYE
ALL LAYE
ALL LAYE
ALL LAYE
Rules are applied in order; therefore, if a rule has already been applied for a given element,
a later rule will not affect it. Using the order specified in the above examples, a LAYE with
PURP ADCA will be placed on level 21 not on level 24. However a LAYE with PURP
XXXX would still be placed on level 24 even if there was a later rule which apparently
placed it elsewhere.
Design elements which can have level rules include: SITE, ZONE, STRU, SUBS, FRMW,
SBFR, EQUI, SUBE, PIPE, BRAN, HVAC, REST, GRDM, PTRA, BOUN, DRAWI (when
owned by a SITE or ZONE) and all Piping Components.
DRAFT elements which can have level rules include: LAYE, NOTE, OLAY, VNOT, GLAB,
SLAB, ADIM, LDIM, PDIM and RDIM.
These rules can operate with a level pool. This consists of one or more levels, which are
allocated as required. For example, a DRAFT Sheet may have several overlays, and you
may want each overlay on a separate DGN Level within the range 50 to 59 (the levels
assigned for overlays in your drawing standards).
A level pool consists of one or more integers or integer ranges, separated by commas, with
the optional characters R, meaning repeat the pool if necessary, and 'D integer' to specify a
default value when the pool is exhausted (see General Mappings).
For example, to use levels 3, 5, 6, and 7 for the first four sites, and then put any other sites
on level 9, specify the switch setting:
7:27
12 Series
7.5.7
7:28
12 Series
7.5.8
%PDMSUSER%\Draft_DGN_LI_log.txt.
Example:
7.5.9
7.5.10
Option name
Value [default]
Description
OutPutFileName
[output.dgn]
SeedFileName
[internal default
seed file]
Units
ScaleFactor
[1.0]
ShiftX
[0.0]
7:29
12 Series
Option name
Value [default]
Description
ShiftY
[0.0]
ExcludeBack
On
[Off]
On
[Off]
On
[Off]
On
[Off]
On
[Off]
On
[Off]
MapLineWeights
[1-11:0-10]
MapLineStyle
[Solid:0,
Dashed:2,
Dotted:1,
Chained:4,
LDashed:3
DDotted:6]
ExcludeOlay
ExcludeSheetFrame
ExcludeFill
ExcludeSolidFill
ExcludeArrowFill
MapLineStyleByPen
MapColour
Maps
DRAFT
colour
numbers
MicroStation colour numbers.
MarkerSize
[1.0]
to
7:30
12 Series
Option name
Value [default]
Description
MapFont
[11-46:105,
SYMBOL:105]
FontSlopes
[On]
Off
[1]
LevelDefault
slopes
to
LevelPen
LevelBack
Level Rules
GroupSymb
GroupFill
GroupFrame
On
[Off]
On
[Off]
On
[Off]
Group Rules
LogFile
LogFileName
[Off]
7:31
12 Series
7.5.11
Limitations
The following limitations apply:
7.6
DRAFT's intelligent blanking primitives are not exported to the DGN file.
User-defined glyphs and line pictures are ignored. However, it is possible to specify a
MicroStation custom line-style for a given DRAFT pen number.
Multi-byte fonts are not supported with MicroStation, for DGN7 format. For DGN8
format they are supported provided that the PC running Draft has appropriate
Language and Regional settings.
7.6.1
7.6.2
7:32
12 Series
Use MicroStation standard fonts similar to the AVEVA fonts, and accept some
differences in text output.
If you use DRAFTs alternative character set for characters such as or you will
need to install AVEVAs symbol font.
It is not possible to install a 16 bit font (.SHX) file into Microstation/J or earlier.
The set of AVEVA fonts required in MicroStation is project dependent. The supplied font
resource file pdmsSamFont.rsc uses the AVEVA fonts associated with the SAM project.
Individual projects may have different fonts in use, so will require a different font resource
file. See Creating a New Font Resource Library for instructions on how to create such
resource files.
Font resource files should be installed alongside the corresponding MicroStation font
resource files, typically in
... \bentley\workspace\system\symb
pdmsSamFont.rsc uses particular MicroStation font numbers (201 to 207 for text fonts and
255 for the symbol font). These are mapped to DRAFT fonts using the MapFont switch in
DRAFT. It is possible that these font numbers may clash with fonts in other font resource
files in use. If this happens, see section Changing MicroStation Font Numbers for
instructions on how to modify MicroStation font numbers.
When you install additional fonts into MicroStation, DRAFT needs additional information on
the font geometry to export the drawing. This is supplied as a set of font geometry files,
fontNNN.dgn (where NNN is a MicroStation font number referred to in the font resources
file).
These fontNNN.dgn files must be in either the current directory, or a directory accessed by
the environment variable OPENDGN_FONT_DIR. This variable OPENDGN_FONT_DIR
should be set to %PDMSEXE%\dgndata or wherever the font geometry files have been
installed.
Font geometry files are supplied for the fonts used in the SAM project. These correspond to
pdmsSamFont.rsc and are supplied in the directory PDMSEXE%\dgndata. Select the
Required .rsc Library contains instructions as to how to create further fontNNN.dgn files for
other fonts.
Mapping the Installed Fonts discusses how AVEVA font numbers are mapped onto font file
names. All AVEVA fonts are supplied in the %PDMSEXE%\autodraftfonts directory, in
AutoCAD format as .shx files.
7.6.3
... \bentley\workspace\system\symb
MicroStation refers to fonts by a number not by the name. AVEVA fonts are supplied as
AutoCAD .shx files as part of AutoDRAFT. These are supplied in the directory
%PDMSEXE%\autodraftfonts (or another location).
7:33
12 Series
Once fonts have been installed, they may be checked using the element/text menu. The
newly installed fonts should be visible together with the font numbers assigned by
MicroStation to the new fonts. If necessary, font numbers may be modified (see Changing
MicroStation Font Numbers.).
The font installation should follow the step-by-step procedure:
Creating a New Font Resource Library
(This step may be skipped if using an existing resource library)
Menu:
Utilities>Install Fonts
Button:
Button:
OK
Menu:
Button:
Button:
Add
Button:
Done
Button:
Button:
OK
Copy
Button:
Done
7:34
12 Series
Menu:
Element>Text
Menu:
Utilities>Install Fonts
Button:
Button:
OK
Font geometry files fontNNN.dgn must then be created to match the font
numbers in the resource file.
Creating a New Font Geometry File
Font geometry files (or magic font-files) are used by DRAFT to export font geometry and
alignment correctly to MicroStation. One of these files is required for each font used. The
MicroStation font number NNN is included in the name of these files. These files contain a
set of instructions and various other text data. These files should not be modified other than
as described below, since the data in these files is required for DRAFT DGN output to work
correctly.
In order to create a font geometry file for a new font, open an existing font geometry file (a
set of these is supplied in %PDMSEXE%\dgndata) and follow the instructions displayed
there. This involves using the MicroStation EDG utility to change the font used. (The EDG
utility is installed alongside MicroStation, for example in \Bentley\Program\Edg\edg.exe.)
The instructions in the fontNNN.dgn files are repeated here.
To create an external font do the following:
The new name must start with 'font' appended with the font number. (e.g. font186.dgn
for MicroStation font number 186)
Open this file in EDG first and type 'modify font=<n> whole' where <n> is the new font
number.
Open this file in MicroStation and type 'mdl load fixrange' (Use Keyin option).
Compress and close the design file. (Use Compress on File menu)
7:35
12 Series
7.6.4
MAPFONT 11-16:201p
For further details, see Configurable DGN Output.
7.6.5
AVEVA
AVEVA font file names follow a naming convention. This is described fully in AVEVAs fontbuilding utilities, but is briefly summarised here.
AVEVA font families are defined by their IR (International Registration) number and Style
number in the system database. Font file names are of the form marrrtswuu, where m=0; a
is the alphabet; rrr is the encoding; ts is the type and sub-type; w is the weight; and uu is a
serial number. AVEVA fonts are exported to AutoCAD as either filled (prefix f), or open
(prefix of). All font-files have an 8-character equivalent short name:
Name
IR Number
Encoding
(marrr)
Short code
Latin-1
01001
L1
Latin-2
01002
L2
UK
01004
LB
Latin-Cyrillic
09998
CL
US
Greek
02018
GG
Cyrillic
03537
CR
SYMBOL
09999
OP
Name
PDMS Style
number
Font type
(tswuu)
Line
11901
Block
Outline 11203
Filled 11203
7:36
12 Series
Name
PDMS Style
number
Font type
(tswuu)
Serif
21191
21291
Italic
22191
22291
Script
31191
31291
Typewriter
21902
Uniform width
16901
Generally, PDMS uses the 8-bit Latin fonts (08901) instead of US fonts (01006), since these
include US characters. Thus IR number 6 Style number 1 is font of0890111901 (short name
O8111901); IR number 4 Style number 3 is of 0100421191 (short name OLB21191), bold
version of 0100421291 (OLB21291).
The fonts available in DRAFT are organised into four font families. Each font family uses up
to two font files to set up a range of six font numbers. For example, font family 3 contains
two font files to set up fonts 31-33 (normal, forward and back-slant) and the equivalent bold
font 34-36.
In addition, DRAFT uses a Symbol font for special characters (e.g. ~D gives the degrees
symbol). The AVEVA SYMBOL font is of0999911901.shx (shortname OOP11901). The
equivalent filled font is f0999911901.shx (shortname FOP11901).
To determine the font families used in a project, the following ADMIN command should be
used:
Q FONTFamily
In typical AVEVA projects, font family 1 is a line font; font family 2 is a block font; font family
3 is a serif font and font family 4 an italic or typewriter font. Different projects will use
different fonts. The following font files are used in the SAM project and are set up in
pdmsSamFont.rsc:
Shortname
Font numbers MicroStation
in Project
Font Number
SAM
(FontNNN.dgn)
Longname
Description
11-16
201
O8111901.shx
of0890111901.shx
US Line
21-23
202
OLB11203.shx
of0100411203.shx
UK Block
(Outline)
24-26
203
FLB11203.shx
f0100411203.shx
UK Block
(Filled)
31-33
204
OLB21191.shx
of0100421191.shx
UK Serif
34-36
205
OLB21291.shx of0100421291.shx
UK Serif
(Bold)
41-43
206
OLB22191.shx of0100422191.shx
UK Hershey
Complex Italic
7:37
12 Series
7.6.6
Longname
Description
44-46
207
OLB22291.shx of0100422291.shx
UK Hershey
Triplex italic
SYMBOL
255
FOP11901.shx f0999911901.shx
PDMS
Symbols
Colours
We supply a MicroStation colour table pdms_col.tbl, which contains colour definitions
matching DRAFTs default settings for Colours 1 to 16, and also for the other named DRAFT
colours. This may be installed in the MicroStation data directory alongside the Bentleysupplied colour tables, typically at:
... \bentley\workspace\system\tables
You may, if you wish, attach this colour table to a seed file or design file and set a suitable
colour mapping, if you wish to match DRAFT colours as closely as possible.
7.6.7
Line Styles
AVEVA supplies a line style resource file containing definitions of MicroStation custom line
styles matching the proportions of DRAFTs named line patterns. This may be installed in
the MicroStation font directory alongside Bentley-supplied font resource files, typically at:
... \bentley\workspace\system\symb
7:38
12 Series
those for linear (line) primitives (15 linestyle and 15 colour attributes)
those for area primitives (one fillstyle and one colour attribute)
those for marker primitives (one markerstyle and one colour attribute)
Generally, there is a style attribute for every colour attribute, except that there are no style
attributes for text primitives only colour attributes.
The term style is used to describe the overall appearance of a line in terms of its thickness
and repeating pattern, or to describe a hatching (fill) pattern, or to describe the size and
appearance of markers. The full list of colour and style attributes is given below:
Attribute type
Style attribute
Colour attribute
Leader-line
LLSTYLE
LLCOLOUR
Label-frame
LFSTYLE
LFCOLOUR
Dimension-line
DLSTYLE
DLCOLOUR
Projection-line
PLSTYLE
PLCOLOUR
Cross-hair
CHSTYLE
CHCOLOUR
Note line
NLSTYLE
NLCOLOUR
Table-row
ROWSTYLE
ROWCOLOUR
Table-column
COLSTYLE
COLCOLOUR
Front-face
FFSTYLE
FFCOLOUR
Back-face
BFSTYLE
BFCOLOUR
Centre-line
CLSTYLE
CLCOLOUR
Obscured-line
OBSTYLE
OBCOLOUR
P-line
PLNSTYLE
PLNCOLOUR
Member-line
MLNSTYLE
MLNCOLOUR
Line
8:1
12 Series
Attribute type
Style attribute
Colour attribute
Outline
OLSTYLE
OLCOLOUR
General text
TXCOLOUR
Dimension-line text
DTCOLOUR
Projection-line text
PTCOLOUR
FSTYLE
FCOLOUR
MSTYLE
MCOLOUR
Text
Fill
Fill (hatch pattern)
Marker
Marker symbol
The colour attributes may be assigned values by colour table index number or by colour
name. See Colours for a listing of the colours available. In some circumstances colour
attributes may be set to the special values: DEFAULT, TEMPLATE, UNCHANGED. See the
relevant sections of this User Guide for details of where these values are allowed.
The linestyle attributes may be assigned values that describe system-defined or userdefined line styles. See System-Defined Line Styles and User-Defined Line Styles for further
details of these. In some circumstances linestyle attributes may be set to the special values:
OFF, DEFAULT, TEMPLATE, UNCHANGED. See the relevant sections of this User Guide
for details of where these values are allowed.
The fillstyle attribute may be assigned values that describe system-defined or user-defined
fill styles. See System-Defined Fill Styles and User-Defined Fill Styles for further details of
these. In some circumstances fillstyle attributes may be set to the special values: OFF,
DEFAULT, UNCHANGED. See the relevant sections of this User Guide for details of where
these values are allowed.
The markerstyle attribute may be assigned values that describe system-defined marker
styles. See Marker Styles for further details of these. In some circumstances markerstyle
attributes may be set to the special values: OFF, DEFAULT. See the relevant sections of this
User Guide for details of where these values are allowed.
User-defined line and fill styles are defined in the PADD database within a hierarchy headed
by a STYLWL element (see DRAFT Database Hierarchy). STYLWL owns Linestyle and
Fillstyle Tables (LSTYTB, FSTYTB), beneath which the definitions of user-defined
Linestyles and Fillstyles are stored.
STYLWL, LSTYTB and FSTYTB are classified as primary elements and can therefore be
claimed.
The creation and maintenance of STYLWL hierarchies is the responsibility of the DRAFT
Administrator.
8.1
Colours
DRAFT allows you to draw in up to 272 colours, numbered 1 to 272. By default all 272
colour numbers have colour definitions assigned to them:
8:2
12 Series
Grey
Colour 9
Brown
Colour 2
Red
Colour 10
White
Colour 3
Orange
Colour 11
Pink
Colour 4
Yellow
Colour 12
Mauve
Colour 5
Green
Colour 13
Turquoise
Colour 6
Cyan
Colour 14
Indigo
Colour 7
Blue
Colour 15
Black
Colour 8
Violet
Colour 16
Magenta
Colour numbers 17 to 272 are mapped to the colours in the standard AutoCAD Colour
Index (ACI).
The system maintains a dictionary of 61 colour names that may be used in place of colour
numbers when specifying a colour or setting the value of a colour attribute. These names
(which include the 16 given above) and their ACI (AutoCAD Colour Index) and RGB values
are as follows:
COLOUR
ACI
RED
GREEN
BLUE
Black
0.000
0.000
0.000
White
1.000
1.000
1.000
Whitesmoke
1.000
1.000
1.000
Ivory
51
1.000
1.000
0.667
Grey
253
0.510
0.510
0.510
Lightgrey
254
0.745
0.745
0.745
Darkgrey
251
0.314
0.314
0.314
Darkslate
129
0.208
0.310
0.286
Red
12
0.741
0.000
0.000
Brightred
1.000
0.000
0.000
Coralred
22
0.741
0.180
0.000
Tomato
20
1.000
0.247
0.000
Plum
215
0.506
0.337
0.506
Deeppink
230
1.000
0.000
0.498
Pink
243
0.741
0.494
0.553
Salmon
21
1.000
0.749
0.667
Orange
40
1.000
0.749
0.000
Brightorange
40
1.000
0.749
0.000
8:3
12 Series
COLOUR
ACI
RED
GREEN
BLUE
Orangered
30
1.000
0.498
0.000
Maroon
226
0.408
0.000
0.306
Yellow
50
1.000
1.000
0.000
Gold
40
1.000
0.749
0.000
Lightyellow
51
1.000
1.000
0.667
Lightgold
41
1.000
0.918
0.667
Yellowgreen
62
0.553
0.741
0.000
Springgreen
110
0.000
1.000
0.498
Green
92
0.000
0.741
0.000
Forestgreen
84
0.122
0.506
0.000
Darkgreen
108
0.000
0.310
0.075
Cyan
0.000
1.000
1.000
Turquoise
132
0.000
0.741
0.741
Aquamarine
120
0.000
1.000
0.749
Blue
0.000
0.000
1.000
Royalblue
160
0.000
0.247
1.000
Navyblue
176
0.000
0.000
0.408
Powderblue
141
0.667
0.918
1.000
Midnight
168
0.000
0.075
0.310
Steelblue
142
0.000
0.553
0.741
Indigo
196
0.204
0.000
0.408
Mauve
204
0.376
0.000
0.506
Violet
221
1.000
0.667
0.918
Magenta
1.000
0.000
1.000
Beige
43
0.741
0.678
0.494
Wheat
31
1.000
0.831
0.667
Tan
32
0.741
0.369
0.000
Sandybrown
42
0.741
0.553
0.000
Brown
36
0.408
0.204
0.000
Khaki
55
0.506
0.506
0.337
Chocolate
38
0.310
0.153
0.000
Darkbrown
48
0.310
0.231
0.000
Blueviolet
190
0.498
0.000
1.000
8:4
12 Series
COLOUR
ACI
RED
GREEN
BLUE
Firebrick
30
1.000
0.498
0.000
Darkorchid
202
0.553
0.000
0.741
Dimgrey
252
0.412
0.412
0.412
Coral
22
0.741
0.180
0.000
Indianred
13
0.741
0.494
0.494
Lightblue
151
0.667
0.831
1.000
Limegreen
80
0.247
1.000
0.000
Mediumaquamarine
121
0.667
1.000
0.918
Sienna
34
0.506
0.251
0.000
Stateblue
173
0.495
0.494
0.741
Note: The actual RGB definitions of these colours have generally changed so as to match
entries in the ACI. This has led to duplication: thus White and Whitesmoke are both
mapped to ACI 7, and Orange, Brightorange and Gold are mapped to ACI 40. The
redundant colour names have been maintained for compatibility with previous
versions of AVEVA Software.
It is possible to change the definitions of colours 1-16 using the COLOUR command. The
syntax can take three forms, either specifying a predefined name from the system colour
dictionary, or a percentage mixture, or an RGB definition. Typical examples would be:
COLour 3 STEELBLUE
COLour 12 MIX RED 80 GREen 50 BLUe 50
COLour 14 RGB 0, 141, 188
Where a percentage mixture is specified all three values must be in the range 0-100. Where
an RGB definition is given all three values must be in the range 0-255.
Colour definitions can be queried thus:
Q COLour 12
Q COLour RGB 55
Colour attributes can be assigned values by number or name, thus:
LLCOLOUR 54
TXCOLOUR NAVYBLUE
When a colour attribute is queried the name (e.g. orange) will be returned if available,
otherwise the colour number will be returned. If a number is specifically required (regardless
of whether a name is available, a special colour-number pseudo-attribute should be used.
The names of these are derived from the normal colour attributes, e.g. LLCONU/MBER,
TXCONU/MBER, FCONUM/BER etc.
It is possible to set all colour attributes on an element to the same value by the
ALLCOLOURS command. As some DRAFT elements have many such attributes this is a
convenient way of changing them to the same colour quickly. To set all the text colours and
8:5
12 Series
all the line colours separately the TEXTCOLOURS and LINECOLOURS commands should
be used, thus, for example:
ALLCOLOURS
RED
TEXTCOLOURS
LINECOLOURS
GREEN
The list of colour attributes are listed. The special colour attribute values of DEFAULT,
TEMPLATE, and UNCHANGED can also be specified but these are only valid in particular
circumstances. See the relevant sections of this User Guide for details of where these
values are allowed.
8.2
Line Styles
A pre-defined set of line styles is provided; it is also possible for you to define your own. A
line style is defined by the thickness of the line, its repeating pattern, and the optional
placement of glyphs and/or text strings along it.
8.2.1
DDASHED
DASHED
DDOTTED
DOTTED
FDOTTED
CHAINED
DCHAINED
LDASHED
TCHAINED
Figure 8:1.
THIN
MEDIUM
THICK
The width definitions for THIN, MEDIUM and THICK are held in the system database for the
project. They can be modified by an administrator in the ADMIN module.
8:6
12 Series
FFSTYLE SOLID
OBSTYLE DOTTEDMedium
PLSTYLE DDOTTEDMedium
CLSTYLE CHAINEDThick
BFSTYLE DASHEDThick
Note that for minimum thickness lines the qualifier THIN is omitted.
For historical reasons an alternative set of line patterns is provided (see Figure 8:2.:
Alternative Pre-defined Line Patterns).
Figure 8:2.
These alternative line-patterns can be combined with widths named WIDE and XWIDE, thus
for example:
NLSTYLE DASHPattern
FFSTYLE SOLIDXWIDE
Note that for consistency WIDE and XWIDE can be also used with the basic pattern SOLID.
8.2.2
8:7
12 Series
the relative lengths of the sequence of dashes and gaps that make up the pattern. These
two ways are defined by the attributes PATNAM and PATDEF; these are mutually exclusive
setting one will unset the other.
PATNAMe
PATDEFinition
A series of integers (max 20) that define the relative lengths of the
dashes and gaps. A dash is represented by a positive value and a gap
by a negative value. Dashes and gaps must alternate and we
recommend that the pattern sequence starts with a dash.
LWIDTH
The width of the line (in mm or inches). Value 0 is allowed and means
the minimum-allowed line width. The maximum allowed width is 2mm
(0.078inch).
PATREPeat
This is a system-defined attribute that will have a unique value within the
MDB. It is this number that should be used when the Linestyle is used.
FUNC
ALTDEF
If set it must refer to another LINEST. If set the referenced LINEST will be
used on hard copy output. Thus if at /My-Linestyle:
ALTDEF is set to /My-Plot-Linestyle it is /My-Plot-Linestyle that will be
used on hardcopy output in place of /My-Linestyle.
When the LINEST element is created a system-defined line style number is allocated
automatically. This is a unique number in the range 1-255 and is held in the LSTYNO
8:8
12 Series
attribute of the LNEST element. This is the number to use for a linestyle attribute (eg
NLSTYLE) when it is required to use that LINEST.
Alternatively, it is usually more convenient to specify a name for the LINEST, and then this is
used to set the linestyle attribute (although it will be the LSTYNO value that will be assigned
to the linestyle attribute). Thus for example:
NLSTYLE 3
DLSTYLE /DimLineStyle-1
Having created a Linestyle it must be defined within the graphics system by an UPDATE
PENSTYLES command if it is to be used during that session of DRAFT. In subsequent
sessions it will be automatically defined during module entry.
Advanced Line Style Functionality
It is possible to add a repeated decoration to a line style. This decoration may be a glyph
or a text string (or indeed both together).
If a repeated glyph is required the following attributes have to be defined:
GLYREF
GLYNUM
These two attributes are mutually exclusive setting one will unset the other. For details of
user-defined and system-defined glyphs see Glyphs. For example:
GLYREF /flow-arrow
GLYNUM SYSpattern 15
GLYNUM may be set OFF. This will cause both GLYNUM and GLYREF to be unset.
DECMOD
A code number (1-6) to signify how the glyphs are to be distributed. The
default value is 3. The code number is interpreted as follows:
1-3
One glyph at the start of the line, with its axes reversed.
A glyph at each end of the line, the first having its axes reversed.
DECSIZ
8:9
12 Series
DECREP
DECGAP
The length of each gap left in the path. This may be 0 if no gaps are
required. If it exceeds the glyph repeat distance then the path itself
will be completely omitted only the glyphs will be drawn. The
default value is 0.
Note: All DRAFTs pre-defined glyphs (except numbers 10, 11 and 20) have their origins at
their centres and thus a repeat distance of 0 with DECMOD = 4, 5 or 6 will cause
them to be centred upon the end(s) of the line. This is generally satisfactory for
balloons, dots, etc but with arrowheads it will cause the line to appear longer than
defined. To avoid this the repeat distance should be equal to the DECSIZ value. This
will cause the origin of each glyph to be positioned at half the repeat distance from
the end of the line.
If a repeated text string is required, attributes DECMOD, DECSIZ, DECREP and DECGAP
must be set as described above. For text strings DECSIZ specifies the character height.
In addition the following attributes must be set:
TXSTRI
TXALIG
FONT
The font to be used. This must be a TrueType font. This functionality is not
available for use with AVEVA fonts.
Text strings and glyphs can both be defined but they have to have common values for
DECMOD, DECSIZ, DECREP, and DECGAP.
Users should note that the DECSIZ, DECREP, and DECGAP parameters are affect by
scale. This means that if a linestyle with these parameters set is used:
8.2.3
to define a Symbol Template then, when that template is instanced by a Symbol, the
size and frequency of the glyphs and texts will be affected by the scale of the Symbol;
to define 3D design graphics then the size and frequency of the glyphs and texts will be
reduced by the View scale.
Glyphs
Glyphs are used in conjunction with user-defined Linestyles to produce special effects, for
example: symbols at the ends of lines or symbols drawn at regular intervals along the line.
A set of pre-defined Glyphs is provided, and you can also define your own, which will be
stored in the database.
Pre-defined Glyphs
25 pre-defined Glyphs are provided, see Figure 8:3.: Pre-Defined Glyphs
8:10
12 Series
System Glyph 1
Double slash
System Glyph 2
System Glyph 3
Cross
System Glyph 4
Zigzag 1
System Glyph 5
Zigzag 2
System Glyph 6
Break symbol
System Glyph 7
Transverse bar
System Glyph 8
System Glyph 9
System Glyph 10
System Glyph 11
System Glyph 12
Circle, unfilled
System Glyph 13
Square, unfilled
System Glyph 14
Hexagon, unfilled
System Glyph 15
Diamond, unfilled
System Glyph 16
System Glyph 17
System Glyph 18
Circle, filled
System Glyph 19
Star
System Glyph 20
Thick bar
System Glyph 21
System Glyph 22
Diamond, filled
System Glyph 23
System Glyph 24
Waveform
System Glyph 25
Square, filled
Figure 8:3.
Pre-Defined Glyphs
8:11
12 Series
User-Defined Glyphs
User-defined Glyphs are defined in the database by GLYPH elements which are members
of a Glyph Table (GLYTB) element. GLYPHs have the following attributes:
GLYNO:
REFSIZe:
FUNCtion:
GLYPH elements may own GLYCIR, GLYREC, and GLYOUT elements that represent
circles, rectangles, and outlines. In addition to the basic attribute(s) that define their
dimensions these glyph-primitive elements may be rotated and offset from the glyph origin,
and may be solid-filled.
Element GLYCIRcle has attributes:
GDIAMeter:
GOFFSet:
(2 Integers) The X & Y offsets of the Circle centre point from the
Glyph origin.
GFILLD:
If set TRUE will cause the Circle to be solid-filled. By default this will
be FALSE.
GXLENgth:
GYLENgth:
GANGLE:
GOFFSet:
(2 Integers) The X & Y offsets of the Rectangle centre point from the
Glyph origin.
GFILLD:
8:12
12 Series
GDEFINition:
GANGLE:
GOFFSet:
(2 Integers) The X & Y offsets of the Outline origin from the Glyph
origin.
GFILLD:
A GLYOUT is a series of spans that may be straight lines or circular arcs. They may be
continuous or discontinuous. The geometry of these is created using the syntax of the
<GDEFIN> graph and stored in the GDEFIN attribute. The syntax is:
-- etc
etc
etc
- etc
- etc
etc
etc
- etc
Where <int2>
<int3>
The sequence must start with the MTO (MoveTo) keyword followed by two integers. This
defines the start point of the Outline. This must be followed by the LTO (LineTo) or ANGTO
(AngleTo) keyword and then two or three integers respectively to define the first span.
8:13
12 Series
Having defined a span another similar span can be defined immediately by the input of two
or three integers or alternatively the type of span can be changed by a LTO or ANGTO
keyword. If a break in the Outline is required the MTO keyword must be used to define the
start of a new sequence.
For example, a symbolic flower-head of reference diameter 120 with alternating filled and
unfilled petals could be defined as follows:
NEW GLYPH
REFSIZ 120
NEW GLYOUT
GDEFIN MTO 10 0
NEW GLYOUT
COPY GLYOUT 1
GANGLE 45
GFILLD TRUE
NEW GLYOUT
COPY GLYOUT 1
GANGLE 90
NEW GLYOUT
COPY GLYOUT 1
GANGLE 135
GFILLD TRUE
NEW GLYOUT
COPY GLYOUT 1
GANGLE 180
NEW GLYOUT
COPY GLYOUT 1
GANGLE 225
GFILLD TRUE
NEW GLYOUT
COPY GLYOUT 1
GANGLE 270
NEW GLYOUT
COPY GLYOUT 1
GANGLE 315
GFILLD TRUE
NEW GLYOUT
COPY GLYOUT 1
GANGLE 180
NEW GLYCIR
GDIAM 15
GFILLD TRUE
8.2.4
Using Glyphs
Glyphs are used in conjunction with LINEStyle elements. The LINEST's GLYNUM attribute
defines the glyph to be used. This may be set as follows:
GLYNUM/ber OFF
GLYNUM SYS/temglyph 10
8:14
12 Series
GLYNUM 3
GLYNUM /My-Glyph
The LINEST's DECSIZ attribute should be set to define the size to which the Glyphs
REFSIZ value is to scaled.
8.3
Fill Styles
Fill Styles are used whenever it is required to hatch an area on a drawing. This hatched area
may either be part of the annotation (a hatched OUTLine element for example) or may be
produced by the auto-hatching capability of the Update Design process.
A pre-defined set of fill styles (including solid-fill) is provided; it is also possible for you to
define your own. A fill style is defined by combining 1 or more hatch patterns. A hatch
pattern is a sequence of parallel lines all drawn with a particular line style (chained,
solidthick, etc.) and at a specified angle and separation. By the careful design of hatch
patterns and line styles complicated fill styles (such as those typically used to denote
brickwork, concrete, grassland, etc) can be created.
8.3.1
8:15
12 Series
Figure 8:4.
Patterns 11-18 are combinations or variants of system patterns 1-10, and are defined as:
Pattern 11:
Pattern 12:
Pattern 13:
8:16
12 Series
Pattern 14:
Pattern 15:
Pattern 16:
Pattern 17:
Pattern 18:
Figure 8:5.
8:17
12 Series
Patterns 19-30 are more complicated patterns making use of differing linestyles.
Pattern 19:
Pattern 20:
Pattern 21:
Pattern 22:
Pattern 23:
Pattern 24:
Pattern 25:
Squares
Pattern 26:
Triangles
Pattern 27:
Grassland
Pattern 28:
Swamp
Pattern 29:
Brickwork
Pattern 30:
Concrete
8:18
12 Series
Figure 8:6.
8:19
12 Series
8.3.2
the style with which the hatch lines will be drawn. This may
either be a system-defined line style, thus: Chained or
DashedThick, or a user-defined line style, specified either by
its LSTYNO value or by its database name. Thick lines may
be used but user-defined line styles that make use of glyphs
cannot be used. By default HLSTYLE will be set to SOLID.
Angle (HANGLE):
Separation (HSEPAR):
Offset (HOFFSET):
8:20
12 Series
HSEPAR 3.5mm
HOFFSE 1mm
will convert /My-Fillstyle into a double-line Fill Style with double lines (1mm between them)
repeated every 3.5mm
Element FILLST also has attributes:
FSTYNO:
SOLFILled:
If set TRUE will cause the Fillstyle to provide solidfill. The default
setting is FALSE.
FUNCtion:
ALTDEF
When the FILLST element is created a system-defined fill style number is allocated
automatically. This is a unique number in the range 1-255 and is held in the FSTYNO
attribute of the FILLST element. This is the number to use for the FSTYLE attribute when it
is required to use that FILLST.
Alternatively, it is usually more convenient to specify a name for the FILLST, and this is then
used to set the FSTYLE attribute (although it is the FSTNO value that will be assigned to the
FSTYLE attribute).
Having created a Fillstyle it must be defined within the graphics system by an 'UPDATE
PENSTYLES' command if it is to be used during that session of DRAFT. In subsequent
sessions it will be automatically defined during module entry.
Advanced Fill Style Functionality
In order to create more complex patterns, such as Triangles, Brickwork, etc it is necessary
to use two additional attributes of HPATTE:
Line Pattern
Advance (PATADV):
Line Pattern
Offset (PATOFF):
Thus for example, in order to create a Fill Style to represent brickwork (with 10mm x 4mm
bricks) we first need to create a suitable linestyle for the vertical lines and then a Fillstyle
with 2 Hatch Patterns:
8:21
12 Series
NEW LSTYTB
NEW LINESTYLE /BrickWork-VerticalLS
PATDEF 50 -50
PATREP 8mm
NEW FSTYTB
NEW FILLSTYLE /BrickWorkFS
NEW HPATTERN
/BrickWork-HorizontalHP
HLSTYLE Solid
HANGLE 0
HSEPAR 4mm
HOFFSE 2mm
NEW HPATTERN
/BrickWork-VerticalHP
HLSTYLE /Brickwork-VerticalLS
HANGLE 90
HSEPAR 5mm
HOFFSE 3mm
PATOFF 2mm
PATADV 4mm
Offsetting the pattern is not strictly necessary and so attributes HOFFSE and PATOFF of
both HPATTEs could be left at 0mm; it is merely done to reduce the chance of the horizontal
and vertical lines coinciding with the edge of the hatched area.
8.3.3
Style elements:
High-level elements:
8:22
12 Series
FSTYLE SYS/temstyle 10
FSTYLE BRICK/work
FSTYLE SOL/idfilled
a User-defined Fillstyle, thus:
FSTYLE 3
FSTYLE /My-FillStyle
Various special values: OFF, DEF/ault, UNC/hanged. These are not all valid in all
circumstances.
8.4
Marker Styles
A system-defined marker style is specified by combining one of five basic marker types with
a scale factor of 1 to 8. The five marker types are:
(STOP)
(CROSS)
(PLUS)
(STAR)
(RING)
8.5
8:23
12 Series
The colour of this graphical feedback feature is magenta by default, but can be changed by
the SETFEEDBACK command.
Example:
SETFEED COL 15
Set rubber banding colour to colour 15
Example:
8:24
12 Series
9.1
Report
The Report (REPO) element may be used to contain brief textual information relating to a
full report (which would exist outside Plant) on the owning drawing registry. The relevant part
of the DRAFT database is shown in Figure 9:1.: Report Database Hierarchy.
REGI
REPO
TEXT
Figure 9:1.
Filename (FLEN). The name of the file containing the report, as a text string
NEW REPO
TITL REPORT ON VALVES IN ZONE 2
FLEN /REP-A-V
CLRF /PURCHASING
9:1
12 Series
9.2
Circulation List
DRAFT gives you the ability to store Drawing Circulation Lists. The relevant part of the
DRAFT database is shown in Figure 9:2.: Circulation List Database Hierarchy.
Library
DRWG
CLRF
REPO
CLRF
CLLB
CIRL
CIRL
RECI
RECI
Figure 9:2.
The Circulation List Library (CLLB) is an administrative element used to group together
Circulation Lists (CIRL), each of which is referred to from the CLRF (Circulation List
Reference) attribute of a Drawing (or Report) element. Each CIRL may contain other CIRL
elements and/or Recipient (RECI) elements. A RECI has the attributes:
Location (LOCA)
9:2
12 Series
NEW CLLB
Create Circulation List Library (at Library level)
RNAM Tom
LOCA Room F21
NEW RECI /RC2
RNAM Dick
LOCA Room G24
COPI 2
/DRWG DR1
Set Circulation List Reference
CLRF /CL1
9.3
Drawing Revisions
The Revision (REVI) element enables you to store drawing revision data. A REVI may be a
member of a Drawing element or of a Sheet element, see Figure 9:3.: Revision Element.
DRWG
SHEE
REVI
CIRL
REVI
CLRF
Figure 9:3.
Revision Element
Approver (APPR)
Revision (RVSN)
9:3
12 Series
RVSN, RVDT and RVAU are all automatically set on REVI creation, but they can then be
edited. The format of the date assigned to RVDT is controlled by the value of the
DATEFOrmat attribute of the relevant DEPT.
Pseudo reference array attributes SREVAY and DREVAY are available to return a list of the
reference of all the REVI elements owned by a Sheet or Drawing. The maximum array size
is 50. The attributes are valid at any element of or below a Sheet or Drawing respectively.
They have been created primarily for use with hash codewords to generate revision data on
drawings, see Accessing Data from the DRAFT Database, Part 2, Drawing Annotation.
9.4
Summary of Commands
9.4.1
At Circulation List . . .
9.4.2
RNAM text
LOCA text
COPI integer
At Revision . . .
APPR text
APDT text
RVSN [text]
RVAU [text]
CLRF name
9:4
12 Series
10
Change Highlighting
Change Rules control how Design and Annotation elements that have been changed are
drawn on a DRAFT View and are similar to Representation Rules. Each Change Rule can
be specific to a given type or types of element, or named elements. Change Rules refer to
Change Styles, either Design Change Styles or Annotation Change Styles, depending
on whether the changed element is a Design element or an Annotation element. The
attributes of the Change Styles define the way in which changed elements will be drawn.
Generally this will be by altering the drawing styles and colours used. Pieces of text may
also have their font changed, be underlined, or be enclosed within a specified style of
parentheses. For more information about styles and colours see Colours and Styles. For
information about Representation Rules see Graphical Representation.
In order to determine whether Design and Annotation elements have changed, it is
necessary to compare the relevant databases at two points in time. One of these two points
is always the current time. The other point used is a Comparison Date. The concept of
Comparison Dates is discussed in Comparison Date.
Design Change Rules (DCRULE) and Annotation Change Rules (ACRULE) are stored in
Change Rulesets (CRST), which in turn are owned by Representation Libraries (RPLB).
RPLBs are also used to store Design Change Styles (DCSTYL) and Annotation Change
Styles (ACSTYL). The reference from a DCRULE to a DCSTYL is made by its DCSTYF
attribute, and the reference from an ACRULE to an ACSTYL is made by its ACSTYF
attribute. When a VIEW references a CRST, the reference is made by its CRSF attribute.
RPLB
VIEW
crsf
RPLB
CRST
DCSTYL
ACSTYL
dcstyf
ACRULE
DCRULE
acstyf
Figure 10:1. Change Rules Database Hierarchy
The hierarchy of database elements for Change Highlighting is similar to that for
Representation and Auto-hatching and allows company or project standards to be imposed.
10:1
12 Series
However, unlike Representation and Hatching Rules, Change Rules cannot be owned
directly by a VIEW and there are therefore no local change rules.
Once the Rulesets and Styles have been set up, it is just a matter of setting the VIEW
attribute CRSF to point to the Ruleset that you wish to use, defining a Comparison Date,
and issuing an UPDATE command with the SHOW CHAnges option (see UPDATE
Command, SHOW CHANGES Option and Error Messages).
10.1
FFSTYLE/FFCOLOUR
SOLIDTHICK/8
Backface Style/Colour
BFSTYLE/BFCOLOUR
DOTTEDTHICK/8
OBSTYLE/OBCOLOUR
LDASHTHICK/8
Centreline Style/Colour
CLSTYLE/CLCOLOUR
CHAINEDTHICK/8
P-line Style/Colour
PLNSTYLE/PLNCOLOUR
DASHEDTHICK/8
MLNSTYLE/MLNCOLOUR
CHAINEDTHICK/8
Outline Style/Colour
OLSTYLE/OLCOLOUR
SOLIDTHICK/8
Fill Style/Colour
FSTYLE/FCOLOUR
SYSTEMPATTERN1/8
Note that DCSTYLs are not exact equivalents of Representation Styles, they do not have
Tubing Flag (TUBEF), Drawing Level (DLEV), etc. attributes. The values of these attributes
are determined from the relevant Representation Styles. The DCSTYL only defines which, if
any, of the standard style/colour values should be overridden in order that changed Design
elements are marked.
Design elements that have no DCSTYL assigned to them will not have any changes that are
made to them marked. Within a VIEW, it is therefore possible to mark changes made to
pipework, for example, but ignore changes made to steelwork.
10.2
10:2
12 Series
specific values or to UNCHANGED. The font attribute may be set to a standard font number
or to UNCHANGED. If any of these four attributes are set to UNCHANGED, the relevant
Label/Dimension/2D Primitives attribute will be used. The two other attributes define
whether changed text is to be underlined or enclosed in brackets.
The ACSTYL attributes, with their defaults, are as follows:
Text Colour
TXCOLOUR
NLSTYLE/NLCOLOUR
SOLID/8
Fill Style/Colour
FSTYLE/FCOLOUR
SYSTEMPATTERN1/8
Font Number
FONT
UNCHANGED
Brackets
BRACKE
NONE
Underline
UNDERL
OFF
10.3
Change Rules
The Change Ruleset (CRST) owns both Design Change Rules (DCRULEs) and Annotation
Change Rules (ACRULEs). Design Change Rules reference Design Change Styles and
Annotation Change Rules reference Annotation Change Styles.
10.3.1
DCSTYF
unset
Selection Criterion
CRIT
unset
For more information on using Selection Criteria refer to DESIGN Reference Manual, Part 1
General Commands.
For changes to be highlighted properly the Selection Criterion should use one of the
functions that make use of the current Comparison Date. These are; CREATED and
MODIFIED. For example:
10:3
12 Series
Note that a third function associated with the Comparison Date, DELETED(), is not relevant
here, deleted design elements will not be shown on DRAFT drawings and hence cannot be
highlighted.
10.3.2
ACSTYF
unset
Annotation Code
ASCODE
Changed
Each CRST therefore only needs to reference one or two ACRULES, one applicable to
Changed Annotations, one applicable to Added Annotations. If more than one ACRULE is
referenced for a type of changed annotation, only the first, in database order, will be applied.
The syntax for the Annotation Change Rule Application attribute is:
ASCODE
10.4
Attribute Setting
The following attributes:
FFSTYLE/FFCOLOUR
OLSTYLE/OLCOLOUR
BFSTYLE/BFCOLOUR
NLSTYLE/NLCOLOUR
CLSTYLE/CLCOLOUR
FSTYLE/FCOLOUR
OBSTYLE/OBCOLOUR
TXCOLOUR
PLNSTYLE/PLNCOLOUR
FONT
MLNSTYLE/MLNCOLOUR
all have the option of UNChanged. This is valid at DCSTYL and ACSTYL elements only.
Assigning UNChanged to these attributes at any other element will generate the following
error message:
10:4
12 Series
ACSTYF
CRSF
10.5
Comparison Date
It is only by comparing a drawing at two states or sessions that it is possible to determine
what has changed. Using the current state of the drawing as one state we must then
reference an earlier state in order to make the comparison. We do this by specifying a
Comparison Date (COMPDATE), that is, the drawing state at a time that we wish to use as a
baseline or datum.
The Comparison Date can be set in one of two ways:
Example:
Q COMPDATE DATE
Q COMPDATE STAMP
A Stamp is a way of referencing combinations of databases and sessions at specified
instances. Stamps are created by the PDMS Administrator. For more information on Stamps
and how they are created and used refer to the Administrator Command Reference Manual
and the Administrator User Guide.
The Comparison Date can be used in queries on any attributes, using the syntax OLD. For
example:
Q OLD XLEN
10:5
12 Series
will output the value of attribute XLEN of the current element at the Comparison Date.
10.6
If the SHOW CHAnges option is given below View level, updating will proceed and the
following error message will be displayed:
If the View's CRSF attribute is unset, it is assumed that default Design and Annotation
Change Rules are to be applied. These are equivalent to the following:
If the View's CRSF attribute is invalid, updating will be abandoned and the following
error message will be displayed:
If the CRSF references a CRST that contains no rules, updating will be abandoned and
the following error message will be displayed:
10:6
12 Series
command), updating will be abandoned and the following error message will be
displayed:
If the DCSTYF or ACSTYF attribute of a Change Rule is unset or invalid, updating will
be abandoned and one of the following error messages will be displayed:
If the CRIT attribute of a DCRULE is unset (with reference to an UPDATE DESI and an
UPDATE ALL command), the following error message will be displayed:
10.7
Querying Commands
10.7.1
10:7
12 Series
10.8
Summary of Commands
10.8.1
10.8.2
CRITeria crit
10:8
12 Series
10.8.3
10.8.4
TXCOLOUR integer/colour_name
TXCOLOUR UNCHANGED
10:9
12 Series
NLSTYLE UNCHANGED
NLCOLOUR UNCHANGED
FONT integer
FONT UNCHANGED
BRACKE SQUARE
BRACKE NONE
UNDERL ON
10:10
12 Series
11
Introduction to Annotation
This Chapter describes the part of the DRAFT database used to store annotation elements,
that is dimensioning elements, labelling elements, and 2D drafting elements (i.e. geometric
primitives, symbols, and text). This part of the DRAFT database hierarchy (see DRAFT
Database Hierarchy) is shown below:
Figure 11:1.
Annotation Elements
Dimensioning and Labelling elements are owned by Layers. Other text, symbols and
graphics are owned by Notes. There are two types of Note:
11:1
12 Series
11.1
Layers
Layers (LAYE) are owned by VIEWs and are administrative elements used to group
together annotation elements. Layers may own Dimension elements, Label elements and
View Note elements. Usually, different Layers are used for different functions, and the
function of a Layer is defined by its PURPose attribute. The PURP attribute is used to
control the types of element that the Layer can own.
The PURP (Purpose) attribute of a Layer is set to a (four character) word, for example:
PURP DIMS
The PURP attribute may also be used to identify the Layer in other commands.
Example:
11.1.1
11.1.2
11:2
12 Series
11.1.3
11.2
Autoblanking
You can use autoblanking to remove an area of graphics from a drawing and leave a clear
area. Generally, graphics added later will be drawn in this clear area. The main purpose is to
allow annotation to be shown clearly in crowded parts of a drawing. The geometry of the
blanked areas is defined by the geometry of the annotation element; for example, a circular
annotation element can define a circular blanked area where no 3D design graphics will
appear. Overlapping 2D, text and other annotation graphics will not be hidden by blanking.
When autoblanking is switched on, the geometry will be hidden in the blanked areas
immediately the annotation that defines them is drawn or modified. When autoblanking is
switched off, the blanks will not be generated on the screen, but switching autoblanking on
will generate all blanks immediately. Blanks will always be generated in plot files generated
from DRAFT, even when Autoblanking is off. The advantage of working with Autoblanking
switched off is that view control operations such as zooming and panning will be slightly
faster.
The command to switch autoblanking ON or OFF for a DRAFT session is:
AUTOBLANKING ON/OFF
Autoblanking can be used for the following annotation elements: LDIM, ADIM, RDIM, PDIM,
GLAB, SLAB, VNOT, and NOTE. The attribute BLNK specifies whether autoblanking is
required, and attribute BMAR specifies the blanking margin to be applied.
BLNK TRUE/FALSE
BMAR value
where value is a real value that is greater than or equal to 0.0. If BMAR is set to 0.0 then a
blanked region will be drawn with no blanking margin.
11:3
12 Series
11:4
12 Series
12
Dimensioning
Dimensions are a form of drawing annotation consisting of both text and geometric
elements; they may be linear, radial (two types) or angular. Linear and radial dimensions
show the distances between particular points in the design model whilst angular dimensions
show the angles between directions.
A simplified view of that part of the Database hierarchy (see DRAFT Database Hierarchy)
that relates to dimensioning is shown below.
VIEW
LAYE
LDIM
RDIM
PDIM
ADIM
(Dimension Directions)
(Dimension Points)
(Dimension Points)
DRAFT allows dimensions to be created quickly and easily (using the cursor), with many
attributes of the dimension elements being set automatically by cascading values from the
owning LAYE element.
12.1
12:1
12 Series
Pitch Circle Dimension (PDIM) elements (see Pitch Circle Dimensions) exist for each pitch
circle dimension that appears on a drawing. PDIM elements own Dimension Point
elements, which specify the points between which dimensions are drawn. The graphics for a
PDIM are similar to those for an RDIM.
Angular Dimension (ADIM) elements (see Angular Dimensions) exist for each angular
dimension that appears on a drawing. ADIM elements own Dimension Direction elements,
which specify the end points of the dimension arc and its origin.
Note: When a Pipe element is dimensioned directly, the Pipe origin is assumed to be the
position of the HEAD of the first Branch visible in the VIEW region, if any. If no
Branch HEADs are visible in the VIEW region, then the position of the HEAD of the
first Branch is used.
12.2
Linear Dimensions
12.2.1
12:2
12 Series
Such a dimension could be produced by typing the following commands, starting at Layer
level:
NEW LDIM
FROM ID @
TO ID @
TO ID @
The Dimension will appear on the display. If only two elements are hit a pair of Dimension
Point elements will have been automatically created, with the last point becoming the
current element.
In the above example the Dimension Points will be DPPT elements - the Dimension Point is
defined by a p-point of the Design element, in this case the origin. Any p-point can be
nominated as a dimension point by replacing the FROM ID @ syntax above by FROM IDP
@/TO IDP @. The Dimension may also be defined explicitly:
Example:
DPBA- allows you to dimension to/from before or after a Design element (in the
Dimension direction).
NEW LDIM
FR POS @ TO POS @
DPBA elements would be created by a sequence such as:
NEW LDIM
FR BEFORE ID @ TO AFTER ID @
The effect of such a command will depend upon the dimension direction - see Principal
Attributes of Angular Dimensions. Figure 12:3.: Single Value Before/After Linear
Dimensions shows an example of such a linear dimension, produced by the same
command but with different dimension directions.
Constructed points (see Point and Line Construction) may also be used to create
Dimension Points.
Note: In cases where the dimension value is less than 0.01 mm, the display of all
dimension point graphics (see Figure 12:2.: Single Value Linear Dimension) will be
suppressed.
When dimensioning BEFORE or AFTER elements such as EQUI, STRU or SUBS, DRAFT
will ignore those primitives with OBST (obstruction level) set to 0 or 1. When dimensioning
BEFORE or AFTER a primitive, its OBST value will be ignored.
12:3
12 Series
Figure 12:4.: Before/After Linear Dimensions on a Single Element shows examples of using
before/after linear Dimensions with a single element. (See Principal Attributes of Linear
Dimensions for details of DOFF and OSHT.)
Note: Under some circumstances the length of the projection line for a DPBA may be
unsatisfactory. In this case changing the value of the NPPT attribute (which supplies
a reference p-point) will correct the situation.
12:4
12 Series
Note: Use of Radial Dimensions would provide a simpler method of drawing the two
dimensions shown on the right-hand side of Figure 12:4.: Before/After Linear
Dimensions on a Single Element - see Radial Dimensions.
Note: Any combination of the above three Dimension-creating commands is permissible.
Example:
FROM ID @ TO BEFORE ID @
FROM POS @ TO ID @
FR AFT ID @ TO POS @
Each FROM command sets the Dimension Points DDNM (Design Data Name) attribute to
the Name of the Design element. The DDNM attribute may be reset immediately to define a
new Dimension Point. If the DDNM is set to refer to an element, which is not in the Id List
referenced from the current VIEW, the Dimension will still be drawn.
The command:
12:5
12 Series
12.2.2
Multi-valued Dimensions
The preceding examples have dealt with single-valued dimensions; where more than two
Dimension Points are involved, the Dimension is said to be multi-valued. Two classes of
multi-valued Dimensions exist, namely chained and parallel. An example of a chained
Dimension is shown in Figure 12:5.: Chained Linear Dimension.
NEW LDIM
FR ID @ TO ID @ TO ID @
An additional link can be inserted in or added to a chained Dimension (or a single-valued
Dimension can be converted to a chained Dimension) through use of the INSERT
command. This is done simply by typing:
INSERT ID @
and using the cursor to nominate the link element. P-points, p-lines, dimension points or 3D
points may also be used as links using:
INSE
INSE
INSE
INSE
IDP @
IDPL @
IDPD @ or
POS @
12:6
12 Series
A Dimension Point may be constructed using DRAFTs point construction facilities (see
Point and Line Construction). For example:
INSE POS OF @
INSE POS OF ENDP OF @
Other constructions such as INTERSECTION and MIDPOINT can be used. The facility
(which is only valid in a plan or elevation View) enables Dimension Points to be positioned
on any line of the Design graphics. The constructed Dimension Point will have a 3D position
(i.e. it is a DPOI) but will not be associated with the identified Design element.
The effect of the INSERT command is to create a new Dimension Point of the appropriate
type at the correct position in the owning LDIMs member list. INSERT can be used at
Dimension Point or LDIM level. Figure 12:6.: Use of the INSERT Command illustrates the
use of the INSERT command.
Dimensions will be drawn in the same order as the LDIMs member list order. If the elements
get out of the correct order then the display of the Dimension will become confused. This
situation can be corrected by the SORT DIMENSIONPOINTS command (minimum
abbreviation SORT DIM), which can be used at Dimension or Dimension Point level. The
effect of the command is shown in Figure 12:7.: Use of the SORT DIM Command.
An example of a parallel Dimension is shown in Figure 12:8.: Parallel (or Tail) Linear
Dimension.
12:7
12 Series
A parallel Dimension can be produced simply by setting the LCHA attribute of an LDIM as
appropriate:
12.2.3
LCHA PARA
- parallel dimension
LCHA CHA
- chained dimension
Note that OSHT, PLCL and DOFF are given initial default values at Layer level when the
Layer is created. These values are cascaded down to Dimension level when those elements
are created subsequently. Following this initial setting, an attribute set to default at
Dimension Point level will take its value from the same attribute of its owning Dimension
element (if appropriate).
The Projection Line Clearance (PLCL) is the distance between the dimension point and
the projection line at the dimension point end. Negative clearances may be specified.
Examples of setting this attribute are:
PLCL 5
PLCL @
PLCL DEF
PLCL may be set at Dimension or Dimension Point level. PLCL set at Dimension level
(which becomes the default PLCL) will apply to all subsequently created Dimension Points.
PLCL set at Dimension Point level can only be reset from the same Dimension Point, not
from Dimension level. When setting PLCL with the cursor, the resulting (paper) coordinate
that does not lie in the same axis direction as the projection line is ignored. These
comments also apply to the OSHT attribute (see below).
12:8
12 Series
The Projection Line Overshoot (OSHT) is the distance by which the projection line
overshoots the end of the dimension line. Negative overshoots may not be specified.
Examples of setting this attribute are:
OSHT 5
OSHT @
OSHT @
OSHT DEF
- the distance by which the dimension line is offset (in the projection
line direction) from the 2D position of the first dimension point.
Projection Line
Direction (PLDI)
- the angle between the projection line and the dimension line.
Dimension Line
Direction (DIR)
DOFF has a related attribute DPOS - the Dimension Line Position. DPOS is a fixed 2D
paper coordinate through which the dimension line will pass. DOFF and DPOS are mutually
exclusive: setting one will unset the other. If a dimensioned element is moved the dimension
line will also move when DOFF is used; if DPOS is used the dimension line will still pass
through the same point.
A feature of these four attributes (DOFF, DPOS, PLDI, DIR) is that although they are
attributes of the Linear Dimension they can also be set at Dimension Point Level without the
need to navigate to the Dimension element.
DOFF and DPOS both control the position of the dimension line and so are mutually
exclusive - setting one will unset the other. Examples of the relevant commands are:
DOFF 20
DPOS @
DIM ABSOLUTE
DIM OFFS
When setting DPOS, the resulting (paper) coordinate that does not lie in the same axis
direction as the required offset is ignored.
12:9
12 Series
PLDI 75
PLDI N10W
PLDI THR/OUGH @
PLDI IDP @
Note: Projection line direction is treated as 90 degrees when it is nearly but not quite 90
degrees. This avoids an unexpected flip in the projection line text orientation.
The dimension direction can be set explicitly by a command such as:
DIR E10N
Another method is to set the true length attribute (TLIN) using the command:
DIR TRUE
This will set the dimension direction as being that from the first to the second dimension
point (TLIN is set to TRUE and DIR is unset). See Figure 12:10.: Definition of True Length
and Figure 12:11.: Effect of True Length Attribute Settings.
P2
DOWN
P2
P1
P1
(i)
(ii)
12:10
12 Series
The true length facility can be useful when it is not clear what explicit direction to set in order
to achieve the desired result. The bottom left-hand dimension in Figure 12:11.: Effect of
True Length Attribute Settings has been created without regard for the Dimension direction,
which turns out to be inappropriate. Setting TLIN TRUE produces the desired picture.
Points to note about the true length facility are:
The true length is 2D, i.e. the length is orthographic, not a slope length - uppings are
ignored.
True length is meaningless for a Dimension with more than two points, unless the
points are in line.
12:11
12 Series
It is possible to set the dimension direction to that of a p-point, using the command:
DIR IDP @
(This command will set the DDNM attribute to the name or reference number of the primitive
concerned, and the PPDI attribute to the appropriate p-point number; DIR will be unset and
TLIN set to FALSE.)
12.2.4
The truncation is produced by the TRUNCATE command, which has two forms as shown in
the examples below.
TRUNCATE BY 5
TRUN TO 10
TRUN OFF
For non-truncated parallel dimensions, the spacing between each dimension line is given an
initial default value calculated to be sufficient to allow room for the dimension value (or a
single line of dimension line text). The spacing is controlled by the Dimension Line
Separator Attribute (DMSP).
Example:
DMSP 30
DMSP @
In a macro, the separation can also be set in terms of Sheet or screen coordinates. Note
that the minimum separation is governed by the DMSP attribute - the calculated spacing
cannot be less than this minimum. Figure 12:13.: Parallel Dimension Line Spacing shows
the effect of varying the spacing.
12:12
12 Series
#DIM in the example above takes the value of the dimension. #DIM is a simple case of
intelligent text - see Intelligent Text. Note that in the case of non-truncated parallel
dimensions, the dimension line spacing will automatically be adjusted to accommodate two
or more lines of text if these are input. Dimension line text may be set at Dimension Point or
Dimension level, although in the latter case the text input will attached to all the dimension
lines involved. Associated commands are:
DMTX DEFAULT
12:13
12 Series
Dimension text is automatically centre-justified, but its position relative to the dimension line
may be varied by changing the setting of the dimension text offset (DTOF) attribute. For
example:
DTOF 0 5
- move dimension text origin 5mm along axis parallel to projection line
in text up vector direction
(= perpendicular to dimension line in most cases)
DTOF @
DTOF N 1 @
DTOF N 2 5
Note also:
DTOF DEF
DTOF STAN
DTANGLE STANDARD
DTANG HORIZ
DTANG VERT
DTANG EXTERNAL
DTANG PARALLEL
PTANG DEFAULT
The STANDARD setting gives dimension line text parallel to the dimension line except when
there is insufficient room for it, when it is drawn parallel to the projection-line - i.e. external
dimension line text. STANDARD is the default setting for Dimension elements. The text is
positioned by default just above the middle of the dimension line except that external text is
centred on the centre of the dimension line. If the text is not external, then its position is
constrained to lie between the projection lines.
The HORIZONTAL and VERTICAL settings cause the dimension line text to be drawn
respectively horizontally or vertically in the VIEW. By default the text is centred on middle of
the dimension line.
The EXTERNAL setting forces the dimension line text to be drawn parallel to the projection
line even though there is room for it to be drawn parallel to the dimension line. By default the
12:14
12 Series
text is centred on middle of the dimension line. If the text would not be external in the
STANDARD case, then its position is constrained to lie between the projection lines.
The PARALLEL setting forces the dimension line text to be drawn parallel to the dimension
line even though there may be insufficient space for it to fit. By default the text is positioned
just above the middle of the dimension line. If the text would not be external in the
STANDARD case, then its position is constrained to lie between the projection lines.
The DEFAULT setting is only available at Dimension Points. This allows the DTANGLE
value to be taken from the Dimension element (LDIM or ADIM). Otherwise the setting at the
Dimension Point is used. This is the default setting for Dimension Points.
Projection line text (PLTX) is set and manipulated in a similar way. For example, the
commands:
12:15
12 Series
Note also:
PLTX STAN
PLTX DEF
Projection line text axes are oriented relative to the projection line. The orientation is
controlled by setting the PTOF attribute.
Example:
PTOF -5 -5
See Figure 12:17.: Projection Line Text Offset for an example of changing the projection line
text offset.
12:16
12 Series
PTOF @
PTOF STAN
PTOF DEF
PTOF N 1 @
PTOF N 2 5
Projection line text is justified towards the appropriate dimension point by default, but may
be justified away from the dimension point or may be centred on the projection line, using
the commands:
PJUST AWAY
PJUST CENTRE
12:17
12 Series
PTANGLE HORIZ
PTANG VERT
PTANG STAN
PTANG DEF
The HORIZONTAL and VERTICAL settings cause the projection line text to be drawn
respectively horizontally or vertically in the VIEW. In these cases, the projection line is not
extended automatically to underline the text but only overshoots the dimension line by the
distance specified by the OSHT attribute.
The STANDARD setting gives the projection line text parallel to the projection line. This is
the default value for Dimension elements.
The DEFAULT setting is only available at Dimension Points. This allows the PTANG setting
to be taken from the Dimension element (LDIM or ADIM), otherwise the setting at the
Dimension Point is used. This is the default setting for Dimension Points.
12:18
12 Series
The standard character height for dimension line and projection line text is 4mm (cascaded
from LAYE level), but this may be varied by commands such as:
DTCH 2
PTCH 2
Initial settings of these attributes are cascaded down from LAYE level.
Other text attributes (present at Dimension and Dimension Point level) are:
PLSP
PFON
DFON
DT COLOUR
PT COLOUR
PTLH
DTLH
Initial settings of these attributes are cascaded down from LAYE level. See Miscellaneous
Text Facilities for details of letter height and text fonts.
12:19
12 Series
Dimension line and projection line text can be edited through use of the EDTEXT
command. In the following examples, the target string is ACCESS DPACE, = ACCESS
SPACE mistyped:
DTER ARROWS
DTER OBLIQUES
DTER DOTS
DTER OFF
Note: The first terminator of a truncated dimension (see Figure 12:12.: Truncated Parallel
Dimension) can be set independently using the FTER attribute. The first terminator
will be drawn 25% larger than the remainder.
FTER can have any of the same settings as DTER, or can be DEFAULT, in which case
FTER assumes the same setting as DTER. FTER is applicable to LDIMs and ADIMs, or can
be set at LAYE level, in which case its setting will be cascaded down to newly-created
dimensions.
12:20
12 Series
TSIZ
The initial settings of DTER and TSIZ are cascaded down from LAYE level.
The line styles and colours used for dimension and projection lines may be set by
DLSTYLE integer/line_pattern,
PLSTYLE integer/line_pattern
DLCOLOUR integer/colour_name
PLCOLOUR integer/colour_name
At an LDIM the initial settings of these four attributes are cascaded down from LAYE level.
At dimension point level their initial values will be DEFAULT, i.e. they use the values from
the owning LDIM. See Colours and Styles for details of colours and line styles.
Gaps in projection lines are most easily defined using the cursor, with either the start and
end points or a mid point and a length being specified. Examples of the relevant commands
are:
GAP @
GAP AT @
SETDEF GAP 15
GAP AT @ L 10
GAP OVER @
- Specify gap start and end points with cursor, and delete all other
gaps in line
GAP DELETE @
Up to ten gaps may be inserted in the projection line. Note that if the position of a Dimension
is changed so as to substantially alter the path of the projection line then it will be redrawn
solid until the gaps are redefined.
Gaps may be highlighted by giving the command:
SKETCH GAPS
at any element that contains gaps. A circle will be drawn with diameter equal to the gap
length, centred on the gap centre. The command:
ERASE GAPS
will remove the circles. Either of the above commands may have an element name after the
main command if the required element is not the current element.
12.3
Radial Dimensions
A Radial Dimension (RDIM) is a form of linear dimension that may be used to draw radius
and diameter dimensions of circular elements. A Radial Dimension does not own Dimension
Point elements, but is defined by a database reference to an element type (the one to be
dimensioned) and an attribute taken from that element which defines whether a diameter or
12:21
12 Series
Dimension Line
Terminator
12:22
12 Series
Radial Dimensions have a dimension centre, defined by the DDNM (Design Data Name)
attribute. This is an attribute of the RDIM itself, and is normally defined by the origin of the
element dimensioned. (See Radial Dimensions for exceptions to this.) This could be (for
example) the origin of a CYLI or of a (filleted) PAVE (Panel Vertex).
The other principal attribute of an RDIM is the dimension attribute key, AKEY. This is a
word attribute that stores the code of a dimensional attribute of the DESIGN element type
that is to be dimensioned. The default value of AKEY is DIAM.
The following table shows which attributes of which DESIGN element types may be
dimensioned using an RDIM.
Element Type
Attributes
CYLI
DIAM
NCYL
DIAM
SLCY
DIAM
NSLC
DIAM
DISH
DIAM
RADI
CRAD
NDIS
DIAM
RADI
CRAD
RTOR
DIAM
RINS
ROUT
NRTO
DIAM
RINS
ROUT
CTOR
DIAM
RINS
ROUT
NCTO
DIAM
RINS
ROUT
SNOU
DIAM
DTOP
DBOT
NSNO
DIAM
DTOP
DBOT
CONE
DIAM
DTOP
DBOT
NCON
DIAM
DTOP
DBOT
VERT
DIAM
FRAD
PAVE
DIAM
FRAD
SEVE
DIAM
FRAD
The command:
Q AKEYLIST
(at a Design element) returns the list of possible AKEY settings.
Most of the AKEY settings allowed above are genuine database attributes; however, the
DIAM keyword has different meanings at different elements. For some Design elements it is
a genuine attribute, for others it is derived:
DIAM is a genuine attribute of Dishes (DISH, NDIS) and all Cylinders (CYLI, NCYL,
SLCY, NSLC).
For a Torus (RTOR, NRTO, CTOR, NCTO), DIAM give the centreline diameter of the
element - i.e. twice the average of RINS and ROUT.
12:23
12 Series
For Snouts (SNOU, NSNO) and Cones (CONE, NCON), DIAM is taken to be DBOT,
the bottom diameter.
For Structural Vertices (VERT, PAVE, SEVE), DIAM is taken to be twice the fillet radius
(FRAD) if it is set. The origin is normally the position of p9 of the vertex.
The centre of a Radial Dimension is normally defined by the origin of the element
dimensioned, except for the following AKEY settings:
12.3.1
For DTOP and DBOT, the dimension centre will be the centre of the appropriate end of
the primitive. This also applies to DIAM for Snouts and Cones.
For FRAD, the centre of the fillet radius is defined by one of the many p-points of the
Vertex (p8 or p9). This also applies to DIAM if the FRAD value is being used.
The RADI attribute of a dish (DISH, NDIS) is the knuckle radius. The CRAD attribute of
a dish is the cap radius. The centres of these radii are derived. Both these AKEY
settings are only sensible for a sideways view of a tori-spherical dish.
NEW RDIM
ON ID @
AKEY RADI
In many cases it will be unnecessary to define AKEY explicitly, since the DIAM setting will
give a sensible result.
Although RDIM elements do not have p-point or p-line attributes it is possible to use p-point
or p-line syntax to select the Design element. This is necessary for vertices (VERT, SEVE,
PAVE) that cannot be picked directly by cursor. However, the Design element can be picked
using the IDP @ command.
12.3.2
120
240
DFLAG RADI
DFLAG DIAM
The Dimension Text (DMTX) attribute has the initial setting #DIM, which gives the value of
the dimension controlled by DLFAG. For example for AKEY RINS and DFLAG DIAM, the
text #DIM will be evaluated as the inside diameter of the element identified. The resulting
value will be output on the drawing in place of this codeword. #DIM is a simple case of
intelligent text - see Intelligent Text.
12:24
12 Series
The Dimension Line Angle (DDEG) attribute controls the angle at which the dimension line
is shown, relative to the 2D coordinate system of the VIEW. The default value is 0
(horizontal in the VIEW). Note that this is only horizontal in the Sheet when the VIEW has
RCOD UP. DDEG may be set explicitly or by using the cursor (i.e. DDEG @).
The Text Radius Flag (DTFLAG) attribute controls whether the text radius DTRAD (see
below) is measured from the CENTRE, MIDPOINT or CIRCUMFERENCE of the radial
dimension. The default setting is CENTRE. For radius dimensions, MIDPOINT is the
midpoint between centre and circumference; for diameter dimensions MIDPOINT is the
same as CENTRE.
The Text Radius (DTRAD attribute) is a signed distance (in Sheet units) that defines the
radial position of the dimension text origin from the centre or circumference (according to
the DTFLAG setting) of the dimensioned object. In the latter case, DTRA= 0 (the default
value) means that the text origin is positioned at the 2D projection of the circumference of
the object dimensioned.
If the text origin lies outside the circumference then the text is justified towards the centre of
the circle. If the text lies inside the circumference then the text is centre justified unless the
DSTYL is LEADER. In this last case, the justification is towards the circumference.
Text radius can be negative. For DTFLAG CIRCUMFERENCE, a negative value means
inside the circumference. For DTFLAG CENTRE, a negative value places the text on the
opposite side of the centre to its usual position. This is equivalent to reversing DDEG with a
positive DTRA value.
240
240
DTRA 0
DTFLA CENTRE
DTRA 0
DTFLA CIRCUM
240
DTRA -10
DTFLA CIRCUM
240
DTRA 10
DTFLA CENTRE
240
DFLAG DIAM
DTFLA MIDPOINT
240
DTRA 10
DTFLA CIRCUM
240
DTRA -10
DTFLA CENTRE
120
DFLAG RADIUS
DTFLA MIDPOINT
12:25
12 Series
The Dimension Text Angle (DTANGLE) attribute controls the Dimension text angle.
Possible settings are:
DTANGLE STANDARD
DTANG HORIZ
DTANG VERT
The default setting of DTANG is STANDARD. In this case the text is orientated radially. See
Figure 12:25.: Radial Dimensions - DTANG Setting for the effects produced by changing
DTANG.
DTANG STAN
DTANG HORIZ
DTANG VERT
The Dimension Text Offset (DTOF) attribute defines the displacement of the text position
from the text radial position. DTOF is a 2-dimensional array attribute. DTOF(1) defines the
displacement along the text path direction (i.e. Radial, Horizontal or Vertical depending on
the DTANG setting), and DTOF(2) in the text upvector direction. The default/initial value of
DTOF is (0,0).
Further control of the text position in the upvector direction is given by use of the vertical
alignment attribute ALIG. The actual position of the text for DTOF(2)=0 will depend on the
value of ALIG. This allows you to align text independently of the character height DTCH.
See Label Text Manipulation for further details of ALIG.
The second component of text offset, DTOF(2), is always applied in the upvector direction.
Its value may be positive, zero or negative. See Figure 12:26.: Radial Dimensions DTOF(2) Setting for the effects produced by changing DTOF(2).
As an alternative to entering two values, DTOF may be set using the cursor, i.e.
DTOF @
Note: In Figure 12:26.: Radial Dimensions - DTOF(2) Setting, ALIG=BBODY unless
otherwise indicated.
12:26
12 Series
DTANG STAN
DTOFF 0 0
DTANG STAN
DTOFF 0 5
DTANG STAN
DTOFF 0 -5
DTANG STAN
DTOFF 0 -5
ALIG TBODY
DTANG HORIZ
DTOFF 0 0
DTANG HORIZ
DTOFF 0 5
DTANG HORIZ
DTOFF 0 -5
DTANG HORIZ
DTOFF 0 -5
ALIG TBODY
DTANG VERT
DTOFF 0 0
DTANG VERT
DTOFF 0 5
DTANG VERT
DTOFF 0 -5
DTANG VERT
DTOFF 0 -5
ALIG TBODY
The definition of the direction of application of the first component, DTOF(1), is more
complex:
For DTANG STANDARD and text outside the circumference (i.e. DTFLAG CIRCUM,
positive DTRAD), DTOF(1) is in the direction of the radial displacement outwards from the
text radial position. (In this case, it is preferable to modify the text radius (DTRAD) rather
than DTOF(1); DTOF(1) is best left set to zero).
For DTANG HORIZONTAL and text outside the circumference, DTOF(1) is horizontal from
the text radial position. In this case, the sign of DTOF(1) is determined by the DDEG
attribute; for DDEG between -90 and +90, positive DTOF(1) adjusts the text position to the
right of the radial position of the dimension text; for DDEG between 90 and 270, positive
DTOF(2) adjusts the text position to the left. See Figure 12:27.: Radial Dimensions DTOF(1) Setting - Text Outside Circumference.
Similarly, for DTANG VERTICAL and text outside the circumference, DTOF(1) moves the
text up for DDEG between 0 and 180; and down for DDEG greater than 180 and less than
360.
12:27
12 Series
DTANG STAN
DTRAD 50
DTANG STAN
DTRAD 55
DTANG STAN
DTRAD 45
DTANG HORIZ
DDEG 45
DTOFF 0 0
DTANG HORIZ
DDEG 45
DTOFF 5 0
DTANG HORIZ
DDEG 45
DTOFF -5 0
DTANG HORIZ
DDEG 135
DTOFF 0 0
DTANG HORIZ
DDEG 135
DTOFF 5 0
DTANG HORIZ
DDEG 135
DTOFF -5 0
In all three DTANG cases, if the text lies inside the circumference, the direction in which
DTOF(1) is applied is reversed. DTOF(1) is always applied in the direction away from the
Circumference.
Thus for DTANG Horizontal and DDEG=45, when the text is outside the circumference then
DTOF(1) adjusts text to the right. However when text is inside the circumference, then
DTOF(1) adjusts text to the left.
For DTANG Standard, then DTOF(1) would move text radially outwards for text outside the
circumference; and inwards for text inside the circumference. However in this case it is
better to leave DTOF(1) set to zero and modify the text radial position DTRAD. See Figure
12:28.: Radial Dimensions - DTOF(1) Setting - Text Inside Circumference.
12:28
12 Series
DTANG HORIZ
DDEG 45
DTOFF 0 0
DTANG HORIZ
DDEG 135
DTOFF 0 0
DTANG HORIZ
DDEG 45
DTOFF 5 0
DTANG HORIZ
DDEG 45
DTOFF -5 0
DTANG HORIZ
DDEG 135
DTOFF 5 0
DTANG HORIZ
DDEG 135
DTOFF -5 0
The Dimension Style (DSTYLE) attribute, combined with DTANG, controls the overall
dimension style. Possible settings are:
DSTYLE DIMLINE
DSTYLE LEADERLINE
DSTYLE EXTERNAL
The default setting of DSTY is DIMLINE. This style shows a radial dimension line with
terminators. For DFLAG DIAM this is drawn across the diameter with two terminators; for
DFLAG RADI this is drawn from the centre to the circumference with a single terminator.
(See Figure 12:23.: Radial Dimensions - DFLAG Setting.) If the dimension text lies inside
the circumference, then the dimension line will be gapped if the text crosses it. The position
of dimension text is controlled by the Dimension Text Offset (DTOFF) attribute - see earlier
in this Section.
The dimension line will be extended beyond the circumference of the object dimensioned if
the text radial position (DTRAD attribute - see earlier in this Section) lies outside the
circumference. If the text is horizontal, then a horizontal line will be drawn from the radial
dimension line to the actual text position. Whatever the text orientation, the line will be
extended to underline the text if indicated by the DTUL attribute (see below).
The LEADERLINE style shows a radial leaderline from the circumference to the text radial
position. If the text is horizontal, then the leaderline will be extended horizontally to the text
offset position. No dimension-line will be drawn.
Text underlining will be controlled by the Dimension Text Underlining attribute, DTUL. This
indicates whether the leaderline is extended to underline the text or not. If DTUL is ON, the
leaderline will always be extended to underline the text even if this causes it to pass through
the text string. The line will be drawn through the text offset position - thus there will be
overlining for ALIG TBODY. DTUL is ignored for DSTYL DIMLINE unless the text radial
position is outside the circumference. The default setting will be OFF.
See Figure 12:29.: Example RDIMs in LEADERLINE Style for examples of the
LEADERLINE style (all shown with DTUL ON).
12:29
12 Series
240
240
DTANG STAN
DTOFF 0 0
DTFLAG CENTRE
DTRAD 0
DTANG STAN
DTOFF 0 0
DTFLAG CIRCUM
DTRAD 5
DTANG HORIZ
DTOFF 5 0
DTFLAG CENTRE
DTRAD 0
DFLAG RADI
DTANG HORIZ
DTOFF 5 0
DTFLAG CIRCUM
DTRAD 10
The EXTERNAL style is a variant on the Dimline style. For Diameter dimensions, two short
radial lines are drawn outwards from the circumference with terminators on the
circumference. If the text radial position lies outside the circumference, then one line is
extended to the text offset position (with optional text underlining).
For Radius dimensions with EXTERNAL style the appearance depends on the text radial
position. If it lies inside the circumference, then a single short radial line is drawn outwards
from the circumference with a terminator on the circumference.
If the text radial position lies outside the circumference, then the dimension is drawn exactly
the same as in the DIMLINE style except that the terminator direction is flipped to be outside
the dimension line. See Figure 12:30.: Example RDIMs in EXTERNAL Style for examples of
the EXTERNAL style (all shown with DTUL ON).
240
240
DTANG STAN
DTOFF 0 0
DTFLAG CENTRE
DTRAD 0
DTANG STAN
DTOFF 0 0
DTFLAG CIRCUM
DTRAD 5
DTANG HORIZ
DTOFF 5 0
DTFLAG CENTRE
DTRAD 0
DFLAG RADI
DTANG HORIZ
DTOFF 5 0
DTFLAG CIRCUM
DTRAD 10
12.3.3
12:30
12 Series
The Dimension Line Style and Colour attributes (DLSTYLE, DLCOLOUR) control the
appearance of the dimension and leader lines. The initial values are cascaded down from
LAYE level. See Colours and Styles for details of colours and line styles.
The Gaps array attribute GAPS - an array of user-defined gaps; no gaps by default. The
gaps defined in this array will be applied to the dimension- and leader lines of the Radial
Dimension. This is in addition to the gap under the dimension text that is inserted
automatically in the dimension line. See Detail Attributes of Linear Dimensions for details.
The command:
GAP TIDY
deletes unused gaps.
Dimension Text will also have the following attributes, similar to those in use for LDIMs and
ADIMs:
12.3.4
Font DFONT
CHOSHT @
Angle Subtended ASUB - default 0. This controls the angle subtended by the optional
projection arcs at the circle circumference. For DFLAG DIAMETER two arcs are drawn,
one at each end of the dimension-line; for DFLAG RADIUS only one arc is drawn. The
midpoint of these arcs will intersect the dimension-line. Note that ASUB=180 generates a
circle for a diameter dimension.
Projection Line Style/Colour (PLSTYLE/PLCOLOUR). These control the appearance of
projection arcs.
For details of setting colour and style attribute values see Colours and Styles.
12:31
12 Series
12.3.5
DIM @
will cause both dimension angle DDEG and text radius DTRAD to be defined in one go.
(The dimension text origin will be at the cursor crosshair position.) It will not modify DTOF.
12.3.6
MODIFY @
Having made the dimension you wish to modify the current element, giving this command
causes the Dimension Modification Form to appear, and the selected dimension is
highlighted with four pickable hot spots that allow modification of the DDEG, DTRA and
DTOF attributes of the dimension. In addition, DTANG can be modified using the Text angle
option button.
To modify the dimension, click on the hot spot(s) that you wish to move, click on the new
position (a transient image of the dimension will appear, which will move as the mouse is
moved), then click on OK on the form. (Cancel allows the command to be aborted with no
change to the dimension; Reset causes the position of the current hot spot to be reset to its
database position; Delete causes the current hot-spot to be deleted or set to a default
position.)
The form also contains the point construction Option list button that allows positions to be
defined in terms of end-points, intersection points, etc.
12.4
12:32
12 Series
defines the value reported in the dimension text. This is consistent with the functionality for
Linear Dimensions (LDIMs) with Direction TRUE (see Principal Attributes of Linear
Dimensions).
12.4.1
NEW PDIM
Create PDIM
PCEN IDP @
PCIRC IDP @
NEW PDIM
PCEN POS @
PCIRC IDP @
The PCENTRE command defines or redefines the centre point of a PDIM. For example:
PCEN IDP @
PCEN IDPL @
PCEN IDPD @
PCEN POS @
12:33
12 Series
PCEN @
If the existing centre point is the wrong database type, then this command will delete it and
create a point of the correct type.
The PCIRCUMFERENCE command defines or redefines the Circumference point of a
PDIM:
PCIRC IDP @
PCIRC IDPL @
PCIRC IDPD @
PCIRC POS @
DDEG TRUE
will change DDEG so that the dimension line passes through the circumference point.
A PDIM may be defined using two cursor hits. These define the Dimension Points and set
DDEG for a PDIM but do not set DTRAD.
Example:
12.5
Angular Dimensions
12.5.1
12:34
12 Series
The dimension origin may either be defined explicitly by attributes of the ADIM or implicitly
by the intersection of two dimension directions. These are illustrated by Figures 12:32 and
12:33.
Figure 12:32. Single Value Angular Dimension with origin defined in database
Figure 12:32 shows an Angular Dimension with its origin defined as a Nozzle in the centre of
the vessel. The two dimension directions are both defined as directions from the ADIM's
origin to the origins of Nozzles. This Angular Dimension could be created by typing the
following commands, starting at Layer level:
NEW ADIM
ON ID @
FROM @ TO ID @
DPOS @
Having pressed Enter when the confirmation command line appears, the Dimension will
appear on the display. A pair of Dimension Direction elements will have been created, with
the last direction becoming the current element.
In this example the ID @ commands could all be replaced by IDP @. This would allow ppoints to be nominated instead of Design items.
The ON command sets the DDNM attribute of the ADIM to the name of the Design element
at the Dimension origin. The NPPT attribute of the ADIM is set to the nominated p-point. If
none is defined (as in this example) NPPT will be set to a default value that equates to the
origin of the element named by the DDNM.
In this example the Dimension Directions will be DPPT elements: these also have DDNM
and NPPT attributes. In this case DDNM is set to the name of the Design element specified
by the FROM or TO keyword, and NPPT to the nominated p-point (or the origin by default).
The DPOS @ command, which allows the position of the Dimension Arc to be defined, sets
the DPOS attribute of the Angular Dimension. Alternatively the Arc radius could be defined
by setting the Dimension's DOFF attribute. For convenience both these attributes can be set
12:35
12 Series
at members of the Angular Dimension. They are mutually exclusive: setting one will cause
the other to be unset.
For the Angular Dimension shown in Figure 12:32 the Q DESCription command will
typically give:
On /C1101-N6
Dimension points
1 DPPT From /C1101-N1
2 DPPT To /C1101-N10
Figure 12:33. Single Value Angular Dimension with origin defined by intersection
Figure 12:33 shows an Angular Dimension with its origin defined implicitly by the
intersection of the two Dimension directions, which are plines of SCTNs.. This Angular
Dimension could be created by typing the following commands, starting at Layer level:
NEW ADIM
DPOS @
Having pressed Enter when the confirmation command line appears, the Dimension will
appear on the display. The position of the Dimension's origin will have been automatically
calculated from the intersection of the two Dimension Directions. A pair of Dimension
Direction elements will have been created, with the last direction becoming the current
element.
In this example the DIR IDPL @ commands could be replaced by either of:
DIR IDP @ in which case the nominated p-points will be used to define directions;
DIR ID SCTN @ in which case the NA pline of the nominated SCTN will be used.
In this example the DDNM and NPPT attributes of the ADIM are left unset. The Dimension
Directions will be APPT elements: these have DDNM, PPDI, and PKEY attributes. In this
12:36
12 Series
case DDNM is set to the name of the Design element specified by the FROM or TO
keyword, and PPDI or PKEY to the nominated p-point or pline as appropriate. PPDI and
PKEY are mutually exclusive: setting one will cause the other to be unset.
Plines and p-points define specific directions (eg UP) but in some cases when defining
Angular Dimensions it is the 'reversed' direction that is required (eg DOWN). This can be
achieved by the use of the REVDIR attribute of APPTs. By default this is False (or OFF) and
the direction of the specified pline or p-point will not be reversed when drawing the Angular
Dimension. If the reversed direction is required it should be set True (or ON).
When using two intersecting APPTs to define an Angular Dimension there are four possible
quadrants in which the Dimension Arc will be drawn. All four possibilities can be obtained by
setting the two REVDIR attributes appropriately. However the required result can be
achieved automatically by setting the DPOS attribute. From the DPOS coordinates DRAFT
will calculate and set the REVDIR attributes of the two APPTs.
For the Angular Dimension shown in Figure 12:33 the Q DESCription command will
typically give:
Position unset
Dimension points
1 APPT From Direction Ppline NA of /F-2
2 APPT To Direction Ppline MEML of /F2-BRAC-1 Reversed
Note: The direction of the second APPT has been reversed by the action of the DPOS @
command so that the Dimension Arc is drawn in the required quadrant.
The other types of Dimension Direction that may be owned by an ADIM element are:
NEW ADIM
ON ID @
FR POS @ TO POS @
Here the FROM and TO commands set the POS attribute of each DPOI to the position
defined by the cursor.
ADIR elements would be created by a sequence such as:
NEW ADIM
ON ID @
FR DIR N30E TO DIR S20W
The DIR attribute of each ADIR will be set to the specified direction.
In each example above, the FROM keyword defines the Direction at the start of the
Dimension's member list, TO defines a Direction after the last item in the list. The Directions
will be drawn in the order in which they appear in the list, and the rotational direction
between the Directions is determined by the minor arc between the first two Directions.
The above examples show the easiest way of creating ADIM elements, but many other
methods are available. The dimension origin can be defined explicitly as a 3D point, as a ppoint, as a proportional distance along a pline, as a Branch Head or Tail, or as (the origin of)
any Design element.
An example of a multi-valued chained Angular Dimension is shown in Figure 12:34.:
Chained Angular Dimension.
12:37
12 Series
Such a dimension is created in a similar way to a chained Linear Dimension. Notice how the
Dimension Arc text is (automatically) oriented and positioned relative to the Dimension Arc
so as to make it easiest to read.
In this example the PLTX attribute of the ADIM is set to '#DIMDIR' and as a result the
dimension directions appear as projection line text. #DIMDIR is an example of an
intelligent text codeword - see Intelligent Text. #DIMDIR is valid in the PLTX of ADIM
elements and their four potential member types.
For the Angular Dimension shown in Figure 12:34 the Q DESCription command will
typically give:
On P 0 of /C1101-N6
Dimension points
1 DPPT From /C1101-N1
2 DPPT To P 0 of /C1101-N8
3 ADIR To E
4 DPPT To /C1101-N10
5 DPPT To P 0 of /C1101-N12
Additional 'links' can be inserted in or added to a chained Dimension (or a single-valued
Dimension can be 'converted' to a chained Dimension) by using the INSERT command in a
similar way to Linear Dimensions.
The SORT DIM command can also be used with Angular Dimensions to reorder any
incorrectly ordered Directions.
An example of a parallel Angular Dimension is shown in Figure 12:35.: Parallel Angular
Dimension.
12:38
12 Series
A parallel Dimension can be produced simply by setting the LCHA attribute of an ADIM to
False (a chained dimension has LCHA True).
12.5.2
12:39
12 Series
DOFF for an Angular Dimension is the radius of the dimension arc and is set by the DIM
RAD command (cf DIM OFFS). Clearly, the PLDI (projection line direction), DIR (projection
line direction) and TLIN (true length) attributes do not apply to Angular Dimensions.
The SENSE attribute enables the rotational direction of the Dimension to be changed. The
standard value is that given by the minor arc from the first to the second dimension point.
The rotational sense may be altered by using:
SENSe REVerse
The standard sense may be restored using:
SENSe STANdard
Important: This attribute should be used with caution. It is primarily intended for use with
parallel Dimensions or those containing two points only. Chained or truncated
Dimensions with more than two points will contain overlapping arcs.
It is also possible to specify an explicit rotational sense:
SENSe CLOCkwise or SENSe ANTIclockwise
However, standard or reverse sense should be used with parallel dimensions.
12.5.3
12:40
12 Series
The DTANGLE (Dimension text angle) attribute is available for Angular Dimensions and
their Dimension Points. However, the settings are restricted to the following:
DTANG
DTANG
DTANG
DTANG
HORIZ
VERT
STAN
DEF
The meanings of these settings are similar to those for Linear Dimensions (see Detail
Attributes of Linear Dimensions).
12.6
Identifying Dimensions
The cursor may be used to identify Dimensions and Dimension Points/Directions as follows:
ID LDIM @
ID ADIM @
ID @
12.7
DLFG PROJ
causes only the projection lines of a Dimension to be drawn. The setting of the LCHAIN
attribute is ignored in this case - all dimensions are treated as chained. This enables
coordinate dimensions to be output - with the coordinate reported in the projection-line text.
DLFG DIM
causes only the dimension lines of a Dimension to be drawn. The default setting, causes
both dimension- and projection lines to be drawn:
DLFG ALL
12.8
For a GRIDLN that passes through a VIEW, DRAFT considers the 2 intersections that it
will make with the VIEW boundary to be ppoints 1 and 2, and the mid-point between
them to be ppoint 3. Dimension points (ie DPPTs) can be attached to these 'ppoints' (ie
attribute NPPT). The default dimension point position (ie NPPT -1) is at P3.
12:41
12 Series
For a GRIDLN that does not pass through a VIEW ppoints 1, 2, and 3 are not defined.
The default dimension point position (ie NPPT -1) is at P0.
It must be stressed that this concept of ppoints on GRIDLNs applies only in DRAFT. These
ppoints only have World positions, their directions are not defined. Ppoint markers are
generated by the Update Design process and can be identified by the 'IDP @' command in
the normal fashion.
12.9
NEW LDIM
FROM valve_id
NEW DPOI
RULE SET POS
12:42
12 Series
FROM ID @
TO ID @-
INSERT ID @
TO AFT ID @
TO BEF ID @
TO POS @
TO IDP @
TO IDPL @
DPOS @
DOFF value
DIM OFFS
DIM ABS
SORT DIM
DIR value
PLDI value
DIR TRUE
- set dimension line direction to be that calculated from the first &
second p-points - sets TLIN true
12:43
PLDI
12 Series
NEW RDIM
ON ID @
AKEY word
DIM @
- defines both dimension angle DDEG and text radius DTRAD in one
go. (Dimension text origin will be at cursor crosshair position.)
MODIFY @
NEW PDIM
- creates PDIM
PCEN IDP @
PCIRC IDP @
NEW PDIM
PCEN POS @
PCIRC IDP @
PCEN IDP @
PCEN IDPL @
PCEN IDPD @
PCEN POS @
PCIRC IDP @
PCIRC IDPL @
PCIRC IDPD @
PCIRC POS @
12:44
12 Series
ON ID @
- creates a Dimension start point with the direction set as the ppoint specified - sets DDNM & PPDI, or if direction specified - sets
DIR. options: PA, PL, PH, PT, PPoint, IDP, N, S, D, E, W, X, Y, X,
HH, HT
TO DIR option
first
SENSE REV
SENSE STAN
DTOF option
STAN
- sets to 0 0
DEF
DTOF N 1 @
DTOF N 2 5
DMTX text
DTCH value
DTLH value
DLSTYLE value
DLCOLOUR value
DLSTYLE DEF
DLCOLOUR DEF
DTCOLOUR value
DTCOLOUR DEF
12:45
12 Series
DTANGLE STAN
DTANG HORIZ
DTANG VERT
DTANG EXTERN
DTANG PARA
PTANG DEF
PTOF option
STAN
- sets to 0 0
DEF
PTOF N 1 @
PTOF N 2 5
PLTX text
- set projection text as text string. Unsets from #DEF (i.e. #DIM)
PTCH value
PTCH DEF
PTLH value
PJUS option
TOW
AW
C
DEF (default)
PTCOLOUR value
PTCOLOUR DEF
PLSTYLE value
PLCOLOUR value
PLSTYLE DEF
PLCOLOUR DEF
PTANGLE HORIZ
12:46
12 Series
PTANG VERT
PTANG STAN
PTANG DEF
GAP @
GAP AT @
GAP AT @ L value
GAP DELETE @
GAP TIDY
LCHA PARA
LCHA CHAI
DMSP value
DMSP @
TRUN BY value
TRUN TO value
DTER option
FTER option
TSIZ 4
OSHT value
OSHT @
PLCL value
PLCL @
12:47
12 Series
DLFG PROJ
DLFG DIM
DLFG ALL
AKEY option
DFLA option
DDEG value
DDEG @
DTFL option
DTRA value
DTRA @
DTAN option
DSTY option
CHSTYLE option
- controls the drawing style used for the optional horizontal and
vertical fixed crosshair markers that mark the centre of the circle/
arc being dimensioned. option = OFF (default), integer or line
pattern.
CHCOLOUR value
- controls the drawing colour for the above. Value can be a colour
number or pre-defined colour name.
CHOS value
CHOS @
12:48
the
12 Series
ASUB value
MODIFY @
12.11.12 Querying . . .
Q DESC
Q SETDEF
Q DDNM X coord
Q DDNM Y coord
Q DDNM X coord Y coord
Q EXTENT DMTX
Q EXTENT PLTX
Q PCENTRE
Q PCIRC
Q AKEYLIST
12:49
12 Series
12:50
12 Series
13
Labelling
Labels are a form of drawing annotation, comprising text and/or graphics, associated with
Design items or Views. The Label elements are the General Label (GLAB), and the Special
Label (SLAB). SLABs are similar to GLABs except that they are generated from templates
rather than individually.
Label elements are owned by Layers or Views; SLAB templates (Text Label Templates,
(TXTMs)) exist as members of Label Libraries (LALBs). The relevant part of the DRAFT
database hierarchy is shown below.
LIBY
LAYE
LALB
GLAB
TXTM
SYTM
DDNM
SLAB
DDNM
TMRF
Design database
element or VIEW
Labels may be created individually, or automatically following the definition of a set of rules
controlling the elements to which the Labels are to be applied (see Autotagging).
Figure 13:2.: A Typical Label Element illustrates a typical Label, showing its principal
features and attributes.
13:1
12 Series
Label Origin. A position within the body of the Label that is used to position it.
Label Position. A 2D position within the VIEW at which the Labels origin is placed;
this may be an absolute VIEW position or a position relative to the Labels attachment
point.
Leader Line. A line from the connection point to the Label attachment point.
Leader Line Connection Point. A position, defined relative to the Label origin, to
which the leader line is drawn.
13.1
13.1.1
NEW GLAB
create new General Label (or NEW SLAB to create a Special Label)
DDNM ID @
position Label attachment point using cursor
13:2
12 Series
The above two commands are all that is needed to create a Label with the features shown in
Figure 13:2.: A Typical Label Element; the text which appears in the Label frame is by
default the name of the Design element at the Label attachment point, all other attributes
having default settings cascaded down from the owning Layer.
The Label attachment point will be at the origin of the element specified by the Labels
Design Data Name (DDNM) attribute.
For elements that have p-points or p-lines the attachment point can be varied by setting the
NPPT or PKEY attributes to the specified p-point number/p-line name respectively.
Example:
NPPT 2
- set NPPT to (p-point) 2
PKEY TOS
- set PKEY to p-line TOS (top of steel)
PKEY MEML
- set PKEY to member line
For elements with p-lines the attachment can be further varied by setting the PKDI p-line
distance) attribute. See P-line Attributes for details.
The ON command allows the DDNM and NPPT or PKEY/PKDI attributes to be set
simultaneously.
Example:
ON
ON
ON
ON
ON
ON
ON
ON
ON
ON
ID@
/PUMP1-1/NOZZ1
IDP @
P2 OF NOZZ4 OF EQUI /1101
PHEAD OF /BRAN2-1
PLEAVE OF /VALVE3
IDPLINE @
PPLINE BOS OF /SCTN.PN1_PN5
IDPDISTANCE @
PPLIN TOS OF /SCTN5 PROP 0.8
With the ON command it is also possible to specify an absolute distance along a p-line,
although the value given will be converted to a proportional value for storage in the
database:
13:3
12 Series
point (although if the clearance attribute (LLCL) is set the leader line will overshoot or stop
short of it). This means that the leader line and its terminator can be moved away from the
p-point to any desired position. By default APOF will be (0,0) - i.e. no offset. APOF may be
set directly, for example:
APOF 15 0
or in terms of Sheet coordinates by:
(or
APOF 0 0
or
APOF UNSET)
The Body Text (BTEX) attribute is by default set to the intelligent text string #NAME, which
translates to the name of the Design element at the attachment point when the Label is
created. If the Design element at the attachment point is unnamed, an error-text string will
appear in the Label frame. This string is customisable and defined by the LAYEs NTEXT
attribute. See Customizing Error Text for further details.
BTEX NOZZLE 2
or can be set using a combination of explicit and intelligent text. For example, the command
Note the special hash-code #/ that generates a new line. See Intelligent Text for a full
description of DRAFTs Intelligent Text System.
The extent of the text defined by the BTEX setting can be queried by
Q EXTENT BTEX
See Text Strings for details.
Label text can be edited through use of the EDTEXT command. For example, if the target
string is NOZZLE 2:
13:4
12 Series
13.1.2
Labelling Views
Labels (GLABs and SLABs) can be applied to Views, allowing View names, scales, etc to be
applied easily. The Label is associated with the View by setting its DDNM attribute to the
View, either directly or using the ON syntax.
Example:
DDNM View
ON /View99
13.1.3
OFFSET
ABSOLUTE
AT X300 Y200
XYPS 20 20
Note: When a Pipe element is labelled directly, the Pipe origin is assumed to be the
position of the HEAD of the first Branch visible in the VIEW region, if any. If no
Branch HEADs are visible in the VIEW region, then the position of the HEAD of the
first Branch is used.
Constructed points (see Point and Line Construction) may also be used for Label
positioning operations. See Summary of Commands section at the end of this Chapter for
examples.
13:5
12 Series
Labels may be oriented by the ANGLE command, which sets the Labels ADEG attribute if
an angle is specified explicitly, or the PPDI attribute if the orientation is specified as a p-point
direction. (The p-point must belong to the associated Design item DDNM but need not be
the same as the Labels attachment point). For example:
ANGLE 30
ANGLE IDP @
ANGLE P2 OF BOX 1 OF
/1502B
ANGLE PPLIN NA OF
/SJ1-1
13.1.4
LFRA ON
LFRA OFF
The appearance of the frame is controlled by the LFSTYLe and LFCOLOur attributes. For
example:
LFSTYL DASHEDMED
LFCOLO 4
For further details of linestyle and colour functionality see Colours and Styles.
The clearance between text and frame is controlled by the GBOX attribute (default 1mm).
Figure 13:5.: Frame Clearance shows the effect of changing GBOX from 1mm to 4mm.
13:6
12 Series
13.1.5
Hiding Labels
A Labels visibility is controlled by its LVIS attribute:
LVIS TRUE
LVIS FALSE
This facility could be used to hide labels attached to obscured Design elements.
13.1.6
LHEI
CSPA
LSPA
Initial (default) values of all these attributes are cascaded to GLABs from their owning LAYE.
All the above attributes are set directly, for example:
CHEI 6
CSPA 1
LSPA 1
The character height and letter height attributes are discussed further in Miscellaneous Text
Facilities.
CSPA and LSPA may be given negative values. For CSPA, small negative values (of the
order of -.1) will cause text to become compressed (values much smaller than this are not
useful). For LSPA, values of the order -.1 will compress lines; values of the order -3 will
reverse the order of lines. (Limits are -10 to +10 for LSPA, -0.5 to +10 for CSPA.)
13:7
12 Series
Figure 13:6.: Label Text - Character Spacing and Line Spacing illustrates the effects of
varying the character spacing and line spacing.
Text justification and vertical alignment are controlled by the settings of the JUST and ALIG
attributes, which may have the following alternative settings:
JUST L
JUST C
JUST R
ALIG BB
ALIG HB
ALIG TB
ALIG BASE
Text aligned with base of first character (on first line of text)
Here, horizontal justification is relative to the Label origin, vertical alignment is relative to the
text body - the area occupied by the text. The text base ignores text descenders (for
example, the tail of a p or a y).
Figure 13:7.: Horizontal Justification and Vertical Alignment illustrates the effect of varying
these attributes.
13:8
12 Series
ALIG BBODY
ALIG BASE
The Label FONT attribute controls the Label text font - see Miscellaneous Text Facilities for
details of text fonts.
The TXCOLOUR attribute controls the text colour - see Colours and Styles, for details of
style and colour settings.
13:9
12 Series
13.1.7
Leader Lines
The label leader line may be drawn or omitted. This is controlled by the LLEAder attribute.
For example:
LLEA OFF
LLEA ON
The leader line may terminate with an arrow, a dot or nothing, at a definable distance from
the attachment point; this distance may be specified by setting either the leader line
clearance attribute (LLCL) or the attachment point offset (APOF) a position.
The terminator is controlled by the LTER attribute:
LTER ARROWS
LTER DOTS
LTER OBLIQUE
LTER OFF
These commands set the Labels LTER attribute, which is set to no terminators by default.
The size of the terminator is controlled by the TSIZ attribute:
TSIZ 4
The initial settings of LTER and TSIZ are cascaded down from LAYE level.
The leader line clearance (attribute LLCL, 0mm by default) is set as follows:
LLCL 4
clearance 4mm
The attachment point offset (APOF), unset by default, is set by commands such as:
APOF 3 0
Labels also have a POS attribute, which by default is unset. If the POS attribute is set, the
3D World position specified will be used as the leader-line attachment point (rather than the
DDNM and NPPT or DDNM, PKEY, and PKDI attributes). A DDNM attribute still has to be
specified for the label to be properly defined. This allows labels to be positioned at a
calculated position (for example, in the centre of a Panel or half-way along a GENSEC)
without having to determine the most suitable p-point or pline to reference.
The leader line may be straight or bent, with one or two bend point positions specified either
explicitly (by defining either a specific point within the VIEW or an offset from the attachment
point), or implicitly by specifying that the leader line is to contain a vertical or horizontal
portion.
Examples of commands used to specify the bend point explicitly are shown below, with the
results of the commands being shown in Figure 13:9.: Bending the Leader Line.
13:10
12 Series
13:11
12 Series
LEAD BENT @
LEAD BENT PT 2 @
LEAD BENT @ @
LEAD STRAIGHT
The above commands set the Labels LSHA (Leader Line Shape) and BPOF (Bend-Point
Offset) attributes.
When defining two bend-points using a single command, the first point to be defined should
be the one nearest the 3D item labelled. The BPOF attribute stores one or two pairs of
coordinates defining the positions of the bend-points relative to the paper position of the ppoint to which the label is attached. The LSHA attribute defines how the values stored in
BPOF are to be interpreted. These attributes may be set (and queried) directly, for example:
LSHA BENT
BPOF -50 0 -75 25
When defining bend point 2 of two individual bend points, bend-point 1 will be set to Offset
X0 Y0 if it does not already exist. When deleting bend point 1, bend-point 2 (if it exists) will
be made the new bend-point 1.
Depending on the position of the bend point, the leader line connection point may change see the bottom illustration of Figure 13:9.: Bending the Leader Line for an example.
In the case of a bent leader line specified as having a horizontal or bent portion, the bend
point will be at the intersection of the horizontal/vertical part of the line and a sloping line
drawn at a user-specified angle to the attachment point. The first of these two portions to be
specified will be at the end nearest to the attachment point. The portion of the leader line
nearest to the connection point will go to a corner of the Label box if the horizontal/vertical
portion is specified first, or to the middle of a box line if the horizontal/vertical portion is
specified last. See Figure 13:10.: Bending the Leader Line - Horizontal/Vertical Portions for
examples of the commands involved and their results.
13:12
12 Series
If a Labels position relative to its attachment point is changed then on Drawing regeneration
the leader line, if bent, will always be drawn specially - you dont necessarily have to
redefine the bend point position.
13.1.8
ABC
CPOF STAN
ABC
CPOF ORIG
ABC
CPOF -3 0
13:13
12 Series
13.1.9
GAP @
GAP AT @
GAP AT @ L 5
GAP OVER @
Insert gap by specifying start and finish points with cursor, and
delete all other gaps in line
GAP DELETE @
GAP TIDY
The default gap length may be set by using the SETDEFAULT GAP command, for example:
SETDEF GAP 5
Gaps in Label leader lines can be sketched and erased in the same way as Dimension
projection line gaps - see Detail Attributes of Linear Dimensions.
MODIFY @
The Annotation Modification Form will appear, and the selected Label is highlighted with
pickable hot spots. These enable the APOF, BPOF, CPOF, XYPS, and ADEG attributes of
the Label to be modified interactively.
Note: For this functionality to be available the Annotation Modification form must be loaded.
The form contains the point construction Option list button that allows positions to be
defined in terms of end-points, intersection points, etc.
To modify the Label, click on the hot spot that you wish to move, and click on the new
position. A transient image of the Label will appear, which will move as the mouse is moved.
You can then do one of the following:
Click on OK on the form, to accept the changes you have made.
Cancel allows the command to be aborted with no change to the Label.
Reset causes the position of the current hot-spot to be reset to its database position; Delete
causes the current hot-spot to be deleted or set to a default position:
The connection point will be set to its default value (i.e. CPOF STANDARD)
13:14
12 Series
13.2
13.2.1
Font
CHEIGHT
Character height
ALIGNMENT
JUSTIFICATION
Text justification
TXCOLOUR
Text colour
LFSTYLE
LFCOLOUR
LLSTYLE
LLCOLOUR
The initial values for these attributes on a newly created SLAB are cascaded from the
owning Layer. See Colours and Styles for more information on colours and line styles.
The text attribute of a TXTM (ie BTEX) can be an explicit or intelligent text string, but in the
latter case the expanded result cannot be shown on the library Sheet (ie LALB). It can only
be evaluated at the SLAB because it will depend upon the SLABs DDNM attribute.
The Example Text attribute (ETEX) of a TXTM is a documentary attribute to allow, for
example, a description of the template.
The ATEX attribute of a SLAB has a special purpose. When the BTEX attribute of the
referenced TXTM contains the hashcode #ATEX it will be replaced by the ATEX value. If
the TXTM does not use #ATEX the SLABs ATEX attribute has no effect. Thus for example
if TXTM /TEMPLATE has:
13:15
12 Series
Then creating a SLAB that references it and setting the ATEX attribute:
NEW SLAB
DDNM /VESS-1
TMRF /TEMPLATE
ATEX 99
will create a label with the text Number 99 attached to /VESS-1.
13.2.2
Text colour
LFSTYLE
Graphics linestyle
LFCOLOUR
Graphics colour
LLSTYLE
LLCOLOUR
Note that a SYTM may be composed of several graphics primitives each drawn in a different
style or colour. Overwriting the SYTM attribute values will cause all the graphics primitives to
adopt the single linestyle or colour specified.
The initial values for these attributes on a newly created SLAB are cascaded from the Layer.
See Colours and Styles for more information on styles and colour.
13.2.3
13:16
12 Series
The SYSZ attribute may be used to change the scale uniformly in both directions, for
example
is equivalent to XYSCALE 2 2
SYSZ 2
Another variation is:
SYSZ @ @
Figure 13:12.: Varying the SLAB XYSCALE attribute illustrates the effects of varying
XYSCALE.
Note: Symbols (SYMB), see 2D Drafting, also have the XYSCALE attribute and may be
manipulated in the same way. XYSCALE is also settable at LAYE level.
XYSCALE 1 1
XYSCALE 1 2
XYSCALE -1 1
XYSCALE 2 1
XYSCALE -1 1
XYSCALE -1 -1
13.2.4
A CIRC primitive, and the SLAB is drawn undistorted (i.e. its XYSC values are equal)
then the leaderline will terminate at the CIRC.
A RECT primitive, then the leaderline will terminate at the nearest corner of the RECT.
A TEXP primitive, then the leaderline will terminate at the nearest corner of the text
box, as occurs with GLABS.
13:17
12 Series
The CPOF attribute can be set explicitly or by using the LEADERLINE CONNECTION
syntax. For example:
LEAD CONN @
CPOF 10 -10
CPOF STAN
CPOF ORIG
The values stored in CPOF define the coordinates of the connection point relative to the
templates origin and they are in the axis system of the template. Hence if the SLABs
orientation is changed the connection point will rotate with it.
For SLABs defined by a SYTM having a TEXP as its first member the leader-line will
terminate at the appropriate corner of the text-box (as occurs with GLABs) unless the
SLABs CPOF attribute defines a specific leader-line connection point.
Note: The CPOF attribute for a SLAB is an offset from the Label origin. For a SLAB that
references a TXTM, this is defined by the JUST and ALIG attributes of the TXTM.
Hence if the JUST or ALIG components of a TXTM are modified the leaderline will be
connected to a different part of the Label.
The selection system makes it possible to do a global change on the CPOF attribute
of all SLABS that use a given TXTM, using a macro such as:
13.3
Autotagging
DRAFTs autotagging facility enables you to generate automatically a series of Labels in
one or more VIEWS of a Drawing, having defined a set of rules to control those elements
that are to be labelled and the (common) appearance of the labels.
The automatically generated labels (which may be GLABs or SLABs) can then be
individually edited. For example, it may be necessary to reposition a label or to modify its
leader line. The editing functionality is subject to a few constraints so as to prevent Labels
from becoming out of line with the criteria under which the autotagging process operated.
13:18
12 Series
The autotagging process is under the control of a Tag Rule (TAGR) element. The relevant
part of the DRAFT database hierarchy is shown overleaf.
A Tag Rule exists as a member of a Layer (LAYE) or of a Tag Ruleset (TRST). Tag Rulesets
are owned by Tag Rule Libraries (TRLB).
The Layer element has a Tag Ruleset Reference attribute (TRSF), which if set will refer to a
TRST. All automatically generated Labels will be owned by a Layer. Those Labels within a
given Layer will have been generated either from TAGRs owned by that Layer or from
TAGRs referenced by the Layer via its TRSF attribute.
Having defined a TAGR element, the Labels are generated by giving the command:
UPDATE TAGGING
The UPDATE TAGGING command should be given whenever the Design changes such
that Labels move (but remain within the VIEW), or if the TAGR itself changes.
LIBY
TRLB
VIEW
TRST
LAYE
TAGR
TRSF
TMRF
GLAB,
SLAB or
template
element
IDLN
GLAB/SLAB
GLAB/SLAB
I d List or
DESIGN
element
SORF
SORF
TAGR
TMRF
GLAB,
SLAB or
template
element
IDLN
Id List or
DESIGN
element
13.3.1
NEW TRLB
NEW TRST
NEW TAGR /TR1
13:19
12 Series
TMRF /LAB1
IDLN /ID6
Note: If the TMRF attribute is set to reference a GLAB or SLAB (as opposed to a TXTM or
SYTM) than that GLAB or SLAB must not have been generated by a Tag Rule.
Having constructed the hierarchy and set up the necessary references, the items to be
tagged are defined by the TAG command, which applies to those elements defined by the
IDLN setting. Examples of the use of the TAG command are:
13.3.2
13:20
12 Series
13.3.3
Querying
TMRF and IDLN are queryable in the usual way. With a TAGR as current element, the query
command
Q DESC
will output the tagging rule used.
A description of all tag rules relevant to a Layer (i.e. those owned by it and those owned by
the TRST it references) may be output by:
Q TRSF DESC
13.3.4
(at LAYE)
Label Generation
Having set up a TAGR element and its associated autotagging rules, the Labels are
generated by UPDATE TAGGING command. This is of the form:
In the latter two cases, whether or not an element is excluded depends upon the position of
the p-point to which the Label is to be attached. Note that Labels will be created for
elements that are not drawn because they are obscured by others. If these Labels are not
required it is recommended that they are made invisible by setting LVIS FALSE. Deleting
them will only cause replacements to be generated on the next UPDATE TAGG command.
If a LAYE element is LOCKed then none of its TAGRs will be updated. An UPDATE ALL
command will still cause the annotation of that Layer to be updated. If a GLAB or SLAB,
which needs to be modified or deleted, is LOCKed then it will be UNLOCKed and the
modification or deletion carried out.
When a Tag Rule is updated a second (or subsequent) time, existing Labels will not be
deleted and recreated from scratch unless the OVERWRITE option is used, i.e.
13:21
12 Series
Using OVERWRITE will destroy any editing of individual Labels that may have been done.
Not using OVERWRITE will cause existing Labels to be updated so as to reflect any
changes that may have occurred in the Design database; new Labels will only be created
for those Design elements found without Labels with correctly set SORF attributes. Any
existing Label (with a correctly set SORF attribute) on a Design element which no longer
exists or which no longer meets the criteria of the Tag Rule (see above) will be deleted.
The following example illustrates the effect of updating a Tag Rule a second time (without
OVERWRITE):
VIEW /VIEW1 has an Id List /LIST1 which calls up four Equipments, /VESS1, /VESS2, /
VESS3 and /VESS4. /VIEW1/LAYE1 owns Tag Rule /TR1 which is simply defined as TAG
ALL EQUI. The IDLN attribute of /TR1 is set to /*, i.e. the whole of /LIST1 is to be scanned
and all EQUIs tagged.
When /TR1 is updated for the first time four Labels are created in /VIEW1, one on each of /
VESS1, /VESS2, /VESS3 and /VESS4. For the sake of convenience we shall refer to these
Labels as /LAB1, /LAB2, /LAB3 and /LAB4, although the autotagging process would not
actually give them names.
The following DESIGN and DRAFT database changes are then made:
/VESS1 - unaltered
/VESS3 - deleted
13.3.5
/LAB3 - deleted
/LAB4 - deleted
TAGGING MESSAGES ON
will result in messages being output during a tagging update operation advising of Label
creation and deletion. Other options are:
13:22
12 Series
13.3.6
If a Label with its SORF attribute set is copied, the new Label will have its SORF attribute
set to Nulref.
SORF may be unset by
SORF =0
SORF NULREF
13.3.7
or
13.3.8
DATAL Transfer
Note that since it is not possible to set the SORF attribute (other than to Nulref) it is not
possible to reproduce the link between a Tag Rule and its GLABs and SLABs by DATAL
output. RECONFIGURER must be used for correct transfer of data between databases.
13:23
12 Series
13.3.9
Schedule Generation
Using Autotagging, tabbing in intelligent text, and the PDMS Programmable Macro
Language (PML) it is possible to generate schedules on drawings easily.
The Tag Rules TMRF attribute should reference a GLAB that has been positioned
absolutely (e.g. AT X1000 Y800 ABS) at the top or bottom of the required schedules
position. The GLABs BTEX attribute should contain a number of code-words separated by
tabbing codes (see Tab Generator Codeword). For instance for a nozzle schedule the BTEX
may be
#NAME#15#P1BOR#25#CREF.
This will create a schedule of three fields giving nozzle name, bore, and connection
reference. The second field will start at character column 15 and the third at column 25. The
width of the fields should be made sufficient to accommodate the expanded codewords. The
GLABs FONT attribute should point to a font set up with fixed-width characters (i.e. styles 6
or 7), its CHEI set to an appropriate value, and its leader line and text frame suppressed.
When the Tag Rule is updated all the GLABs generated will be in the same position. A
macro should be written that scans around the Layer looking for GLABs with their SORF
attribute referencing the Tag Rule. Each such GLAB found should be moved up or down
(depending upon whether the template GLAB was positioned at the bottom or top of the
schedule). The size of the move should be calculated from the character height of the GLAB
and its number in the scan.
The macro should also create a TABL element to provide the frame of the schedule and its
horizontal lines, a TEXP element to define the field headings, and vertical STRA elements to
separate the fields. To achieve this it will be found necessary to use the Q EXTENT BTEX
feature (see Entering Text from DRAFT) to determine the lengths and positions of text
strings.
13.4
13:24
12 Series
13:25
12 Series
was used to define a window within which the labels to be repositioned lie. By default, the
Labels will be offset by 25mm (in the X and Y directions) from the Label attachment point.
The SPREAD LOCAL command can be used with the PDMS general selection syntax (see
the DESIGN Reference Manual, Part 2). Other variations of the SPREAD LOCAL command
are:
With remote positioning, labels will be positioned around the VIEW border. It is possible to
define a margin outside the VIEW frame that will define the positioning of the Labels. It is
also possible to define a side of the VIEW frame alongside of which repositioned Labels will
not be placed, and the minimum permissible gap between any two Labels can also be
specified.
Labels will be repositioned at the (allowed) VIEW side nearest to their attachment points.
Labels along the top and bottom sides will be rotated through 90 (readable from the righthand side) unless otherwise specified. To avoid overlapping, some leader lines will be
doglegged at 45.
Examples of the SPREAD REMOTE command are:
Note: All options must be specified on the same command line; the previous SPREAD
parameter settings will not be remembered.
13:26
12 Series
13.5
For a GRIDLN that passes through a VIEW, DRAFT considers the 2 intersections that it
will make with the VIEW boundary to be ppoints 1 and 2, and the mid-point between
them to be ppoint 3. Labels can be attached to these 'ppoints' (i.e. attribute NPPT). The
default label position (i.e. NPPT -1) is at P3.
For a GRIDLN that does not pass through a VIEW ppoints 1, 2, and 3 are not defined.
The default label position (i.e. NPPT -1) is at P0.
It must be stressed that this concept of ppoints on GRIDLNs applies only in DRAFT. These
ppoints only have World positions, their directions are not defined. Ppoint markers are
generated by the Update Design process and can be identified by the 'IDP @' command in
the normal fashion.
13.6
Summary of Commands
13.6.1
ON ID @
specify the Design element for the label attachment - sets DDNM
AT @
offset the Label from the default using the cursor - sets XYPS, OSET
AT @ ABS
absolute position for the Label using the cursor - sets XYPS, OSET
ANG value
FRA option
ON
OFF
13:27
12 Series
13.6.2
JUST option
ALIG option
13.6.3
13.6.4
justify text
options:
BB
HB
TB
BA
LFSTYLE value
LFCOLOUR value
LLSTYLE value
LLCOLOUR value
13:28
12 Series
13.6.5
13.6.6
BTEX text
CHEI value
LHEI value
CHEI TEM
(Special Labels only) - set text height to that of Template (TXTM) element
CSPA value
LSPA value
OFFS
set text position as an offset from the p-point - sets OSET TRUE (default)
ABS
set text position as a specific position on the Sheet - sets OSET FALSE
LEAD option
LTER option
LEAD STRA
TSIZ 4
LEAD BENT @
13:29
12 Series
LEAD BENT PT 2 @
13.6.7
CPOF STAN
CPOF ORIG
LEAD CON @
13:30
12 Series
13.6.8
13.6.9
Setting Gaps . . .
GAP @
GAP AT @
GAP AT @ L value
GAP DELETE @
GAP TIDY
Querying . . .
Q LAB option
Q DESC option
Q TRSF DESC
LEA
leader line
POS
ORIG
origin
ATTA
point annotated
TEX
text
STY
text style
- (at GLAB)
- (at SLAB)
- (at LAYE)
13:31
12 Series
13.6.11 Autotagging . . .
TAG selection_option
sets the CRIT attribute for the current tag rule explicitly
TAGG MESS ON
UPDATE TAGG
UPDATE element_identifier
TAGG
UPDATE element_identifier
TAGG IGNORE
UPDATE element_identifier
TAGG OVERWRITE
13:32
12 Series
14
Intelligent Text
Intelligent text allows data to be automatically extracted from the Design, Catalogue or
Drawing databases and entered on a Drawing. Intelligent text uses codewords, which all
begin with a # character.
Example:
If the data in any of the three databases changes then when the Drawing is updated the
correct new values will be automatically obtained and entered upon the Drawing.
You do not have to navigate through the relevant database, retrieve the data, return to
the DRAFT database and enter the data manually.
The same text string with its embedded codewords can be used many times to
generate text strings that are similar in format but different in detail.
The text strings where you can use intelligent text are:
14.1
DMTX
PLTX
BTEX
Codewords
The codewords fall into one of six categories:
Codewords that access data associated with the Design or Catalogue element
referenced by the DDNM attribute of the Drawing database element. See Accessing
Data from the DESIGN or Catalogue Databases.
Codewords that access data associated with the Drawing database element that owns
the text string. Accessing Data from the DRAFT Database.
14:1
12 Series
14.2
#SITE
#BRAN
#POS
#POSE
#POSN
#POSU
For users that work in XYZ format the alternative codewords: #POSX, #POSY, #POSZ are
provided.
The position attributes that can be modified in this way are: POS, HPOS, TPOS, APOS,
TPOS, NPOS, POSS, POSE, DRPS and DELP. Note that the codeword #POSE can have
two meanings depending on the context: for SCTNs it means the POSE attribute (Section
End Position), in other cases it means the Easting of the POS attribute.
For other position attributes single coordinates can be obtained by using a single index
qualifier. For example:
#GCOFG[2] would provide the Northing (or Y coord) of the Gross Centre of Gravity position.
Only single index qualifiers are allowed, thus: #GCOFG[2,3] will generate an error.
The position codewords generate values in World coordinates. It is possible to generate
values in the coordinate systems of other elements by the use of transform keywords - see
Transforming Position/Direction Data.
Note: As an alternative to the standard ENU or XYZ formats, positions can be output in '+/' format by appending '+' to the codeword. For example:
#POS
#POS+
#POSE+
#POS+[3]
14:2
12 Series
14.2.1
P-point Data
P-point data can be obtained by a codeword of the form:
#Pnxa
For example:
#P3BOR
bore at p-point 3
#PLBOPU
#P1POS
position of p-point 1
Ppoint codewords can have an optional ^ delimiter between the p-point number and the
attribute, for example:
#P2^POS
The delimiter is optional, but it must be used when the number is omitted, for example:
#P^POS
in which case the value from the NPPT attribute of the relevant piece of annotation will be
used.
14.2.2
P-line Data
The P-line syntax may refer to the p-line used for annotation (i.e. that defined by the PKEY
attribute) or to a specified p-line. A specific codeword defining the p-line precedes strings
requesting position, direction and offset.
The syntax for p-lines is
#PK
(for PKEY). This syntax on its own is a request for the p-line name (e.g. NA or TOS, stored
as the PKEY attribute). #PK may optionally be followed by the p-line name, for example
#PKNA for p-line neutral axis. The p-line name (if present) may be 1-4 characters long. #PK
may also be followed by MEML (i.e. #PKMEML) if data for the Sections member-line is
required. (This is only valid if the SCTN has its MEML attribute set.)
The p-line name ma
#PK^DIR
or
#PKNA^POSSU
The last format would mean Upping of Start position of Neutral axis p-line.
The internal delimiter ^ is necessary to separate the p-line attribute from the p-line name.
There is nothing to stop you from having p-line names such as NAPO or even DIR. Names
such as these would be impossible to separate from the p-line sub-codeword without this
delimiter. Spaces are not permitted between the codeword and sub-codeword.
14:3
12 Series
The following sub-codewords may follow the p-line codeword #PK or #PKname:
^DIR
p-line direction
^POSS
^POSSE
^POSSN
^POSSU
^POSE
^POSEE
^POSEN
^POSEU
^PKDI
^PKDIE
^PKDIN
^PKDIU
For example:
#PKNA^POSS
#PK^DIR
The #PK^PKDI keyword will extract the position along a p-line at which a Label is attached.
This will generate the position defined by the PKDI attribute of the label. Thus if PKDI = 0
the Label will be positioned at the start of the p-line (defined by the PKEY attribute) and the
start position will be generated. If PKDI = 0.5 it will be at the p-lines mid-point and its midpoint position generated.
Besides GLABs and SLABs, the VNOT, ADIM, DPPT, RPPT and PPPT elements also
possess the PKDI attribute.
Note: In DRAFT p-lines are always cut back by SCTN end-preparations and member-lines
are always extended to the working point. The positions generated by these
codewords reflect this functionality.
The transform qualifier (see Transforming Position/Direction Data) may be used with any of
these sub-codewords, but not for p-line name. For example:
#PKTOS^POSEU<WRT
/DATUM>
14:4
12 Series
14.2.3
#PKTOS^POSEU+<WRT
/DATUM>
#DERPOS[a]
#PROPERTY^WIDTH
#PRTITLE^WIDTH
The Property Default (PRDEFAULT) and Property Purpose (PRPURPOSE) settings can be
obtained in a similar manner. In each case the first part of the codeword (i.e. PROPERTY
etc) can be abbreviated to four characters.
PROPERTY values are evaluated as distances or bores if the PTYPE attribute of the
relevant DDTA (or DDAT) element is set to DIST or BORE respectively.
14.3
#DRWG
Attributes of other DRAFT elements can be accessed using the FROM qualifier. For
example:
#AUTH<FROM DRWG>
#STITL
#VTITL
14:5
12 Series
Special functionality is provided for the following codewords that extract revision data:
#APPR
Approve
#APDT
Approval date
#RVSN
Revision
#RVDT
Revision date
#RVAU
Revision author
These codewords extract their data from the first REVI element in the Sheets list. If the
qualifier <FR DRWG> is appended then data will be extracted from the first REVI element in
the Drawings list. To extract data from a specific REVI element a qualifier should be used.
The REVI element can be specified by name, for example:
#RVAU<FR/REV3>
or the pseudo-reference array attributes SREVAY and DREVAY can be used. For example:
#RVDT<FR SREVAY[2]>
#APPR<FR DREVAY[3]>
For details of the SREVAY and DREVAY attributes see Drawing Revisions.
For details of the FROM qualifier see Extracting Attribute Data from any Specified Element.
14.4
#DEF
Use default text string supplied by owning ADIM or LDIM (Must appear
alone in a text attribute, e.g BTEX #DEF is valid, name #DEF is not.)
#DIR
The following codewords are valid in the PLTX of LDIMs and their members, and cause the
3D Dimension Point position to be generated in World coordinates.
#DIMPOS
3D position
#DIMPOSE, #DIMPOSN,
#DIMPOSU
#DIMPOSDD
For example, if the Dimension Direction is North, the Northing of the Dimension Position will
be output - i.e. exactly the same result as #DIMPOSN. If the Dimension Direction is not
14:6
12 Series
orthogonal, the full 3D position will be output (i.e. as would be generated by #DIMPOS)
together with error message
64,399: /ldim-name: Dimension direction not orthogonal, so unable to calculate single
coordinate for codeword #DIMPOSDD
These codewords may be used in conjunction with the WRT qualifier (see Transforming
Position/Direction Data) to generate relative positions.
At a DPOI which has POS and optionally DDNM attributes set, #POS will always obtain data
from the element referenced by DDNM. #POS will only obtain data from the POS attribute
setting if DDNM = 0/0. Hence you should always use #DIMPOS to generate the coordinates
of DPOI elements.
The following codeword is valid in the PLTX of ADIMs and their members, and causes the
3D Dimension Point direction to be generated in World coordinates.
#DIMDIR3D direction
No qualifiers may be used with this codeword.
14.5
#:UDA1
All relevant qualifiers (see Substrings - Extracting Attribute Data from any Specified
Element) that apply to ordinary codewords may also be applied to UDAs. The output of data
follows a format similar to that used by existing UDA queries. Real UDA may have distance
or bore units and will be reported as such. Other uses of UDA reporting are described in
Transforming Position/Direction Data.
14.6
#BDATE
#CDATE
#ADATEX
#BDATEX
#CDATEX
DFDATE
#TIME
14:7
12 Series
#SYSUSE
#PROJECT^NUMBER
Project number
#PROJECT^NAME
Project name
#PROJECT^DESCRIPTION
Project description
#PROJECT^MESSAGE
Project message
#PROJECT^CODE
Project code
DEPT and LIBY elements have a DATEFOrmat attribute. It controls the format of the values
of DATE (of DRWGs) and RVDT (of REVIs) attributes which are automatically generated.
DATEFOrmat may be set to:
DDMMYYYY
DDMMYY
MMDDYYYY
MMDDYY
DDMONYYYY
DDMONYY
14.7
14.7.1
Template Codeword
#Tname is the Template codeword, which enables complex text strings to be defined once
in a Text Template (TXTM element). This template may then be referenced from other
elements.
name refers to a text template TXTM. For example:
#T/TEM24
#T may be used in PLTX or DMTX attributes of Dimensions or Dimension Points, or in the
BTEX attribute of Labels (GLAB or SLAB) or text primitives (TEXP).
The codeword #T/name must be the only content of the text string. The referenced text
string may contain intelligent text codeword strings. However the BTEX attribute of a TXTM
cannot itself contain a #T codeword since this could lead to recursion.
14.7.2
14:8
12 Series
The tabbing codeword controls tabbing, taking the form #n, where n is the number of the
column where the next character is to be output. For example:
#NAME#24#CATR
The blanks in the output character string will be padded with spaces. For example:
ABC#10DEF
would appear on a drawing as
ABCvvvvvvDEF
(where v is used here to denote a space). The string
#NAME#15#CATR#25#CREF
would expand (typically) to
/PUMP1/NSvvvvv/NFJJvvvvv/PIPE1-1
If the number specified is already exceeded by the length of the output character string then
a single space will be inserted. For example:
#NAME#5#CATR#10#CREF
would expand to
/PUMP1/NSv/NFJJv/PIPE1-1
Tabbing will take account of linefeeds within the text string, whether specified explicitly or by
the new line generator code #/. Hence
#5#NAME#/#8#CATR#/#8#CREF
would expand to
vvvv/PUMP1/NS
vvvvvvv/NFJJ
vvvvvvv/PIPE1-1
The use of this feature in combination with a fixed-width font (e.g. style 6 or 7) allows you to
arrange text neatly in a tabular form. Used in combination with Autotagging and the PDMS
Programmable Macro Language (PML), it is possible to generate schedules on drawings
easily. See Schedule Generation.
14.7.3
14.7.4
# Character
The codeword ##outputs a single # character.
14:9
12 Series
14.7.5
Underlining
#<
start underline
#>
finish underline
When a GLAB text string has been underlined, GBOX should be set to zero in order for the
leaderline to meet the underline.
14.7.6
%B
%b
%I
%i
The codes above apply only to intelligent text rendered using a TrueType font. They are not
treated as codewords when the AVEVA font is in use. If one of the above codes is used,
when the corresponding style is already set as requested by the codeword, it is not treated
as a codeword.
Note: The TrueType font assigned to the element can be set upfront as Bold or Italic
without having to use the above codes in the string, when selecting a True Type font
from the selection form:
14:10
12 Series
14.8
Substrings
There are two methods of specifying that a substring of the data associated with a code
word is required for output.
14.8.1
(Cn1:n2)
where C indicates that n1 and n2 refer to character positions and n1 and n2 are integers
that indicate the leftmost and rightmost character positions of the substring respectively; if
n1 is omitted then 1 is assumed by default, and if n2 is omitted then the last character of the
string is assumed. For example:
14.8.2
(P-n1:n2)
Here P indicates that n1 and n2 refer to delimiter numbers and - indicates the character
used as the delimiter. If omitted, / is assumed. The delimiter must not be numeric.
n1 and n2 are integers that indicate respectively the delimiter numbers at which the
substring is to start and finish; the delimiter before n1 is always included in the output
substring but the delimiter after n2 is always excluded. If n1 is omitted then the substring will
start at the beginning of the parent string, and if n2 is omitted then the substring will end at
the end of the parent string. The start and end of the parent string are always assumed to
be delimiters. For example:
If #PIPE expands to the parent string /ZONE-4/PIPE-6 then
()
This is shorthand for (C1:)
14:11
12 Series
This form can be used for putting codewords back to back in a text string where the other
codeword delimiters are not suitable, for example, when a space is not required between
codeword data. For example:
14.9
#POS #NAME
would, when expanded, have a space between the two data items:
#POS()#NAME
would not.
Array Indexing
The format used for the array indices is:
[n]
or
[n,m]
where n and m are integers and m is greater than n. The first format generates a single
array element; the second generates a range of array elements. For example:
#CRFA[2]
#:ARRAY[4,6]
Embedded spaces are allowed within an array index but are not mandatory. In the second
format, one of the integers may be omitted. Omission of the first integer implies n=1, and
omission of the second implies m=K, where K is the significant length of the array.
Array indices may be used (where appropriate) with both basic and UDA codewords.
Array indices cannot be used with text, displacement, or direction attributes but can be used
with all positional codewords, refer to Accessing Data from the DESIGN or Catalogue
Databases for more information.
The length of an array attribute can be extracted and applied to a sheet using:
codeword[SIZE]
SIZE may be abbreviated to 'S' and may be lower-case. The [SIZE] suffix may be used with
any hash code-word for which array indices are valid.
#P1POS<WRT /1201A>
This will output the position of p-point 1 of the DDNM element with respect to element /
1201A. The word parameter may either define an element type or a reference attribute, for
example:
14:12
12 Series
#POS<WRT ZONE>
#POSU<WRT OWNE>
If an element type is specified, it must refer to an owner of the Design element specified in
the DDNM attribute. This may be the immediate owner or an element in the database
hierarchy above the DDNM element.
If a reference attribute is specified, it should refer to a reference attribute of the DDNM
element, for example OWNE or CREF. The reference attribute may also be a UDA
<WRT OWNE>
<WRT HREF>
<WRT :uda>
Individual components of reference array attributes may also be used:
<WRT CRFA[3]>
<WRT :UDARR[2]>
The default coordinate system is the Design World - i.e. the implied syntax is:
<WRT WORL>
The qualifier CE must be used to refer to the coordinate system of the current element. For
example, to report the position of P3 of a Box with respect to the Box origin:
#P3POS<WRT CE>
Only position, direction, displacement and orientation codewords may have transform
qualifiers. This includes some P-line and p-point attributes.
When outputting a qualified position in +/- format, the + must appear before the qualifier, for
example:
#P1POSU+<WRT /DATUM>
#POS<FROM /VESS1>
#POSE<FROM SITE>
#DTXR<FROM TUBE>
14:13
12 Series
#HBOR<FROM CREF>
#SPRE<FROM :fred>
#PARA[3]<FROM SPRE
CATR>
#DUTY<FROM CRFA[2]>
The first three examples refer explicitly to elements by name or type. The next three contain
reference attributes of the current element, the referenced element being accessed. The
last is a reference array attribute and must be followed by an array index.
More than one navigation parameter may be used to enable compound navigation to acces
14:14
12 Series
If the navigation qualifier is omitted, the appropriate current element is usually used for data
extraction. However certain codewords extract data from a specific element type rather than
from the current element. An example of this is #PRFL. Data is extracted from the PRFL
attribute of the SUBS element which owns the current element.
Standard Codewords such as #BRAN and #DRWG are equivalent to #NAME<FROM
BRAN> etc.
Pseudo- reference attributes can be used within codeword navigation qualifiers. For
example #XXXX<FR SPREF> will extract the data for attribute XXXX of the element
referenced by attribute SPREF of the current Design element. (Note that SPREF is a
pseudo-attribute of NOZZ as well as being a standard attribute for all Piping Components.)
UCOD CM DIST
UCOD CM BORE
INCH USA
INCH PDMS
INCH DECIMAL
14:15
12 Series
The setting is NOMINAL by default. The UCOD setting controls the bore sizes output to a
drawing by DRAFTs intelligent text system. The two qualifiers have exactly the same effect
as the general PDMS PRECI BORE NOM (or PRECI BORE ACT) commands.
UCOD settings can be queried by using the pseudo-attributes:
Q UCODD
and
Q UCODB
Alternate Units
MM
MM
UCOD INCH US
MM
MM
UCOD FINCH US
MM
UCOD MM
INCH DECI
UCOD CM
INCH DECI
UCOD METRE
INCH DECI
The switch units code is %U so, for example, to generate a dimension in both Imperial and
metric units, with the second value in brackets, the intelligent text string:
#DIM() %U(#DIM())
should be used. The units may be switched back to the standard units by a subsequent use
of a %U code.
14:16
12 Series
Angles output in degrees, minutes or seconds will be in the standard format (i.e. using , or
). Angles output in the decimal format will have no symbols. If required a symbol can be
accessed from DRAFTs alternative character set by using the code ~0.
Data output in metre or centimetre format will be to the precision specified by the PCODE
MM option. Thus if the MM precision is set to 1 dp, output will be set to 4 dp for metre output
and 2 dp for centimetre output.
Four pseudo-attributes exist to allow the querying of the individual parts of the PCODE
attribute:
Q PCODMms
Q PCODInches
Q PCODFractions
Q PCODAngles
REGI
DRWG
SHEE
VIEW
LAYE
LIBY
SHLB
OVER
DRTMLB
DRTMPL
SHTMPL
These two attributes control the output format of the positional codewords that request the
position of certain elements (e.g. #POS, #P2POS, #PKNA^POSS, #PKTOP^POSE).
Test equivalent
(query system)
Description
ENU
XYZ
14:17
12 Series
Value
Test equivalent
(query system)
Description
SHIP
NUM/BERS
If the project does not define the FR or LP positions along one or more of the axes, the
request for a corresponding coordinate expressed in the Ship Reference System will return
instead the coordinate expressed as a pure number in millimetres, as if the XYZ expansion
had been requested (e.g. X=FR40, Y=LP4, Z=5000).
The value of the attribute will cascade down from the DEPT or LIBY element to their child
elements when they are created.
If the + modifier follows the position code word (e.g. #POS+), it overrides the expansion
format setting defined by the LAYE, requesting a purely numerical output (NUMBERS
format). Other than using the + suffix, there is no other way to override the expansion
format individually for a given code word. However, a separate LAYE with different settings
can be created, and the element using intelligent text placed there.
Example:
POSFOR SHIP
sets the output format for positional codewords to ship reference coordinate format.
GRSYS NULREF
tells DRAFT to use all available grid systems with the default orientation (0, 0, 0) and
the purpose SHIP when searching for the nearest GRIDLN element
GRSYS /RO-RO
tells DRAFT to use the grid system /RO-RO exclusively when searching for the
nearest GRIDLN element.
14:18
12 Series
NTEXT No data
NTEXT may consist of up to 12 characters. It is an attribute of DEPT, REGI and DRWG.
LIBY, SHLB, OVER and LAYE elements, and its setting will be cascaded down the
hierarchy.
#CRFA[2]<FROM /VFWA1>
#HREF<FROM OWNE>(P/2:3)
#PKNA^POSE<WRT FRMW>
14:19
12 Series
#PK^POSSE
#POSE
#OWNE<FROM CRFA[2]>
#NAME<FROM CREF
:udarr[2]>
#:FRED[3]<FROM EQUI>
#T/T24
#DTXR<FROM ROD>
#VRAT[1]<FR VIEW> to
#VRAT[1]<FR VIEW>
14.16 Notes
In the codeword descriptions given in this section, the words owner or owning (enclosed
in quotes) refer to the element of the type described equal to or above the referenced
element in the database hierarchy - not necessarily the true owner. Where the word owner
appears (unenclosed by quotes) then this means the true owner.
General points:
All text strings have a maximum length of 1000 characters in unexpanded form, 1500
characters in their expanded form.
Lower case and upper case (but not mixed case) forms of all codewords are valid.
When a piece of text generated from a # code word itself contains a # code (or a ~ code
or % code, see Miscellaneous Text Facilities) then this code is not expanded unless
the original piece of text comes from either a DRAFT or DESIGN database text
attribute or a text user-defined attribute (UDA) from any database.
#NAME
#TREF
#TDIR
#OWNER
#SPREF
#ABOR
#EQUI
#CATR
#LBOR
#PIPE
#POS
#POSa
#HPOSa
#TPOSa
#BRAN
#HPOS
#CREF
#TPOS
#HREF
#HDIR
#PRFL
#FUNC
#PTSP
#DUTY
14:20
12 Series
#DSCO
#INSC
#STEX
#LENG
#BORE
#TEMP
#PRES
#LNTP
#HBOR
#TBOR
#FLOW
#HCON
#TCON
a = N, E or U
Pnxu, where n = integer 0-99 or L or A
x = POS, DIR, BOR, BOP, TOP or CON
u = blank, E, N or U (for x = POS, BOP, TOP only
e.g. P3BOR
#CRFA
#JOIS
#JOIE
#LSTU
#HSTU
#LSRO
#STSP
#MATR
#ISPE
#INRE
#GRA
#FIRE
#ZDIS
#CUTB
#ANTY
#DESC
#FIXT
#NPOS
#NPOSE
#NPOSN
#NPOSU
#POSS
#POSSE
#POSSN
#POSSU
#POSE
#POSEE
#POSEN
#POSEU
#DERCUT
#DERLEN
#DRPS
#DRPSE
#DRPSN
#HSRO
#DRPSU
#DTITL
Drawing title
#STITL
Sheet title
#VTITL
VIEW title
#DRWG
Drawing name
#DIMPOSa
#AUTH
#APPR
approver
#APDT
date of approval
#RVSN
revision
14:21
12 Series
#RVDT
date of revision
#RVAU
revision author
#Tname
template codeword
#/
new line
##
single #
#<
start underline
#>
finish underline
#n
14.17.5 Sub-Strings...
(Cn1:n2)
Substring by characters
(P/n1:n2)
Substring by parts
()
or #codeword[n,m]
where n and m are integers and m is greater than n. The first format generates a
single array element; the second generates a range of array elements.
14:22
12 Series
^DIR
p-line direction
^POSS
^POSSE
^POSSN
^POSSU
^POSE
^POSEE
^POSEN
^POSEU
^PKDI
^PKDIE
^PKDIN
^PKDIU
14.17.10 Querying...
Q EXBTEX
Q EXPLTX
Q EXDMTX
14.17.11 Updating...
14:23
12 Series
UCODE MM BORE
set bores in mm
Q UCODD
Q UCODB
Q PCODMms
Q PCODInches
Q PCODFractions
Q PCODAngles
POSFOR ENU
POSFOR XYZ
14:24
12 Series
POSFOR SHIP
POSFOR NUMbers
GRSYS NULREF
GRSYS name/reference
Note: The GRIDSY attribute is taken into account only if the POSFOR attribute has the
value SHIP.
14:25
12 Series
14:26
12 Series
15
15.1
15.2
AVEVA Fonts
DRAFT makes use of the four AVEVA font families. These can include user-defined fonts,
which can be set up in ADMIN. (See the Administrator Command Reference Manual for
details.).
There are three text font attributes - FONT, DFON, and PFON. These are used to define the
appearance of the various text strings that can appear on Drawings. These font attributes
can be set to 1, 2, 3, or 4 in which case the normal version of the relevant font family will be
obtained. Variations on these normal versions can be obtained by setting the font attributes
to a value obtained from the table below.
Normal
Bold
Upward
Forward
Reverse
Upward
Forward
Reverse
11
12
13
14
15
16
21
22
23
24
25
26
31
32
33
34
35
36
41
42
43
44
45
46
For example, font 35 is variation 5 of font family 3. Variation 5 is always bold and forwardsloping. From the table it will be seen that fonts 11, 21, 31, and 41 are equivalent to 1, 2, 3,
and 4. (For completeness the font attributes can also be set to 10, 20, 30, and 40 which are
also equivalent to 1, 2, 3, and 4). Bold fonts are not provided for all font families. In such
cases the selection of a bold option will result in the use of the appropriate normal font.
15:1
12 Series
15.3
%46
- switch to font 46
%02
%30
%37
%51
%2
%P
%T
%C
Font switching can be prevented and the escape character output by doubling it (i.e. %%).
Invalid codes (e.g. %51) will be output literally. The font switching character sequence does
not have to be preceded or followed by blank characters. For example
ABC%04DEF%pGHI will be output as the 9-character string ABCDEFGHI with the two
sub-strings ABC and GHI in the principal font, and the middle three characters (i.e. DEF)
in variation 4 (i.e. upright bold) of the principal font.
The special handling of the '0' digit (preserving the current font family or variation) applies to
AVEVA fonts only. Since the font numbers 05, 06, 07, 08, and 09 are reserved for TrueType
fonts, the font switching sequences %05, %06, %07, %08, and %09 are interpreted literally,
as the font switch to a TrueType font specified after the '%' character.
15.3.1
BTEX ~I
The tilde may be input as normal text by doubling it (i.e. ~~ produces a single tilde). Normal
text, intelligent text and alternative characters may be input in any combination.
See Figure 15:1.: Alternative Character Set for the full list of available symbols.
15:2
12 Series
Symbol
Code
Meaning
Symbol
Code
Meaning
Footnote symbol
Omega
Centreline symbol
Superscript `1'
Diameter symbol
Superscript `2'
Superscript `3'
Degrees symbol or
superscript 0
E
F
Steelwork Channel
Steelwork Angle
Steelwork H-Section
Steelwork I-Section
Steelwork T-Section
Steelwork L-Section
Mu
Yen sign
Plate symbol
Copyright symbol
<
Left arrow
Hash
>
Right arrow
Up arrow
Trademark symbol
U
V
Down arrow
Line
15.4
Editing Text
Editing a text attribute is achieved through use of the EDTEXT command, which gives a
simple case-sensitive, string exchange facility operating on the attribute in question (see
below).
15:3
12 Series
is the text attribute in question, which can be any DRAFT text attribute,
including the name attributes OSFN and BSFN. If text_type is not
specified, BTEX is assumed.
number
Several editing instructions may be given in the same command line. The command
EDT text_type APP string
will append the given string to the specified text attribute.
The different syntax options of the EDTEXT command are illustrated by the examples given
below.
Target string: The dog, the cat and the rabbit were in the garden
EDT the that
gives:
The dog, that cat and the rabbit were in the garden
The dog, the cat and that rabbit were in the garden
EDT PLTX 3 we a
EDT OSFN A3 A4
Note: When editing intelligent text the intelligent text code itself must be specified, not the
resultant text.
15.5
Querying Fonts
You can display information about all the fonts configured on the system using the
command:
15:4
12 Series
Q FONTS
This may provide, for example the following information:
Fontdirectory /%PDMSEXE%
Fontfamily
1 IR
6 Style
1 Angle
17
Fontfamily
2 IR
6 Style
2 Angle
17
Fontfamily
3 IR
4 Style
3 Angle
17
Fontfamily
4 IR
6 Style
6 Angle
17
(Times)
Arial
TrueType fonts:
(Arial)
The commands
Q FONTS PDMS
Q FONTS TRUETYPE
will show either AVEVA or TrueType fonts only.
15.6
Assigning Fonts
The attributes FONT, DFON, and PFON identify the font to be used for displaying textual
information in a drawing. They can be assigned the font number directly, as in the following
examples:
FONT 1
or
PFON 5
DFON 19
In the above example, the FONT attribute is assigned a AVEVA font no. 1, whereas PFON
and DFON identify TrueType fonts (see the Administrator User Guide).
For TrueType fonts it is possible to preset the fonts as Bold and/or Italic. Therefore:
PFON 1005
PFON 2005
PFON 3005
Note that for AVEVA fonts the font itself determines its style (Bold, Italic, etc.).
For TrueType fonts it is also possible to specify the font by name:
15:5
12 Series
FONT
FONT
FONT
FONT
FACE
FACE
FACE
FACE
'Times
'Times
'Times
'Times
New
New
New
New
Roman'
Roman Bold'
Roman Italic'
Roman Bold Italic'
The addition of the FACE keyword instructs the system to search for the font face name
instead of its description. This new syntax is compatible with the querying syntax:
Q FONTNAME
Q PFONTNAME
Q DFONTNAME
which return the string containing the description of the font followed by the possible 'Bold'
and 'Italic' style descriptions. Note that if the font description is empty, its face name is used
instead.
15.7
Character Height
DRAFT measures character height from the character base line to the top of the character
body. See Figure 15:2.: Character Height.
Top of body
Capitals line
Base line
Bottom of body
Letter
Height
Character
Height
The gap between the capitals line and the top of the character body is 20% of the character
height, so the letter height = 0.8* character height. The gap for descenders between the
base line and the bottom of body is one third of the character height. (These proportions do
not apply to the SCRIPT font.)
Letter Height
Character Height
15:6
12 Series
16
16.1
Basic Annotation
Structural elements, like other Design elements, may be labelled, dimensioned and used in
2D drafting. This means that positions and directions in the Design World must be
obtained for these elements.
Annotation elements which (may) require a 3D position include labels (GLAB, SLAB); View
Notes (VNOT), drafting primitives whose drafting point references (PTRF or PTFA) use a
PPPT (drafting point with design data); Angular Dimension elements (ADIM) and two types
of dimension points: DPPT and DPBA. Dimension points of type DPBA do not require p-line
data since they are concerned with the limits of a Design element.
Annotation elements that require a 3D direction include Linear dimension elements (LDIM)
and Dimension Points of type APPT. In addition, where the direction of a p-line is used for
position on a Label or View Note, it may also be used to define the angle of the Label or
View Note to the horizontal in the view region.
Fittings, Nodes and Joints with p-points are treated in the same way as other elements.
There is no change in the functionality for annotating these.
16.2
16:1
12 Series
When no p-line position is stated explicitly the default value for proportional distance is
used. This default may be altered by using the PKDI SETD command (see P-line Distance).
The initial value is 0.5, meaning the mid-point of the p-line.
16.3
16.4
16:2
12 Series
However, for Labels (GLAB, SLAB) and View Notes (VNOT), there is an additional
possibility. If the p-line is used for position, then the same p-line may also be used instead of
the ADEG attribute to store angle.
The syntax for p-line angle is as follows. This is normally used to set the ADEG attribute:
ANGle PPLINe word OF element_identifier [+] plxyz
ANGle PPLINe word OF element_identifier - plxyz
ADEGrees PPLINe word OF element_identifier [+] plxyz
If p-line is required for angle on a Label or View Note, there is a simple way of setting it. This
is done using the following syntax:
ANGle PKEY
or
ADEGrees PKEY
This command first checks that a p-line is in use for position, and uses it to define the angle
of the Label or View Note.
The ANGle PPLINe syntax may also be used to store p-line for angle in the database.
However this will only be done if both of the following criteria are satisfied:
16.5
P-line Attributes
The syntax for position, direction and angle described above is stored in the database using
the following attributes:
under special circumstances, PPDI will be used to specify p-line for angle.
16.5.1
16.5.2
P-line Name
The p-line name is identified by the PKEY attribute of the annotation element. Where no pline name is specified, the value 0 is taken to mean the neutral axis of the specified Design
element. This may be NA, NAXI or ZAXI as set up in the Catalogue data. The value 0 is the
default value for the PKEY attribute.
The PKEY attribute may be set directly using the following syntax:
PKEY word
The word given should refer to an existing p-line of the Design element, if that is set.
16:3
12 Series
16.5.3
P-line Distance
P-line distance is stored in the PKDI attribute of the appropriate annotation elements (GLAB,
SLAB, VNOT, ADIM, DPPT and PPPT). This stores the proportional distance along the pline from its start. The default value for this attribute may be altered by the user. Its initial
value is 0.5, meaning the midpoint of the p-line.
The PKDI attribute may be set directly using the syntax:
PKDIstance STart
PKDIstance ENd
These commands set the values 0.0 and 1.0 respectively.
PKDIstance [PROPortion] value
This value may also be obtained by cursor using the PKEY and DDNM attributes of the
current element (if suitable):
PKDIstance @
The point input is converted to a proportional distance.
PKDIstance DEFault
This command resets the PKDI attribute to the default value. The default value may be
altered using the syntax:
SETDefault PKDIstance value
The current value of the PKDI default setting may be queried:
Query SETDefault PKDIstance
16.5.4
P-line Direction
No additional attributes are required to define this. The p-line is defined by the PKEY and
DDNM attributes. The p-line direction is along the length of the p-line.
P-line direction is used on LDIM and APPT elements.
16.5.5
P-line Position
P-line position is defined by the p-line attributes PKEY and DDNM, with the addition of the
distance attribute PKDI to define a position on that p-line.
P-line position is used on the following elements: GLAB, SLAB, VNOT, ADIM, DPPT and
PPPT.
16.5.6
P-line Angle
A p-line may be used for angle on the following elements: GLAB, SLAB and VNOT.
It is defined by the p-line attributes (PKEY and DDNM) together with a special value of the
PPDI attribute. The value
PPDI -2
16:4
12 Series
means that the p-line used to position the annotation is also used for angle.
16.6
DRGP=0
DRGP=2
DRGP=1
DRGP=0
(a)
(b)
Users should be aware that using this functionality in non-orthogonal Views may produce
slightly distorted results. This is because when producing the graphics the SCTNs are
'shifted' slightly in the View direction by an amount relative to the SCTN's DRGP value to
allow the hidden-line-removal code to function. Distortion is especially likely to be noticed if
large values of DRGP are used. We would recommend that DRGP values are kept as small
as possible and preferably less than 10.
16:5
12 Series
16:6
12 Series
17
17.1
Using Plotfiles
The command syntax for underlaying and overlaying a plotfile is as follows:
BSHEE FILE /plotfile name
To remove an underlay or overlay from a Sheet, the following commands can be used:
BSHEE UNSET
OSHEE UNSET
Note that BSHEE is valid at LAYE or below, whereas OSHEE is only valid at OLAYs.
An overlay is positioned on the current Sheet by changing the OPOS and OANG attributes
of the Overlay element (see next section), which determine the position and angle
respectively. For example:
OPOS @
Alternatively, file specification and positioning may be combined into a single OSHEE
command, for example:
OSHEE ANGLE 60 @
17:1
12 Series
OSHEE @
OSHEE BY @
17.2
DRWG
LIBY
BSRF
SHLB
SHEE
BSRF
OLAY
BACK
OVER
OSRF
NOTE
VIEW
NOTE
Elements for use as backing and overlay sheets may be created in DRAFT and stored in the
DRAFT database. The relevant part of the database hierarchy is shown DRAFT Database
Hierarchy - Overlay/Underlay Elements.
The SHLB (Sheet Library) exists as a member of a LIBY and is used as an administrative
element to group together BACK (Backing Sheet template) and OVER (Overlay Sheet
template elements.
17:2
12 Series
A BACK would probably be used as a frame sheet and would contain frame lines,
authorisation boxes etc. These would exist as (member) NOTE elements created via
DRAFTs geometric 2D drafting facilities. Any hash codewords defined by TEXP elements
will be expanded when the BACK is referenced. These codewords will typically extract data
from the DRAFT database. See Accessing Data from the DRAFT Database.
OVER elements may also own NOTEs as well as VIEW elements, and would probably be
used to overlay graphic details such as keyplans on drawing sheets. An OVER shares many
of the attributes of a SHEE. Note that Point Construction (see Section 11) can be used to
create BACK and SHEE elements.
Most Overlay Sheet attributes are held by the Overlay (OLAY) element.
BACKs and OVERs are referred to by the relevant drawing Sheets BSRF and the relevant
Overlays OSRF attributes (respectively). (BSRF may also be set at Drawing level.) The
BACK/OVER to be used may be specified by using commands such as:
BSHEE /BS1
OSHEE /OS1
The Overlays OSLV (overlay sheet view layers visible) attribute defines those Layers of
the overlay sheet (i.e. the LAYE element(s) owned by the VIEW(s) owned by the OVER
referenced by the drawing Sheet) that are to be visible.
The Overlays XYSCALE attribute allows independent scaling in the X and Y directions of
the instanced overlay sheet or plotfile. For example:
XYSCALE 2 1
Either or both values may be negative, but zero is not allowed.
Note that when an Overlay Sheet is instanced (i.e. attribute OSRF is set), text is only
affected by the scale in the Y direction. It is not possible to generate backwards or distorted
text. However, when a plotfile is used (i.e. attribute OSFN is set), then there is no such
safeguard and text could be distorted if differing X and Y scales are specified. See also
Scaling and Mirroring Special Labels.
Control of complex overlays may be achieved by using multiple OLAY elements.
The Layers which are to be visible may be referred to either by Layer purpose (i.e. the
PURP attribute) or by their member list position under the VIEW(s) owned by the OVER. Up
to 12 Layers may be made visible at once. The Layers that are to be visible are specified by
a further option of the OSHEET command. For example:
OSHEE ALL
The Design graphics may be made visible by including Layer DESI. If the overlay sheet has
more than one VIEW then the Layer visibility statement will apply across all VIEWs. (It is not
possible to specify, for example, a Layer with PURP DIMS to be visible for /VIEW1 but not
for /VIEW2, assuming both VIEWs own such Layers.) The setting of a Layers LVIS attribute
has no bearing on the visibility questions discussed in this section.
17:3
12 Series
The above functionality is only available when an overlay sheet template reference is used.
No distinction between Layers can be made when using overlay sheet graphics from a file.
17.3
Summary of Commands
17.3.1
Underlays...
17.3.2
17.3.3
BSHEE UNSET
UPDATE BSHEETS
Overlays...
OSHEE UNSET
Manipulating Overlays...
OPOS @
OANG value
OSHEE @
OSHEE BY @
17:4
12 Series
18
2D Drafting
DRAFTs 2D drafting facilities are designed to be complementary to its main drawing
production facilities. 2D drafting allows you to add to drawings such features as notes,
plane and boundary lines, keyplans, tables of symbols etc. In addition, backing sheets,
overlay sheets and symbol templates may be created.
2D drafting shapes (or primitives) may be positioned explicitly, with a cursor hit or by a
construction. Because the principle of point construction can be applied to all DRAFT
primitives that have a position attribute, point construction is described in Point and Line
Construction. 2D positions generated by a cursor hit will be snapped to a grid position if
snapping is ON. See Snapping 2D Points to a Grid.
Note: For 2D drafting purposes, it is possible to enter DRAFT having specified a multiple
database (MDB) that does not contain a DESIGN database. Clearly, in this draftingonly mode, intelligent text that extracts data from a Design database cannot be
used.
18.1
18.1.1
18:1
12 Series
SHEE
SHLB
NOTE
BACK
OVER
VIEW
LAYE
VNOT
VIEW
LAYE
NOTE
NOTE
CIRC
ELLI
RECT
TABL
ETRI
DMND
HEXA
MRKP
STRA
ARC
OUTL
VNOT
TEXP
SYMB
A BACK (backing sheet template) element would probably be used as a frame sheet and
would contain frame lines, authorisation boxes etc. These would exist as (member) NOTE
elements (see below).
OVER (overlay sheet template) elements may also own NOTEs as well as VIEW elements,
and would probably be used to overlay graphic details such as keyplans on drawing sheets.
An OVER shares many of the attributes of a SHEE.
Sheet Note (NOTE) elements exist to own the 2D drafting elements themselves (see The
Drafting Elements). This means that NOTEs can be used to group drafting elements
together - changes to the NOTEs position and orientation will affect all of its member
drafting elements. As well as the basic attributes of XYPS (2D Sheet position), ADEG
18:2
12 Series
(orientation) and LVIS (visibility), NOTEs/VNOTs have a set of attributes that are used to
store defaults values that are cascaded down to their members. These are:
NLSTYLE/NLCOLOUR
FSTYLE/FCOLOUR
MSTYLE/MCOLOUR
TXCOLOUR
Text colour
JUST
Horizontal justification
ALIG
Vertical alignment
FONT
Text font
CHEI
Character height
CSPA/LSPA
Character spacing
The first three are cascaded to geometric primitives and the others to text primitives.
View Note (VNOT) elements are similar to NOTEs, the only difference being that VNOTs
may be positioned using 3D Design World coordinates or on a Design item, p-point or p-line
(or using 2D Sheet coordinates).
Having created a NOTE or VNOT in accordance with the hierarchy shown in Figure 18:1.:
DRAFT Database Hierarchy - Sheet Library/2D Drafting Elements, drafting elements may
be created and manipulated as desired - see The Drafting Elements.
18.1.2
Symbol Templates
User-defined symbols (consisting only of 2D drafting elements) may be created as Symbol
Templates (SYTMs). These can then be picked from a Library sheet element, with position,
size and orientation attributes being altered to suit. The relevant part of the DRAFT
database hierarchy is shown overleaf.
Symbol Library (SYLB) and Label Library (LALB) elements can be regarded as Sheets that
can be displayed in an area view. Symbol Templates can then be created on the Library
sheet using the 2D drafting elements.
Setting the TMRF (Template Reference) attribute of a SYMB (Symbol Instance) element or
SLAB (Special Label) will cause the referenced SYTM to appear on the relevant Sheet. The
Symbol can then be positioned, sized and orientated to suit - see the description of scaling
and mirroring SLAB elements in Scaling and Mirroring Special Labels for details of how to
do this.
18:3
12 Series
SYLB
LAYE
SYTM
SLAB
TMRF
NOTE
LALB
SYMB
SYTM
TMRF
CIRC
ELLI
RECT
TABL
ETRI
DMND
HEXA
MRKP
STRA
ARC
OUTL
TEXP
SYMB
Figure 18:2. DRAFT Database Hierarchy - Symbol Template and Related Elements
18.2
18:4
12 Series
Symbol instances can be nested - the instanced SYTM may itself own SYMBs that
reference other SYTMs. However, second-level and higher SYTMs must be owned by
SYLBs, not LALBs. Any intelligent text codes in TEXPs owned by such SYTMs will not be
expanded.
18.3
2D Drafting Primitives
These are basic geometric shapes that can be drawn on a Sheet or a VIEW Layer. The
primitives exist in the hierarchy as members of NOTEs, VNOTEs or SYTMs.
Primitives that exist as members of VNOTs may have their dimensions and positions
defined in terms of 3D Design values
There are eleven types of geometric primitive element corresponding to the shapes shown
in Figure 18:3.: Drafting Primitives.
Note: The denotes the shapes (default) origin and is not part of the shape itself.
Note: The Outline (OUTL) primitive consists of a number of connected straight lines and
circular arcs, as defined by the user. The shape shown above is an example only.)
18:5
12 Series
As a primitive element is created, its position is stored separately, with a reference to the
position being stored as the primitives PTRF (or PTFA) attribute. An important feature of
this system is that if a series of primitives is created, each primitives position reference (or
drafting point) will (initially) be the same, enabling a series of connected shapes to be
quickly and easily created. For example, the command sequence
18.3.1
18:6
12 Series
18:7
12 Series
OCOD CEN
OCOD @
18:8
12 Series
In this case the Sheet coordinates of the origin remain unchanged and the primitive
moves so as to place itself correctly according to the new origin code.
In either case the origin position may be changed at the same time by using commands
such as
SKETCH ORIGIN
The command
ERASE ORIG
erases the display of the origin(s).
Moving Individual Primitives
Primitives may be moved using commands such as
AT @
AT X300 Y250
POS ID @
POS W5500 N12345 D1200
ON
ON
ON
ON
ID @
IDP @
/PUMP1
P1 OF /PUMP2/NS
BY @
BY X10.5
BY N500 W1200
or
FPT node_identifier
DRAG BY @
DRAG BY X120 Y-45
DRAG BY S3500 D500
18:9
12 Series
DRAG
DRAG
DRAG
DRAG
DRAG
DRAG
TO
TO
TO
TO
TO
TO
@
POS @
IDP @
X120 Y-45
S3500 D500
P1 OF /VESS2/N6
FPT DRAG TO @
(The above DRAG operations have similar interpretations to the AT/ON/BY/POS commands
listed previously.)
Querying Primitives
The primitives with drafting points in common with the current element may be queried by
giving the command
Q COMMON
This lists the primitives that will be dragged with the current element. The primitives that
may be dragged with any named drafting node of a STRAIGHT or an ARC may be queried
by
Q node_id COMMON
where node-id is the FPT or TPT (etc) of a STRAIGHT or ARC.
The origin and position of a primitive may be queried by
Q ORIG
The offset of a drafting node or primitive origin from the note origin may be set and queried:
Q node_id OFFSET
Q OFFSET
node_id OFFSET X value Y value
ORIGIN OFFSET X value Y value
where node_id is the node of a straight or arc primitive, i.e. FPT, TPT, MPT, THPT or CPT.
(See list of DRAG commands above for examples of node_id.)
The principal dimensional and positional attributes of a primitive may be listed by using
the
Q DESC
command at the primitive concerned (or at the owning View Note (position and angle)).
A drafting point on a STRAIGHT, ARC or span of an OUTLINE may be queried using
Q IDNN @
This allows you to pick one of these points by picking an appropriate position on the
primitive. The query reports the appropriate point, the identity of the primitive picked and the
position of the picked point. For example:
18:10
12 Series
For STRAIGHTS and ARCS, the point identified will be the same as that returned by the Q
IDN @ command where the current element is a STRA or ARC. Q IDNN @ allows both the
point and the primitive to be picked by one cursor hit.
The database reference ID and the cursor-hit position of any linear element on the Sheet
(for example a STRA, side of a RECT, part of Design item, etc) may be queried using:
Q IDLINE @
The query returns the database of the picked element (DRAFT or DESIGN), the identity of
the element, the pair of 2D coordinates that define the linear element, and the 2D position of
the cursor hit.
For example, if the query were applied to a STRA element with FPT X100 Y100 and TPT
X200 Y200, the following could be returned:
At a primitive
At a primitive
For a Straight these are FPT (from point), TPT (to point) or MPT (midpoint); and for an Arc
these are FPT, TPT, CPT (centre point) or THPT (through point).
The node must be currently used by the Straight or Arc. A Straight has a single node, MPT
or two nodes, FPT and TPT. An Arc has an FPT, TPT and either a CPT or a THPT. If an
unset node or an illegal node is specified, then an error is output.
Moving all Primitives in a NOTE or VNOT
Moving all of the member primitives of a NOTE or VNOT is done simply by changing the
NOTE/VNOTs origin position (XYPO attribute). This is the offset of the origin from the origin
of the NOTE/VNOTs owner (i.e. SHEE/VIEW respectively). The origin of a SHEE is at its
18:11
12 Series
bottom left-hand corner and that of a VIEW at the centre of the VIEW rectangle. XYPO may
be changed directly or by the OFFSET command, for example
AT @
AT X400 Y400
position NOTE/VNOTs origin at given position on SHEE
BY @
BY X60 Y-20
shift NOTE/VNOTs origin by given amount
ADEG 30
rotate NOTE to 30 from horizontal
Note: If a VNOT is moved or rotated, only primitives positioned in 2D will move with it. The
positions of primitives positioned in 3D or on Design elements will remain
unchanged.
Rotating a Primitive
A primitive of type ARC, CIRC, STRA, ELLI, RECT, HEXA, TABL, DMND, ETRI, OUTL or
MRKP can be rotated using the ROTATE command to specify an angle of rotation and a
point to rotate about. Any position reference may be used to specify the rotation point. For
example:
ROTATE 45 @
Use cursor to specify the 2D point to rotate it about
ROTATE 45 IDP@
Use cursor to specify the Design p-point to rotate about
Mirroring a Primitive
A primitive of type ARC, CIRC, STRA, ELLI, RECT, HEXA, TABL, DMND, ETRI, OUTL or
MRKP can be mirrored using the MIRROR command to specify a mirror axis. The current
element may be mirrored in an existing linear element or two independent points may be
specified to define the mirror axis. In the latter case, any position reference may be used to
specify the axis points. For example:
MIRROR IN @
Use cursor to specify existing linear element to mirror in
MIRROR ABOUT @ @
Use cursor to specify two points to define mirror axis
Copying a Primitive
Copying a primitive to another position or series of positions is done by using the REPEAT
command with the primitive you wish to copy as current element. The REPEAT command
has three syntax variations, illustrated by the following examples:
18:12
12 Series
Produce five copies of the current primitive, each displaced (X20, Y20) from the last
REPEAT 5 BY @
Produce five copies of the current primitive, using the cursor to define displacement
REPEAT 5 @
Produce five copies of the current primitive, but with first copy at cursor position,
displacement of second and subsequent copies equal to that of first copy from original
REPEAT @
Produce five copies of the current primitive, but just one repetition
Figure 18:6.: Drafting Primitives - Use of the REPEAT Command illustrates the use of the
REPEAT command.
25
REPE 10 BY Y -25
Graphical Feedback
Many cursor commands generate graphical feedback (rubber banding) which makes the
interaction process easy - holding down the left-hand mouse button and moving the mouse
enables the primitive being created to be dragged out to the required size/orientation. Use of
the commands listed below gives the Point Construction Option form, from which you can
choose to define point(s) not only as simple 2D cursor hits but also as line end-points, circle
centre-points, intersection points etc. The relevant commands are:
Command
Valid Elements
REGN @
VIEW
DEF @
ADEF @
ARC
DIAMETER @
CIRC, HEXA
SPAN @
VRTX
18:13
12 Series
18.3.2
Command
Valid Elements
RADIUS @
ASUB @
ARC
TPT @
STRA, ARC
FPT @
STRA, ARC
MPT @
STRA
CPT @
ARC
THPT @
ARC
When a drafting point is created without specifying its position it will be positioned using
the default drafting point. This is normally the last point used. (This applies to the initial
node for a Straight or an Arc.) For example the series of commands:
When a primitive is positioned very close to an existing drafting point in the same
NOTE, VNOT or SYTM then the point will be re-used to position the new primitive. The
default tolerance for re-use of points is 1 mm on the Sheet, although some commands
(e.g. BY) work to a tolerance of 0.001 mm.
The tolerance used may be controlled by the TOLERANCE command, for example:
TOL DEF
Control over the TOLERANCE setting is particularly important for the re-input of DATAL
macros. The re-use of drafting points within the TOLERANCE limit can lead to
unsatisfactory performance when a NOTE contains a large number of points. This may
happen, for example, when Symbol definitions or Backing Sheets are input from
macros.
Q TOL
The current tolerance will also be output to file by the RECREATE DISPLAY macro.
If neither of these methods is appropriate, the current primitive must be explicitly positioned
on the required drafting point. The drafting points used by a specified primitive may be
identified by querying its PTRF attribute (PTFA attribute for a Straight or Arc) or by using the
IDDP @ command.
18:14
12 Series
The current primitive may then be positioned on the required drafting point by commands
such as:
ORIGIN point_identifier, e.g. ORIG IDDP@
ORIGIN IDDP @
FPT point_identifier
e.g. FPT IDP@
DRAG TO IDDP @
(The Q IDN @ command may be used to identify the FPT or TPT of a STRAIGHT.)
18.3.3
18.3.4
ENHANCE
ENHANCE
ENHANCE
ENHANCE
SOLELY CE
SOLELY ALL CIRC FOR LAYER
ALL STRA WI ( ATTRIB LENG GT 400 ) FOR /SHEET12
ALL WI ( NLPN GE 11 AND NLPN LE 20 ) FOR NOTE
If the SOLELY option is used then all existing enhancing will be removed, otherwise existing
enhanced elements will be unaffected by this command.
The FOR element_identifier command option is important; without it the selection system
will scan around the entire MDB.
Enhancing may be removed by the UNENHance command, which may optionally specify a
selection criterion. The brief command
UNENHANCE
removes all enhancing and should always be used for that purpose.
The command
UNENHANCE ALL
should NOT be used as it causes the entire MDB to be scanned.
The list of currently enhanced elements may be queried by:
Q ENHAnce [LIst]
The colour in which elements are enhanced may be changed and reset by:
18:15
12 Series
18.3.5
NLSTYLE
NLCOLOUR
RADI
Radius
ASUB
Angle subtended
TCOD
by defining the positions of the end-points and a through point (from which the values
of Radius (RADI) and Angle Subtended (ASUB) can be derived if required).
by defining the position of the centre point, from point and Angle Subtended (from
which the position of the to points and the value of RADI can be derived if required).
by defining the position of the centre point and two end points.
The method:
NEW ARC
DEF @
results in three points being prompted for (the start, end and through points). A line is
drawn through the points and TCOD is set to ENDPOINT. See Positioning (absolute)
overleaf for the second method. If used with an existing ARC any existing values of RADI
and ASUB are altered accordingly.
18:16
12 Series
Defining or redefining an Arc with a centre- and two endpoints is achieved using the
command:
ADEFine <dfnpt> <dfnpt> <dfnpt>
where <dfnpt> defines a position (2D, 3D, p-point etc).
The first two points are the centre - (CPT) and from point (FPT) of the Arc. These two
points define the radius. The third point defines the angle subtended by the arc. The TOpoint (TPT) lies in this direction from the Centre (CPT) at the same distance as the FPT from
the CPT. The TCOD attribute is set to CENTRE.
This command may also be used with the cursor:
ADEFine @
A prompt requests three 2D points to be input for CPT, FPT and angle subtended. 3D points
may also be input using the cursor:
ADEFine ID@ ID@ ID@
DEFine IDP@ IDP@ IDP@
Changing Radius and Angle Subtended
RADIUS value [DESIGN]
Sets RADI. For TCOD CENT this moves the from and to points radially (by the change in
the value of the radius). Centre point position and ASUB are not altered. For TCOD ENDP
this moves the through point and changes ASUB; the positions of from and to points are
unchanged.
RADIUS X value Y value
RADIUS E value N value U value
RADIUS IDP @
etc.
For TCOD ENDP this is like THPT @.
ASUBTENDED value [ANTICLOCKWISE]
ASUBTENDED value CLOCKWISE
Sets ASUB. (A positive angle is anticlockwise, a negative one clockwise.)
For TCOD ENDP this repositions the through point (mid-way along the Arc) and changes
RADI; from and to point positions are unaltered. For TCOD CENT this moves the to
point of the arc. Centre and from points and radius are unchanged.
ASUBTENDED CLOCKWISE
ASUBTENDED ANTICLOCKWISE
Sets the value of ASUB to be negative or positive, respectively.
ASUBTENDED @
For TCOD ENDP this is like THPT @; For TCOD CENT this alters the angle subtended and
hence moves the to point of the Arc. The new position of the to point lies on the line joining
the centre-point and the cursor position; centre and from points and radius are unaltered.
Positioning (absolute) (of an arc point)
The syntax is similar to that for FPTs of STRAs. Possible points are CPT (centre point), FPT
(from point), TPT (to point) and THPT (through point).
18:17
12 Series
CPT @
etc.
This changes the arc to be one with TCOD CENT (if not already so). The Centre is moved
whilst keeping the from point and ASUB unaltered. The to-point and radius are
recalculated.
THPT @
etc.
This changes the Arc to be one with TCOD ENDP (if not already so). The position of the
through point is moved whilst keeping the from and to points fixed - i.e. both radius and
angle subtended are altered.
FPT @
TPT @
etc.
For arcs with TCOD ENDP, the from or to point of the Arc (as appropriate) is moved whilst
maintaining the positions of the other end point and the through point.
For Arcs with TCOD CENTRE, the from or to point of the Arc (as appropriate) is moved
whilst maintaining the position of the centre and the angle subtended. Thus the radius may
change and the position of the other end point will be moved to preserve the angle
subtended.
Repeated Copying
See Circles.
Querying
Similar to Straights, but referring to RADIUS, ASUBTENDED, CPT, FPT, TPT and THPT as
appropriate. The Q IDN @ command may also be used
Dragging another primitive to which the Arc is connected
During the course of a DRAG operation on another primitive, the points of the Arc may
move. The effect on the Arc is as follows.
for arcs with TCOD ENDP, Radius and Angle subtended are changed.
for Arcs with TCOD CENT, if the centre point is dragged, then the positions of the from
and to points are also moved to preserve the Arcs appearance.
For Arcs with TCOD CENT, if an end point is dragged, then a rotation about the other
endpoint takes place, i.e. the centre point is moved and the radius changed.
18:18
12 Series
CIRCLE (CIRC)
Attributes
PTRF
NLSTYLE
NLCOLOUR
FSTYLE
Fill style
FCOLOUR
Fill colour
OCOD
ADEG
DIAM
Circle diameter
18:19
12 Series
ORIG CENTRE
Sets ORIG as required and changes position of origin to point specified. The Circle
itself does not move.
ORIG CIRCUMFERENCE
Positioning (absolute)
ORIG X value Y value
ORIG CENTRE @
ORIG CIRCUMFERENCE @
ORIG IDP @
ORIG POS @
ORIG ID @
ORIG IDDP @
The last option (ORIG IDDP @) places the primitive on the drafting point used by another
primitive and hence ensures connectivity for the DRAG command.
Moving about the origin
OCOD CIRCUMFERENCE
Moves origin to circumference of Circle. See Figure 18:7.: Moving about the Origin Use of the ORIG Command.
18:20
12 Series
Figure 18:7. Moving about the Origin - Use of the ORIG Command
18:21
12 Series
Q OFFS
Queries the position relative to the NOTE origin
DIAMOND (DMND)
Attributes
PTRF
NLSTYLE
NLCOLOUR
FSTYLE
Fill style
FCOLOUR
Fill colour
OCOD
ADEG
Angle in owner
XLEN
X axis length
YLEN
Y axis length
Resizing
As for Ellipses.
All other operations are as for Circles.
ELLIPSE (ELLI)
Attributes
PTRF
NLSTYLE
NLCOLOUR
FSTYLE
Fill style
FCOLOUR
Fill colour
OCOD
ADEG
Angle in owner
XLEN
X axis length
YLEN
Y axis length
18:22
12 Series
Resizing
XLEN value [DESIGN]
YLEN value [DESIGN]
XLEN @
XLEN IDDP @
XLEN IDG @
XLEN IDP @
XLEN ID @
YLEN @
YLEN IDDP @
YLEN IDG @
YLEN IDP @
YLEN ID @
NLSTYLE
NLCOLOUR
FSTYLE
Fill style
FCOLOUR
Fill colour
OCOD
ADEG
Angle in owner
FRAD
Fillet radius
LENG
Side length
18:23
12 Series
Resizing
LENGTH value [DESIGN]
Sets side length
THROUGH @
THRU @
Prompts:
Input a point on the current sheet
Sets LENG so that the triangle passes through the point specified.
This may not necessarily be a corner - ADEG will not be altered.
THR X value Y value
Manual method
FRADIUS value [DESIGN]
Sets FRAD to value specified. If this is too big for the existing value of LENG then a
warning is output, the triangle is drawn sharp-cornered, but the FRAD attribute is set
as specified and will be used when the LENG value is made large enough.
Redefining the Origin
ORIG @
prompts: Select a possible origin for the ETRI
ORIG APEX
ORIG BASE
ORIG LSIDE
ORIG RSIDE
ORIG BLEFT
ORIG BRIGHT
All other operations are as for Circles.
HEXAGON (HEXA)
Attributes
PTRF
NLSTYLE
NLCOLOUR
FSTYLE
Fill style
FCOLOUR
Fill colour
OCOD
ADEG
Angle in owner
DIAM
18:24
12 Series
MSTYLE
Marker style
MCOLOUR
Marker colour
All other operations on Markers are similar to those for Circles (where relevant).
OUTLINE (OUTL) and VERTEX (VRTX)
An Outline consists of a user-defined series of connected straight lines and circular arcs
(collectively known as spans). OUTL elements do not have any geometry or positional data
themselves, because they are of indeterminate complexity. This is provided by a list of
owned Vertex (VRTX) elements. The origin of an OUTL is considered to be at the position of
its first VRTX. As an alternative to straight lines and circular arcs, a smooth quadratic curve
may be drawn through the vertex points of the OUTL (see CURFIT below).
Attributes
(OUTL)
NLSTYLE
NLCOLOUR
FSTYLE
FCOLOUR
Fill colour
MSTYLE
Marker style
MCOLOUR
Marker colour
CURFIT
Setting CURFIT to CUBICFIT will cause a smooth quadratic curve (which approximates a
series of cubic curves) to be drawn through the vertex points of the OUTL. CURFIT
DEFAULT turns off the curve-fit function.
18:25
12 Series
(VRTX)
PTRF
Point reference
BULG
Bulge factor
NLSTYLE
NLCOLOUR
Not in colour
MSTYLE
Marker style
MCOLOUR
Marker colour
CHAM
Chamfer distances
FRAD
Fillet radius
Bulge Factor
The BULG attribute is unique to the VRTX element, and is the ratio of the maximum
departure of the arc from the chord joining two VRTXs to the chord half-length. It is positive
when the span lies to the right of the chord when viewed in the direction VRTX1 to VRTX2,
negative when it lies to the left. A straight span has a BULG of 0, a counter-clockwise
semicircle a BULG of 1.0, and a clockwise semicircle a BULG of -1.0. BULG would not
normally be set explicitly, but indirectly by the SPAN command (see below).
Chamfering
A chamfer may be applied between two VRTXs using
CHAMFER value [value]
The value(s) supplied in the above syntax must be greater than or equal to 0. If two values
are supplied then the first chamfer distance will correspond to the chamfer joining the
current VRTX to the previous one, and the second will correspond to the chamfer joining the
current VRTX to the next. If only one chamfer distance is supplied, then both chamfer
distances will be set equal. Setting the chamfer distance to 0 is equivalent to setting it to
OFF. If the chamfer distance is set on a VRTX then the spans on either side of it will be
drawn straight, i.e. the BULG attribute of the current and next VRTX will be ignored.
CHAMFER OFF will remove the chamfer.
Filleting
A fillet may be applied to a VRTX using
FRADIUS value
Any value may be supplied in the above syntax. A positive value will correspond to a convex
fillet radius at the VRTX, a negative value to a concave fillet. Setting FRAD to 0 is equivalent
to setting it to OFF. If the fillet radius is set on a VRTX then the spans on either side of it will
be drawn straight, i.e. the BULG attribute of the current and next VRTX will be ignored.
VRTX Basic Creation Method
The OUTL and VRTX elements may be created and deleted in the usual manner, e.g.
NEW OUTLine
NEW VRTX AT @
DELETE VRTX
18:26
12 Series
The position of a VRTX and the shape of the span drawn to it from the previous VRTX are
defined by the SPAN command. This command is valid at any VRTX except the first in list
order. Variations of the SPAN command are:
SPAN TO position
Vertex point defined by <position>
SPAN THROUGH position
Span defined as a circular arc passing through position. Defines BULG.
SPAN TO position THROUGH position
SPAN THROUGH position TO position
SPAN TO CLOSE
Vertex point coincident with starting vertex.
SPAN STRAIGHT TO position
Straight line span with vertex at <position>
SPAN RADIUS value
Set radius of circle of which (arc) span forms a part. Converts straight line span to an
arc.
SPAN ASUB value
Sets angle subtended by (arc) span. Converts straight line span to an arc.
SPAN BY xypos
Move the two VRTXS of the current span by the given displacements.
SPAN DRAG BY xypos
Move the two VRTXS and all connected drafting primitives of the current span by the
given displacements.
position can be a Design p-point, a 3D point or an explicit Sheet coordinate. A cursor hit can
be used with all except the CLOSE, RADIUS, ASUB and STRAIGHT options. The position
of a VRTX can also be constructed - see Point and Line Construction. If a VRTX is made
coincident with the drafting point of another 2D primitive then a logical connection will be
established and the DRAG command will affect the VRTX and the other 2D primitive.
The TO option defines the position of the VRTX without affecting the bulge factor and is thus
similar to the standard DEF command. The CLOSE option positions the current VRTX to be
coincident with the first VRTX of the OUTL and thus closes the Outline. This does not have
to be the last VRTX though - subsequent VRTXs can be created.
The BY and DRAG BY options move the VRTXs at the start and finish of the span by the
specified amount - bulge factor and curvature are unaffected. The THROUGH, RADIUS and
ASUB options only define the bulge factor - knowledge of the through point, radius and
angle subtended are lost. They do not change the position of VRTXs, only the curvature of
the span.
The RADIUS option can have a negative value - this will result in a negative BULG and
hence a span drawn in a clockwise direction. If the radius specified is not large enough to
define the curvature of the span between two VRTXs then the command will be ignored and
18:27
12 Series
a warning message output, giving the minimum possible radius. By default the command
gives the minor arc, the major arc being given by
SPAN RADius value MAJor
The command SPAN @ (or NEW VRTX SPAN @) gives a simplified way of defining the
span. By default, you must define the TO position by a cursor hit, a straight-line span being
assumed. The Outline Span Construction form will appear, giving you various span
definition options. See the on-line help for details.
Querying
Q DESCription is valid at OUTLs and VRTXs, giving details of origin coordinates and span
radius and angle subtended (if appropriate). Q SPAN RADius and Q SPAN ASUBtended
are valid at VRTXs only (but not at the first VRTX in an OUTL).
Miscellaneous Commands
The Q COMmon, HIGhlight, SKEtch POInts, SKEtch ORIgins and ID @ commands are all
valid at OUTLs and/or VRTXs. Note that SKETCH ORIG ALL does not sketch all VRTX
origins - only the origins of the owning OUTLs - i.e. the first VRTX below each OUTL.
RECTANGLE (RECT)
Attributes
PTRF
NLSTYLE
NLCOLOUR
FSTYLE
Fill style
FCOLOUR
Fill colour
OCOD
ADEG
Angle in owner
XLEN
X axis length
YLEN
Y axis length
FRAD
Fillet radius
18:28
12 Series
Resizing
XLEN value [DESIGN]
YLEN value [DESIGN]
XLEN @
YLEN @
Manual method
THROUGH @
THRU @
Manual method
For example:
18:29
12 Series
ASDEF X400 Y400 X500 Y450 Defines a RECT 200 square with its centre at
X400 Y400 and a corner at X500 Y500.
These commands may also be used with the cursor, for example:
ADEFine @
A prompt requests two 2D points to be input.
All other operations are as for Circles.
STRAIGHT (STRA)
Attributes
PTFA
NLSTYLE
NLCOLOUR
LENG
Length
ADEG
Angle in owner
TCOD
By defining the positions of the end-points (from which the values of length and angle
can be derived if required).
By defining the position of the mid-point and values of LENG and ADEG (from which
the positions of the end-points can be derived if required).
The commands:
NEW STRA
DEF @
results in two points being prompted for; a line is drawn between the two points and TCOD
is set to ENDPOINT. See the section on Positioning (absolute) below for the second
method.
The command:
ODEF @
prompts for two points. The straight will be vertical or horizontal depending on the relative
sizes of the horizontal and vertical offsets between the two points given.
18:30
12 Series
ADEG value
LENGTH @
ALENGTH @
Positioning (absolute)
A STRA may have its from point, mid point or to point positioned or moved. Apart from
the initial keyword (FPT, MPT, TPT) specifying which point you are setting the syntax is
similar throughout, as the following examples show::
To position at a 2D (i.e. X,Y) position
FPT @
FPT X 50 Y -250
FPT POS @
FPT E12500 S5000 U0
To position on a p-point:
FPT
FPT
FPT
FPT
ID @
IDP @
/PUMP2/N1
P1 OF /PUMP2/N1
If the MPT command is used, the TCOD will be set to MIDPOINT. This is a single point
STRAIGHT and must have its LENGTH set.
A straight can also be created by giving an orthogonal To point:
OPPT x 50 y 97
OTPT @
The straight will be vertical or horizontal depending on the relative sizes of the horizontal
and vertical offsets between the From point and the To point.
Points on a STRA (FPT, TPT etc) may be identified using the command:
Q IDN @
Positioning (relative)
It is possible to move a STRA or one of its points by a given amount. For a single point
STRA (i.e. one with a mid-point) there will be no difference between moving the STRA itself
18:31
12 Series
or its mid-point, but for a two point STRA moving its from or to point will cause its length
and/or its slope to change; the position of the other point will remain unchanged.
BY @
prompts:
or:
FPT BY @
BY X55 Y-678
BY N500 W1200
DRAG BY @
DRAG BY X120 Y-45
DRAG BY S3500 D500
prompts:
or:
the
the
the
the
Repeated Copying
See Circles.
Querying
Q DESC
queries the Length and point attributes, i.e.
LENGTH value
ADEG value
FPT X value Y value
TPT X value Y value
Q FPT
Queries the position of the 'from' point if set. Similarly for TPT, MPT
Q OFFS
Queries the offset positions of the points set (relative to the Note origin)
Q FPT OFFS
Queries the offset of the 'from' point relative to the Note origin (similarly for TPT, MPT)
SKETCH POINTS
Sketches all points currently in use for the STRA
SKETCH FPT
18:32
12 Series
Sketches the from point (if set) - similarly for the TPT and MPT
SKETCH ORIG
Sketches first node
SKETCH POINTS ALL
At NOTE level, displays all the points currently in use for all member primitives
SYMBOL INSTANCE (SYMB)
Attributes
PTRF
TMRF
Template reference
XYSCALE
Scale in X, Y directions
ADEG
Angle in owner
When instancing a symbol (SYMB), the TMRF attribute should reference a symbol template
(SYTM) in the symbol library (SYLB). If this attribute is not set, nothing will be drawn.
Changing Size and Orientation
XYSCALE value value
SYSIZE value
SYSZ @ @
SYSIZE @ @
ALENGTH value
ALENGTH @
You are requested to input two points; the first point selects a position on the symbol, the
second point sets a new position for the selected point. The new symbol size is calculated
from the ratio of the distances of those two points from the symbol origin.
SHIFT @ @
18:33
12 Series
TABLE (TABL)
Attributes
PTRF
NLSTYLE
NLCOLOUR
OCOD
ADEG
Angle in owner
XLEN
axis length
YLEN
Y axis length
NROW
No.of rows
NCOL
No.of columns
ROWSTYLE
ROWCOLOUR
COLSTYLE
COLCOLOUR
All operations, including definition using the ADEFine, ASDEFine and SDEFine
commands, are similar to those for Rectangles, except that FRAD does not apply. Internal
rows and columns are drawn using NLSTYLE/NLCOLOUR by default. If ROWSTYLE/
ROWCOLOUR or COLSTYLE/COLCOLOUR are set, internal rows and columns may be
drawn in a different style and colour to the outline rectangle.
TEXT PRIMITIVE (TEXP)
Attributes
PTRF
BTEX
ADEG
Angle in owner
FONT
Text font
TXCOLOUR
Text colour
CHEI
Character height
LHEI
Letter height
CSPA
LSPA
18:34
12 Series
JUST
Justification
ALIG
Vertical alignment
Resizing
Set the CHEI, LHEI, CSPA or LSPA attributes.
Redefining the Origin
Set JUST (justification) or ALIG (alignment).
All other positioning operations are as for Circles (see CIRCLE (CIRC)).
18.4
Text Strings
18.4.1
18:35
12 Series
18.4.2
ALIG TB JUST L
OPENFILE /filename READ !TOKEN
READFILE $!TOKEN !RECORD
NEW TEXP AT @ BTEX $!RECORD
VAR !EXTENT EXTENT BTEX
The EXTENT query (together with PML array and string-handling commands) may be used
to calculate the position of the next line of text.
Successive READFILE and TEXP commands may be used until the file is exhausted. The
file may then be closed using:
CLOSEFILE $!TOKEN
Note that any $ characters in the file should be doubled.
PML is detailed in the Software Customisation Guide.
18.5
Summary of Commands
18.5.1
Creating Primitives . . .
18.5.2
ORIG @
OCOD @
OCOD CEN
SKETCH ORIG
18:36
12 Series
18.5.3
18.5.4
18.5.5
18.5.6
AT @
AT X300 Y250
POS ID @
POS W5500 N12345 D120
ON ID @
ON IDP @
ON /PUMP1
ON P1 OF /PUMP2/NS
BY @
BY X10.5
BY N500 W1200
ROTATE 45 @
ROTATE 45 IDP@
MIRROR IN @
MIRROR ABOUT @ @
DRAG TO @
DRAG TO X120 Y-45
DRAG TO POS @
DRAG TO IDP @
DRAG TO S3500 D500
DRAG TO P1 OF /VESS2/N6
DRAG BY @
DRAG BY X120 Y-45
18:37
12 Series
18.5.7
18.5.8
18.5.9
Querying Primitives . . .
Q ORIG
Q COMMON
Q OFFSET
Q DESC
Q IDN @
Q IDNN @
Copying Primitives . . .
REPEAT 5 BY @
REPEAT 5 @
REPEAT @
Outlines . . .
NEW OUTL
NEW VRTX AT @
SPAN TO @
SPAN TO IDP @
SPAN TO CLOSE
SPAN STRAIGHT TO
X value Y value
18:38
12 Series
CURFIT CUBICFIT
CURFIT DEFAULT
FRAD value
SKETCH ORIGIN
SKETCH POINTS
SKETCH POINTS ALL IN identifier d drafting points of all drafting primitives at/below the
isplays
specified element
SKETCH FPT
will sketch the from point (if set) - similarly for the
TPT and MPT
UNENHANce
Q ENHAnce [LIst]
18:39
12 Series
18:40
12 Series
19
ISODRAFT Symbols
You can create symbols in DRAFT to be used on the isometrics produced by ISODRAFT.
The symbols are created as ISODRAFT Symbol Templates (ISOTMs), which are similar to
normal symbol templates, except that they can only own STRAs and MRKPs. They have
additional attributes, described in Creating ISODRAFT Symbol Templates.
ISOTMs are stored in ISODRAFT Symbol Libraries (ISOLBs), which are identical to SYLBs
except that they can only own ISOTMs. The relevant part of the DRAFT database is shown
in Figure 19:1.: ISODRAFT Symbol Libraries and Related Elements.
ISOLB
ISOTM
MRKP
STRA
Figure 19:1. ISODRAFT Symbol Libraries and Related Elements
19.1
STRAs owned by ISOTMs should have their PURP attributes set to LINE, INSU or
TRAC (to describe whether the straight represents the pipeline, its insulation or its
tracing).
MRKPs owned by ISOTMs should have their PURP attributes set to one of ARRI,
LEAV, TEE or SPIN.
The Arrive and Leave points of the symbol will be used as the reference points for
dimensioning.
19:1
12 Series
19.1.1
19.1.2
SKEY
BKEY
SCALe value
SPINdle
ORIN NONE
ORIN FLOW
ORIN REDUCER
ORIN FLANGE
FLWArrow TRUE
FLWArrow FALSE
DIMEnsion TRUE
DIMEnsion FALSE
INSL TRUE
INSL FALSE
TRCG TRUE
TRCG FALSE
FILL TRUE
Symbol to be filled
FILL FALSE
Wildcards in SKEYs
You can use the * character as a wildcard to define a symbol for several similar SKEYs. For
example:
SKEY VB**
19:2
12 Series
This illustrates the use of the ** characters to cover all end conditions, i.e. BW (butt weld),
CP (compression), SW (socket weld), FL (flanged), SC (screwed) and PL (plain), when
defining a new range of SKEYs. This sequence therefore defines the SKEYs VBBW, VBCP,
VBSW, VBFL, VBSC and VBPL in a single operation.
Note: The wildcard option applies only to the definition of SKEYs. You must specify a
particular end condition when you set the SKEY attribute of a DTEX element in the
Catalogue DB; for example, by setting it to VBBW or VBCP but not to VB**.
19.1.3
Example
The following commands are an example of how to create an ISODRAFT Symbol Library
and an ISODRAFT Symbol Template:
NEW ISOLB
NEW ISOTM
XYPS X200 Y200
SKEY SSSS
SPIN NONE
FLWA TRUE
BKEY VV**
SCAL 100
FILL TRUE
NEW MRKP
PURP TEE
ORIG OFFS X0 Y0
NEW STRA
PURP LINE
TPT OFFS X4.0 Y1.0
NEW STRA
PURP LINE
TPT OFFS X8.0 Y1.0
NEW STRA
PURP LINE
TPT OFFS X8.0 Y-1.0
NEW STRA
PURP LINE
TPT OFFS X4.0 Y-1.0
NEW STRA
PURP LINE
TPT OFFS X0 Y0
19:3
12 Series
NEW MRKP
PURP LEAVE
ORIG OFFS X8.0 Y0
19.2
19.3
Q ALL ISOLB
Q ISOSYM
list symbol keys and base symbol keys in the library file
Q ISOSYM NUMBER
Q ISOSYM n
gives the symbol key and base key for entry number n.
19:4
12 Series
20
20.1
Introduction
A drafting point position may be specified explicitly, for example
A 2D position:
A 3D position:
A Design Item:
A p-point:
A position on a p-line:
2D_vector specifies an offset position from the owner origin of the primitive concerned, for
example
20:1
12 Series
distance gives a distance and a direction from a point, and may be one of the following in a
NOTE or SYTM:
units_value
ANGLE value
HORIZONTAL
VERTICAL
2D_vector
For example:
ORIG
ORIG
ORIG
ORIG
X50
X50
X50
X50
Y50
Y50
Y50
Y50
DIST
DIST
DIST
DIST
200MM ANG 30
200 HORI
200 VERT
100 X100 Y100
20.2
X, Y Filtering
A 2D position may be defined in terms of the X or Y coordinates of other points. For
example, rather than an explicit point definition such as:
AT X200 Y200
a constructed point could be defined by:
AT X200 Y OF point
The above command would define a position whose Y coordinate would be the Y coordinate
of point, where point could include:
A tangency point
An intersection points
The constructed point could also be defined explicitly or by a cursor hit. For example:
20:2
12 Series
AT X200 Y OF @
Set the Y coordinate to the Y coordinate of the cursor hit
AT X OF @ Y OF @
X coordinate from first cursor hit, Y coordinate from second cursor hit
The process of deriving a coordinate from a coordinate of another point is known as X, Y
filtering. X and Y filters may be used in any command that requires a 2D position on a
Sheet, including edits on various Dimension attributes. For example:
PTOF X OF /VALV1 Y @
DTOF X @ Y250
PLCL X @ Y OF POS E3000 S2000 U0
Y coordinate set to the Y coordinate of 2D projection of given 3D position.
3D positions may also be constructed, but this only applies to 2D drafting primitives that are
members of VNOT elements. X, Y filtering can be used with any 2D element which has a
position attribute, e.g. VIEWs, Labels, Dimension Points etc.
Examples
1. NEW STRA
FPT X100 Y100
TPT X OF @ Y OF @
(or NEW STRA DEF X100 Y100 X OF @ Y OF @)
Here a straight line is created with one of its endpoints defined explicitly and the other
constructed using cursor hits. See Figure 20:1.: X, Y Filtering - General 2D Position.
500
2
1
100
100
500
20:3
12 Series
Here, the to point of the line takes its X coordinate from the X coordinate of hit 1 (at
200, 300) and its Y coordinate from the Y coordinate of hit 2 (at 500, 400). The to point
is therefore (200, 400).
2. DTOF X @ Y250
With a cursor hit at (400, 900), the above command would move a Dimension text
origin to (400, 250).
3. PLCL X @ Y OF POS E3000 S2000 U0
Here, a projection line clearance X coordinate would be set to the X coordinate of the
cursor hit, the Y coordinate being set to the Y coordinate of the 2D projection of the
given 3D position.
20.3
Construction of 3D Positions
A specified 2D point may be projected into 3D, enabling 3D positions to be constructed by
picks on any line in the Design graphics. This is done using the POSition OF <point>
syntax. For example:
NEW STRA
DEF @
TPT POS OF ENDP OF @
Position TO point at end of 3D line.
A Q DESC command would return a 3D coordinate for the TPT of the line. This facility is
only valid in Plan or Elevation VIEWs.
Note that the Q ENUPOS and Q SHPOS commands (see Querying Position Data) also
calculate conversions between 2D and 3D positions.
20.4
Midpoint Position
This form of construction derives a position as the midpoint of two other positions, which
may be defined explicitly or by cursor hits.
20.4.1
20.4.2
1. NEW STRA
FPT MIDPOINT OF @
TPT MIDPOINT OF @
(or NEW STRA DEF MIDPOINT OF @ MIDPOINT OF @)
Here, the line would take its endpoints as the midpoints of the two hit items. If the two
hit items were an arc and another straight line then the situation could be as shown in
Figure 20:2.: Use of the MIDPOINT Construction.
20:4
12 Series
The required midpoint could also be that of one side of a closed polyline primitive, e.g.
a rectangle. Line definitions of other elements (such as a line that comprises a piece of
a design item shown in a VIEW) can be extracted by cursor. As well as using a cursor
hit, the STRA or ARC may be identified explicitly.
Note: Note that with this variation of the MIDPOINT syntax, the presence of the OF
keyword is mandatory.
20.5
NEW STRA
FPT @
TPT TOP OF ID @
constructed point
Quadrant points of an arc or ellipse may also be identified. If an ellipse is rotated, the
nearest extreme of the ellipse will be selected. For example
NEW STRA
FPT @
TPT TOP ELLI /ELLI1
constructed point
20:5
12 Series
20.6
Endpoint Position
This form of construction derives a position as the endpoint of an identified element
(typically a line or an arc). A qualifier may be added if there is any ambiguity about which
endpoint is to be used. If there is any ambiguity, and if the qualifier is omitted, then a solution
will be chosen and returned arbitrarily.
The required endpoint could also be that of one side of a closed polyline primitive, e.g. a
rectangle. Line definitions of other elements (such as one side of an EQUI, or a line that
comprises a piece of a design item shown in a VIEW) may be extracted by cursor.
Examples
2. NEW STRA
FPT X150 Y250
TPT ENDPOINT OF @
(or NEW STRA DEF X150 Y250 ENDPOINT @)
Here, the line has one of its endpoints defined explicitly, the other as the endpoint of the
hit arc.
500
(150, 250)
100
100
500
3. NEW STRA
FPT X150 Y150
TPT ENDPOINT OF PREV ARC QUAL X400 Y400
Here, the line has its from point defined explicitly and its to point as the endpoint of
the previous ARC in the list order closest to (X400, Y400).
20:6
12 Series
Y
previous ARC in list order
500
(400, 400)
(150, 250)
100
100
500
20.7
1. NEW STRA
FPT X150 Y250
TPT CEN OF @
(or NEW STRA DEF X150 Y250 CEN OF @)
Here, the line has one of its endpoints defined explicitly, the other as the centre of the
element (in this case a circle) hit by the cursor.
500
(150, 250)
100
100
500
20:7
12 Series
3. NEW STRA
FPT @
TPT FOC OF /ELLI1 QUAL @
Here, the to point of the line is placed at the focus of ellipse /ELLI1 qualified by a
cursor hit.
constructed point
1
Figure 20:8. Use of the FOCUS Construction
20.8
Nearest To Position
This form of construction derives the point on a primitive that is nearest to a specified
qualifying point.
Example
1. NEW MRKP
DEF NEAREST PREV STRA QUAL X150 Y250
In the left-hand case shown below, the MRKP element and the position (X150, Y250)
lie on the perpendicular to the STRA. In the right-hand case, the MRKP lies at the
endpoint of the STRA. In both cases, the MRKP element is the nearest point that lies
on the previous STRA in the list order to the given qualifying point.
Y
Y
newly defined MRKP
(150, 250)
(150, 250)
100
100
100
500
100
500
2. NEW STRA
FPT X150 Y250
TPT NEAREST PREV ARC QUAL @
Here, the STRA has its from point defined explicitly, its to point being defined as the
nearest point which lies on the previous ARC in list order to the given qualifying point.
20:8
12 Series
Y
newly defined STRA
(150, 250)
100
100
500
3. NEW MRKP
DEF NEAR @
Here, the MRKP element would be snapped to the primitive nearest the cursor hit. Note
that in this case a qualifying point is not needed.
20.9
Intersection
Here, a point is constructed which is at the intersection of two primitives. The primitives
should be chosen from STRA, ARC, or CIRC, although line-parts of more complex
primitives may be identified by cursor. An ellipse (ELLI) is also an allowable primitive, but it
is only possible to calculate the intersection point between an ellipse and a straight line. A
qualifying point may also be specified when there is more than one point of intersection (cf.
use of qualifier in Endpoint Position)
Examples
1. INT @
This variation uses a single cursor hit to pick the intersection point explicitly.
constructed point
2. INT BETW @ @
This constructs a point at the intersection of two hit primitives:
20:9
12 Series
constructed point
3. INT BETW @ @
In this case the second cursor hit acts as a qualifier:
constructed point
1
2
constructed point
(100, 100)
5. NEW STRA
FPT INT BETW PREV ARC AND PREV CIRC QUAL X200 Y300
TPT MIDP OF PREV STRA
Here, the STRA has one endpoint defined as that intersection between the specified
arc and the specified circle which is the nearest to the qualifying point, the other
endpoint being the midpoint of a specified line.
Y
newly defined STRA
500
(200, 300)
100
100
500
20:10
12 Series
1. NEW STRA
FPT X100 Y100
TPT X300 Y200 TAN @
500
This STRA element has an explicit FPT; its TPT is the point on the ARC that, together
with (X300, Y200), forms a tangent to the ARC. Here the cursor hit acts as a qualifying
point. Notice that the STRA produced here is not a tangent line.
2. NEW STRA
FPT X200 Y100
TPT X200 Y100 TAN PREV CIRC QUAL @
Here, the STRA has one endpoint defined explicitly and the other defined as the point
where the tangent line through (X200, Y100) intersects the previous CIRC in list order
which is closest to the cursor-specified qualifying point.
500
100
(200, 100)
100
500
20:11
12 Series
The qualifier is necessary since in this case there are two possible tangents. (Other
tangent shown dashed.) Other cases would not need a qualifier since only one tangent
would be possible (see below).
generated point
(200, 100)
3. NEW STRA DEF @ @ TAN @
In this case, the first cursor hit defines one endpoint of the STRA, the second defines
one end of a tangent, and the third picks the circle and also acts as a qualifier. The
resulting STRA intersects the tangent. See below.
1
Figure 20:14. Use of the TANGENT Construction to give a Line perpendicular to a Tangent
TANLINE @ @
Figure 20:15.: Use of the TANLINE command to give a Tangent Line shows various
examples of the use of the tangent line facility. Notice how (right-most illustration) the
tangent line may lie on the complement of an ARC.
20:12
12 Series
1. NEW STRA
FPT X300 Y100
TPT X300 Y100 PERP PREV STRA
Here, the STRA has one endpoint defined explicitly and the other defined as the
intersection of the perpendicular from the specified reference point to the previous
STRA in list order. See Figure 20:16.: Use of the PERPENDICULAR Construction.
500
100
(300, 100)
100
500
Where the specified primitive is a line, the constructed point may lie beyond the ends of
the line (as above).
Other variations of the PERPENDICULAR Construction are shown below.
2. NEW STRA
FPT X0 Y0
TPT X0 Y0 PERP PREV CIRC QUAL @
Here (see opposite), two constructed points are possible and so a qualifying cursor hit
is used.
20:13
12 Series
500
100
500
500
100
500
20:14
12 Series
The first point to be specified must be explicit, i.e. it cannot itself be a constructed point. A
3D position may be constructed if appropriate.
FILLETRAD 10 @ @
FILLETRAD -10 @ @
FILLETRAD -5 @ @
CONLINE @ 30
This would give:
20:15
12 Series
Sheet boundary
Note: that if the current SHEE size is changed, the FPT (From point) and TPT (To point) of
the STRA will not be updated.
RAYLINE @ 30
RAYLINE @ 210
Note: that if the current SHEE size is changed, the TPT of the STRA will not be updated.
BISECT @ @
BISECT @ @
Note: that if the current SHEE size is changed, the TPT of the STRA will not be updated.
20:16
12 Series
CHAMFERD 20 @ @
CHAMFERD 20 40 @ @
CHAMFERD 20 40 @ @
Note: in the above example the effect of changing the order in which the lines to be
chamfered are identified. (The same effect could be achieved by leaving the order of
identification unchanged but switching the chamfer distances values in the
command.) If a single value is specified, this is used for both chamfer distances.
20.17.1 Labelling
Point construction is available in all syntax that requires the input of a single 2D position. For
example,
GAP AT INT @
could be used to introduce a gap in a leader line at the point at which it crosses another line
(which may be part of the design graphics or annotation).
20.17.2 Dimensioning
Point construction is available in all syntax that requires the input of a single 2D (or, if
appropriate, a 3D position). For example,
DIM CENTRE OF @
could be used to position a Dimension line to run through the centre of an existing CIRC
element.
When creating linear and angular Dimensions, it is possible to dimension to a constructed
2D point using the
TO POS OF @
syntax. (Similarly FROM POS OF @. This procedure is possible provided the current VIEW
is orthogonal, and the 2D position lies in the current VIEW. For example, the syntax
20:17
12 Series
set the VIEW size and position using the VREGION command
20:18
12 Series
A.1
Basic Hierarchy
WORLD
STYLWL
LIBY
GLYTB
LSTYTB
FSTYTB
GLYPH
LINEST
FILLST
OLINES
HPATTE
DEPT
(see overleaf)
REGI
REPO
DRWG
LIBY
TEXT
(see overleaf)
REVI
SHEE
TEXT
NOTE
OLAY
REVI
VIEW
(see overleaf)
LAYE
ADIM
LDIM
PDIM
RDIM
VNOT
RRUL
GLAB
HRUL
SLAB
VSEC
TAGR
(see overleaf)
A:1
12 Series
A:2
12 Series
M46-2107-20-13
where the first two numbers are the database reference of the picture element. The third
number is the value of the EXFI attribute (which is normally the database/extract file number
at the time the picture was saved). The final number is the picture version number (PVNO
attribute). This is incremented every time the picture is modified.
Only those picture elements that may include design graphics (that is SHEEs and OVERs)
have picture files. The graphics for other picture elements (LALBs, BACKs etc.) are created
when required.
Folder Structure
The picture file folder %<project>PIC% is split to improve the file system performance on
large projects, with increasing numbers of picture files. There are 32 subfolders numbered
00 through to 31 and the picture files are distributed among these subfolders according to a
pseudo-random algorithm based on database reference. The algorithm is designed to
distribute picture files homogenously among the subfolders; there is no user-configurable
option.
The picture filename may be queried at the picture element (SHEE, OVER) using the
command:
Q PICFilename
This returns the picture directory and file name, for example:
%ABCPIC%/27/M46-2107-20-13
Note: The details of the distribution algorithm are an internal feature of DRAFT. AVEVA
might adjust it in future versions so user applications should rely on the PICFilename
pseudo-attribute, as it is guaranteed always to return a valid picture file path.
B:1
12 Series
B:2
12 Series
Index
Numerics
A
ABSOLUTE command . . . . . . . 13:5, 13:29
ADD command . . . . . . . . . . . . . . . 3:5, 3:24
ADEFINE command . . . . . . . . 18:17, 18:29
ADEG attribute . . . . . . . . . . . . . . . . . . . 3:11
ADIM (Angular Dimension) element . . 12:35
AKEY attribute . . . . . . . . . . . . . . . . . . 12:23
ALARM command . . . . . . . . . . . . . . 2:3, 2:6
ALENGTH command . . . . . . . . . . . . . 18:31
ALIG (text alignment) attribute . 12:26, 13:8,
13:28
ALPHA command . . . . . . . . . . . . . . . . . . 2:4
ANGLE command . . . . . . . . . . . . . . . . . 13:6
Angle of turn (ADEG) attribute . 13:6, 13:14,
13:27, 18:2, 18:6, 18:12
Angle Subtended (ASUB) attribute 12:31, 12:49
Angular Dimension (ADIM) Elements . 12:2,
12:34, 12:45
ARC element . . . . . . . . . . . . . . . . . . . . 18:16
Arc tolerance . . . . . . . . . . . . . . . . . . . . . 3:13
Arc tolerance (ATOL) attribute . . . . . . . 3:13
AT command .13:5, 13:27, 18:9, 18:10, 20:2
Attachment point
of Labels . . . . . . . . . . . . . . . . . . . . . 13:2
Attachment point offset . . . . . . . 13:3, 13:14
Attribute Key (AKEY) attribute 12:23, 12:48
Autoblanking . . . . . . . . . . . . . . . . . . . . . 11:3
AUTOSCALE command 3:3, 3:6, 3:10, 3:26
Autotagging
B
BACK (Backing Sheet Template) element 17:2,
18:2
Background Process . . . . . . . . . . . . . . 3:21
Before/After linear dimension . . . . . . . . 12:3
Bent leader lines . . . . . . . . . . . . . . . . 13:10
BISECT command . . . . . . . . . . . . . . . 20:16
Blank areas . . . . . . . . . . . . . . . . . . . . . 11:3
BPOF (Bend Point Offset) attribute 13:12, 13:14
BSHEE command . . . . . . . . . . . . 17:3, 17:4
BSRF (Backing Sheet Reference) attribute 17:3
BTEX (Body Text) attribute 13:4, 13:23, 13:29,
14:1, 18:35
Bulge factor (BULG) attribute . . . . . . . 18:26
BY command . . . . . .5:10, 5:12, 18:9, 18:10
C
CENTRE keyword . . . . . . . . . . . . . . . . 20:7
Chained dimensions . . . . . . . . . . . . . . . 12:6
CHAMFERDIST command . . . . . . . . 20:17
CHANGE ACTION command . . . . 5:9, 5:11
Character Height (CHEI) attribute 12:19, 13:7,
13:29
CHECK REFERENCES command . . . 12:5
CIRC (Circle) element . . . . . . . . 18:6, 18:19
CLMO (Centreline Mode) attribute . . . . . 5:3
Colours, default . . . . . . . . . . . . . . . . . . . 8:3
COLSTYLE, COLCOLOUR attribute . 18:34
Common draughting primitives
handling . . . . . . . . . . . . . . . . . . . . 18:11
CONLINE command . . . . . . . . . . . . . 20:15
Index page i
12 Series
D
Databases
switching between . . . . . . . . . . . . . . 2:3
DDNM attribute . . . . . . . . . . . . . . . 2:2, 12:5
DDNX system attribute . . . . . . . . . . . . . . 2:2
DEFINE command 18:16, 18:19, 18:30, 20:2
DELETE command . . . . . . . . . . . . . . . . . 3:7
DELETE NULL ANNO command . . . . 12:50
DELETE NULL IDLI command . . . 3:7, 3:28
DELETE STEP command . . . . . . 5:10, 5:12
DESADD command . . . . . . . . . . . 3:6, 3:24
Design Data Name (DDNM) attribute . 12:5,
12:12, 12:23, 12:35, 12:45, 12:49,
12:50, 13:3, 13:20, 13:23, 13:27, 13:31
Design elements
hatching . . . . . . . . . . . . . . . . . . . . . . 4:8
Design Symbol (DESSYM) . . . . . . . . . . 3:18
Design Symbol Layer (DSLAYE) element 3:18
Design Symbol Link (DRSYLK) . . . . . . 3:18
DESREMOVE command . . . . . . . 3:6, 3:24
DESSYM (Design Symbol) element . . . 3:18
DFLAG attribute . . . . . . . . . . . 12:24, 12:48
DGN Output . . . . . . . . . . . . . . . . . . . . . 7:15
DIM @ command . . . . . . . . . . 12:32, 12:44
Dimension arc . . . . . . . . . . . . . . . . . . . 12:35
Dimension attribute key (AKEY) . . . . . 12:23
Dimension Line Angle (DDEG) Attribute 12:25,
12:32, 12:44, 12:48
Dimension Line Direction (DIR) . . . . . . 12:9
Dimension Line Position (DPOS) attribute . .
12:39, 12:43
Dimension Line Spacing (DMSP) attribute .
12:12, 12:40, 12:47
Dimension line terminators . . . 12:20, 12:47
Dimension lines . . . . . . . . . . . . . 12:2, 12:43
truncating . . . . . . . . . . . . . . . . . . . 12:47
Dimension Offset (DOFF) attribute 12:4, 12:8,
12:9, 12:39, 12:43, 12:45
Index page ii
12 Series
H
Hatch pattern
in automatic hatching . . . . . . . . . . . 4:11
Hatching
automatic . . . . . . . . . . . . . . . . . . . . . 4:8
Hatching Rules . . . . . . . . . . . . . . . . . . . . 4:9
Hatching Ruleset Reference (HRSF) attribute
3:13
HEXA (Hexagon) element . . . . . . . . . 18:24
Hidden line views . . . . . . . . . . . . . . . . . 3:16
Hidden lines . . . . . . . . . . . . . . . . . . . . . 3:14
HIGHLIGHT command . . . 6:6, 18:11, 18:14
I
E
EDTEXT command . 12:20, 13:4, 15:3, 15:4
ELLI (ellipse) element . . . . . . . 18:19, 18:22
Enclosed planes . . . . . . . . . . . . . . . . . . . 5:1
ENDPOINT keyword . . . . . . . . . . . . . . . 20:6
ENHANCE command . . . . . . . . . . . . . 18:15
ERASE command . . . . . . . . 5:11, 5:13, 18:9
ETRI (Equilateral Triangle) element . . 18:23
F
Fill Style . . . . . . . . . . . . . . . . . . . . . . . . 8:15
FILLETRADIUS command . . . . . . . . . 20:15
Filtering
X,Y . . . . . . . . . . . . . . . . . . . . . . . . . 20:3
Flat Plane (FPLA) element . . . . . . . 5:1, 5:5
FONT attribute . . . . . . . . . . . . . . 13:9, 15:1
FPLA element . . . . . . . . . . . . . . . . . . . . . 5:5
FPT (From Point) command 18:9, 18:18, 18:31,
20:2
FRAD (fillet radius) attribute . . 18:23, 18:28
Frame clearance (GBOX) attribute . . . 13:27
FROM command . . 12:3, 12:5, 12:35, 12:43,
12:45
FRPO (From Point) VIEW attribute . . . . 3:12
J
JUST (text justification) attribute 13:8, 13:28
12 Series
M
Marker Style . . . . . . . . . . . . . . . . . . . . . 8:23
Marker Style/Colour (MSTYLE/MCOLOUR)
12:31
MIDPOINT keyword . . . . . . . . . . . . . . . 20:4
MIRROR command . . . . . . . . . 18:12, 18:37
MLNP (Member line style/colour) attribute 4:4
Modelled wireline view . . . . . . . . . . . . . 3:15
N
NCOL, NROWS attributes (of Table) . 18:34
NEAREST keyword . . . . . . . . . . . . . . . 20:8
NORM attribute . . . . . . . . . . . 5:5, 5:9, 5:11
NOTE (Sheet Note) element 18:2, 18:5, 18:6,
18:11, 18:35
NPPT attribute . . . . . . . . . . . . . . 12:35, 13:3
NSIZE attribute . . . . . . . . . . . . . . . . . . . 3:18
O
OANG (Overlay Sheet Angle) attribute 17:1,
17:4
Obstruction (OBST) level control . . . . . 12:3
OCOD (origin code) attribute 18:6, 18:8, 18:19
ODEF command . . . . . . . . . . . . . . . . 18:30
OFFSET command . . . . . . . . . . 13:5, 18:12
Omitting from RRULEs . . . . . . . . . . . . . . 4:6
ON command 6:3, 12:24, 12:35, 12:45, 13:3,
18:9, 18:10
Orientation
view contents . . . . . . . . . . . . . . . . . 3:11
OSET (offset) attribute . . 13:5, 13:27, 13:29
OSHEE command . . . . . . . . . . . . 17:3, 17:4
OSLV attribute . . . . . . . . . . . . . . . . . . . 17:3
OSRF (Overlay Sheet Reference) attribute 17:3
OTPT command . . . . . . . . . . . . . . . . . 18:31
Outline (OUTL) element . . . . . . . 18:5, 18:25
OVER (Overlay Sheet Template) element 17:2
Overlay (OLAY) element . . . . . . . . . . . 17:3
Overlay Sheet Position (OPOS) attribute 17:1
Overshoot (OSHT) attribute 12:4, 12:8, 12:9,
12:39, 12:47
P
Parallel dimensions 12:6, 12:12, 12:39, 12:40,
12:47
PCENTRE command . . . . . . . . . . . . . 12:33
PCIRCUMFERENCE command . . . . 12:34
PCOPTION command . . . . . . . . . . . . 20:18
PDIM element . . . . . . . . . . . . . . . . . . 12:32
Perpendicular Flat Plane (PPLA) element 5:1,
5:4
PERPENDICULAR keyword . . . . . . . 20:13
PERS attribute . . . . . . . . . . . . . . . . . . . 3:11
Perspective . . . . . . . . . . . . . . . . . . . . . 3:11
controlling . . . . . . . . . . . . . . . . . . . 3:11
Picture files . . . . . . . . . . . . . . . . . . . . . . . B:1
Index page iv
12 Series
Q
Qualifiers:in point construction . . . . . . . 20:6
Querying . . . . . . . . . . . . . . . . . . . . . . . 13:21
AKEYS . . . . . . . . . . . . . . . . . . . . . 12:23
Id Lists . . . . . . . . . . . . . . . . . . . . . . . 3:8
spatial map . . . . . . . . . . . . . . . . . . . 3:8
symbols . . . . . . . . . . . . . . . . . . . . . 19:4
view contents . . . . . . . . . . . . . . . . . 3:20
view direction . . . . . . . . . . . . . . . . . 3:12
QUIT command . . . . . . . . . . . . . . . . . . . 2:4
R
Radial Dimension (RDIM) elements 12:1, 12:44
creating . . . . . . . . . . . . . . . 12:32, 12:44
modifying . . . . . . . . . . . . . . 12:32, 12:44
Radial Dimension Position Point (RPOI) element
12:32
Radial Dimension P-Point (RPPT) element .
12:32
Radial Dimensions
including projection arcs with . . . . 12:31
Radius Dimension
obtaining from Diameter . . . . . . . 12:24
RAYLINE command . . . . . . . . . . . . . . 20:16
RCOD (rotation code) attribute . 3:11, 12:25
Recipient (RECI) element . . . . . . . . . . . 9:2
Recipient name (RNAM) attribute . . 9:2, 9:4
RECREATE command . . . . . . . . . . . 2:1, 2:5
RECT (rectangle) element . . . . 18:19, 18:28
Reflected points . . . . . . . . . . . . . . . . . 20:15
Registry (REGI) element . . . . . . . . . . . . 3:2
REMOVE command . . . . . . . . . . . . 3:5, 3:24
Remove Entry (REME) element . . . . . . . 3:5
REPEAT command . . . . . . . . . . . . . . 18:12
Report (REPO) element . . . . . . . . . . . . . 9:1
Representation Rules
Querying . . . . . . . . . . . . . . . . . . . . 4:11
Setting up . . . . . . . . . . . . . . . . . 4:5, 10:3
Representation Ruleset Reference (RRSF) at-
Index page v
12 Series
S
SAVEWORK command . . . . . . . . . 2:2, 2:5
Scale, of view . . . . . . . . . . . . . . . . . . . . 3:11
SCALFG (Scaling Flag) element . . . . . . 3:18
Scaling Flag (SCALFG) element . . . . . . 3:18
SCTN ends
representation of . . . . . . . . . . . . . . 16:5
Selective styles . . . . . . . . . . . . . . . . . . . . 4:7
SENSE attribute . . . . . . . . . . . 12:40, 12:45
SETFEEDBACK command . . . . . . . . . . 8:24
Sheet (SHEE) element . . . . . . . . . . . . . . 3:1
Sheet Library (SHLB) element . . . . . . . 17:2
SIZE attribute . . . . . . . . . . . . . . . . . . . . . 3:8
SKETCH command . 5:10, 5:13, 18:9, 18:32,
18:39
SLAB (Special Label) element . . . . . . . 3:18
SMOD (Section Mode) attribute . . . . . . . 5:3
SNAP command . . . . . . . . . . . . . . . . . . . 6:4
SORT DIMENSIONPOINTS command 12:7,
12:43
SPAN command . . . . . . . . . . . . . . . . . 18:27
Spatial map
use of by ADD WITHIN command . . 3:7
Special Label (SLAB) element 3:18, 13:1, 18:3,
18:35
SPLA element . . . . . . . . . . . . . . . . . . . . . 5:7
STEP command . . . . . . . . . . . 5:7, 5:8, 5:11
Stepped Plane (SPLA) element . . . 5:1, 5:7
STRA (straight line) element . . . . . . . . 18:30
Straight leader lines . . . . . . . . . . . . . . 13:10
Style attributes
use of to define representation style 4:2,
10:2, 10:3, 10:4
Styles, selective allocation . . . . . . . . . . . 4:7
Sub-strings
of intelligent text . . . . . . . . . . . . . . 14:11
SWITCH command . . . . . . . . . . . . . . . . . 2:3
SYMB (Symbol Instance) element 18:3, 18:33
T
Tabbing
within intelligent text . . . . . . . . . . . . 14:9
TABL (Table) element . . . . . . . . . . . . 18:34
TAG command . . . . . . . . . . . . . 13:20, 13:32
Tag Rule (TAGR) element . . . . . . . . . 13:19
Tag Rule Library (TRLB) element . . . 13:19
Tag Ruleset (TRST) element . . . . . . . 13:19
TAGGING MESSAGES command 13:22, 13:32
TANGENCY keyword . . . . . . . . . . . . . 20:11
TANLINE command . . . . . . . . . . . . . . 20:12
TCOD (Type Code) attribute . . . 18:6, 18:30
Terminator size
controlling . .12:21, 12:47, 13:10, 13:29
TEXP (Text Primitive) element . 18:34, 18:35
Text
alternative character set . . . . . . . . 15:2
Text Alignment (ALIG) attribute 12:26, 13:8,
13:28
Text extent
querying . . . . . . . . . . . . . . . . . . . . 18:35
Text justification (JUST) attribute 13:8, 13:28
Text Label Templates (TXTM) . . . . . . . 3:18
Text Radius (DTRA) attribute . . . . . . . 12:25
Text Radius Flag (DTFL) attribute . . . 12:25
Text colour:defining . . . . . . . . . . . . . . 18:34
Text, editing . . . . . . . . . . . . . . . . . . . . . 15:3
THPO (Through Point) VIEW attribute . 3:12
THPT (Through Point) command 18:17, 18:18
TLIN (true length) attribute . . . . 12:10, 12:12
TMRF (Template Reference) attribute 13:20,
13:23, 18:3, 18:33
TO command . . . . .12:3, 12:6, 12:43, 12:45
TOLERANCE setting . . . . . . . . . . . . . 18:14
TPT (To Point) command 18:18, 18:31, 20:2
TRACE command . . . . . . . . . . . . . . . . . 2:3
True length (TLIN) attribute 12:10, 12:40, 12:43
Truncated dimension . . 12:12, 12:40, 12:47
TXCOLOUR (Text Colour) attribute 13:9, 18:3,
18:34, 18:35
TXTM (Text Label Template) element . 13:1,
13:23
Index page vi
12 Series
U
UCOD attribute . . . . . . . . . . . . . . . . . . 14:15
UDA (User-defined attribute) codewords 14:20
Units Code (UCOD) attribute . . 11:2, 14:15
Universal representation . . . . . . . . . . . . 3:17
UPDATE ALL command . . . . . . . . . . . . 3:25
UPDATE ANNO command . . . . 3:25, 12:42
UPDATE BSHEETS command . . . . . . . 3:25
UPDATE command . . . . . . . . . . . . . . . . 3:25
UPDATE DESIGN command . . . . . . . . 3:12
UPDATE IGNORE command . . . . . . . . 3:25
UPDATE INSTANCES command 2:3, 18:33
UPDATE NAMES command . . . . . . . . . . 2:2
UPDATE NOWAIT command . . . . . . . . 3:25
UPDATE PICTURE command . . . . . . . 3:26
UPDATE REFRESH command . . . . . . 3:25
UPDATE REFS command . . . . . . . . . . . 2:2
UPDATE TAGGING command 13:19, 13:21,
13:32
USE command . . . . . . . . . . . . . . . . . . . . 4:7
W
Warning Messages . . . . . . . . . . . . . . . . 2:4
Wireline views . . . . . . . . . . . . . . . . . . . 3:14
WPOS element . . . . . . . . . . . 5:7, 5:9, 5:11
X
X, Y filtering . . . . . . . . . . . . . . . . . . . . . 20:3
XY position (XYPS) attribute 13:5, 13:14, 13:27
XYPS attribute . . . . . . . . . . . . . . . . . . . . 3:9
XYSC (XY scaling) attribute . . . . . . . . . 3:18
XYSCALE attribute . . . . . 13:16, 17:3, 18:33
Z
Z-coordinates
in DXF files . . . . . . . . . . . . . . . . . . . 7:5
V
Vertex (VERT) element . . . . . . . . . . . . 18:25
VGRID command . . . . . . . . . . . . . . . . . . 6:5
View . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17
centre . . . . . . . . . . . . . . . . . . . . . . . . 3:9
direction . . . . . . . . . . . . . . . . . . . . . 3:12
frame . . . . . . . . . . . . . . . . . . . . . . . . 3:8
gap length . . . . . . . . . . . . . . . . . . . . 3:13
limits . . . . . . . . . . . . . . . . . . . . . . . . . 3:7
orientation of on Sheet . . . . . . . . . . 3:11
ratio . . . . . . . . . . . . . . . . . . . . . . . . 3:10
scale . . . . . . . . . . . . . . . . . . . . . . . . 3:11
size . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8
type . . . . . . . . . . . . . . . . . . . . . . . . . 3:14
View contents
orientation . . . . . . . . . . . . . . . . . . . . 3:11
querying . . . . . . . . . . . . . . . . . . . . . 3:19
VIEW element . . . . . . . . . . . . . . . . . . . . 18:2
View Gap (VGAP) attribute . . . . . . . . . . 3:13
View Scale (VSCA) attribute . . . . . . . . . 3:18
View Section (VSEC) element . . . . 5:3, 5:9
Views
labelling . . . . . . . . . . . . . . . . . . . . . 13:5
querying . . . . . . . . . . . . . . . . . . . . . 3:20
Visibility
of primitives . . . . . . . . . . . . . . . . . 18:15
VNOT (View Note) element 18:3, 18:5, 18:6,
18:11, 18:35
VRAT attribute . . . . . . . . . . . . . . . . . . . 3:10
VREGION command . . . . . . . . . . . 3:9, 3:26
VSCA (View Scale) attribute . . . . . . . . . 3:18
12 Series