Pdms Draft User Guide

DRAFT User GuideAVEVA Solutions Ltd Disclaimer Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law. Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or entity for any actions, claims, loss or damage arising from the use or possession of any information, particulars, or errors in this publication, or any incorrect use of the product, whatsoever. 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 AVEVA Solutions Ltd or its subsidiaries. All other rights are reserved to AVEVA Solutions Ltd 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 Ltd Where such permission is granted, it expressly requires that this Disclaimer and Copyright notice 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 Ltd. The user may also not reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution. The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms and conditions of the respective licence agreements, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited. First published September 2007 © AVEVA Solutions Ltd, and its subsidiaries AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom Trademarks AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden. AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its subsidiaries, registered in the UK, Europe and other countries (worldwide). The copyright, trade mark rights, or other intellectual property rights in any other product, its name or logo belongs to its respective owner. DRAFT User Guide DRAFT User Guide 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 General and Database Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 Saving and Restoring the Current Display Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 Saving Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2 Seeing Changes Made by Other Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2 Database Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2 Cross-Database Referencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2 Switching Between Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3 Updating Symbol Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3 Miscellaneous Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3 Audible Error Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switching Text Output Off (DEVICE TTY only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging the Alpha Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling Output of Warning Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3 2:3 2:4 2:4 Summary of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4 Entering DRAFT.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4 Leaving DRAFT... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4 i 12.0 DRAFT User Guide Saving and Restoring the Current Display Status... . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving and Getting Work... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Update Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audible Error Trace.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text Output of Current Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling and Logging the Alpha Display... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Suppressing Warning Messages... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5 2:5 2:5 2:5 2:6 2:6 2:6 2:6 Drawing the Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1 Introducing the DRAFT Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1 Creating a Drawing, a Sheet and a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2 Defining the Contents of a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3 Defining View Contents Using the AUTO Command . . . . . . . . . . . . . . . . . . . . . 3:3 Defining VIEW Contents Using Id Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4 Adding Elements to 3D View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selective Additions to the Id List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Spatial Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Limits of the View Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cleaning Up Id Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying Id Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5 3:5 3:6 3:6 3:7 3:7 Changing the Picture by Changing VIEW Attributes . . . . . . . . . . . . . . . . . . . . . 3:7 VIEW Frame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8 View Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8 View Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9 View Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10 Orientation of View Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10 Perspective. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:11 3D View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:11 Looking Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:11 Representation Ruleset Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12 Hatching Ruleset Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12 Change Ruleset Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12 Arc Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12 View Gap Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12 Suppressing View Clipping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:13 Ignoring the DUNION attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:13 More on the AUTO Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:13 Hidden Line Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:13 ii 12.0 DRAFT User Guide 2D Symbolic Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17 Scaling Design Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:18 Orienting Design Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19 Querying Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19 Querying View Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19 Querying Whether an Element Appears in a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19 Querying the Nearest Side to an Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:20 Background Process Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:21 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initiating and Using the BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Jobs using the Background Process Manager Form. . . . . . . . . . . . . . . . . . . . . Tabbed Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cancel, Delete and Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Jobs Collectively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Jobs Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:21 3:21 3:21 3:23 3:23 3:23 3:23 3:24 Summary of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:24 At Id List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At DRWG and below . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Anywhere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying Contents of a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:24 3:25 3:26 3:28 3:28 Graphical Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Representation Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 Representation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Representation Rules for 2D Symbology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selective Style Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 4:6 4:7 4:8 4:8 Automatic Hatching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8 Hatching Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9 Which Elements can be Hatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10 Hatching Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10 The Hatch Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:11 iii 12.0 DRAFT User Guide Querying Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:11 Querying Rulesets and Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:11 Querying Hatching Rulesets and Styles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:12 Summary of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:12 At Representation Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At Representation Style . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At Hatching Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At Hatching Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:12 4:12 4:13 4:14 Section Planes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1 Creating and Using Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3 Perpendicular Plane (PPLA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4 Flat Plane (FPLA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5 Stepped Plane (SPLA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7 Altering Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9 Plane Querying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10 Summary of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:11 Setting Plane Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For SPLAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Section Plane Points Directly . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switching Retain/Discard Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving Section Plane Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Section Plane Points . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up the VIEW to Accept Section Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Plane Sketching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Plane Erasing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:11 5:11 5:11 5:11 5:12 5:12 5:12 5:12 5:13 5:13 Using the Cursor with DRAFT Comments . . . . . . . . . . . . . . . . . . . . 6:1 Identifying Elements Using the Cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Picking P-points and Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 P-point Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:3 Picking Structural Elements and P-lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:3 Querying Position Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4 Snapping 2D Points to a Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4 Highlighting Displayed Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:6 Summary of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7 iv 12.0 DRAFT User Guide Cursor Identification/Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-point Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Highlighting Elements... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Snapping 2D Points to a Grid.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7 6:7 6:7 6:8 6:8 Plotting and Drawing Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 Extended Output Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2 Standard DXF Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:4 Creating the DXF File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DXF File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File Header Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encoding of Multi-Byte Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaling .............................................................. 7:4 7:4 7:5 7:6 7:6 Configurable DXF and DWG Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:6 Configuration Datasets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:6 Switches and BLOCK Rules to Control DXF and DWG Export . . . . . . . . . . . . . . . . . . . . . . 7:9 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:14 Configurable DGN Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:14 Configuration Datasets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:14 Sample Configuration Datasets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:16 Common Features of Option Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:17 General Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:17 Quoted Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:18 Continuing Long Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:18 File-Related and Miscellaneous Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:18 OutputFileName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SeedFileName. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Units ........................................................................... ScaleFactor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ShiftX ........................................................................... ShiftY ........................................................................... ExcludeBack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ExcludeOlay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ExcludeSheetFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ExcludeFill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ExcludeSolidFill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ExcludeArrowFill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MapLineWeights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MapLineStyle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MapLineStyleByPen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MapColour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MarkerSize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:19 7:19 7:19 7:20 7:20 7:20 7:20 7:20 7:20 7:21 7:21 7:21 7:21 7:21 7:22 7:22 7:23 Line/Colour Related Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:21 v 12.0 . . . . . . . . . . . . .. .. . . . . . . . . . . . . . . . . . . . . . . 7:24 Level-Related Options . .. . . . . . . . . 7:23 FontSlopes . . . . . . . . . . . . . . . .. . . . . . . . . . . Selecting the Library Destination. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . 8:10 vi 12. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . PDMS Font File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . GroupFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:33 7:33 7:33 7:33 7:33 7:34 7:34 7:34 Mapping the Installed Fonts . . . . . . . . . . . .. . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . 7:27 Summary of Switches and Rules to Control DGN Export . . Copying the Fonts into the Library . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . LevelBack . . . . . . . . . . . .. . 7:31 Installing PDMS Fonts into MicroStation . . . . . . . . . .. . 8:9 Glyphs . . . .. . . . . . . 8:6 User-Defined Line Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:24 7:24 7:25 7:25 7:26 7:26 7:26 7:26 Group Related Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . . . . . . . . . . . . . . . . . . . 8:6 System-Defined Line Styles . . .. . . . . . . . Group Rules . . . . . . . . . . . . .. . . . . Changing MicroStation Font Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 7:27 Validation feature and options . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 7:31 Guidelines for Importing DGN Files from DRAFT into MicroStation. . . . . . . . . . . . . . . . . . . . . . . . . Level Rules . . . . . . . . . . . . . . . . . . . . . . . . . . .DRAFT User Guide Font Related Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:10 Pre-defined Glyphs . . . . . . .. . . . . 7:23 MapFont . . . . . . . . . . 7:27 LogFileName . . . . . .. .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . .rsc Library . . . . .. . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. .. . . . . . . . . . . . . GroupFill . . . . . . . . . . Line Styles . . . . . . . . . LevelPen . . .. . . . . . . . . . .. . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .shx Files to Add to Resource Library . . . . . . . . . . . . . . . . . . . . . . . . 7:35 7:35 7:36 7:37 Colours and Styles . . . . . . . . . . . . . . . . . . . . 8:7 Basic Line Style Functionality . . . . . . . . . . . . . . . . .. . . . . . . . . 8:3 Line Styles . . . . . .. . . . 7:26 Product Support Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . 7:31 Introduction. . . 7:28 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:32 Creating a New Font Resource Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:31 Exporting DRAFT Drawings Containing PDMS Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . . . . . . . . . . . . . . . . . . 8:1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GroupSymb . . . . . . . . . . . . . . . . . . Creating a New Font Geometry File . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Installation . 8:7 Advanced Line Style Functionality .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . . . . . . . . . Colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:24 LevelDefault . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select the Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1 Colours . . . . . . . . . Selecting . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:12 8:12 8:12 8:13 Using Glyphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:15 User-Defined Fill Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circulation Lists and Revisions . . . . . . . . . . . . . . . . . . . . . 8:20 Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:4 Attribute Setting . . . . . . . . . . . . 8:15 System-Defined Fill Styles . . . . . . . . . . . 8:14 Fill Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .DRAFT User Guide User-Defined Glyphs . . . . . . . . . . . . . . 10:3 Annotation Change Rules . . . . . . . . . . Element GLYCIRcle has attributes: . . . .0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:9 At Annotation Change Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 8:18 Using Fillstyles . . . . . . . . . 10:8 At Design Change Rule . . . . . . . . . . . . . . . . . . . . 10:8 At Design Change Style . . . . 9:2 Drawing Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2 Annotation Change Styles . . . . . . 9:3 Summary of Commands . . . . . . . . . . . . . . . Element GLYRECtangle has attributes: . . . . . . 9:4 At Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2 Change Rules . . . . . . . . . . 10:6 Querying Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:7 Querying Change Rulesets and Design or Annotation Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:8 At Annotation Change Rule . . . . . . . . . . 8:19 Graphical Feedback Style and Colour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Element GLYOUTline has attributes: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SHOW CHANGES Option and Error Messages . . . . . . . . . . . . 10:10 vii 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:7 Summary of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4 At Circulation List . . . . . . . . . . . . . . . . . . . . . . . 8:19 Marker Styles . . . . . . . . . 10:3 Design Change Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 Circulation List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1 Design Change Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4 Change Highlighting . . . . 10:5 UPDATE Command. . . 10:4 Comparison Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Radial Dimensions through Graphical Interaction . . . . . . . Positioning the Dimension Line . . . . . . . Setting Dimension Directions . . . . . . . . . . . . . . 12:1 Dimension Element Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appearance of Radial Dimensions . . . . . . . . . . . 12:39 Suppressing the Display of Dimension and Projection Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:8 Detail Attributes of Linear Dimensions . . . . . . . . . . . . . . . . Appearance of Radial Dimensions . . . . 12:38 Detail Attributes of Angular Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:24 12:24 12:30 12:31 12:32 12:32 Pitch Circle Dimensions . . . 12:32 Creating Pitch Circle Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:6 Principal Attributes of Linear Dimensions. . . . . 11:1 Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .DRAFT User Guide Introduction to Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . Appearance of Radial Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2 Intelligent Text Attributes . . . . . . . . . . . . . . . . .General Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:39 Identifying Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:33 Angular Dimensions . . . . . . . . . . . . . . . . . . . Creating Radial Dimensions using the Cursor . . . . . . . . . . . . .Ancillary Graphics Attributes. . . . . . . . . . 12:21 Creating Radial Dimensions. . . . . 12:1 Linear Dimensions . . . . . . . . . . . . . . . . . . . . . . . 12:34 Principal Attributes of Angular Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Specific Attributes . . . . . . . . . . . . . . . . . . . . . 12:41 12:41 12:41 12:42 viii 12. . . . . . . 11:2 Design Symbol Layers . . . . . . . . . . . . . . . . . . . . . . . . . . 12:40 Updating Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:40 Summary of Commands . . . . 12:12 Radial Dimensions . . . . . . . . . . . . . . . . . . . . 11:2 Dimension and Label Attributes . . . . . . . 11:3 Autoblanking . 12:41 Creating Linear Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating and Modifying Radial Dimensions . . . . . . 12:39 Dimensioning Skewed Pipe in Isometric Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 12:2 Multi-valued Dimensions . . . 11:3 Dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:34 Angular Dimensions and How to Create Them . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:2 Linear Dimensions and How to Create Them . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:6 Hiding Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:18 Defining the Autotagging Hierarchy and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Labels and Text Label Templates . . . . . . . . . . . . . . . . . . . .0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Projection Line and Projection Line Text . . . . . . 13:10 Varying the Leader Line Connection Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:18 Introduction. . . . . . . . . . . . . Querying . . . . . . . . . . . . . . . . . . . . . SLAB Leaderline Connection Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Label Generation . . . . . . . . . Setting Gaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Label Editing and Copying . . 13:7 Leader Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:42 12:43 12:43 12:44 12:45 12:45 12:46 12:47 12:48 Labelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:13 Leader Line Gaps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Labels and Symbol Templates . . . . . . . . . . . . . . . . . . Miscellaneous Operations on Dimensions . 13:7 Label Text Manipulation . . . . . . . . . . . . . 13:20 Elements to be Tagged . . . . . . . . . . . . . . . . 13:5 Label Frame Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:19 Controlling Label Appearance and Elements to be Tagged. Radial Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:20 13:21 13:22 13:23 13:23 ix 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:14 Modifying Labels through Graphical Interaction . 13:1 Creating and Manipulating Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Unwanted Dimension Points . . . . . . . . . . . . . . . . 13:2 Labelling Views . . . . .. . . . . . . Tag Rule Editing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:15 Introduction. . . . . . . . . . . . . . . . . . . . . . . 13:14 Special Labels and Label Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:5 Positioning and Orienting Labels . . . . . . Creating Angular Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2 Creating Labels and Label Text . . . . . . . . . . . . . . . . . . . . . . . 13:15 13:15 13:16 13:16 13:17 Autotagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .DRAFT User Guide Creating Pitch Circle Dimensions . . . . . . . . . . . . . Scaling and Mirroring Special Labels . 13:20 Label Appearance . . . . . . . . . . . . . . . . . . . . 13:1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Dimension Line and Dimension Line Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:20 Querying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tracking the Autotagging Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:27 13:27 13:27 13:28 13:28 13:29 13:30 13:30 13:30 13:31 13:31 Intelligent Text . . . . . . . . . Setting Leader Line Attributes (SLABs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . 14:8 14:8 14:9 14:9 14:9 14:9 Substrings . . . . . . . . . . . . . . . . . . . 14:2 P-point Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Underlining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aligning the Label Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:3 Accessing Data in Catalogue Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Emboldening and Italicising . . . . . . . . . 14:7 Codewords with Special Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:10 String Definition by Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Autotagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Label Text Attributes . . . . . . . . . . . . . . . . . New Line Generator . . . . . 14:5 Accessing Dimensioning Data . . # Character. . . . . . . . 14:2 P-line Data . 14:6 Accessing UDA Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab Generator Codeword. . . Setting Label Frame Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Leader Line Attributes (GLABs) . . . . . . . . . . . . . . . . . 14:6 Accessing Administrative Data . . . . . . .0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:10 Array Indexing . . . . . . . . . . . . . . .DRAFT User Guide DATAL Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:10 Substring Definition by Parts . . . . . . . . . . . . . . . . . . . . . . . . 14:8 Template Codeword . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:27 Setting Label Attributes . . . . Querying . . . . .. . . . . . . . . . . . . . . . 14:1 Codewords . . . . . . . . . . . . . 13:23 Schedule Generation . 14:1 Accessing Data from the DESIGN or Catalogue Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:24 Intelligent Label Placement . . . . Spreading Label Positions . . . . . . . . . . . . . . . . . . . . . . . . 14:11 x 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Gaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting unwanted Labels . . . . . . . . . . . 13:24 Summary of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:4 Accessing Data from the DRAFT Database . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:19 14:20 14:20 14:21 14:21 14:21 14:21 14:22 14:22 14:22 14:22 14:23 14:23 14:23 14:24 14:24 Summary of Commands . .. . 14:18 Intelligent Text Syntax . . Setting Units (at LAYE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying. . . . . . . . . . . . . . . . . .. . . . . . . . Position and Bore Data Output . . . . . . . . . . . . . . 14:16 Position Output Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15:5 Assigning Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DRAFT Drawing World Hash Codes. . . . . . . . . . . . . . .. Attribute Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hash Code Delimiters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15:1 True Type Fonts . . . . . . . . . . . . . . . . . .. . . . . . . 15:1 Multiple Fonts within Text Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . .. . . . . . . . . . . . . . . . . .0 . . . . . . . . . . . . . .DRAFT User Guide Transforming Position/Direction Data . . . . . . . . . . . . . . . . . 15:2 Alternative Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:14 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:15 Controlling the Precision of the Generated Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15:3 Querying Fonts. . . . . . . . . . . . . . . . . . . 14:13 Distance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Summary .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . Array Indexing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Position Output Format . 14:18 Notes . . . . . . . . . . . . . . . . . . . . . Specifying the Grid System (for GRIDLIN search) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . . . . . . 14:12 Extracting Attribute Data from any Specified Element. . . . .. Transforming Position/Direction Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous Text Facilities . . . . . . . . . . . . 15:1 PDMS Fonts . . . . . . . . . . . . . . . 15:5 xi 12. . . . .. . . . . . . . . . . . . . . 14:17 GRSYS (Grid System) Attribute . . . . . . . . . . . . . . . . 14:17 Customizing Error Text . . . .. . . . . Extraction of P-line Data. . . . . . . . . . . . . .. . . . . . . . .. . . . . . . . . . . .. . . . . . Sub-Strings. . . . . . . . . . . . . . . . . . Updating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:20 Design World Hash Codes (examples). . . . . . . . . . . . . . . . . . . . Controlling the Precision of the Generated Output. . . . . . . . . . . . . . . . . . . . 15:2 Editing Text. . . . . . . . . . . . . . . 14:14 Mixed Units within Intelligent Text Strings . . . . . . . . . . . . . 14:16 POSFOR (Positional Code Word Format) Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:1 Database Elements for Underlays and Overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:4 Underlays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-line Direction . 16:1 Basic Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:3 P-line Design Element . . . . . . . . . . . . 18:6 Shifting the Origin . . . . . . . . . . . . . . . . . . . . 16:2 P-line Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:1 Symbol Templates . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 18:11 xii 12. . . . . . . . P-line Angle . . . . . . . . . . 18:8 Moving Individual Primitives . . P-line Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:9 Querying Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:9 Moving Groups of Primitives . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:1 Introduction . . . . . . . . . . . . . . . . 17:4 Manipulating Overlays. . . . . . . . . . . . . . . . 16:3 16:3 16:4 16:4 16:4 16:4 Representation of SCTN Ends . . . . . . . . . . . . . . . . . . . . . . . . . . .0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .DRAFT User Guide Character Height . . . . . . . 17:1 Using Plotfiles . . . . . . . . . . . . . . . . . . . . . . . . . 18:1 Introduction . . . . . . . . . . . . . . . . . 16:2 Angle from a P-line . . . . . . . . .Common Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:4 2D Drafting Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:1 Where 2D Drafting is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:10 Handling Common Drafting Primitives . . . . . . P-line Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:1 3D Direction from a P-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:1 Backing and Overlay Sheets . 17:4 2D Drafting . . . . . 15:6 Annotating Structural Elements in DRAFT . . . . . . . . . . . 18:3 The Drafting Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:5 Underlays and Overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-line Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 17:2 Summary of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:1 3D Position from a P-line. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:4 Overlays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:5 Creating and Manipulating Drafting Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:6 Creating Primitives and Varying Basic Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphical Feedback . . . . . . . . . . . . . . . . . . . . . . . . Mirroring Individual Primitives . . 18:36 Creating Primitives . . Copying a Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating and Manipulating Drafting Primitives . . . . . . . . . . . . . . . . . . . . . . . . 19:1 Attributes of ISODRAFT Symbol Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19:3 Outputting ISODRAFT Symbols . . . . . . . . . . . . . . . . . . . . . . . . . OUTLINE (OUTL) and VERTEX (VRTX). . . . . . . . . . . . . . . . . . . . . . . . . . . Rotating Individual Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EQUILATERAL TRIANGLE (ETRI) . 19:2 Wildcards in SKEYs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:36 18:36 18:37 18:37 18:37 18:37 18:38 18:38 18:38 18:39 18:39 ISODRAFT Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:12 18:12 18:12 18:13 18:13 Re-use of Drafting Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sketching Drafting Points . . . . . . . . . . . . . . . ELLIPSE (ELLI) . . . . . . . . . . . . . . . . . . . . SYMBOL INSTANCE (SYMB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:35 Entering Text from DRAFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhancing Drafting Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MARKER PRIMITIVE (MRKP) . . . . . . . . . . . . . . . . Enhancing Display of Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying Primitives . . . . . . . . . . . Copying Primitives . . . . . . RECTANGLE (RECT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19:3 Example . . . . . . . . . . . . . Moving Individual Primitives . . . . . . . TABLE (TABL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .DRAFT User Guide Moving all Primitives in a NOTE or VNOT. . . . . . . . . . . . . HEXAGON (HEXA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:14 18:15 18:15 18:16 18:16 18:19 18:22 18:22 18:23 18:24 18:25 18:25 18:28 18:30 18:33 18:34 18:34 ARC (ARC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIAMOND (DMND) . . . . . . . . . . . . 19:1 Creating ISODRAFT Symbol Templates . . . . . . . . . . . . . STRAIGHT (STRA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19:4 xiii 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:36 Summary of Commands . . . . . Shifting the Origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving Groups of Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Visibility of Drafting Primitives . . . . . . . . . . . . . . . . CIRCLE (CIRC) . . . . . . . . 18:35 Displaying Text from a File on the Drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rotating a Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mirroring a Primitive . . . . .Specific Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text Strings . . . . . . . . . . TEXT PRIMITIVE (TEXP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drawing the Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:16 Chamfer Lines . Overlay Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:17 Non-Drafting Applications of Point Construction . . . . 20:12 Perpendicular Intersection Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:13 Reflected Points . . . . . . . . . . . 20:9 Tangency Point . . . . . . . . . . . . .0 . . . . . . Other Non-Drafting uses of Point Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:11 Tangent Lines. . . . . . . . . . . . 20:8 Intersection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:6 Centre or Focus Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19:4 Point and Line Construction . . . . . . . . . . . . . . . .B:1 xiv 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .DRAFT User Guide Querying ISODRAFT Symbol Templates . . . . . . . . . . . . . . . . . 20:16 Bisector Lines. . . . . . . . . . . . . 20:15 Constructed Lines. . . . . . . . . . . . . . . . . . . . . 20:2 Construction of 3D Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:1 Picture File Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:17 20:17 20:18 20:18 20:18 20:18 DRAFT Database Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:1 X. . 20:7 ‘Nearest To’ Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:17 Labelling . . . . . . . . . . . Dimensioning . . . . . . . . . . . 20:15 Fillet Arcs . . . . . . . . . . . . . . . 20:15 Ray Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:4 Midpoint Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:4 Midpoint of an Existing Straight Line or Arc . . . . . 20:4 Quadrant Point Position . . . . . . . . . . . . . . . . . . . . . . . . 20:4 Midpoint of Two Defined Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:5 Endpoint Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:15 Constructed Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Y Filtering . . . . . . . . . . . . . . . . . . . . .A:1 Basic Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . Ray Lines and Bisector Lines . . . . Point Construction Option Form . . . . . . . . . . . . . . . . . . It is assumed that you are familiar with the normal way of using DRAFT. see the Software Customisation Guide and Software Customisation Reference Manual. through the supplied Graphical User Interface (GUI).3 Who Should Read this Manual This is a command-level manual. For general information about customising the graphical user interface. 1. including not only dimensioning and text but also such items as leader lines and label boxes. The drawing can be displayed on the screen and processed to produce a hard copy plotfile. 1.1 Introducing DRAFT What does DRAFT do? DRAFT produces fully annotated scale drawings showing selected parts of the design model created in DESIGN. DRAFT is fully integrated with DESIGN. A drawing may contain more than one view of a 3D model. with hidden detail automatically removed or shown in a different linestyle. The DRAFT database does not contain information describing the geometry of the graphics that make up a drawing. see Drawing Production User Guide. but gives a description of how those graphics should be presented on a drawing. 1:1 12. for example. All the graphic items exist as.0 . elements in the DRAFT database. For information about DRAFT System Administration. For an introduction to using DRAFT via the GUI. Graphics to provide backing and overlay sheets which will be common to a number of drawings. a front elevation and an isometric view may be displayed simultaneously. It describes all the DRAFT commands. written for people who are writing or customising their own graphical user interface. 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. A model can be viewed from any direction. with worked examples where appropriate. or are defined by. In DRAFT an annotated drawing is made up of different types of graphics: • • • Graphics that represent the 3D model. Graphics providing annotation.DRAFT User Guide Introducing DRAFT 1 1.2 DRAFT Database The DRAFT database (DB) contains a complete definition of a DRAFT drawing. a plan view. as required. see the AVEVA DRAFT Administrator Application User Guide. describes how dimensions are added to drawings in DRAFT.DRAFT User Guide Introducing DRAFT 1. It describes how Change Rules are defined and describes the part of the DRAFT database that stores the Change Rules. text quality. 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.0 . describes how to label and dimension structural elements. Drawing the Design. editing text attributes. which are available in DRAFT. describes some general commands. describes how. Graphical Representation. at any time during the drawing process. using Planes in DRAFT. describes how to create a DRAFT picture without annotations. font selection. reports and circulation lists. Plotting and Drawing Output. Underlays and Overlays. describes the use of underlays and overlays on a Sheet to add standard elements such as borders. • • • • • • • • • • • • • • • 1:2 12.4 Organisation of the DRAFT User Guide The DRAFT User Guide manual is divided into the following chapters: • • General and Database Commands. inserting symbols using the alternative character set. describes labels. Circulation Lists and Revisions. with many DRAFT commands. which are the areas used to display Design elements. 2D Drafting. Dimensioning. describes the use of code words to automatically extract data from the Design. you can use the cursor to identify an element in the graphics window by using the ID command followed by an @. Using the Cursor with DRAFT Comments. Miscellaneous Text Facilities. common to several Plant/Marine modules. a plotfile consisting of a single Sheet. describes how the following text parameters can be manipulated in DRAFT. keyplans. describes how to create the drawing office administrative elements. Change Highlighting. Colours and Styles. describes DRAFT's two-dimensional drafting facilities and explains how these can be used to complement its main drawing production facilities. It also describes how DRAFT handles revision numbers. which can be displayed at VIEW level. It also describes how to apply 3D data to annotation elements. Intelligent Text. It also describes the part of the DRAFT database that stores dimensions. It also describes Views. describes how Design elements are defined and drawn using Representation Rules. describes the part of the DRAFT database that stores annotation elements. View. It describes how Representation Rules are defined and describes the part of the DRAFT database that stores the Representation Rules. Labelling. how they are created and the part of the DRAFT database that stores them. and how to use structural elements in 2D drafting. describes how you can generate. title blocks. Annotating Structural Elements in DRAFT. used for the automatic hatching of faces of Design elements. describes how you use Change Rules to control how Design and Annotation elements that have been changed are drawn on a DRAFT View. etc. defines the attributes that are associated with pens and describes how to set these attributes. or the content of an Area View. Section Planes. It also describes Hatching Rules. describes how you can construct sections through Design items. character height. Reports. It describes the part of the DRAFT database that stores the main administrative and graphical elements and how to create them. using multiple fonts within a text string. and how to define their content. Catalogue or Drawing databases. describes how ISODRAFT Symbols can be created in DRAFT and exported to an ISODRAFT Symbol File. DRAFT Database Hierarchy provides a graphical representation of the DRAFT database structure. describes how a drafting position can be defined by reference to other positions rather than explicitly. describes the structure of picture file names.0 . Picture File Naming Conventions.DRAFT User Guide Introducing DRAFT • • • • ISODRAFT Symbols. Point and Line Construction. 1:3 12. DRAFT User Guide Introducing DRAFT 1:4 12.0 . for restoration later. changes from default Style/Colour configuration. common to several Plant/Marine modules. Example: RECREATE /DS1 saves the display status in file /DS1. text quality etc. (Refers to file saved by RECREATE. 2:1 12. RECREATE /DS1 OVER as above. units. refer to the AVEVA Database Reference Manual. and some useful database commands.g. e. 2.1 2.) Note: Forms resized or moved using the cursor will be INSTALLed to their original size.0 .1 Saving Saving and Restoring the Current Display Status If the intention is to leave DRAFT for a short period only the RECREATE/INSTALL facility allows the display setup (including the full forms and menus set) to be saved.DRAFT User Guide General and Database Commands 2 General and Database Commands This Chapter describes some general commands. For information on using commands relating to multiple and multiwrite databases. INSTALL SETUP /DS1 restores the display definition stored in file /DS1.1. but an existing file /DS1 is overwritten. RECRE DISPLAY /DS2 saves modal settings. Read back in using $M/name. not RECREATE DISPLAY. The element_identifier can be omitted.1. IDLN. 2. 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. IDLX. These three attributes can be queried but not set by the user.3 Seeing Changes Made by Other Users The command: GETWORK updates the DRAFT database with the changes made by other users. and IDNM attributes of element_identifier. It is good practice to use this command on a regular basis during a long DRAFT session to ensure maximum data security.DRAFT User Guide General and Database Commands 2. and IDNX respectively. in which case the current element will be assumed. so long as those elements referenced from DRAFT databases are all named. to match the values obtained from the associated text attributes. These messages will be of the form: 2:2 12.0 . Setting a DDNM.1 Database Commands 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. or IDNM reference attributes also have ‘system’ text attributes DDNX. and all elements below it in the DRAFT database hierarchy.e. and IDNX attributes to match the values obtained from the associated reference attributes. All DRAFT elements with DDNM. IDLN or IDNM attribute will also cause the associated ‘system’ text attribute (i. values in DDNX. This means that if a DESIGN database is deleted and rebuilt then. This option has been included primarily to allow a full set of these new text attributes to be generated for existing DRAFT databases.2 2. DRAFT will always use the DDNM.2 Saving Work The command: SAVEWORK saves the current DRAFT additions or modifications without leaving DRAFT.2. IDLX. references in DRAFT databases can easily be kept up to date. IDLX and IDNX will be ignored.1. DDNX. IDLN. IDLX and IDNX respectively) to be set to the name of the Design element referenced. The second command will change the DDNX. so long as it is named. 2. In each case no change will occur if a value cannot be obtained from the name/ reference encoding/decoding process. if the database has been opened in multi-write mode. IDLN and IDNM attributes. 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. If the current element is a Catalogue Component. the element name is not displayed. TRACE is always set to OFF automatically. This command allows the audible warning to be switched on or off either interactively or via a macro.2 Switching Between Databases You can switch between the DESIGN.3 Updating Symbol Instances The command: UPDATE INSTANCES (valid at SHEE. 2:3 12. ALARM OFF suppresses the audible tone until it is turned on again.2 Switching Text Output Off (DEVICE TTY only) The TRACE command is only relevant in TTY mode. it will sound whenever an error alert is displayed.3.3 2. the name of an element is displayed as it is accessed. OLAY and BACK elements are in the same category.0 . With TRACE set to ON. OVER. 2. there is an audible alarm at the workstation to signal that the error has occurred.PIPES GLAB 1 of /D1/S1/V1/LAYER1: unable to update DDNX attribute 2. For example. With Trace set to OFF. DRAFT and Catalogue Databases using the command: SWITCH If the current element is in the DESIGN database.2.1 Miscellaneous Facilities Audible Error Trace When a macro error occurs. ALARM ON sets the audible tone to be on. SYLB. giving the SWITCH command when in the DRAFT database will return to the element last selected in the Design database. SWITCH will return to the last Design element accessed. Similarly. When macros are being run. SWITCH will make the element last selected in the DRAFT database current.2. 2.DRAFT User Guide General and Database Commands VSEC 2 of /VIEW2: IDLN attribute updated to /ZONE1.3. BACK. If the audible warning is ON. You can go directly to the DRAFT database or DESIGN Database using the commands: CONTEXT DRAWING CONTEXT DESIGN 2. a SYMB is an ‘instance’ of a SYTM. It controls the automatic output of the Current Element name. Occasionally. macro errors can be anticipated and no audible warning is required. LALB or above) scans the database hierarchy and updates all those parts of picture files which use the graphics ‘instancing’ mechanism. 2:4 12.. not the system's responses.2 Leaving DRAFT.4.0 . 2. DRAFT enters DRAFT 2..DRAFT User Guide General and Database Commands Example: TRACE OFF TRACE ON stops the automatic name output. saving database changes.3. (default) restarts automatic output of Current Element name..3 Logging the Alpha Display The ALPHA command allows you to log commands and responses displayed in the Command Input & Output window.3.1 Summary of Commands Entering DRAFT.4.4 2. without saving database changes. module_name switches to named module. 2.4 Controlling Output of Warning Messages The WARNINGS command allows you to suppress the output of warning messages: WARNINGS OFF WARNINGS ON suppress the output of warnings enable the output of warnings (default). 2. QUIT module_name switches to named module. QUIT leaves DRAFT without saving database changes.. but overwrite existing file /LF1 finish logging information ALPHA FILE will only record commands you give. Examples of the ALPHA LOG command are: ALP LOG /LF1 ALP LOG /LF1 OVER ALP LOG END log displayed alpha information in file /LF1 as above. IDLX and IDNX attributes of element_identifier.6 Database Switching SW switch Design/Drawing contexts CONT DRAW switch to Drawing context CONT DES switch to Design context 2:5 12. changes from default pen configuration. SYLB. units. 2. and all elements below it in the DRAFT database hierarchy. UPDATE element_identifier NAMES changes the DDNX.4. OVER. (OVERWRITE option overwrites existing file of the same name) RECREATE DISPLAY name OVERWRITE] saves modal settings..g..4. e.DRAFT User Guide General and Database Commands 2. UPDATE INSTANCES (valid at SHEE.4.0 . text quality etc.5 System Update Commands UPDATE element_identifier REFS changes the DDNX. not RECREATE DISPLAY.4 Saving and Getting Work.) 2. 2.4. BACK.. RECREATE name [OVERWRITE] saves the display status in the named file. (Refers to file saved by RECREATE. to match the values obtained from the associated text attributes.. SAVEWORK saves the current DRAFT additions or modifications without leaving DRAFT GETWORK updates drawings with any changes made to the PADD database by other users.3 Saving and Restoring the Current Display Status. IDLX and IDNX attributes to match the values obtained from the associated reference attributes. Read back in using $M/name. LALB or above) scans the database hierarchy and updates all those parts of picture files which use the graphics ‘instancing’ mechanism. INSTALL SETUP name restores the display definition stored in the named file. .. ALARM OFF turns audible error trace ON or OFF. 2:6 12.10 Suppressing Warning Messages.4.7 Audible Error Trace..8 Text Output of Current Element Name TRACE OFF. ALARM ON. 2.4.4.0 . WARNINGs OFF suppress the output of warnings WARNINGs ON enable the output of warnings (default).9 Controlling and Logging the Alpha Display. ALP LOG /LF1 log displayed alpha information in file /LF2 ALP LOG /LF1 OVER as above.DRAFT User Guide General and Database Commands 2. TRACE ON stops or starts automatic name output.... but overwrite existing file /LF1 ALP LOG END finish recording alpha information 2.4. 2. DRAFT User Guide Drawing the Design 3 Drawing the Design This Chapter describes how to create an unannotated DRAFT picture. which correspond to the sheets of a paper drawing (‘Sheet 1 of 3’. All other database elements are also named using four upper-case letters (e. view (lower case letters) means an area view. through point.1 Introducing the DRAFT Database The top-level graphical elements in the DRAFT Database hierarchy are shown below. position and orientation of the region on the Sheet that the View occupies 3:1 12. Note: Throughout this manual. but may also be referred to in unabbreviated form with just a leading upper-case letter (e. whereas VIEW (upper-case letters) refers to the VIEW database element. A Sheet may own one or more VIEW elements.g. 3. etc) define the size. All the elements below DRWG in the hierarchy are used to store the information required to completely define the Drawing. LIBY). alpha view or plot view.0 . A VIEW element has attributes that: • • define the viewing parameters (looking direction. DRAFT Database Hierarchy . ‘Sheet 2 of 3’ etc). Drawing instead of DRWG). and how to define their contents. These are projections of parts of the Design Database. which is the Database equivalent of the traditional paper drawing. A Sheet is the highest-level element that may be displayed within a view. DRAWING SHEET VIEW Figure 3:1.g. It then describes Views. DRWG. and how to create them. scale. A Drawing can consist of a single Sheet.Principal Graphic Elements The principal element is the Drawing (DRWG). It describes the part of the DRAFT database that stores the main administrative and graphical elements. SHEE. A Drawing can own one or more Sheet (SHEE) elements. which are the areas used to display design elements. The full DRAFT database hierarchy is illustrated in DRAFT Database Hierarchy. one Registry and one Sheet on the Drawing. Users cannot delete or create the World.DRAFT User Guide Drawing the Design • refer to another DRAFT database element that contains a list of the Design (or Catalogue) elements that make up the VIEW picture. 3. as shown in the following diagram.2 Creating a Drawing. Departments (DEPT) and Registries (REGI) are administrative elements. REME Top part of the DRAFT Database Hierarchy 3:2 12. you can create the hierarchy under the World using a command sequence such as: 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. Departments own Registries. a Sheet and a View The top-level element in a database is the World.0 . Starting with the World as the current element. WORLD DEPT REGI DRWG LIBY SHEE DLLB REPO (or to a DESIGN database element) VIEW DESIGN Database IDLI IDLN ADDE Figure 3:2. If the administrative elements do not exist they will be created automatically. by referencing a DRAFT database element. See Defining VIEW Contents Using Id Lists. 3. The VIEW’s VSCA (VIEW Scale) attribute is set to a value calculated such that the defined picture will fit within the VIEW. the graphics will be read from the picture file without the need for the UPDATE command. A second AUTO command will not change the IDLN. Note: AUTO only sets the IDLN attribute if it has not already been set. you may wish to initiate it as a Background Process (see Background Process Manager). 3. This is done by typing: UPDATE DESIGN SAVEWORK Note: The UPDATE command creates the VIEW graphics in a central picture store within the computer's memory. and so graphics in the central picture store will be saved to picture files. or different views of the same part of the model. For example: AUTO /ZONE1 This command carries out the following operations: • • • The VIEW’s IDLN (ID List Name) attribute is set to the name of the Design element to be displayed (/ZONE1 in our example). Each VIEW can contain a picture of a different part of the Design model. Leaving DRAFT by switching to another module will perform an implicit SAVEWORK. The projection of the Design model must now be created before a picture can be produced. Where it is known that the Update Design operation will take a considerable time. by referencing a single Design database element. If you leave DRAFT via a QUIT command the graphics in the central picture store will not be saved and any existing picture files will not be updated. The SAVEWORK command is not necessary but it is recommended. It will save the graphics in the central picture store to picture files in the picture file directory.2. See Changing the Picture by Changing VIEW Attributes for details of manipulating the contents of a VIEW. The AUTO command by itself will use the existing IDLN setting.0 . Specifying the contents indirectly.1 Defining the Contents of a View There are two methods of specifying the contents of a VIEW: • • Specifying the contents directly. which can be set up so as to refer to a set of Design database elements. The VIEW’s THPO (Through Point) attribute is set to the Site coordinates corresponding to the centre of interest of the view.DRAFT User Guide Drawing the Design Note: You can have several VIEWs on a Sheet.3 Defining View Contents Using the AUTO Command The AUTO command adds a specified design element to the View. See Defining View Contents Using the AUTO Command. 3:3 12. In a subsequent DRAFT session. 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.PIPES REMOVE /VESS1. /BRAN3 3:4 12.4 Defining VIEW Contents Using Id Lists You can add many elements to a VIEW by displaying the contents of an Id List (IDLI element). In particular if / LIST3 is being used to remove a number of Branches (say) from /LIST1 then it should be defined as: ADD /BRAN1. BRAN 2 OF /PIPE3 The ADD and REMOVE commands automatically create the Add Entry (ADDE) and Remove Entry (REME) elements shown in Figure 3:2. 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. also setting those ADDE and REME attributes which refer to (in this example) appropriate elements in the DESIGN database. /BRAN3 and NOT as: REM /BRAN1.: Top part of the DRAFT Database Hierarchy.: Top part of the DRAFT Database Hierarchy) • Library (LIBY) elements can appear at four positions in the hierarchy (see Appendix A). the library part of the database is set up as in the following example: NEW LIBY /LIB1 NEW DLLB /DLB1 NEW IDLI /ID1 (See the left-hand part of Figure 3:2.PIPES2-1 ADD /ZONE. Id Lists are contained within Drawing List Libraries (DLLB elements). The DLLB is used to group together Id List (IDLI) elements. /BRAN2. They are administrative elements used to group together several types of sublibrary. /BRAN2. Starting at World level. /ZONE1. The Id List contains a list of the elements to be displayed. respectively.EQUIP. for example: ADD /ZONE1.EQUI2-1 REMOVE /PIPE2-1-12 REM /PUMP2-1-12 ADD and REMOVE may be combined on a single line.DRAFT User Guide Drawing the Design 3. Other Id Lists may be added or removed in the same way.0 . For example: ADD ALL EQUI FOR /SITE/99 REM ALL BRAN WITH (HBOR LT 25 AND TBOR LT 25) FOR /ZONE/PIPES ADD ALL FROM !COLLECTION where !COLLECTION is a local variable containing a list of Design element references.EQUI2-1 DESREMOVE /PIPE2-1-12 DESREM /PUMP2-1-12 This sequence of commands adds elements /ZONE. and the resulting list of elements stored.0 . In the above examples the Selection criteria are not stored in the database but expanded. Hence a Remove Entry should never be the first element in an Id List. Consider the command sequences: Sequence 1 Sequence 2 ADD /ZONE. For example: DESADD /ZONE. This is normally activated by the interface. For example : 3:5 12. This can result in very long Id Lists. You can define criteria.4.PIPES2-1 and /ZONE. and removes /PIPE2-1-12 and /PUMP2-1-12.4. 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.PIPES ADD /PIPE1-1 REM /PIPE1 ADD /ZONE. 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 View Contents Using the AUTO Command. For an entry to be removed it must have been (implicitly) added previously. 3.including / PIPE1-1 which has been added by the second command (and implicitly by the first).PIPES REM /PIPE1 ADD /PIPE1-1 In Sequence 1 the final command removes all branches owned by /PIPE1 .1 Adding Elements to 3D View The DESADD and DESREMOVE commands allow for the addition and removal of Design elements to a 3D view. which are stored in the database.PIPES2-1 DESADD /ZONE. The syntax is similar to the ADD and REMOVE commands described above. and only expanded at the time of an UPDATE DESIGN command using the RULE keyword. 3.2 Selective Additions to the Id List The Selection syntax can be used to generate Id Lists.DRAFT User Guide Drawing the Design If an Id List has Remove entries then the member list order is important.EQUI2-1 to a 3D View. The spatial map is a simplified geometric representation of the design model.DRAFT User Guide Drawing the Design ADD RULE ALL ZONE WITH ( FUNC EQ 'PIPING') REM RULE ALL BRAN WITH (HBOR LT 25 AND TBOR LT 25) You must be sure to use the RULE keyword in these cases. and very many ADDEs and REMEs may be created. for example: NEW ADDE CRIT ALL BRAN WITH (PSPE EQ /RF300) In this case the RULE keyword is not required. WITHIN variation of the ADD command uses the PDMS spatial map. Note: If the spatial map is not up-to-date the list of elements generated may not be correct. 3:6 12.3 Spatial Map The ADD . This is done using the LIMITS command. The CRIT attribute can also be set directly.. LIMITS @ TO @ Set limits as 3D coordinates using the cursor... and removed from. Example: LIMITS E1000 N8000 U1000 TO E5000 N1000 U900 Define limits explicitly. These forms of the ADD and REMOVE commands set the CRIT attribute of the ADDE and REME elements. LIMITS ID @ ID @ Set limits as 3D coordinates via Design elements selected with the cursor. otherwise the criterion will be evaluated when the Rule is defined.. The ADD . Better results may be yielded by setting the IDLI’s LIMI attribute (see Command Summary section at the end of this Chapter) to define the required volume and only ADD the relevant SITEs and ZONEs to the Id List. These are liable to become out-of-date as elements are added to.4 Changing the Limits of the View Contents The display of Design elements within a VIEW can be changed without affecting the Id List by changing the LIMI attribute of the IDLI element.4.0 . one for each significant element that is in /ZONE99 and which overlaps the specified volume. 3. one for each significant element in the current MDB that overlaps the specified volume. WITHIN method may produce very long Id Lists. The second example would generate a list of REMOVE entries. For example: ADD /ZONE99 WITHIN E5000 N5000 U5000 TO W1000 S1000 U0 REMOVE WITHIN E2500 N1000 U500 TO E0 N0 U0 The first example would create a list of ADD entries.4. the Design databases. 3. 3:7 12.4. The Id List name/VIEW name is not required if the current element is the Id List itself or a related VIEW. Note that querying the Id List in the usual way will list its ADDE and REME elements.0 .4. Attributes can be set explicitly in the usual way. a more comprehensive output can be obtained by: Q DESCRIPTION (at IDLI.e. Q IDLN DESC (at a VIEW) outputs Id List members and limits. ADDE or REME elements) Other querying commands relating to Id Lists are: Q MAP Lists status of spatial maps in the current MDB Q VOLUME identifier Gives encompassing volume of given element Q WINDOW volume Lists significant elements in the given volume 3.e. or at a VIEW.DRAFT User Guide Drawing the Design 3. partially included in the named Id List (i.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.5 Changing the Picture by Changing VIEW Attributes This section describes the effects of changing the VIEW attributes. 3. and the effect on an element’s attributes of giving the various DRAFT commands can be seen by giving a QUERY ATTRIBUTES command for the element concerned. in the Id List but some member elements REMOVEd). in the Id List and no member elements REMOVEd).6 Querying Id Lists Q FOR /design_element_name At an IDLI. Q IDLN FOR /design_element_name A series of Design element names may be specified. or absent from the named Id List. separated by spaces or commas These commands will output information on whether the named element is wholly included in the named Id List (i. DRAFT User Guide Drawing the Design 3.5. The SIZE command can also be used at SHEE level to change the Sheet size. The SIZE attribute is also be changed by the VREGION command. For example: Example: VREGION FROM @ TO @ Opposite corners of VIEW defined by cursor VREG X100 Y100 TO X500 Y500 Opposite corners of VIEW defined explicitly 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 frame will be drawn using the View’s NLSTYLE/NLCOLOUR attributes. See Colours and Styles for a description of colours and styles. The frame is OFF by default.5.2 View Size SIZE is the ‘paper size’ of the VIEW rectangle. LFRA FALSE (or FRAME OFF) turns the frame off. which may be used to resize and reposition the VIEW. 3. 3:8 12. LFRA TRUE (or FRAME ON) turns the frame on.1 VIEW Frame LFRA controls the visibility of the VIEW frame.0 . but moves the point at the centre of the picture to the centre of the new VIEW frame. Changing the size by a command such as SIZE 400 400 leaves the scale of the VIEW contents unaffected. The VREGION command also affects the XYPS attribute (see View Centre). Changing VIEW ONPOS ONPO 3:9 12. The default XYPS is at the centre of the Sheet. for example: ONPO 45 -25 See Figure 3:4. which are the coordinates of the centre of the VIEW relative to the bottom left corner of the Sheet. Figure 3:3. so an UPDATE DESIGN command must be given. Changing ONPOS will make the existing VIEW graphics out-of-date. Changing VIEW XYPS ONPOS is the position of the centre of the VIEW contents.0 .3 View Centre XYPS controls the position of the centre of the VIEW on its owning Sheet. ONPOS is set directly. VIEW contents are centred within the VIEW by default.DRAFT User Guide Drawing the Design 3.: Changing VIEW ONPOS.5. so this attribute takes the default values x0 y0. The attribute can be set directly by commands such as AT @ Nominate new XYPS with cursor XYPS 350 250 Change attribute directly See Figure 3:3. relative to the centre of the VIEW.: Changing VIEW XYPS. This attribute takes two numeric values. ONPO Figure 3:4. The AUTO command calculates and sets VSCA directly so this will also cause VRAT to be unset. Setting VRAT will cause the existing VIEW scale (VSCA attribute) to be recalculated. 3. VIEW scale may be expressed in terms of a ratio using the VRAT (VIEW Ratio) attribute. and can be set to any angle. ADEG can be set directly or by using the TURN command. the larger are the displayed objects. ADEG 0 Figure 3:5. Figure 3:5.5 Orientation of View Contents ADEG controls the orientation of the VIEW contents. for example: VRAT 1 TO 75 VRAT 1/16in TO 1ft Two positive values have to be specified but the TO may be omitted. Changing Orientation of VIEW Contents ADEG 90 Note that the degree of rotation produced is relative to an ADEG value of 0. The AUTO command takes the ONPOS value into consideration when it calculates the VSCALE. Care should be taken when changing VSCA. 3:10 12. not to the last value of ADEG.4 View Scale VSCA controls the scale of the VIEW contents. e. for example: TURN 60 ADEG -120 A positive value results in an anticlockwise rotation.g. The attribute has a default value of 0.5.: Changing Orientation of VIEW Contents illustrates the effect of changing ADEG. but can be changed if necessary. as it is easy to move the VIEW contents over the VIEW frame. Setting VSCA directly causes VRAT to be unset.05 The larger the VSCA value. 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).0 . VSCA 0.DRAFT User Guide Drawing the Design 3.5. which would be the normal setting for drawings. The Through Point and From Point may be set explicitly by commands such as: LOOK LOOK FRPO THPO THROUGH N53426 W632764 U2125 FROM N53426 W632764 U2125 N125671 E67342 U11254 N125671 E67342 U11254 Changing the Direction. 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.8 Looking Direction The View’s line of sight is fully defined by any two of: • • • Looking Direction From Point Through Point which are defined by the attributes DIR. The default value of 0 gives a parallel projection. corresponding to the direction of the ‘top’ of the VIEW region relative to the top of the screen. down by default. DIR (Direction) specifies the Looking Direction. DOWN.DRAFT User Guide Drawing the Design Varying RCOD (rotation code) produces a similar effect to varying ADEG. The THPO (Through Point) attribute is set to the Design coordinates corresponding to the centre of interest of the view.6 Perspective PERS (perspective) can be used to give a perspective projection.0 . assuming they are both already set. Setting one of these will unset one of the other two. 3. Through Point or From Point will make the existing VIEW graphics out of date. THPO and FRPO. RCOD may be set to UP. LEFT or RIGHT. These will be calculated automatically from the VIEW’s related Id List by the AUTO command. Elements can be added using the DESADD command (see Adding Elements to 3D View).7 3D View A 3D View can be generated from a 2D View using the GENERATE MODEL command.5. an UPDATE DESIGN command must be given to change the picture. 3. This view can be amended using the user interface.5. except that the VIEW is rotated as well. the value taken by the PERS attribute being related to the view angle. If PERS is changed. 3. FRPO (the From Point) is the position (in Design coordinates) at which the observer is deemed to be. so this must be updated by typing 3:11 12.5. Default is UP. 9 Representation Ruleset Reference The RRSF (Representation Ruleset Reference) attribute refers to elements that control the representation style to be used. 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.DRAFT User Guide Drawing the Design UPDATE DESIGN before any change in the picture will be seen. See Automatic Hatching. in a plan VIEW with RCODE UP (the default).10 Hatching Ruleset Reference The HRSF (Hatching Ruleset Reference) attribute refers to elements that control the representation style to be used for hatching. The 3D view direction equivalent to 2D Sheet direction may be queried using Query VIEWDIRection <sheet-dir> where <sheet-dir>is Left.5. (Default value 15. etc. For example.11 Change Ruleset Reference The CRSF (Change Ruleset Reference) attribute refers to elements that control the representation styles to be used for changed design items and annotations. See Change Highlighting.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. centrelines.5.5mm. Right.0 . 3.5.13 View Gap Length The VGAP attribute allows you to define the size of the gap that DRAFT inserts in View lines where they are crossed by non-solid primitives such as Plines.) 3. being set in units of hundredths of a millimetre on the drawing. Up or Down. See Representation Rules. 3. for a plan VIEW with RCODE LEFT. 3. DRAWIs. The default value is 1. 3:12 12.5. This command gives an error when the VIEW has Perspective or the current database position is not at or below a VIEW.5. then the query Q VIEWDIR LEFT would give: Viewdirection Left W However. 3:13 12. 3.: Typical Wireline View.5. STRU. or an explicit 3D coordinate. After changing the NOCLIP attribute an UPDATE DESIGN will be required. 3.14 Suppressing View Clipping By default the Design graphics are clipped by the View frame. (The default value is FALSE).DRAFT User Guide Drawing the Design 3.7 Hidden Line Representation The VTYP (view type) command controls the hidden-line representation of displayed pictures. However it is possible to ignore all DUNION values by setting the View's IGNDUN attribute (Ignore Dunion) to TRUE.15 Ignoring the DUNION attribute Use of the DUNION attribute on DESIGN elements such as FRMW. 'Section 5. 3. After changing the IGNDUN attribute an UPDATE DESIGN will be required. The default VTYP setting is WIRELINE.6 More on the AUTO Command Previous sections have described the use of the AUTO command to add Design elements to views.5. the Id List relevant to the VIEW is assumed. origin of a named element. The position may be specified using the cursor (3D point or p-point).14. which gives a conventional wireline picture as shown in Figure 3:6. explicit p-point reference. etc is described in the Design Reference Manual: Creating the Model. However it is possible to prevent this happening by setting the View's NOCLIP attribute to TRUE. ignoring any Design items in the VIEW. There are two other uses of AUTO: AUTO LIMITS OF /idlist_name Here the VIEW’s VSCA and THPO attributes are calculated using only the LIMI attribute of the referenced Id List. This facility allows you to produce preliminary and intermediate drawings (where graphical accuracy may be of secondary importance) quickly. The DUNION values are used during an UPDATE DESIGN process to determine whether common edges between FRMWs (say) should be drawn or omitted. (The default value is FALSE).0 .2 Controlling Edge Representation in DRAFT'. AUTO FROM position TO position The VIEW’s VSCA and THPO attributes are calculated from the box defined by the two 3D coordinates given. Six possible VTYP settings are provided. If the Id List name is omitted. leaving only finished drawings to incur the greatest processing overhead. These give progressively greater graphical accuracy at the expense of increasing processing requirements. but without incurring the computational overheads of removing hidden lines.DRAFT User Guide Drawing the Design Figure 3:6.0 .: Typical Modelled Wireline View shows a modelled wireline display. Typical Modelled Wireline View 3:14 12. Figure 3:7. Figure 3:7. Typical Wireline View Modelled Wireline representation gives slightly greater realism by blending the intersection of primitives. This gives a picture as shown in Figure 3:9.: Typical Local Hidden Lines Removed View. Typical Wireline with Hidden Lines Removed View 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. etc) but not from items hidden behind them.DRAFT User Guide Drawing the Design Wireline Hidden Line Removed representation produces a View where hidden lines are removed from individual significant elements (EQUI. 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.: Typical Wireline with Hidden Lines Removed View. SUBS. A typical View is shown in: Figure 3:8. Figure 3:8. 3:15 12.0 . g.: UNIVERSAL VIEW Type) gives a picture where all hidden lines are removed (as in Global HLR).DRAFT User Guide Drawing the Design Figure 3:9. giving a picture as shown in Figure 3:10. EQUI and STRU or SUBS and SUBS) are generated. 3:16 12.0 . but in addition intersection lines between clashing significant elements (e. Figure 3:10.: Typical Global Hidden Lines Removed View. Typical Local Hidden Lines Removed View Global Hidden Line representation gives a picture where all hidden lines are removed. 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. Typical Global Hidden Lines Removed View Universal representation (see Figure 3:11. Design symbols can consist of geometrical elements or text or can be a combination of both. Symbolic representation may either replace or be in addition to the normal geometric representation of the elements. 3:17 12. Figure 3:11. It is also more likely to be needed in non-orthogonal Views. including DRAFT Intelligent Text hash-codes. UNIVERSAL VIEW Type Alternative methods of setting VTYP are as follows: VTYP WIRE VTYP MWIR VTYP WIREHL VTYP LOCAL VTYP GLOBAL VTYP UNIV wireline (default) modelled wireline wireline with hidden lines removed local hidden lines removed global hidden lines removed global hidden lines removed and intersection lines generated 3. where missing intersection lines are most noticeable.0 .1 2D Symbolic Representation Introduction DRAFT allows design elements to be represented symbolically in a 2D View when the UPDATE DESIGN command is executed.8 3.8.DRAFT User Guide Drawing the Design rather than vice versa. Design symbols can be scaled and oriented as required. e. with no user control over these operations. irrespective of View Scale and paper size. the array elements of the XY scaling (XYSC) attribute of the design symbol are set equal to the NSIZE attribute of the referenced SYTM. DSLAYEs and DESSYMs are created and deleted automatically by DRAFT. These are the Symbol Templates (SYTM) and the Text Label Templates (TXTM). etc). The DESSYM elements are added as members of a Design Symbol Layer (DSLAYE) element. Refer to Basic Hierarchy for a diagram of the DRAFT database hierarchy. this will adjust the symbol to the appropriate size for the View (uniform scaling). DESSYM is a soft-type variant of the Special Label (SLAB) element. could depend on both the View direction (i. This allows several templates to be associated with a design element so that it can be represented differently in different types of Views. plan or elevation) and the View classification (e. regardless of the aspect ratio of that design element.8. and will therefore change correspondingly when the View Scale changes (and after an UPDATE DESIGN command).2 Scaling Design Symbols 2D symbols can be specified as scaled or non-scaled. when a normal geometric representation is not required in addition to design symbols). and under which circumstances. From the above it can be seen that 2D symbols are created as part of the annotation of the View. Cabling. DESSYMs will not be created for any design item whose origin falls outside the View rectangle or whose origin (or datum point) is excluded by the action of section planes. is stored in the Catalogue database. The size of a scaled symbol depends upon the View Scale (VSCA attribute of the View). used for generation of geometric elements or text elements. The design symbols are created as Design Symbol (DESSYM) database elements. Non-scaled symbols are a fixed size. DRAFT will not attempt to determine whether the design items would have been hidden by the action of the Hidden Line Removal process.e. Setting and X and Y scaling factors of XYSC independently on the Design Symbol Link (DRSYLK) element enables non-uniform scaling of the design symbol. The 2D symbols are generated from templates stored in the DRAFT database. these are described in Representation Rules. For non-scaled design symbols which reference a symbol template (SYTM). respectively. and the DSLAYE will be removed if it subsequently ceases to own any child DESSYMs. Only one occurrence of DSLAYE will be created per View during the UPDATE DESIGN process. Where only a symbolic representation is required (i. This enables the design symbol (DESSYM) held in the PADD database to be scaled to the correct size for the design element that it is intended to replace in the DRAFT View. the actual size on the sheet will depend on the View Scale.g. 3:18 12. Room Design. For a scaled design symbol which references an SYTM. rather than design graphics. by setting the array elements of the XYSC attribute equal to the VSCALE attribute of the View.DRAFT User Guide Drawing the Design Graphic representation of design elements are controlled by Representation Rules. for example. and is therefore a member of a View. The data defining which templates to use for a given design element. The Scaling Flag (SCALFG) of a design element has the value 1 when the design symbol can be scaled within a view and zero it is non-scaled.0 . The representation of a light fitting. The NSIZE attribute is used to scale the symbol to its actual size on the sheet and. 3. which is a soft-type variant of the Layer (LAYE) element. they will not be found unless they own visible primitives.0 .DRAFT User Guide Drawing the Design 3.9 3. TMPL. design_id must refer to a Design significant element. Then the value of the PPDI attribute on the SYTM or TXTM is set to the value of the P-point Number (%NUM) attribute on the Catalogue component. This is achieved either by selecting an existing P-point on the Catalogue component. BRAN. In addition the system administrator must associate the SYTM and TXTM with orientation of the component in the Catalogue that the DESSYM will represent. The IN view_id may be omitted if your current database position is at or below a View.9. SYTMs and TXTMs are created and modified in DRAFT Administration Mode. This allows the 2D Symbology functionality to use the direction of the P-point.8.9. or by creating a new P-point. 3. DRAFT determines whether design items are visible by scanning the data in the picture. Note: A significant Design element will not be found in a View if it only owns other significant elements. STRU and FRMW elements. This affects EQUI. This command cannot determine how much of the element is visible. You can: • Request a list of all significant elements that are visible in a View.3 Orienting Design Symbols The correct orientation of a DESSYM in a DRAFT View is obtained by copying the value of the P-point Direction (PPDI) attribute from the Symbol Template (SYTM) or Text Label Template (TXTM) to the PPDI attribute of the DESSYM. to align the X-axis of the SYTM or TXTM. SUBE. not by scanning the IDList. Q VSCAN design_id IN view_id • • For example: Q VSCAN /PIPE100-B-1-B1 Specify selection criteria to determine matching design elements visible in a View. FRMW. which is determined by the P-point direction (PTCD) attribute on the P-point element. SBFR. Q VSCAN FOR selection_criteria IN view_id • For example: Q VSCAN FOR ALL (VALVE VTWAY VFWAY) WITH (ABOR GE 50) In the above examples. or HANG. SUBS.1 Querying Commands Querying View Contents You can query which Design elements are visible in a specified DRAFT View using the Q VSCAN command. Q VSCAN SIGNIFicant IN view_id • • For example: Q VSCAN SIGNIF IN /VIEW-01 Specify a significant design element and request a list of all its primitives that are visible in a View. which is EQUI. It must own visible primitives. Thus elements hidden by the hidden-line-removal process will not be found.2 Querying Whether an Element Appears in a View You can query whether low-level design elements and their owners appear in a given View using the command: 3:19 12. STRU. 3. the VIEW’s RCOD attribute) to be considered if required. For example: 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. 3. Point 1 in Figure 3:12.3 Querying the Nearest Side to an Item You can query the nearest side of a View to a given P-point. This affects EQUI. proportional distance along a Pline.9.e.0 . or origin of a Design element in the current View using the command: Q VSIDE [ROTated] OF 3d_point_definition For example: 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. STRU and FRMW elements. Figure 3:12.5 The ROTATED option allows the rotation (i. For example: Q FIND /BOX99 IN /SH1/V1 Q FIND /VESS-05 IN VIEW Q FIND ILEAVE TUBE OF /VALVE-24 IN /VIEW/02 The view identifier can be omitted if it is the current element. Querying the nearest side to an item 3:20 12.: Querying the nearest side to an item will be LEFT UP OUTSIDE. For example. they will not be found unless they own visible primitives.DRAFT User Guide Drawing the Design Q FIND gid IN view where gid is the general identifier of the element and view is the view identifier. and also whether the item is inside or outside the View. The response will be the nearest and next-nearest sides. including Views in the same Sheet. In the DRAFT module.10. or multiple VIEWs contained in a SHEET.3 Initiating and Using the BPM The actions to initiate a background process are as follows: 1.DRAFT User Guide Drawing the Design 3. for example. It also contains the BPM log file. the PDMS macro. Each BPM job updates a single VIEW.0 . DESIGN NOWAIT command. For example.bat enables to PDMS environment variables. or the total set of VIEWs contained in multiple SHEETs of a DRAWING. A batch file BPM. 2. This allows you to carry on with your work while updating is performed. XXXMAC and XXXPIC must be defined for each project XXX to which the BPM is applied.10.2 Prerequisites Certain environment variable settings must be defined before the BPM can be used: • • • PDMSEXE. the BPM reads the next entry in the queue and creates a ‘hidden’ DRAFT session running in the background to run the job.bat is supplied to enable the above environment variables automatically and to start the BPM in much the same way as PDMS. Once started. you will be notified. The foreground design session and the BPM do not need to be active at the same time.1 Background Process Manager Introduction A facility is provided to allow updating a design to take place as a background process. XXXISO. the design session could submit any number of design updates as background processes.10 3. Since the output is a set of individual VIEW files. Facilities are provided to cancel and delete jobs as well as purging unwanted files. (How to start the BPM is described below. the queue manager can run overnight. while the background process is running.) 3:21 12. 5. Set and save the viewing parameters. 3. normally via associated 4. the regenerated VIEW files and the DRAFT log file. The system then creates an entry in the BPM queue and returns immediately for the next action. they may be imported to refresh existing VIEWs selectively. as picture files are not updated directly by the process. since it contains the job XML file. using a SAVEWORK command. other views can be worked on. A design session must then be started in order to refresh the updated Design view. PDMSWK. When required. a process only starts after the previous one has finished. Issue an UPDATE applicationware. before the BPM is even started. or collectively for the owning SHEET or DRAWING. The project environment variables XXX000. 3. Once a background process has been completed. navigate to the VIEW (or SHEET or DRAWING) to be updated. Background processes are run one at a time. The two processes are completely independent.10. Background processes are managed using the Background Process Queue Manger (BPM). 3. To avoid unlimited multiple copies of DRAFT being initiated. since it contains the module to be executed in the background. log extension. Each background DRAFT session started by the BPM writes a standard PDMS log file to the PDMSWK folder. 2. Processing of ‘Not Started’ jobs is initiated from the Background Process Manager form. Be careful to save any outstanding changes to other VIEWs in the same SHEET before refreshing another VIEW. the Background Process notification icon appears in the notification area on the Windows task bar. When one or more jobs appear in the job list. 9. if necessary. click on the Start manager hyperlink to start the processing of jobs with Status ‘Not Started’. An exit code of ‘Success’ means that the updated VIEW (SHEET or DRAWING) can be refreshed into the foreground DRAFT session. as required. 9. Once the process has finished. the original SHEET should be re-selected to re-load the old contents. which is signalled by an icon in the Windows notification toolbar. Once the BPM is in the ‘Stopped’ state it may be exited using the File>Exit menu selection. a notification is raised. 8. Note: If a refreshed VIEW is unacceptable. Instead. The Background Process Manager form may then be restored.bat start-up file. Note that the hyperlink changes to Stop manager at this point. 7. 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. 5. See Managing Jobs using the Background Process Manager Form for details of the Background Process Manager form. you may save them permanently using a SAVEWORK. Initiate the BPM by invoking the BPM. Once the process for a job has finished. 7.0 . This is a picture file prefixed with the letter ‘X’ instead of the standard ‘M’. The log file has the same name as the initiating XML job file but with the . This enables you to refresh selected VIEWs only (or a SHEET or a DRAWING). 4. as usual. 8. 6. Each VIEW updated by the BPM will generate its own IVF. The form shows the job currently running and provides facilities to start job processing or stopping the current job. A log file of the processing is saved to the PDMSWK folder and is called BPM_ddmmyyyy_hhmmss. 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.DRAFT User Guide Drawing the Design 6. You may then re-enter ‘foreground’ DRAFT and navigate back to the original VIEW (SHEET or DRAWING) to load the new picture. which displays details of each job together with its Status of ‘Not Started’ or ‘Finished’ and an exit code showing success or failure. Issue an UPDATE REFRESH command to refresh the current VIEW (SHEET or DRAWING). The Background Process Manager form may be iconised at this point. 10. 3. To start and use the Background Process Manager: 1.log 3:22 12. The Background Process Manager form then appears. The next waiting job is then started automatically. If the refreshed VIEWs are acceptable. to view the updated Status and Exit Codes. you should NOT issue a SAVEWORK to save it permanently. • Managing Jobs Collectively The File pull-down menu is used for this.0 . The log file should contain a record of all processing in the Background Process session. including errors.DRAFT User Guide Drawing the Design where: ddmmyyyy is the standard date and hhmmss is the standard time that the process was started.changes to Start Manager. Stop manager stops the processing of the jobs currently listed . 3. The options are: • • Start manager starts the processing of the jobs currently listed . 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.changes to Stop Manager. 3:23 12.10.4 Managing Jobs using the Background Process Manager Form • Tabbed Windows The Manager log tabbed window contains the BPM log of jobs processed. 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. The Job tabbed window is used to display the log file of the finished job. DESREMOVE design_element_identifier [design_element_identifier. REM design_element_identifier [design_element_identifier.1 Summary of Commands At Id List . • • • • View log displays the log file of the selected job in the Manager log tabbed window.e. Cancel job cancels the selected job...11.0 . • • • • Managing Jobs Locally The right-mouse button menu options on a row in the job list table are used for this. Exit exits the BPM... Delete job deletes the selected job.] 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..DRAFT User Guide Drawing the Design • Purge finished jobs purges all jobs with status ‘Finished’ and deletes corresponding XML.11 3. . Restart job restarts the selected job. Refresh refreshes the job list table. Delete all jobs deletes all jobs irrespective of their status. i... . 3.] adds Design element to 3D View. ADD design_element_identifier [design_element_identifier. LIMITS @ TO @ set limits as 3D coords with the cursor 3:24 12. clears it and then repopulates it from scratch.] adds Design element to Id List.] 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.. MAC and LOG files. but deleted design elements (specified in Id List) ignored (and UPDATE process does not abort) UPDATE DESIGN NOWAIT initiates a Background Process (see Background Process Manager). UPDATE ALL updates annotation. will re-evaluate hash codewords on it. Full syntax is: UPDATE DESIGN [IGNORE] [SHOW CHANGES | NOCHECK] NOWAIT UPDATE REFRESH refreshes the current view after a Background Process (see Background Process Manager). Also. UPDATE DESIGN updates picture to latest VIEW and Design parameters UPDATE DESIGN IGNORE as UPDATE DESIGN. .11. .the number is the member list number DELETE ADD number delete an Add item.0 . but deleted design elements (specified in Id List) ignored (and UPDATE process does not abort) Full syntax is: UPDATE [IGNORE] [OVERWRITE] [SHOW CHANGES | NOCHECK] NOWAIT 3:25 12. Ensures that the latest version of the referenced BACK is used.DRAFT User Guide Drawing the Design LIMITS ID @ ID @ set limits as 3D coords via Design elements using the cursor DELETE ENTRY number delete either an ADDE or REME from the Id List members .2 At DRWG and below . UPDATE ALL IGNORE as above. tag rules and Design graphics (but only for that part of the picture file determined by the level in the hierarchy at which the command is used). number corresponding to number of the element out of the Adds only DELETE REM number delete a Remove item. UPDATE ANNO updates Drawing annotation (including Backing Sheets) to latest Design data and VIEW attributes UPDATE BSHEETS updates Backing Sheets. number corresponding to the number of the element out of the Removes only 3. . it cannot be used for a Layer. Updates annotation graphics (but not Design graphics). centre of Sheet. UPDATE PICTURE regenerates Sheet level picture. Use at Sheet level or equivalent. UPDATE ANNO and UPDATE ALL commands can be specified with the option SHOW CHANGES.DRAFT User Guide Drawing the Design (The above commands can be given from anywhere in the hierarchy if an appropriate element identifier is inserted after the UPDATE keyword. For more information see Change Highlighting. x. 3276 mm respectively. say. . Use only when the picture file is corrupted. 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. Min.3 At VIEW . This option is only valid at View elements or above. Through Point and Id List reference. 3:26 12. If idlist_name is omitted the IDLI relevant to the VIEW is assumed.) 3.y values are 1 mm. e.e.0 . for example UPDATE DESIGN SHOW CHANGES. Database changes will be shown in the manner defined by the View's Change Ruleset. Max.g. SIZE paper_size set VIEW size to a standard paper size.11.) The UPDATE DESIGN. SIZE xvalue yvalue set VIEW size in mm with origin at default i. DRAFT will prompt the user when this is necessary. ) set Through Point of VIEW in 3D coords THPO ID @ (or LOOK THROUGH ......) 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. LOCAL.) set From Point in 3D coords with cursor FRPO ID @ (or LOOK FROM .. explicit p-point reference.. Options: WIRE.0 ..) set Through Point as Design element p-point (converted to 3D coord) FRPO E value N value U value (or LOOK FROM . GLOB. UNIV LOOK value (or DIR value) set VIEW direction ISO value set isometric VIEW direction 3:27 12. MWIR. (position includes cursor specification of a 3D point or p-point.) VSCALE value set Scale of VIEW THPO E value N value U value (or LOOK THROUGH .. or an explicit 3D coord.. The VIEW’s VSCA and THPO attributes are calculated from the box defined by the two 3D co-ordinates specified by position. origin of a named element.DRAFT User Guide Drawing the Design AUTO LIMITS OF /idlist_name use limits box of Id List to define VIEW AUTO FROM position TO position use specified limits box to define view.) set From Point of VIEW in 3D coords FRPO @ (or LOOK FROM . DELETE NULL IDLI deletes all ADDE and REME elements whose IDNM attribute is null or which references an unknown element 3.11. LVIS FALSE makes the VIEW invisible LVIS TRUE makes the VIEW visible (default) Q VLIMITS gives 3D limits of View (View must be orthogonal. LEFT or RIGHT (default UP) Q VIEWDIR option query 3D view direction equivalent to 2D Sheet direction LFRA option set visibility of VIEW frame FRAME option Options: TRUE or FALSE (LFRA) ON or OFF (FRAME). with no perspective) 3. Options: UP. E. .DRAFT User Guide Drawing the Design PLAN set plan VIEW direction ELEV option set elevation VIEW direction options: N.11.4 Anywhere . DOWN. .0 .5 Querying Contents of a View Q FIND gid IN view queries whether a design element appears in a given View Q VSCAN SIGNIFicant IN view_id Outputs a list of all significant elements that are visible in a View 3:28 12. S and W PERSPECTIVE angle set VIEW perspective ATOL value set arc tolerance RRSF name set reference to Representation Ruleset (RRST) element RCOD option set rotation code. e.DRAFT User Guide Drawing the Design Q VSCAN design_id IN view_id Specify a significant design element and request a list of all its primitives that are visible in a View. next nearest side. 3:29 12. or origin of a Design element in the current View. proportional distance along a pline. and whether the item is inside or outside the View. Q VSCAN FOR selection_criteria IN view_id Specify selection criteria to determine matching design elements visible in a View Q VSIDE [ROTated] OF 3d_point_definition queries the nearest side.0 . 3d_point_definition can be p-point. The ROTATED option allows the VIEW rotation (i. the VIEW’s RCOD attribute) to be considered if required. 0 .DRAFT User Guide Drawing the Design 3:30 12. Representation Rules Database Hierarchy 4:1 12. Local Rules override Library Rules. The attributes of a Style define a series of drawing styles and colours. the reference is made by setting the RRSF attribute of the View. refer to 2D Symbolic Representation. The reference from an RRUL to a STYL is made by setting the STYF attribute of the RRUL. Figure 4:1. For more information about styles and colours see Colours and Styles. or named elements. backface and centreline. for example. See Local Rules for more information about the order in which Rules are applied. Each Rule can specify a given type or types of element. in which case they are known as local rules. RPLBs are also used to store STYLs.1 Graphical Representation Introduction Representation Rules control how Design elements are drawn.0 . Representation Rules also control which design elements are to be replaced by symbols when a 2D View is created. Representation Rules can be created in a Library and be referred to from a VIEW. for frontface.DRAFT User Guide Graphical Representation 4 4. which in turn are owned by Representation Libraries (RPLB). When a View references a RRST. Representation Rules (RRUL) are stored in Representation Rulesets (RRST). or they can be owned directly by a VIEW. For a description of 2D symbology. and whether items such as p-lines and obstruction volumes are shown. Representation Rules refer to Styles. 4:2 12. In wireline VIEWs these attributes control the style and colour to be used to represent all edges. Piping Component Insulation will be drawn using the frontface style and colour (FFSTYLE/FFCOLOUR). for example: FFSTYLE SOLID M FFCOLOUR 1 Use a SOLID line of MEDIUM thickness and Colour 1 for the frontface FFSTYLE may be set to OFF to allow special effects. are as follows: Tube flag Centreline flag Piping Symbol flag Obstruction flag Insulation flag Profile flag P-line flag Drawing Level Frontface Style/Colour Centreline Style/Colour Backface Style/Colour Obscured Style/Colour P-line Style/Colour Member line Style/Colour TUBEF CLIN PSYM OBSTF INSU PRFG PLFG DLEV FFSTYLE/FFCOLOUR CLSTYLE/CLCOLOUR BFSTYLE/BFCOLOUR OBSTYLE/OBCOLOUR PLNSTYLE/PLNCOLOUR MLNSTYLE/MLNCOLOUR OFF ON ON OFF OFF OFF ON 0 SOLID/1 CHAIN/1 OFF OFF LDASH/1 OFF TUBEF. (See the DESIGN Reference Manual for details. OBSTF and DLEV are standard PDMS display representation controls and are not described here. For details of how changes to design elements can be shown see Change Highlighting.0 . PRFG. The style/colour attributes allow different parts of chosen items to be drawn differently.DRAFT User Guide Graphical Representation This Section also describes Hatching Rules. The outline of the piping Components will be hidden by the insulation in hidden-line views. except for holes that will be drawn with a dashed line of the same colour as the FFCOLOUR. 4. See Automatic Hatching. which are used for automatic hatching of faces of Design elements. If insulation and Components are required to be displayed.) If INSU is ON. Set directly. two similar views (that use different Styles) will need to be defined and superimposed. All edges are shown. with their defaults. PSYM. The STYL attributes.2 Representation Styles The Representation Style (STYL) defines the appearance of the elements specified by a RRUL that references it. and are used as follows: • Frontface Style/Colour. CLIN. PLFG. the centreline will not be obscured by the piping Components. BFSTYLE DOT BFCOLOUR 1 Use a DOTTED line of minimum thickness and Colour 1 for the backface BFSTYLE would normally be set OFF for hidden line VIEWs. In hidden line VIEWs.0 . Set directly. it is not necessary to superimpose two VIEWs with different Styles. e. SUBE.g. or PTRA will be drawn using the centreline style/colour of the STYL specified.g. DRAWI elements owned by EQUI. Set directly. the LEVEL attribute should be used to control whether the DRAWI appears on the drawing. CKSTYLE DASHED CLCOLOUR 1 • Use a DASHED line of minimum thickness and Colour 1 for centrelines Backface Style/Colour. See Figure 4:2.: Use of Backface Style/Colour (shown dotted) for an example of the use of the Backface Style/Colour. When drawing pipework with TUBEF ON. Figure 4:2. SUBS.DRAFT User Guide Graphical Representation • Centreline Style/Colour. Also used for drawing LINE elements of Catalogue Components. CENTRELINE ON. These attributes control the style and colour to be used for representing centrelines. STRU. For these DRAWIs the setting of the STYL’s centreline flag (CLFG) will be ignored even though the centreline style/colour is used. These attributes have no effect in wireline views. e. these attributes control the style and colour to be used to draw the rear edges of items (set to OFF by default). (Unlike FFSTYLE. Use of Backface Style/Colour (shown dotted) 4:3 12. but if required can be used to set the style and colour to be used for drawing the rear edges of items. Use of the Obscured Style/Colour (shown dotted) • P-line Style/Colour.4mm and Colour 1 for member lines MLNSTYLE may be set to OFF. Set directly. Figure 4:3. for example: MLNSTYLE SOLIDT MLNCOLOUR 1 Use a SOLID line of thickness 0. 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). • Member line Style/Colour. Set directly. 4:4 12. for example: PLNSTYLE CHAINED PLNCOLOUR 1 Use CHAINED lines of minimum thickness and Colour 1 for p-lines PLNSTYLE may be set to OFF. OBSTYLE DOT OBCOLOUR 1 use a DOTTED line of minimum thickness and Colour 1 for obscured front facing edges These attributes have no effect in wireline and local hidden line VIEWs. See Figure 4:3. e. In global hidden line VIEWs.: Use of the Obscured Style/Colour (shown dotted) for an example of the use of the Obscured Style/Colour. These attributes control the style and colour to be used to draw SCTN and GENSEC member lines.DRAFT User Guide Graphical Representation • Obscured Style/Colour.g. This attribute controls the style and colour to be used to draw plines.0 . Set directly. sequence 2 would give Nozzles in style /S2. Representation Rules can reference IDLIsts. FIRST EQUI. and a style set. for example: USE /S2 FOR /PUMP1-1 /VESS1 Note: That the Design element must have a name: identifiers such as CE.1 Representation Rules Introduction The Representation Ruleset owns a series of Representation Rules. An example of the commands for setting up a Ruleset is: NEW RRST /RSET1 NEW RRUL /R11 USE /S2 FOR crit . For example: USE /STYLE1 FOR /LIST24 /LIST25 USE /STYLE2 FOR ALL IDLISTS WITH ( FUNC EQ 'STEAM' ) Once a Rule has been created. 4. See Colours and Styles for a description of colour and linestyle functionality.DRAFT User Guide Graphical Representation P-line and member line styles and colours apply only to drawing steelwork Section elements. crit = Design element name or selection criteria When more than one Rule is created. using expressions if required.set Style reference (STYF). A Ruleset can therefore be used to produce several graphical representations of the same VIEW. You can also assign a style reference to an individual named Design element or a series of named elements. STRU 4 etc.create Rule . /S2 must already exist. each of which contains a reference to a different Representation Style.create Ruleset .3. the order of the command sequence is important.0 . the selection criteria can be changed without specifying the style by giving the command: USE FOR crit 4:5 12.3 4. cannot be used. Consider the command sequences: Sequence 1 Sequence 2 NEW RRUL /R1 USE /S2 FOR ALL EQUIP NEW RRUL /R2 USE /S2 FOR ALL NOZZ NEW RRUL /R1 USE /S2 FOR ALL NOZZ NEW RRUL /R2 USE /S1 FOR ALL EQUIP Sequence 1 would result in Nozzles being drawn according to style /S1. Example: CRIT ALL BRAN WITH ( HBORE LE 80 ) You can set up a rule to omit elements from a selection. the CRIT attribute can be set explicitly.2 Representation Rules for 2D Symbology The syntax for defining Representation Rules to control how 2D Symbology is implemented is as follows: USE SYMBOLOGY FOR crit USE SYMBOLOGY AND style-name FOR crit sets the Style Reference (STYF) attribute 4:6 12. 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. which will not be drawn at all: NEW RRUL /SMALLBORE OMIT ALL BRAN WITH ( HBORE LE 80 AND TBORE LT 30 ) NEW RRUL /BRANCHES USE /S2 FOR ALL BRAN Named elements can also be omitted: Example: OMIT /EQUIP99 The OMIT command sets the OMITFG attribute of the Rule. the following Rules (in the given order) will have the effect of drawing all Branches in Style S2 except small bore Branches. 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.0 . For example.DRAFT User Guide Graphical Representation Example: USE FOR ALL BRAN WITH ( HBORE LE 80 ) Alternatively.3. see 2D Symbolic Representation. if you wish to draw small-bore Branches in style /ST1 and the rest in style /ST2. The comparators available are: EQ. Part 1 General Commands. see the AVEVA DESIGN Reference Manual. Selection criteria should not be used unnecessarily. For example. for example:: USE /S3 FOR ALL BRAN WITH (PSPE EQ /RF150 ) USE S4 FOR ALL BRAN WITH ((HBORE LE 50) OR (TBORE LE 50) USE S5 FOR ALL BRAN WITH ((HBORE GT 80) AND (TBORE GT 80) USE /S6 FOR ALL BRAN WI ((PSPE EQ /RF200) AND ((HBOR GT 60) OR (TBOR GT 60))) USE /S7 FOR ALL SCTN WI (CUTL GT 5000) USE /STYLE1 FOR ALL BRAN WI (ISPE EQ NULREF) Note: For full details of using expressions.PIPES) Without the brackets the selection criterion would only be applied to SUBS. GT (although in some instances only EQ and NE are valid). LE. GE. 4. to create a Representation Rule to use 2D Symbology for an office table. for example: WI (PSPE EQ /RF300 WI (ABORE GT 80) is equivalent to is equivalent to WI /RF300 EQ PSPE WI 80 LE ABORE Note: That it is possible to apply a selection criterion to a list of class types by enclosing them in brackets. NE. it is only necessary to say: USE /ST1 FOR ALL BRAN WI (HBOR LE 80 OR TBOR LE 80) USE /ST2 FOR ALL BRAN 4:7 12.3. • • Each logical expression can be preceded by NOT. For example. for example: USE /ST1 FOR (ALL BRAN ALL SUBS) WI (ZONE EQ /ZONE. for example: WI (PSPE EQ /RF300 AND NOT BUILT) The operands on either side of a comparator are interchangeable.DRAFT User Guide Graphical Representation where crit = the design element name or selection criteria style-name = the name of the style (STYL) to be used to draw the Design element Note that the ‘&’ character can be used as an alternative to AND in the above.0 . the following might to used: NEW RRUL /SYMB_RRUL_OFFICE_TABLE USE SYMBOLOGY &/DRA/PRJ/STYL/STEEL/NORMAL FOR /OFFICE-TABLE For a description of the use of 2D Symbology to represent Design elements.3 Selective Style Allocation Style references may be applied selectively using PML expressions. LT. Hatching Rules and Rulesets are similar to Representation Rules and Rulesets.4 Local Rules Local Rules may be set up as VIEW members in the same way as Library rules. all small-bore Branches will match the first criterion and the rest. the resulting graphical representation is determined as follows: • • Local Rules always have priority over Rules within Rulesets in Libraries. For more information on Section planes see Section Planes. A Rule’s priority is determined by its position in the list.3. and they reference Hatching Styles (HSTYL elements). 4.5 Setting the VIEW Once the Rulesets and Styles have been set up. The hatching is carried out automatically as part of the Update Design process. having failed to match the first criterion. Hatching Styles define the styles and colours to be used to draw the hatching. and allows you to impose company or project drawing standards.DRAFT User Guide Graphical Representation As long as the criteria are defined in this order. Hatching Rules are stored in Hatching Rulesets (HRST elements). 4:8 12. 4. and surfaces of specified Design primitives can be hatched automatically by defining and applying Hatching Rules. The hierarchy of database elements for hatching is similar to the Representation Rules. Local Hatching Rules can be defined by creating HRULs owned directly by Views. See Autoblanking. but a Local Rule will still have a higher priority than the top Ruleset Rule.1 Automatic Hatching Introduction Model faces created by section planes. 4. will match the second.0 . and updating the design.4 4. the higher in list the higher its priority. Hatched areas can be auto-blanked to allow annotation placed on top of them to be legible. The Hatching Rules (HRUL elements) define the faces to be hatched. Hatching Styles and Rulesets are stored in RPLBs.3. it is just a matter of setting the VIEW attribute RRSF to point to the Ruleset that you wish to use. This means that you should always place the more specific rules earlier in the list.4. The Local Hatching Rules directly reference Hatching Styles (HSTYL). in which case the face will only be hatched if it is perpendicular to the viewing direction.DRAFT User Guide Graphical Representation Figure 4:4. For each Hatch Rule you can specify: • • Whether it applies to faces created by a section plane or to primitive surfaces.0 . Specified Direction. The normal of a face is the vector perpendicular to it and pointing out of the solid primitive. The orientation of the faces to be considered for hatching. Perpendicular Direction. The HRUL attributes.2 Hatching Rules Each Hatching Rule references a Hatch Style element that defines the hatch pattern to be applied. Thus the normal of the uppermost horizontal surface of a box is Up. Hatching Rule Database Hierarchy 4. in which case the face will only be hatched if its normal matches a specified value. default null Sectioned-Faces All-Directions unset unset 4:9 12.4. are as follows: Hatch Style Ref Face Code Direction Code Face Normal Selection Criteria HSTYF FCODE DCODE NORM CRIT reference to HSTYL. with their defaults. There are three options: • • • All Directions. in which case the face will be hatched regardless of its orientation. For example.DRAFT User Guide Graphical Representation 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. and it is not possible to hatch differently the three surfaces of a BOX element that are visible in an isometric View. 4. not their primitives. 4. The Outline Style and Outline Colour (OLSTYLE and OLCOLOUR) attributes define the lines that may be drawn around the edges of the faces. with their defaults. If it selects on BOXes or VALVs (say) no hatching will be applied. not both. Only one Hatch Rule can be applied to a Design element. and so a Hatch Rule that applies to Sectioned Faces must select on significant elements. either style may be set OFF. EQUI. it is possible to emphasise an area by drawing a thick line around it without actually hatching it. A Hatch Rule can only be applied to Sectioned Faces or Primitive Surfaces. This means. and a different hatching pattern again to the top surfaces of panels representing an escape route. are as follows: Outline Style Outline Colour Fill Style Fill Colour Pipe-end Symbol Flag OLSTYLE OLCOLOUR FSTYLE FCOLOUR PIPESYM Off Colour 1 SYSTEM PATTERN 1 Colour 1 TRUE 4:10 12. For more information about hatch-patterns see Hatching Rules. The HSTYL attributes. that you cannot hatch both types of face of a Design element. an HRUL can also be defined by: USE hstyl FOR criteria which will set the HSTYF and CRIT attributes. For example.0 .4 Hatching Styles Each Hatching Style defines two style/colour pairs.4. FRMW. etc) are sectioned. The Fill Style and Fill Colour (FSTYLE and FCOLOUR) attributes define the hatch pattern to be applied to the selected faces.3 Which Elements can be Hatched Significant elements (BRAN. you could define three Hatching Rules for to a View to apply different hatching patterns to concrete and steel items cut by a section plane. for example.4. SUBS. Note: Hatching in Isometric Views may not be entirely satisfactory. optionally separated by commas. or View orientation. irrespective of the element type specified at the RRUL. Typical Tubing ‘Sectioned Symbols’ The PIPESYM attribute of Hatching Styles allows this functionality to be suppressed and replaced by normal hatching. View scale. and so the faces created by a stepped section plane will all be hatched at the same angle and separation for a given Design element.DRAFT User Guide Graphical Representation By default. they are unaffected by factors such as Sheet size. 4:11 12.4. there is no way of altering the hatching parameters to suit the orientation of the face hatched. and of a single-line thickness. solid. separation. The parameters that define each set of lines (that is. DRAFT will generate a typical sectioned symbol rather than just apply the hatch pattern to the face: Figure 4:5.5 4. Cross-hatching can be created using two sets of lines that are not parallel.1 Querying Commands Querying Rulesets and Styles Q DESC Q RRSF DESC QSTYF FOR /design_element identifier .0 . 4.at VIEW or Ruleset The last example returns the Style used for the specified design element. For more information on hatch patterns. Double-line hatching can be created using two sets of lines that are parallel. offset from sheet origin) are absolute. see Fill Styles.5 The Hatch Pattern The hatch pattern is composed of either Solid Fill. and can only be straight. or one or two sets of lines all the same colour. The lines within a set are all parallel and equally spaced.5.at Ruleset or Rule . The hatching of two connected faces will be continuous even though the faces will have different orientations in 3D space. that is. when a length of implied tubing or a DUCT or STRT (ducting straight) element is cut and the resulting face is circular or rectangular. A list of design element identifiers may be entered. angle.at VIEW . For example. 4. 2 At Representation Style . At a VIEW: Q HRSF DESCription will output an ordered list of descriptions starting with those of the HRULs it owns & then those of the HRST it references. FFSTYLE integer/line_pattern.6. 4. CRITeria crit set the CRIT attribute for the current rule OMIT elements omits the elements specified. . which may be an expression.1 Summary of Commands At Representation Rule . The <design-id> may be repeated if the HRULs for a list of design items are required.DRAFT User Guide Graphical Representation 4. . . . see above. FFCOLOUR integer/colour_name FFSTYLE OFF set style and colour for drawing edges (modelled wireline VIEWs) or visible (front face) edges (hidden-line VIEWs).6.5.6 4.one for each of its HRULs. 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. At a VIEW or HRST: Q HSTYF FOR design-id will return the HRUL that is relevant for the specified design item. by name or type.2 Querying Hatching Rulesets and Styles The querying facilities are similar to those provided for RRULs. Thus at a HRUL: Q DESCription will output a description for that HRUL with the format: USE hstyl FOR criteria At a HRST: Q DESCription will output an ordered list of descriptions . USE stylename FOR crit set drawing style for Design generic types. from the representation 4. 4:12 12.0 . PLNCOLOUR integer/colour_name PLNSTYLE OFF set style and colour for drawing p-lines MLNSTYLE integer/line_pattern. OBSTYLE integer/line_pattern. OBCOLOUR integer/colour_name OBSTYLE OFF set style and colour for drawing frontfacing edges of items that would otherwise be obscured by other objects (global hidden-line VIEWs only).6. DCODE ALLDirections All faces will be hatched. DCODE SPECifieddirection Faces whose normals match the direction specified in the NORM attribute of the HRUL will be hatched. CRITeria crit set the CRIT attribute for the current HRUL. BFCOLOUR integer/colour_name BFSTYLE OFF set style and colour for drawing rear edges of items (no effect in modelled wire line VIEWs). FCODE PRIMitivefaces Primitive faces will be hatched.DRAFT User Guide Graphical Representation BFSTYLE integer/line_pattern.0 . . The normal of a face is the vector perpendicular to it and 4:13 12. FCODE SECTionedfaces Sectioned faces will be hatched. CLSTYLE integer/line_pattern.3 At Hatching Rule . MLNCOLOUR integer/colour_name MLNSTYLE OFF set style and colour for drawing member lines PROFile ON PROFile OFF set profile flag PLINes ON PLINes OFF set p-line flag 4. . regardless of direction DCODE PERPendiculardirection Faces perpendicular to the viewing direction will be hatched. PLNSTYLE integer/line_pattern. CLCOLOUR integer/colour_name CLSTYLE OFF set style and colour for drawing centrelines. see above. USE hstylename FOR crit set hatching style for Design generic types. 4:14 12.DRAFT User Guide Graphical Representation pointing out of the solid primitive. . FCOLOUR integer/colour_name Set style and colour for hatching selected faces. OLSTYLE OFF Selected faces will not be outlined. 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. NORM direction Standard direction syntax 4. OLCOLOUR integer/colour_name Set different style and colour for drawing outline of selected faces.0 . FSTYLE integer/hatch_pattern. FSTYLE SOLidfilled Selected faces will be filled with solid colour.6.4 At Hatching Style . OLSTYLE integer/line_pattern. Thus the normal of the uppermost horizontal surface of a box is Up. FSTYLE OFF Selected faces will not be hatched. . A stepped plane is illustrated in Figure 5:1.1 Introduction DRAFT gives you the ability to construct sections through specified Design items. The simplest form of stepped plane would be defined by two points and would be equivalent to a Flat Plane.: Stepped Plane. All Planes are database items and can therefore be used with more than one VIEW. A Flat Plane is similar to a perpendicular flat plane. the ends of the plane also extending to infinity. The VIEW contents that are discarded can be on either side of the plane. An Enclosed Plane. This type of plane would be used as either a section or a backing plane. See the Drawing Production User Guide for details. Any VIEW direction can be used and the VIEW contents on either side can be discarded. Any VIEW direction can be used and either the inside or outside of the ‘tube’ can be removed. 5. • • • 5:1 12. but can be oriented to allow views of the section from any angle.e. An enclosed plane is illustrated in Figure 5:2.: Enclosed 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.DRAFT User Guide Section Planes 5 Section Planes Note: There are extensive graphical facilities for creating and manipulating Section Planes in DRAFT’s Graphical User Interface. the results of which can be displayed at VIEW level. There are three types of Plane element that can be used to define four types of section plane. Note that the two end spans must not intersect each other or an inner span. A Stepped Plane is a folded plane (i. 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. a series of non-intersecting straight line spans) that extends to infinity in both directions along a specified axis.0 . The shape is defined by a series of points. Planes can only be used with modelled VIEWs. The Plane can be used in either ‘standard’ or ‘reverse’ mode. that is not with basic wireline views. 5:2 12. Stepped Plane Figure 5:2. This allows the Plane to be used in different VIEWs both as a section or backing plane.0 . Enclosed Plane All Planes have a standard ‘retain’ and ‘discard’ side. depending on how the Plane is defined in the database. which effectively switches the Plane’s action without altering its definition.DRAFT User Guide Section Planes Figure 5:1. SMOD (a View attribute) . All lengths of implied tube that lie outside the front and back sectioning planes will be removed from the drawlist.2 Creating and Using Planes All Planes are created and held within a Library structure. This attribute only affects piping components and implied tube in orthogonal. Database Hierarchy . All other piping components will be drawn completely. /*). OFF switches the plane off. The default is STANDARD.DRAFT User Guide Section Planes 5.e.the section mode attribute. even if they are cut by one of the sectioning planes. and not on the actual volume • • • • 5:3 12.0 . VSEC attributes are: • • PLRF (Plane Reference) . i. This means that all elements in the VIEW’s Id List will be sectioned. the side to be retained or discarded. you need to create a View Section (VSEC) element under a VIEW.: Database Hierarchy . In this case the test for lying outside the sectioning planes will be based on the vector Parrive -> Pleave. If SMOD is set to OMIT FRACtional PCOMponents.e. which has no effect on functionality. which defines how small parts of piping components and implied tube that are cut by the front and back sectioning planes will be treated. all elements will be sectioned in the usual way. and are owned by a Planes Library (PLLB) element.Plane Elements To use a plane to produce a sectioned VIEW. If it is set to OFF then the section will not be applied to line elements of Piping Components. REVERSE switches the side to be retained or discarded. If left undefined this will default to the World (i. which is as the plane is set-up. PMOD .Plane Elements. LIBY VIEW PLLB VSEC PLRF PPLA FPLA SPLA WPOS Figure 5:3. CLMO (centreline mode) By default this is set to ON. The part of the DRAFT database hierarchy relating to Planes is shown in Figure 5:3. IDLN . All other non-solid primitives are sectioned normally and are unaffected by the value of attribute CLMO. This allows you to remove Components and tubing by a section plane.the mode in which the plane will be used to section the VIEW.the name of the plane to be used. If SMOD is set to STANDARD (the default). but leave the centreline to show the path of the Branch.an Id List name for the section to operate on. non-perspective Views. A single Design item name can be used. 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. set POS attribute to a 3D Design position or . Several VSEC elements can be used to produce as complex a section as you require. the retained side being that towards which the VIEW direction points. After setting up the VSEC it is just a matter of updating the design (with an UPDATE DESIGN command). a plan view will return U0.DRAFT User Guide Section Planes occupied by the length of tube. which you may need to alter to give the required section. or Modelled wireline.: Use of the Perpendicular Plane (PPLA) illustrates the use of a perpendicular Plane. Figure 5:4. ADD /VALVE1 / VALVE2 /VALVE3) the functionality will not apply. Global or Universal hidden line removal. positioned at the pump coupling.1 Perpendicular Plane (PPLA) A PPLA has a single attribute POS which defines the 3D point through which the plane passes. but the larger the number the slower the operation will be. remembering that sectioning will only take place if the VIEW attribute VTYPE is set for Local. 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 View’s IDList that fall outside the clipping box and would therefore not be drawn in any case. For example. 5. Where an IDList is defined by a set of piping components (for example. Lengths of tube that lie within or cross the front or back sectioning planes will be drawn completely.create a PPLA . the looking direction of such a VIEW will determine which coordinate is returned as zero.0 .2. 5:4 12.set POS attribute to the 3D Design position of a Design element . The basic command syntax for creating a PPLA is: NEW PPLA POS @ POS ID @ POS IDP @ . The orientation of the plane will always be perpendicular to the direction that you specify for the VIEW.set POS attribute to the 3D Design position of a Design element p-point Note: You can only input a 3D Design position on orthogonal VIEWs. DRAFT User Guide Section Planes Figure 5:4.2.0 . The retained side is that towards which the normal points. Use of the Perpendicular Plane (PPLA) 5. and an attribute NORM which defines the vector normal to the plane.2 Flat Plane (FPLA) A FPLA has an attribute POS. which defines a 3D. point through which the plane passes. The basic command syntax for defining an FPLA is: NEW FPLA POS @ NORM direction 5:5 12. positioned at the pump coupling and with a NORM direction of N45W.0 .: Use of the Flat Plane (FPLA) illustrates the use of a flat Plane. N45W. e.DRAFT User Guide Section Planes The NORM direction can be any standard direction. Figure 5:5. Figure 5:5. in which case the result will be stored as a 3D vector and the reference will be lost.g. Use of the Flat Plane (FPLA) 5:6 12. ISO2. or can be by reference to a Design element p-point. automatically creating WPOS elements.3 Stepped Plane (SPLA) A Stepped Plane can be ‘Open’ or ‘Closed’.see Figure 5:6.DRAFT User Guide Section Planes 5. the type being determined by the setting of the SPLA’s GTYP attribute. GTYP CLOSED defines a closed Stepped Plane or Enclosed Plane. The default is GTYP OPEN. A ‘handy’ rule for determining the ‘retain’ side (with PMODE STANDARD) is to hold the thumb. which determines the Plane’s extrusion direction.0 . but in practice only four points can be defined by a single STEP 5:7 12. The order in which the points are defined plus the direction of the plane’s extrusion determines which side of the plane is retained. whose sole attribute is POS. which will enable 3D positions or Design ppoints to be identified.: Defining a Stepped Plane. index finger and middle finger of the left hand mutually at right angles. one per plane ‘step’. the step’s 3D Design position. if the thumb points in the extrusion direction and the index finger points towards the last step point then the middle finger will point towards the retain side . Defining a Stepped Plane The SPLA shown above would be created by a sequence of commands such as: NEW SPLA DIR U GTYP OPEN STEP @ @ @ @ Define a series of points through which an SPLA will be constructed The STEP command will invoke the cursor. DRAFT imposes no limit on the number of steps. An SPLA owns WPOS elements. The only other attribute is DIR. Specifying a 3D position automatically creates a WPOS element and sets the POS attribute. Figure 5:6.2. A similar ‘rule’ applies for Enclosed Planes. further STEP commands will enable additional points to be appended to the existing member list. If a plane with more than four steps is required.see Plane Querying. Figure 5:7.: Use of the Stepped Plane (SPLA) illustrates some examples of Stepped Planes. 5:8 12. which will have the effect of a Flat Plane. Figure 5:7. if satisfactory then a message of the form: Splane /name is satisfactory is output. 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.: Plane Errors illustrates this situation. Use of the Stepped Plane (SPLA) (The pictures in the left half of Figure 5:7. Generally. Figure 5:8. The minimum number of points required to define an SPLA is 2.: Use of the Stepped Plane (SPLA)7 illustrate the use of the SKETCH PLANE facility .) If the STEP command is used then once a series of points are entered a check is made to ensure correct SPLANE definition.0 . an SPLA will be incorrect if parts of the plane overlap even if extruded to infinity at the ends. If the plane is not satisfactory then the message will indicate what the problem is.DRAFT User Guide Section Planes command due to command line length restrictions. for example: CHANGE ACTION /PL2-5 CHANGE ACTION . The CHANGE ACTION command. 5:9 12.3 Altering Planes If you wish to change which side of a plane is retained or discarded. 5. Of course.DRAFT User Guide Section Planes Figure 5:8. the plane can be corrected by either reordering or repositioning one of the points or by adding a new point.0 . How to move points is discussed in the next Section. Plane Errors If you have defined a plane that is unsatisfactory then it will have to be manipulated. Alternatively the plane could be made an enclosing type. A PPLA cannot have its action reversed since it does not have an orientation. but whereas the former operation only changes the view section representation. you can do this by reversing the plane’s orientation if it is an FPLA and by changing the DIR or reordering the WPOS points for a SPLA. In example C the plane can only be corrected by either reordering the points or by repositioning one or more of them. The CHANGE ACTION command is valid at any Plane element. In examples A and B.alter named Plane . the latter operation changes the Plane database element itself. changing the PMOD of the appropriate VSEC element would have the same apparent effect as a CHANGE ACTION operation in this case. and at WPOS element level in the case of a Stepped Plane.alter current (Plane) element will do this for you by altering either the DIR or NORM attributes depending on the plane type. DRAFT User Guide Section Planes If you require a plane point to be moved.at plane level . 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.from anywhere Figure 5:7. the BY command can be used. irrespective of VIEW or area view manipulation. either a POS attribute for a PPLA or an FPLA.from anywhere . e. one that is orthogonal to the axis of the plane) by using the following commands: SKETCH PLANE IN /view_identifier SKETCH PLANE /plane_identifier SKETCH PLANE /plane_identifier IN /view_identifier .at Plane level (or at WPOS elements) The plane referred to by the PLRF attribute of the VSEC can be queried by: Q PLRF DESC .4 Plane Querying Once a plane has been created. For example: BY N500 BY @ Move by the difference between two cursor hits on the same orthogonal VIEW For an SPLA.g. 5.0 . and the POS attribute of a WPOS element for an SPLA. for a Plan view only the Easting and Northing are required.at VIEW level .: Use of the Stepped Plane (SPLA) shows the SKETCH PLANE command in use. i. the POS attribute will be changed for all of the SPLA’s member WPOS elements.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 @ Q SIDE /plane_identifier @ Q SIDE /plane_identifier E value N value U value .e. i. Only one plane at a time can be sketched. You can make any plane visible in a suitable VIEW (i.e.e.from anywhere In the latter case. only two coordinates need to be given dependent on which orthogonal view direction you are working on.at Plane level . Once the plane has been sketched then it will always be visible. A plane can be erased by either of the following commands: 5:10 12. it can be queried in the following ways: Q DESC . the BY command will move the complete plane. Set POS attribute to a 3D Design position . .Create WPOS element . POS @ POS IDP @ NORM direction . OPEN will define a stepped plane. . Any change made to a sketched Plane will not result in a corresponding change to the displayed sketch . . CLOSED will define an enclosed plane .Set GTYP. .Set position attribute 5. . N45E .Set POS attribute to the 3D Design position of a design element p-point . . . . DIR value GTYP OPEN or CLOSED STEP @ @ @ .5.reverse the action of an FPLA or SPLA by reversing the direction of the NORM or DIR attributes respectively 5:11 12. .5 5.at VIEW level . CHANGE ACTION /plane gid .Set extrusion direction Use any direction syntax e.4 Switching Retain/Discard Side .Set an FPLA normal direction 5. NEW WPOS POS E value N value U value .DRAFT User Guide Section Planes ERASE PLANE ERASE PLANE IN /view_name .2 For SPLAs .5.from anywhere Note that the sketch facility is only a ‘drafting aid’ and is not part of the VIEW annotation. .5.3 Creating Section Plane Points Directly . 5.g.5.Define a series of points through which an SPLA will be constructed 5.1 Summary of Commands Setting Plane Position . . .another SKETCH PLANE command will be needed.0 . At Plane level .Move the point in 3D Design World coordinates explicitly . Planes Q DESC Q PLRF DESC Q SIDE @ Q SIDE /plane_name @ . . . The default is either STANDARD. .At VSEC level Retained/Discarded side .5. BY N500 BY @ .The Mode in which the plane will be used to section the view. .The reference name of the plane to be used .5. .Move by the difference between two cursor hits on the same orthogonal view 5.An Id list name for the section to operate on.7 Setting up the VIEW to Accept Section Planes .e. this has the same result as using the CHANGE ACTIONS command. .5. . DELETE STEP value value .8 Querying .At plane level . which switches which side is retained or discarded. any Removes will be ignored.DRAFT User Guide Section Planes 5. If left undefined will default to the Id list specified by the VIEW.where value is the list position of the point to be deleted 5. For a SPLA or FPLA. which side will be retained or discarded.From anywhere Q SIDE /plane_ name E value N value U value .0 . PMOD [STANdard | REVerse | OFF] .Create a VIEW Section element under a Layer . A single Design item name can also be used. . The Id list can only have Added items. i.5 Moving Section Plane Points . which is as the plane is set up.From anywhere 5:12 12.6 Editing Section Plane Points . 5. or REVERSE.5. NEW VSEC PLRF name IDLN name . At VIEW level .At Plane level .DRAFT User Guide Section Planes 5. .From anywhere 5.9 Plane Sketching . SKETCH PLANE IN /view name SKETCH PLANE /plane name SKETCH PLANE /plane name IN /view name .From anywhere 5:13 12.5. .5.0 . ERASE PLANE ERASE PLANE IN /view name . .10 Plane Erasing .At VIEW level . . 0 .DRAFT User Guide Section Planes 5:14 12. 1 Using the Cursor with DRAFT Comments Identifying Elements Using the Cursor With many DRAFT commands. FLANGES) may be accessed. EQUI. Dimension Points and Labels may also be accessed in this way. Catalogue or Drawing element (e. Dimensions.select and identify nozzle You can specify up to 20 element types. i. will be picked). Elements down to and including DESIGN primitives or Catalogue piping components (e.g. Labelling and 2D Drafting for ID commands relating to Dimensions.select and identify valve or VTWA . a primitive.select and identify valve . picking an element with the cursor will select and identify the displayed element (the lowest-level element.e. SHEE) . Other cursor identify commands are: ID element_type @ ID VALV @ ID VALV VTWA @ ID NOZZ @ ID NOZZ @ .g.element_type is any Design.0 .select and identify nozzle . Labels and 2D drafting respectively.select and identify p-point or structural node (PNOD or SNOD 6:1 12. For example: ID VALV VFWA VTWA @ See Dimensioning. The following command can only be used as part of a command: IDP @ For example ON IDP @ You can restrict items picked to be either DESIGN database elements or DRAFT database elements by using the commands: . you can use the cursor to identify an element in the graphics window by using the ID command followed by @: ID @ At this point.DRAFT User Guide Using the Cursor with DRAFT Comments 6 6. g. STRU or SUBS elements.e.Design primitive p-points made visible . or quit out of the command line by clicking on Cancel on the Status Form. for example the end of a cylinder axis for identifying primitives below EQUI. direction and position of the point will appear in the DRAFT Command Input & Output form and the p-point display markers will disappear. 6. The main uses are: • • for positioning annotation at a particular point on a primitive. the edge of a Sheet) you will move to that element within the DRAFT database. a Cylinder primitive in a vessel) you will move to the DESIGN database.DRAFT User Guide Using the Cursor with DRAFT Comments ID DESEL @ ID PADEL @ ID DRAEL @ Picking an element with the cursor will make the item the current element (i. Selecting a p-point is achieved by releasing the mouse button with the cursor over the required point.0 . A p-point or node may be identified using Q IDP @ In addition. you will be able to zoom or pan the view. The identifier. PNODs and SNODs) may be picked by the cursor. 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. 6:2 12.g. as the cursor moves across (by default) a significant element its p-points will become visible. the current position in the database will move to that item).even when in ‘Design primitives’ mode.attach annotation to specified p-point or node To identify a p-point. 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 . Releasing the left-hand mouse button without selecting a p-point will leave the current set of p-points visible. P-points that lie outside the view rectangle will not be shown.query current setting In the latter case.2 Picking P-points and Nodes P-points and structural node points (that is. the p-point may be directly selected. if you select a Drawing element (e. move the cursor across the VIEW display with the left-hand mouse button held down (the cursor changes its appearance). picking on one of these lines will cause all the p-points of the significant element to be made visible .significant element p-points made visible . also. Lines generated by a section plane (see Section Planes) are assigned to the significant element and not to the primitive sectioned. If you select a DESIGN element (e. for example ON IDP @ . identifying a length of implied tube will cause only the Branches Head and Tail p-points to be made visible. the appearance of the cursor will change. for example.0 . see Graphical Feedback Style and Colour.DRAFT User Guide Using the Cursor with DRAFT Comments 6. The command IDPDistance @ will return the proportional distance along the identified p-line.65 In the former case the default value for proportional distance will be used.select and identify p-line start or end 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: Pline RTOS of /SCTN-98 start Pline MEML of /SCTN-99 end depending how far along the p-line the cursor hit was made. see Marker Styles. This may be used. For example: NEW GLAB ON IDPE @ Q IDPE @ will position a GLAB on the identified p-line at either its start or end point. 6. For example a GLAB can be positioned by either of: ON IDPL @ ON IDPD @ Examples of text returned by these commands could be (respectively): ON PPLINE BOS OF /SCTN. You can change the marker type and scale. 6:3 12. They are shown as markers.PN1_PN5 PROP 0.3 Picking Structural Elements and P-lines A p-line (or member line) may be identified by cursor hit using the commands: IDPL @ IDPE/ND @ . 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).1 P-point Style P-points will be drawn for Design elements in all VIEW types. will return the ENU position of the start or end point of the identified p-line.select and identify p-line . to position annotation at the start or end points of p-lines or to obtain the 3D coordinates of these points. You can change the colour using the SETFEEDBACK command.PN1_PN5 ON PPLINE BOS OF /SCTN.2. X 574 Y 200 As with the ENUPOS query command. This command returns the projection of the explicit or implied 3D position onto the Sheet for the current VIEW. This command returns the back-projection of this position at Z=0 into the 3D world coordinate system of the current or specified VIEW. This position (which must be within the VIEW rectangle) may be specified by cursor. This position or item may be specified by cursor. The grid is defined by the SNAP command. 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. or an explicit 3D coordinate. 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) The response will be of the form: ID =123/456 ORIGIN W 0000mm N 0000mm U 0000mm 6. To derive a 3D position from 2D data use: Q ENUPOSITION OF sheet_position (at/below a VIEW) where sheet_position is a position on the Sheet.4 Querying Position Data There are two query commands that enable you to convert between 2D Sheet positions and 3D design data positions.DRAFT User Guide Using the Cursor with DRAFT Comments 6.define a rectangular grid 6:4 12. For example.0 . for example: SNAP ON SNAP OFF SNAP ON 10 . 10mm in both X and Y directions SNAP ON SPACING X25 Y40 . explicit p-point reference. origin of a named element.define a square grid.turn the snap grid on . the specified VIEW must be axonometric without perspective and the specified position must lie within the VIEW rectangle. for example: W 15500 N 10020 U 0 The specified VIEW must be axonometric without perspective.5 Snapping 2D Points to a Grid Cursor commands which request 2D points will be rounded to the nearest point on the SNAP grid (if on).turn the snap grid off (the default) . The initial setting (on entry to DRAFT) is a square grid at the Sheet origin. ISOLB or SYLB) owning the specified element. The spacing of the visible grid may be changed by commands such as VGRID SNAP 2 . the initial SNAP spacing is one inch square. so it is advisable to reset the grid (with another VGRID ON command) if the SNAP settings are changed. The snap grid may be queried using the command: Q SNAP The same information will also be output to file by a RECREATE DISPLAY command. i. OVER. the SNAP grid origin is positioned at the bottom left-hand corner of the Sheet. where sheet identifier identifies a picture element or an owned element: 6:5 12. Overlay Sheets etc) when SNAP is ON.DRAFT User Guide Using the Cursor with DRAFT Comments When the SNAP grid is ON. LALB. all 2D cursor hits (including the BY @ command) will be snapped onto the nearest grid point.define snap origin with cursor SNAP settings apply to all Sheets (and Symbol Libraries. for example: VGRID /VIEW1-2 ON This command would turn the visible grid on for the picture element (i.e. whether or not the visible grid (see VGRID command below) is displayed.define snap origin explicitly . Snapping only applies to cursor-generated positions. Cursor hits will be snapped on any picture. Visible Grids VGRID ON Visible grids are not output to plotfiles. with snapping switched off. The visible grid is not maintained with changes in SNAP settings. SNAP OFF AT X 0mm Y 0mm SPACING X 25mm Y 25mm If the current units on module entry are INCH or FINCH.e. BACK. 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. the SHEE. Y axes of the Sheet. This origin may be changed by commands such as SNAP AT X100 Y100 SNAP AT @ . An element identifier may be specified as part of the command.0 . positions entered explicitly from the keyboard or via a macro are not snapped.change visible grid spacing to twice that of snap grid 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). By default. and is drawn parallel to the X. This does not affect graphics picking or pseudo-3D cursor hits. Labels. Layers. Overlay (OLAY) elements may also be highlighted. 2D Drafting primitives). Dimensions. Note: For the permanent highlighting of 2D Drafting primitives. including implied Tubing and Rodding) or DRAFT annotation elements (i. For example: HIGHLIGHT HIGHLIGHT IN /VIEW1-1 HIG IN ID VIEW @ Highlight current annotation element in all area views in which it appears Highlight current element (design or notation) in named VIEW Highlight current element in cursor-identified VIEW VIEW HIG /1501B IN ID VIEW @ Highlight named design element in cursor-identified HIG HIG HIG HIG IARRIVE TUBE OF /VALVE1 IN /VIEW4 ILEAVE TUBE OF CE IN /PLAN_VIEW HEAD TUBE OF /BRAN99 IN CE TAIL TUBE OF CE IN /E_ELEVATION Example commands for highlighting implied tubing HIG IN _f1_v1 HIG /1501B HIG /1501B IN _f1_v1 Highlight current element in named area view Highlight named Design element in all area views in which it appears Highlight named element in named area view only Elements may also be highlighted simply by passing the cursor over them in the display with the left-hand button held down. see the ENHANCE command in Enhancing Drafting Primitives.e. It is also possible to query whether a specified Sheet currently has a visible grid displayed. The elements concerned may be Design elements (from significant element downwards.DRAFT User Guide Using the Cursor with DRAFT Comments VGRID [sheet identifier] OFF ERASE AIDS [IN sheet identifier] ERASE VGRID [IN sheet identifier] The following causes all visible grids to be erased: 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. using. Q VGRID sheet_identifier 6. 6:6 12.6 Highlighting Displayed Elements Displayed elements can be highlighted (flashed) by using the HIGHLIGHT command.0 . PPOINTS SIG PPOINTS PRIM . EQUI.Design primitive p-points made visible 6:7 12.derives a 3D position from 2D data . .select and identify p-line .select and identify valve .select and identify any Design.DRAFT User Guide Using the Cursor with DRAFT Comments 6. .0 . ON IDP @: IDP @ IDPL @ IDPE/ND @ ID DESEL @ ID PADEL @ ID DRAEL @ .Significant element p-points made visible .derives a 2D position from 3D data You can query the 3D origin in World coordinates of any Design element using: Q IDORI @ Q IDORI sheet_position (at/below a VIEW) returns the 3D origin in World coordinates of a Design element 6.7. .select and identify bends or elbows .select and identify p-point .select and identify any displayed element . ID @ ID element_type @ ID VALV @ ID VALV VTWA @ ID BEND ELBOW @ ON IDP @ ON IDPL @ ID NOZZ @ .g. SHEE. Q ENUPOSition OF sheet_position Q SHPOsition OF position .7. .7 6.select and identify any Design element .attach annotation to specified p-line .select and identify valve or VTWA . . PJOIN) .select and identify p-line start or end .3 P-point Visibility .ID BEND ELBOW @ . For example.1 Summary of Commands Cursor Identification/Selection .attach annotation to specified p-point . .7.2 Querying . Drawing or Catalogue element (e.select and identify any Draft element 6.identify a Nozzle The following can only be used as part of a command. change visible grid spacing to integer times that of snap grid .highlight named element in named area view only .7.query snap grid .return to default visible grid spacing .DRAFT User Guide Using the Cursor with DRAFT Comments 6.0 .turn snap grid on .define a rectangular snap grid .highlight current element in all area views in which it appears . 10mm in both X and Y directions .highlight named DESIGN element in VIEW picked by cursor 6.turn visible grid on .define snap grid origin with cursor ..query visible grid snap multiple 6:8 12..7.highlight current element in named area view .4 Highlighting Elements.5 Snapping 2D Points to a Grid..highlight named DESIGN element in all area views in which it appears .define a square snap grid.. HIGHLIGHT HIG IN _f1_v1 HIG /1501B HIG /1501B IN _f1_v HIG /1501B IN ID VIEW @ . SNAP ON SNAP ON 10 SNAP ON SPACING X25 Y40 SNAP AT X100 Y100 SNAP AT @ VGRID ON VGRID SNAP integer VGRID SNAP Q SNAP Q VGRI .define snap grid origin explicitly . plotfile style definitions can be made different from those on the screen.PLT A1 CUT OFF BORD 25 FRAME OVER If required. on the screen could be made thick. There are three additional options which may be specified between papersize and OVERWRITE: • • • CUTMARKS. this can be suppressed by CUTMARKS OFF. 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: PLOT /SHEET1 /SH1.DRAFT User Guide Plotting and Drawing Output 7 Plotting and Drawing Output At any time during the drawing process. It does not control the frame around the edge of the plotfile (see CUTMARKS above). By default the rectangular limit of the plotfile will be shown. Hence a line that appears as thin. Existing plotfiles will not be overwritten unless the OVERWRITE option is used. 7:1 12. An example of a PLOT command using its entire syntax is: PLOT SHEE FILE /S3. View or the contents of an Area View. solid. you can generate a plot that consists of a single Sheet.0 . on plotfiles.PLT A3 If the paper size is not specified then it will be taken as the same as the item being plotted.1 General Plotfiles are produced by the PLOT command. 7. dashed. The BORDER value option will cause a border to be left within the specified paper size. FRAME can only be used in concert with the BORDER option and marks the inside edge of the border. You can query the size of a plotfile using the command: Query PLOTFile name SIZE The response will be the size rectangle of the plot. See User-Defined Line Styles. The FRAME option causes a frame to be drawn around the image. The image size of the item being plotted will be reduced accordingly.PLT PLOT VIEW FILE /VW1. The option NOVIEW is also available and is the default. There are no specific options for the production of EMF file. PDF files. special control of print form box for automatic drawing production in batch operation with the ONEDIALOG and NODIALOG options. For these output forms the PLOT command takes the following alternative forms: PLOT uuname [FILE] PRINT 'Options. 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. tif-G4.' [papersize] [OVERWRITE] PLOT uuname [FILE] PDF /filename 'Options.0 . This ensures that there is the best contrast in the output.22.MINL 0. png. The COLOUR option defines how colour is to be handled when the drawing is output.' [papersize] [OVERWRITE] PLOT uuname [FILE] IMAGE /filename 'Options. The following are examples of the commands: Example: PLOT CE PRINT 'MINL 0.2 Extended Output Formats The PLOT command controls the direct output of DRAFT drawings to printers. The default setting in the options string would be 'COLOUR STANDARD'. The specific options for printing cover: automatic adjustment of the drawing size to fit size and orientation of the paper with the REDUCETOFIT. tif with LZW compression.22... image files and Windows Enhanced Metafiles (EMF).COL COLOURPLUS' A0 PLOT /PLAN1 PDF /plan.' [papersize] [OVERWRITE] The DRAFT commands for the extended output types are an extension of the existing PLOT command and include the output type name and a configurable option string.' [papersize] [OVERWRITE] PLOT uuname [FILE] METAFILE /filename 'Options.pdf 'MINL 0. EXPANDTOFIT and ROTATETOFIT options. • • • • The following options apply to all of the output types: 7:2 12.COL BW.. which will use the defined colours of the drawing unchanged..22' A4 PLOT /PLAN3 METAFILE /plan3. bmp and gif.DRAFT User Guide Plotting and Drawing Output 7.VIEW' A3 PLOT /PLAN2 IMAGE /plan2. Support for these output formats is itself important but also enables the production of higher quality graphical output including the use of TrueType text.. A tif image can contain a multiple pages.png 'IMAGE PNG. The command used for each of the output types includes an options string to control the drawing process. a standard print form is displayed for the user to select a printer and set preferences. The output of an image file is in one of the following standard formats: jpg. Some options apply to all output types while others are specific to a particular type.22' A3 OVER The following options apply to specific output types: • • When printer output is used...pdf 'MINL 0. uncompressed tif.. Plotting a PDF file has the option to automatically launch the reader by selecting the VIEW option. STANDARD retains the defined colours by the drawing. An example of this in an options string is 'BGCOL 15'. GRAYSCALE converts all colours to an equivalent shade of gray. The FRAME option draws a thin frame around the drawing using the specified colour number.g. COLOURPLUS converts all shades of gray to black or white to provide a contrast with the background colour. e.DRAFT User Guide Plotting and Drawing Output The option 'COLOUR GRAYSCALE' converts all of the colours to an equivalent shade of gray. Select the Image format. pdf 7:3 12. • The MINLINEWIDTH option specifies the minimum line width in mm. The option 'COLOUR COLOURPLUS' converts all gray. The BGCOL option sets the background colour to a specified colour number. a typical value is 0. This adds contrast to the output drawing. BW changes all colours to black or white to provide contrast with the background colour. black and white colours to black if the background is white and white if the background is white. 0. the default is TIF image The COLOUR option allows the defined colours to be all adapted to suit output requirements.22'. MINL/INEWIDTH value VIEW NOVIEW Set the minimum line width to be used to draw expressed all in mm.22 mm and would appear in the option string as 'MINL 0. This value affects the quality of the graphical output. • • • 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 F/RAME value 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 Description Output Types Draws a thin frame around the drawing using the specified all colour number.22 Launch the Adobe Reader to automatically view a PDF pdf after it has been written to file.0 . Suppress the PDF VIEW action. The default background colour of all of these output types is white. 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. An example of this in an options string is 'FRAME 3'. all These colours may be used in tty mode when the standard colour table is not available. The initial print settings including paper selection are used for subsequent prints. this option reduces and/or rotates the drawing to fit within the current paper size. The default printer is selected with all of its user defined settings.DXF A3 OVER It is recommended that the CUTMARKS OFF option be used when generating DXF files.3 7. ISOCOL/OURS Use the Isodraft colour table instead of the default table. 7:4 12. 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. all These colours may be used in tty mode when the standard colour table is not available. followed by the TABLES section. EXPAND/TOFIT ROTATE/TOFIT ONEDIALOG NODIALOG When this option is selected for printing no print dialog is print displayed. as necessary.3. Use the Dictionary colour table instead of the default table. Fills the drawing background using the specified colour all number. This is useful for automatic drawing production.2 DXF File Contents The DXF file created has a brief header section. For example: PLOT SHEE DXF /SHEET1.1 Standard DXF Output Creating the DXF File DXF format plotfiles (for use in AutoCAD) can be generated in a similar way to PDMS plotfiles simply by adding DXF to the command. and the ENTITIES section. DICTCOL/OURS BGCOL value 7. which defines text styles and line types. 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.3.DRAFT User Guide Plotting and Drawing Output Option Name and Arguments REDUCE/TOFIT Description Output Types When a drawing size is larger than the selected paper size print and/or the page orientation is different. 7. No expansion or reduction is performed When this option is selected for printing.DXF PLOT /SHT1/V1 DXF /VIEW1. as necessary. the normal dialog print is displayed before the print job and no further dialog will be displayed for subsequent jobs.0 . which contains the drawing data. The DXF BLOCK section is not used. This is useful for automatic drawing production. which is defined in file acadxf. prefixed by ‘GT’. BYLAYER in AutoCAD).g.Unterminated If the ZCOORD option is used. Note that the Layer colour for all DRAFT layers is white. GTSOLID. $LTSCALE and $DIMSCALE.as above. The line types are the standard DRAFT predefined set. the DXF file produced will contain Z-coordinates of value 0.DXF CADC ZCOOR . GTDOT etc.3. For example.0 . as a minimum. 7:5 12. where n is a number that corresponds to a PDMS colour. Two sets of text styles are available corresponding to horizontal and vertical text (paths Right and Down). File acadxf. and is normally closed by the standard AutoCAD EOF. then the DXF file produced will contain a header. Text height and shear are supported. but use AVEVA header If no header type is specified. Instructions for installing these can be found in the AVEVA PDMS Installation Guide.DRAFT User Guide Plotting and Drawing Output The HEADER section contains two comments.DXF ACAD ZCOOR PLOT SHEE DXF /SHEET1.(terminated by an ENDSEC keyword) ENTITIES section (optional) . Example commands are: PLOT SHEE DXF /SHEET1. giving file creator's name and the time/date of creation. The only other variables set are $LIMMIN and $LIMMAX (the limits of the drawing Sheet). e. • • • • Lines are passed as POLYLINE entities consisting of two or more points. the following: • • • • HEADER section (terminated by an ENDSEC keyword) TABLES section (terminated by an ENDSEC keyword) BLOCK section (optional) . which are the DRAFT names. and in polyline vertices and TEXT entities. These layers are named GT_n. the brief AVEVA header is assumed.3 File Header Options DXF files may have full AutoCAD headers and Z-coordinates in the ENTITIES section.000 (i. • • The ENTITIES section then follows. code 30 entries) in the $EXTMIN and $EXTMAX parameters in the header section. The corresponding set of font files is defined in the TABLES section of the DXF file. 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 TABLES section defines all required text styles and line types. they have been given names for AutoCAD use. text in Font 21 is output in style HTX21. All text is justified to the bottom-left corner of the text string.hdr must contain.e. The available linestyles have names prefixed by ‘GT’. Colours are maintained according to Layer (i. If the ACAD option is used. Line thicknesses are available.include AutoCAD headers and Z-coordinates . All text strings are passed as TEXT entities in the appropriate font. Note that non-zero character spacing is not supported in DXF output. See User-Defined Line Styles.hdr in the PDMS executable directory (as defined by global variable PDMSEXE).e. AutoCAD font files are provided as part of the AutoDRAFT software. Arcs/Circles are currently passed as POLYLINE entities with bulge factors. Layers are assigned to entities according to their colour definition within DRAFT. 7. If required.4.1 Configurable DXF and DWG Output Configuration Datasets It is possible to control the format of DXF and DWG output using configuration datasets. 7. line thickness and character height will all be affected.).DXF ACAD ZCOORD EUC SCALEUP 100 This will cause all values in the file to be increased by 100. Japanese) may be encoded in the DXF file in one of two formats. This will create a DXF file with a name and format defined in the specified dataset for the current picture element (e. For example: PLOT SHEE DXF /SHEET1. Enables database elements to be assigned to AutoCAD layers. the 7:6 12.DXF output is the only supported feature. Allows database attribute information to be exported from DRAFT as AutoCAD Block attributes.DXF CADC ZCOORD SHI/FTJIS If no encoding format is specified.DRAFT User Guide Plotting and Drawing Output 7.4 7. SHEE. usable at Sheet level. namely Extended UNIX Code (EUC) and Shift-JIS.5 Scaling The output written to the DXF file can be scaled using the SCALEUP command option. Maps fonts.DXF ACAD ZCOORD EUC PLOT SHEE DXF /SHEET1.g. EUC will be assumed.0 . These options will have no effect if only single-byte characters are output. The configuration dataset controls how the database information is to be mapped into DXF format. Configurable DXF Output The following example command uses the configuration data set ’MyConfigData’ to control the export of DXF information: LIEXEC /Draft_DXF_LI ’DXFOUTR13’ ConfigData ’MyConfigData’ Here ’DXFOUTR13’ is an application feature. colours and linestyles between DRAFT and AutoCAD.3. This option allows the effects of VIEW scaling to be reversed to some extent. The format required will depend upon the machine for which the DXF file is intended. 7. DXFOUTR13 for producing AutoCAD Release 13 . SYLB. The format should be specified after the header and Z-coordinate requirements. Before giving the above command. It does the following: • • • • Controls how DRAFT graphics are to be grouped as AutoCAD Block and Group definitions. The export application can be executed using the LIEXEC command (which also loads the application if it has not already been loaded).3. etc. At the current release of PDMS. the scaling value should be specified after the Z coordinate and character encoding requirements. For example: PLOT SHEE DXF /SHEET. The configurable DXF and DWG facility uses ‘loadable image’ (LI) applications. Factors such as paper size.g.4 Encoding of Multi-Byte Characters Multi-byte characters (e. Note that blocking commands for Design graphics in this file are only intended as an example.mac Defines the default configuration settings.mac full_dxf. 7:7 12.dxf' Configurable DWG Output The following example command uses the configuration data set 'MyConfigData' to control the export of DWG information. and can be one of the following: R13 R14 R15 R18 R21 for 2000.0 . for example LIEXEC /Draft_DXF_LI 'DXFOUTR13' HeaderFileName 'header. 2005. 2006 for versions 2007. which do not support full AutoCAD Release 13 DXF file format. in particular the Outputfilename switch would normally be overridden by an LIEXEC option. For example: LIEXEC /Draft_DXF_LI 'DXFOUTR13' CONFIGDATA 'MyConfigData' OutputFileName '%PDMSUSER%/new.DRAFT User Guide Plotting and Drawing Output configuration dataset must have been defined in DRAFT by typing in the configuration data at the command line or by reading in a predefined macro file. The {configuration options} will contain the BLOCK and SWITCH syntax that control the content of the DXF file produced. minimal in size. The format of the configuration data set is identical to that for DXF output. 2008. grouped and layered DXF files closely mapped to the DRAFT Sheet exported. See Switches and BLOCK Rules to Control DXF and DWG Export for a full list of the switches and their permissible and default values. graphics_dxf. in which case the default values of all the switches will be assumed and no blocking will take place. in such a case a DXF header file must be specified. LIEXEC /Draft_DWG_LI 'R15' ConfigData 'MyConfigData' 'R15' indicates the AutoCAD version number.dxf' It is also possible to omit the CONFIGDATA. 2002 for versions 2004. Defines a sample set of configuration settings to produce fully blocked. 2009 Configuration Datasets A DRAFT Configuration Dataset is made up of a series of switches and Blocking rules. Three example macro files are provided: default_dxf. Defines a configuration for graphics-only DXF files. which can be imported into systems. However. and may require modification to suit your own requirements.mac The configuration options may be overridden by LIEXEC command line options. This provides compatibility with AutoCAD Release 12. Attributes can be included in block definitions. ZONE. SUBS. but are shown as mixed case here to aid legibility. SUBE.DRAFT User Guide Plotting and Drawing Output Example: SWITCH GroupGLAB ON Group GLABs into AutoCAD groups SWITCH HeaderFileName 'header. REST Other Commands Other commands related to this facility are: LILIST DLICON Lists features of application(s) loaded by LILOAD/LIEXEC. HVAC. INCLUDE NAME BLOCK ALL BRAN WITH ( HBOR GE 100 OR TBOR GE 100 ) .dxf' Specify the DXF header file name The switch names are case-independent. For example: DLICON {configuration options} EXIT The datasets currently defined within DRAFT can be determined by: DLICON LIST The definition of a specific dataset can be determined by: DLICON name DUMP The value of a specific switch within a dataset can be determined by: DLICON name CHECK SWITCH switchname Whether or not there is a blocking rule applicable to a specified Design element can be determined by: DLICON name CHECK BLOCK element_identifier 7:8 12. Example: BLOCK ALL STRU. SBFR. Standard selection syntax is used to define Blocking Rules. INCLUDE NAME SPREF Elements that can be blocked are: SITE. Defines a named set of configuration options. FRMW.0 . BRAN. EQUI. STRU. PIPE. These specify how design elements are to be organised into DXF Blocks. Suppresses overlay layering. … 1. [ OFF ] LayerZone ON [ OFF ] LayerSite ON [ OFF ] LayerBack ON [ OFF ] LayerOlay ON [ OFF ] LayerNote ON [ OFF ] 7:9 12.2 ]. Prevents primitive thickness from being represented in AutoCAD. Creates a layer for each overlay and places the overlay information on that layer in AutoCAD. Arcs and Text with no Polylines. Suppresses any numeric layer name view prefix. Creates a unique layer for each Design ZONE and places all design information from that zone onto the layer. Creates a unique layer for each Design SITE. Defines the scaling of width factors translated from DRAFT to AutoCAD. Suppresses site layering.1.DRAFT User Guide Plotting and Drawing Output 7. 0.3. The PlineWidthFactor switch defines the scale of width factors used by DXF export. Suppresses note layering. OFF PlineWidthFactor 0. Creates a unique layer for the backing sheet and places the backing sheet information on that layer in AutoCAD. Suppresses zone layering.0 . All entities are generated using Lines. Polyline width is defined by: [( LTHICK .0 ViewNumberPrefix ON Adds a unique numeric view prefix value to the beginning of each AutoCAD Layer name created from DRAFT views. Suppresses backing sheet layering. Creates a layer for each note and places the note information on that layer in AutoCAD. [ 0.2 Switches and BLOCK Rules to Control DXF and DWG Export Switch name PrimitiveThickness Value (default) [ ON ] Description Allows primitive thickness to be represented by Polyline width in AutoCAD.4.1 ) * PlineWidthFactor]. and places all design information from that site onto the layer. Colour numbers above 15 are mapped directly to AutoCAD colours in the range 1 to 254. Maps DRAFT text styles using AutoDRAFT equivalent AutoCAD font styles. Uses explicit X. Suppresses DRAFT layer to AutoCAD layer mapping. ColourMapping [ ON ] OFF IncludeZCoordinates ON [ OFF ] 7:10 12. Unsupported or undefined linepattern names are exported to AutoCAD using an equivalent DRAFT style name. mapped using “BYLAYER” in AutoCAD. Uses explicit X and Y co-ordinate values in the DXF file. DRAFT colours 1 to 15 are mapped to equivalent AutoCAD colour numbers.Y and Z co-ordinate values in the DXF export file. Uses the standard AutoCAD “STANDARD” (txt) font style for all fonts in AutoCAD. Suppress colour mapping and assign all DRAFT colours to AutoCAD colour “BYLAYER”. If Z is not equal to 0. Maps DRAFT linepattern definitions onto equivalent AutoCAD linetype definitions contained within the DXF header.0 . where Z is assumed to be 0. it will be output explicitly. with a standard dashed representation. [ OFF ] FontMapping [ ON ] OFF LinetypeMapping [ ON ] OFF All DRAFT linepatterns are represented by the default “CONTINUOUS” linetype.DRAFT User Guide Plotting and Drawing Output Switch name LayerLaye Value (default) ON Description Creates an equivalent layer in AutoCAD matching DRAFT annotation layers and places information from the DRAFT layers onto subsequent AutoCAD layers. Handles. dictionaries and table information. yet hierarchically related blocks can be grouped together using the GroupBlocks switch. Block definitions that contain multiple subcomponent blocks will be represented by a collection of individual blocks as opposed to a single block definition. This switch can be used to produce AutoCAD release 12 compatible DXF files and can be used to minimise DXF information in terms of file size and production time with the following switches set to OFF: LinetypeMapping. Exports AutoCAD release 13 AcDb object markers in all entities in the DXF file. This option may be required for less tolerant DXF interpreters. ColourMapping.0 . IncludeZCoordinates The following switches are forced OFF when the GraphicsOnlyDXF switch is ON: EntityAcDbMarkers and Include DXFHeaderEntities All Group switches are ignored when this option switch is used although blocking is permitted! [ OFF ] EntityAcDbMarkers ON Exports DXF information using a well defined full AutoCAD release 13 DXF format. Except: Layers. [ OFF ] NestedBlocks ON [ OFF ] 7:11 12. including Objects. These individual. Linetypes and Styles. Suppressing AcDb markers in the DXF file can significantly reduce the resulting DXF file size. Suppresses AutoCAD release 13 AcDb object markers in all entities. AcDb markers. Allows hierarchically related blocks to be nested into a single block hierarchy in AutoCAD. Prevents hierarchically related blocks from being nested together in AutoCAD.DRAFT User Guide Plotting and Drawing Output Switch name GraphicsOnlyDXF Value (default) ON Description Exports minimal DXF header information and omits all R13 specific data. BlockOlay [ ON ] OFF BlockSymb ON [ OFF ] BlockFill [ ON ] OFF BlockGraphicFile ON [ OFF ] GroupDims ON [ OFF ] GroupNote ON [ OFF ] GroupVnot ON [ OFF ] GroupFrame ON [ OFF ] GroupGlab ON [ OFF ] GroupSlab ON [ OFF ] 7:12 12.0 . Suppresses Grouping of SLAB labels. Groups dimensions into unique AutoCAD release 13 groups. Suppresses Grouping of dimensions. Creates a single Block definition for each instanced DRAFT symbol. Suppresses blocking of Graphic plot spooled files. Groups SLAB labels into unique AutoCAD release 13 groups. Groups notes into unique AutoCAD release 13 groups. Groups GLAB labels into unique AutoCAD release 13 groups. Creates a single Block definition for each DRAFT overlay sheet. Suppresses Grouping of notes. Suppresses Grouping of view notes. Suppresses blocking of backing sheets. Groups frames into unique AutoCAD release 13 groups. Suppresses blocking of overlay sheets. Suppresses Grouping of frames. Suppresses blocking of symbols. Groups view notes into unique AutoCAD release 13 groups. Suppresses blocking of hatch patterns. Creates a single Block definition for each DRAFT hatch/fill pattern.DRAFT User Guide Plotting and Drawing Output Switch name BlockBack Value (default) ON [ OFF ] Description Creates a single Block definition for the DRAFT backing sheet. Creates a single Block definition for each occurrence of a plot spool file used to represent backing sheets or overlays. Suppresses Grouping of GLAB labels. dxf’' OutputFileName [‘output.dxf’] Specifies the DXF header file name. it must be a valid AutoCAD release 13 DXF file. 7:13 12. Under normal export circumstances. If the search path is set to off. Specifies font mapping should be applied using the default EUC standard. based on the default ‘draft_dxf_li. This option can be used if the relevant AutoCAD shape files are located in the ACAD support directory path.dxf’] Specifies the output DXF file name produced when exporting DXF file information. generated from blocking structures and sub-structures or sub-frameworks.0 . This switch should only be used when the NestedBlocks switch is set to OFF. this switch should be omitted or set to OFF. Specifies font mapping should be applied using the Shift JIS standard. Suppresses Grouping of related Blocks Specifies the search path used to locate AutoDRAFT font shape files. [ OFF ] FontFilePath ‘/search/ path/…’ [ OFF ] UseShiftJISFonts ON [ OFF ] IncludeDXFHeaderEntities ON [ OFF ] HeaderFileName [‘%PDMSEXE%/draft_dxf_li.DRAFT User Guide Plotting and Drawing Output Switch name GroupBlocks Value (default) ON Description Groups together hierarchically related blocks. Allows drawing information contained within the DXF header file to be merged with the exported DRAFT drawing information. Ignores all DXF entities in the ENTITIES section of the DXF header file. This value is appended to the beginning of all font style records created in the DXF file. If a header file name is specified. no directory path is appended to the start of font style records. which will be read into DRAFT and used as a backbone template for generating the DXF information. 0 ] Scale Factor 1. It does the following: • • • • Controls how DRAFT graphics are to be grouped as DGN Group definitions. User-defined glyphs and line pictures (see Line Styles) are ignored. • • 7. enable Full scale Design units to be output in (default 1. It is possible to control the format of DGN output using configuration datasets. Allows the DXF export application to search and compare configuration data-set BLOCK rules against database information in order to block components in the DXF export file. Enables database elements to be assigned to DGN Levels.DXF File in Annotation units Note: The default values specified in this table are those set up by the configuration macro default_dxf. 7. 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.0 .1 Configurable DGN Output Configuration Datasets DGN files (for use in MicroStation/J) may also be created from DRAFT Sheets. Maps linestyles.DRAFT User Guide Plotting and Drawing Output Switch name IgnoreBlockRules Value (default) [ ON ] Description Allows the DXF export application to ignore all BLOCK rules in the configuration data-set. used to speed up processing of non-blocked DXF export.5.0 .mac.5 7. 7:14 12. This definition can be redefined in AutoCAD to provide the linestyle required.0) the DXF File [ 1. colours and fonts between DRAFT and DGN. OFF ScaleFactor Positive Real Scale Factor applied to entire DXF File to No. The configuration dataset controls how the database information is to be mapped into DGN format.3 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. User-defined line styles (see Line Styles) are assigned to a fixed (dashed) linetype definition in the DXF or DWG file using the DRAFT line pattern name as the AutoCAD linetype name. Allows database attribute information to be exported from DRAFT as DGN Group attributes. DGN is a binary format. as supplied with the product. Differentially scaled symbols are not supported.4. Rules for Groups and Levels use PML expressions. similar to those used in Representation rules. Group rules and Level rules. and should be quoted. usable at Sheet level. but are shown as mixed case here to aid legibility. This keyword may also take the values ‘DGN7’. The DGN export application can be executed using the LIEXEC command (which also loads the application if it has not already been loaded). 'ON 32' Level 32 to be used for NOTE elements Switch names are case-independent. GROUP rules may be followed by the INCLUDE argument to tag the group with attribute data. Part 1. For example: DLICON /myconfig configuration_options EXIT A DRAFT Configuration Dataset is made up of a series of Switches. The configuration_options will contain the GROUP. by building up the required mappings using the DRAFT applicationware. This will create a DGN file with a name and format defined in the specified dataset for the current Sheet element. The following example command uses the configuration dataset ’MyConfigData’ to control the export of DGN information: LIEXEC /Draft_DGN_LI ’DGNOUT’ ConfigData ’MyConfigData’ Here ’DGNOUT’ is an application feature. the configuration dataset must have been defined in DRAFT. which will be tagged with its name LEVEL ALL NOTE. Note: For full details of using expressions in PDMS. Switch values are text strings. Defines a named set of configuration options.dgn' Specifies the DGN header file name GROUP ALL EQUI. LEVEL and SWITCH syntax that controls the content of the DGN file produced. ‘DGN8’. Example: SWITCH LevelDefault '63' Level 63 to be used by default SWITCH SeedFileName 'seed. LEVEL rules should be followed by a text string defining the level or range of levels to be used. and is used to indicate the version of Microstation for the exported file. Before giving the above command.DRAFT User Guide Plotting and Drawing Output The configurable DGN facility uses ‘loadable image’ (LI) applications. or by reading in a predefined macro file. Other commands related to this facility are: LILIST DLICON name Lists features of application(s) loaded by LILOAD/LIEXEC. 7:15 12. This may be done either by typing in the configuration data at the command line.0 . see the AVEVA DESIGN Reference Manual. INCLUDE NAME A group will be created for each equipment. in which case the default values of all the switches will be assumed. Note that the grouping and levelling commands for Design graphics in this file are only intended as an example. The supplied configuration files include:) dra-dgn-basic.DRAFT User Guide Plotting and Drawing Output The configuration options may be overridden by LIEXEC command line options. and no grouping or levelling will take place. In particular. in imperial-units dra-dgn-imperial. Further configuration files can be created using the DRAFT applicationware.dgn' It is also possible to omit the CONFIGDATA. Defines an equivalent set to dra-dgn-pdms.pmldat.pmldat Defines a restricted range of essential settings for configured DGN output Defines a sample set of configuration settings to produce fully-grouped and levelled DGN files closely mapped to the DRAFT Sheet exported. the internal default seed will be used. Example: LIEXEC /Draft_DGN_LI 'DGNOUT' CONFIGDATA 'MyConfigData' OutputFileName '%PDMSUSER%/new. to query whether the configuration contains a level rule which applies to /PUMP1:1 DLICON /myconfig CHECK LEVEL /PUMP1 • Sample Configuration Datasets Sample configuration files are provided in the %PDMSDFLTS% directory as PML data files (pmldat). and may require modification to suit your own requirements.pmldat dra-dgn-pdms. The datasets currently defined within DRAFT can be determined by: DLICON LIST The definition of a specific dataset can be determined by: DLICON name DUMP The value of a specific switch within a dataset can be determined by: DLICON name CHECK SWITCH switchname For example. to query the value of the UNITS switch in the configuration /myconfig: DLICON /myconfig CHECK SWITCH Units Whether there is a grouping or levelling rule applicable to a specified DESIGN or DRAFT element can be determined by: DLICON name CHECK GROUP element_identifier DLICON name CHECK LEVEL element_identifier For example. the OutputFileName switch would normally be overridden by an LIEXEC option.0 .pmldat 7:16 12. pmldat Defines a sample set of configuration settings that uses levelling by pen number. The macro file %PDMSUSER%/name.pmldat’ !dgn. The following rules apply: • • • • • The left-hand list must not be empty.pmldat Note: These configuration files may be converted to command-line macro files for batch creation of DGN files.5. Multiple elements are separated by a + character. These mappings are all handled in the same way. 7. DRAFT colour numbers may be mapped to MicroStation colour numbers. A right-hand list of integers can include the characters 'R' (repeat) or 'D integer' (default). using the Plant applicationware as follows: !dgn = object dgnout() !dgn. each element in the left list is mapped to the corresponding element in the right list. each element of the right-hand list is used in turn once only. Each mapping consists of one or more sub-mappings. and DRAFT line styles may be mapped to MicroStation numbered or customised line-styles.0 . For example. and uses text size to select levels for annotation (metric units) Defines a sample set of configuration settings that uses levelling by functional descriptions (imperial units dra-dgn-dddd.mac is created when the PML data file is saved. 7:17 12. If the right-hand list has the same number of elements as the left-hand list. then the default value is used for all further mappings as necessary. all values in the left-hand list are mapped to the same value.load( !!file( ‘%PDMSDFLTS%/name.pmldat’ where name is one of the supplied configuration datasets. Each submapping has a left-hand (DRAFT) list and a right-hand (MicroStation) list separated by a colon. Each list can include elements that are numbers (non-negative integers or reals) or strings (quoted or unquoted). Integers may be separated by a '-' character to represent an inclusive range. separated by commas.2 • Common Features of Option Switches General Mappings Several of the option switches map one set of values (DRAFT) to another (MicroStation).save( !!file( ‘%PDMSUSER%/name.DRAFT User Guide Plotting and Drawing Output dra-dgn-nnnn. 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. If the right-hand list contains integers with an 'R' option. If the right-hand list has a single element. DASHED:pdmsDashed. DDOTTED:pdmsDdotted. For example. etc.3 File-Related and Miscellaneous Options Several switches in this section represent pathnames. 23:3. you must use an extra set of quotes to prevent the name being treated simply as {dash. 24:6. In order to map to this MicroStation custom line-style. 7. medium}'.) • Quoted Strings Strings within mappings may be quoted.12-20:33-41' '1-20:26-30R' '20-29:1-3D6' (maps 1:26.. 25:6. They cannot be used in the LIEXEC command syntax. for example: 7:18 12.) (maps 20:1. and inner ones to tell Draft_DGN_LI where each line-style name ends. For example.5. long }'| could be split over the following switch setting SWITCH SWITCH SWITCH SWITCH MapLineStyle MapLineStyleA MapLineStyleB MapLineStyleC |CHAINED:pdmsChained| |DDOTTED:pdmsDdotted| |DASHED:'{ dash. medium}. 21:2.g. some MicroStation custom line-styles have names that include a comma or colon. long }'| Note: Continuation switches can be used in DLICON configuration syntax. colon or plus character. the following long switch setting (all one line): SWITCH MapLineStyle |CHAINED:pdmsChained. long}'| A string must be quoted if any of the following apply: • • • • It contains a comma. switches may be continued. It starts with a minus. • Continuing Long Mappings Some mappings may require string lengths longer than the permitted maximum (about 100 characters). These can include standard PDMS environment variable settings.0 . with ' or | characters. such as {dash.DRAFT User Guide Plotting and Drawing Output Example: 'CHAINED:pdmsChained. It starts with a digit but is not a number (e. medium }'. 7:27. You need outer quotes to tell DRAFT where the option string ends. These must be used in alphabetic order.LDASHED:' (dash. if necessary. 2:27. 345P). 6:26. It starts or ends with a space or tab. single quote or vertical bar. DDOTTED: pdmsDdotted' '1-11:15. 4:29. Continuation switches have the same name as the base switch. but extended by a single letter between A and Z. To achieve this.LDASHED:'{ dash. DASHED:'{ dash. 3:28. medium }'| |LDASHED:'{ dash. 5:30. thus: SWITCH MapLineStyle |DASHED:'{dash. etc. If no seed file name is provided.dgn' A file name can include internal spaces without problems. In this case.dgn' The use of a seed file is optional. The most common scenarios will be: • The working units are set up in the seed file. The Units switch may be used to override the settings in the seed file. For example. the Units switch should be: SWITCH Units 'MASTMM:25. ratio per master unit SU Ratio per sub-unit PU These keywords are not case-sensitive. and must not contain any inconsistent element data. A sample seedfile pdmsSeed2d.dgn|' • OutputFileName Specifies the output DGN file name produced when exporting DGN file information. but there is no universal set of descriptions in use. for example: SWITCH SeedFileName 'C:\Program Files\MicroStation\from PDMS. size in millimetres MASTMM Description SUBNAME. Sub-Units and Positional Units (or Units of Resolution).4' 7:19 12.0 . The seed file contains the size ratios of these three units. and may contain descriptions (max. but spaces at the start or end of the file name require additional quotes. Note: In configurations that use the supplied seedfile. Any tag-set definitions in the seed must not conflict with those created by Draft_DGN_LI. two characters) of the master and sub-units. For example: SWITCH OutputFileName '%PDMSUSER%\DGN_file_name.dgn' • SeedFileName Specifies the DGN seed file name to be used to create the output DGN file.dgn is supplied with Draft_DGN_LI. with master units inches. but the values of MASTNAME and SUBNAME are case-sensitive.DRAFT User Guide Plotting and Drawing Output SWITCH SeedFileName '%PDMSEXE%\dgndata\pdmsSeed2d. the MapColour switch should be set to ‘1-256:0-255’ • Units MicroStation uses three levels of working units: Master Units. with an imperial seed file. The seed file must be a valid MicroStation 2D seed file. the Units switch just contains the size of a master unit in mm. This contains a colour table that maps the default PDMS colours 1-16 into Microstation colours. and must contain the size of a master unit in millimetres (MASTMM): Master Units Sub-Units Positional Units Description MASTNAME. an internal default seed will be used. For example: SWITCH SeedFileName '%PDMSEXE%\dgndata\pdmsSeed2d.dgn' SWITCH SeedFileName '| seed with leading spaces.dgn' SWITCH SeedFileName 'mySeedFile. with one sub-unit per master unit. • ShiftY A vertical shift is applied to everything written to the DGN file to position the drawing at any required place on the Design Plane. The default value is 1. you must set up the working units in the seed file.PU:100. any Backing Layer of the DRAFT drawing is not transferred to the DGN file.SUBNAME:". the Units switch should be: SWITCH Units 'MASTNAME:mm.DRAFT User Guide Plotting and Drawing Output • The working units in the configuration override those in the seed file: all Units options are needed.0.MAS TMM:1. Only the first two characters of these values are significant.SUBNAME:mm. but can include characters such as " (inches) and ' (feet). any Overlays on the DRAFT drawing are not transferred to the DGN file.PU:1270.0 . and the default value is 0. and the default value is 0. MASTMM:304.0' The MASTNAME and SUBNAME values cannot be quoted strings.SU:12. and metres accurate to 0.0. (the default is Off).SU:1.0. (the default is Off).) For example. and 1270 positional units per sub-unit. The shift is measured in MicroStation Master Units. the sheet frame on the DRAFT drawing is not transferred to the DGN file. to set both the master and sub-unit names to millimetres. • ExcludeOlay If this switch is set to On. (A minor exception is that if the MASTNAME setting is recognised as a common value.0' • ScaleFactor A Scale Factor is applied to the entire DGN file to enable full-scale Design units to be output in the DGN file. (If you wish to use a space or comma in MASTNAME and SUBNAME values. The shift is measured in MicroStation Master Units. • ShiftX A horizontal shift is applied to everything written to the DGN file to position the drawing at any required place on the Design Plane.8| SWITCH Units 'MASTNAME:m. 7:20 12. MASTMM may be omitted.01mm: SWITCH Units |MASTNAME:'. MASTMM:1000. • ExcludeSheetFrame If this switch is set to On.SUBNAME:mm. as in the first scenario.SU:1000. respectively for Master units in feet accurate to 1/ 64th inch. and it is not possible to include a space or comma in them. • ExcludeBack If this switch is set to On (the default is Off).) Some more examples of Units settings.PU:64. MicroStation documentation recommends using named styles. • • Any ScaleFactor (see ScaleFactor) is applied to custom line-styles used in the DGN file. (the default is Off).3:5. Any unmapped line-styles map to Solid lines. • ExcludeArrowFill If this switch is set to On. The following example maps DRAFT’s named line-styles to their nearest equivalents in MicroStation’s numbered styles. For example. Note: More than one of these switches to Exclude Fill may apply to the same entity. This may be useful for good performance in MicroStation. either ExcludeSolidFill or ExcludeArrowFill could be used to exclude the fill for dimensionline arrowheads. since hatching is transferred as a set of lines. LDASHED:3. ExcludeArrowFill is more specific.DDOTTED:6' 7:21 12.5.rsc supplied with PDMS contains custom line-styles equivalent to the default named PDMS line-patterns. (the default is Off).CHAINED:4. any solid fill for terminators on dimension-lines and label leader-lines is omitted from the transfer to the DGN file. However. (the default is Off).4-11:31' SWITCH MapLineWeights '1-11:0-10' The second example is the default. DRAFT also uses a mixture of named and numbered line-patterns. ignoring line picture and glyphs. • MapLineStyle MicroStation has seven numbered line-styles. Other solid fill and hatching is transferred. The MapLineStyle option maps the DRAFT line-pattern to a MicroStation line-style.2:1.) A resource file pdms_lsty. and can also have named custom line-styles. If any of these switches is true. but some drawing standards specify numbered ones. then the entity will be excluded. The links between them are controlled by the MapLineWeights option.DOTTED:1. However. This is the default: SWITCH MapLineStyle 'SOLID:0. • ExcludeSolidFill If this switch is set to On.4 • Line/Colour Related Options MapLineWeights MicroStation has 32 line-weights (numbered 0-31).0 . DRAFT has 11 line thicknesses (numbered 1-11). no hatching (including solid fill) in the DRAFT drawing is transferred to the DGN file. (See MapLineStyleByPen for how to map line-styles involving line pictures or glyphs. other Hatching is still transferred. for example: SWITCH MapLineWeights '1:0.DASHED:2. all solid fill is ignored and not transferred to the DGN file.DRAFT User Guide Plotting and Drawing Output • ExcludeFill If this switch is set to On. 7. DASHED:pdmsDashed .6:15.2:51.0 . For this you could use the switch setting: SWITCH MapLineStyleByPen '217:Pneumatic.15:25416:37' The second example gives a fairly close fit in MicroStation to the DRAFT colours used if no seed-file is specified.9:51. (Note that this is the pen number as stored in the database.TCHAINED:pdmsTChained' Custom line-style names can include spaces and punctuation. As this mapping can get long.5:3.3:22.9:33. you may need to use the continuation facilities described in Continuing Long Mappings. As this mapping can get long. 10:0.SOLID:0. line picture. which is not the same as the pen number in the DRAFT Administrator User Defined Pen Settings form.12:13.14:197. This is the default mapping.DRAFT User Guide Plotting and Drawing Output The next example maps DRAFT named line-styles to some custom line-styles provided as a MicroStation resource file: SWITCH MapLineStyle'CHAINED:pdmsChained.2:1. you may need to use the continuation facilities described in Continuing Long Mappings.7:49.15:254' SWITCH MapColour '1:96. 8:64. To map these combinations onto MicroStation line-styles. • MapColour Both DRAFT and MicroStation use colour numbers.13:63.5:50.6:4. for example.11:96.3:6.DOTTED:pdmsDotted.7:5. the default MicroStation/J installation includes styles { -E. (the preceding example is a single line mapping). See Quoted Strings for details of when you must quote the style-names. For example: SWITCH MapColour '1:11.8:37.4:2. you must map them by Pen Number. line thickness and glyph. you might have DRAFT pen numbers 217 and 222 set up as: setpen 217 colour 4 solid lthick 2 lpic 4 glyph 1 lpicture 22 mode 3 size 2 repeat 12 gap 4 setpen 222 colour 6 solid lthick 1 lpic 22 glyph 12 and wish to map these to the MicroStation custom line-styles Pneumatic and ‘Data link’ respectively.4:52. See Quoted Strings for details of when you must quote the style-names. The following mapping should be used with this seed-file: SWITCH MapColour ‘1-256:0-255’ 7:22 12. Any unmapped colours are mapped to MicroStation colour 0. and the mapping between them is controlled by the MapColour switch.dgn contains this mapping. The sample seed-file pdmsSeed2d. • MapLineStyleByPen More complex DRAFT line-styles can be set up by the combination of line-pattern.) For example.} and { Cable / Tele }.10:0.222:|Data link|' Custom line-style names can include spaces and punctuation. The interpretation of these colours by MicroStation depends on the colour-table loaded (this can be included in the seed file).LDASHED:pdmsDashed .DDOTTED:pdmsDdotted. the default MicroStation/J installation includes styles { -E.} and { Cable / Tele }. for example. 2 of a character height.dgn. This mapping should be used when the supplied seedfile is used. The following summarises the requirements: • The DRAFT fonts supplied with the AVEVA product (PDMS fonts) must be set up in MicroStation using a fonts resource file. may be set up using MicroStation. 41-46) and the special SYMBOL to MicroStation font numbers. 31-36. and the overall ScaleFactor switch setting (see ScaleFactor). The contents of this file are project-specific. Such files fontnnn.21-23:6. 3 and 30 as equivalent to 31.8 horizontally and a factor of 1. it is necessary to set up an environment variable %OPENDGN_FONT_DIR% which points to this directory. the scale of the relevant DRAFT pen. 7:23 12. 4 and 40 as equivalent to 41.2' This scales the font by a factor of 0. For example: SWITCH MapFont '11-16:133.0. • MarkerSize This option sets the size of a DRAFT marker in millimetres (at scale 1).8h1. The default is 1.5.44-46:181. Any unmapped colours are mapped to MicroStation colour 0.2u0.DRAFT User Guide Plotting and Drawing Output The default mapping is 1-256:0-255.25) Adjustments for a MicroStation native font (default). 21-26. for example: SWITCH MapFont '11-16:133w0. • • MapFont This option maps from DRAFT's font numbers (11-16.25h1.5 Font Related Options In addition to the font switches below. DRAFT font numbers 1 and 10 are treated as equivalent to 11. The control codes include: w h u r s l p m Width Factor Height Factor Offset Up Offset Right Slope (in degrees) Underline separation Adjustments for a PDMS font (this includes scaling of w1.0 . 7.2 vertically. The size of a marker in the DGN file will be the product of this size. In order to use these files. it is also necessary to use font geometry files during the transfer to the DGN file. where nnn is the Microstation font number. 2 and 20 as equivalent to 21. This is covered more fully in Guidelines for Importing DGN Files from DRAFT into MicroStation.41-43:173. A pdmsSamFont. and shifts it up by 0.31-33:172. 34-36:177. In order for the geometric data required to be exported to MicroStation.SYMBOL:186' It is possible to modify the MicroStation font size and position by fractions of the original size.rsc file is provided. These files are provided in the dgndata directory below %PDMSEXE%.24-26:134. based on the fonts used in the SAM project supplied with AVEVA Plant/Marine. further work is required to import DRAFT text correctly into MicroStation. 24-26:134p.34-36:205p. the following font mapping should be used: SWITCH MapFont ‘11-16:201p.44-46:207p. the bold font is mapped to a MicroStation native font.41-43:206p. Each DGN graphical element is on one and only one level.34-36:177p. which is not the same as the pen number in the DRAFT Administrator User Defined Pen Settings form. 31-33:172p.0 . • LevelDefault This switch sets the default level: i.5.SYMBOL:186p’ This font mapping maps PDMS fonts with a best fit for adjustment factors.21-23:6p.6 Level-Related Options MicroStation/J supports a maximum of 63 levels (numbered 1-63). the level that will be used if no other switches or rules apply. The default value is 1. Example: SWITCH LevelDefault '63' • LevelPen This switch can set a mapping to DGN levels associated with DRAFT pen numbers.41-43:173p. This allows fine control of which levels are used for which parts of the DRAFT drawing. For PDMS Font family 1.24-26:203p. The SYMBOL font is included in the MicroStation resource file pdmsSamFont. When using the supplied resource file.SYMBOL:105' 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.44-46:181p.) Example: SWITCH LevelPen '10-20:30-40. (Note that this is the pen-number as stored in the database.21-23:202p. MicroStation also offers names for levels.rsc supplied with AVEVA Plant/Marine. The default is: SWITCH MapFont '11-46:105.100-200:63' 7:24 12.DRAFT User Guide Plotting and Drawing Output Example: SWITCH MapFont ‘11-13:133p.14-16:105m. 31-33:204p. 7. but Draft_DGN_LI always refers to levels by number.SYMBOL:255p’ • FontSlopes This option controls whether DRAFT font slopes are translated into MicroStation text slants (default On) or are ignored (Off).e. 'ON 36' LEVEL LEVEL LEVEL LEVEL LEVEL LEVEL LEVEL ALL BRAN ALL EQUI ( /C1101 ALL LAYE ALL LAYE ALL LAYE ALL LAYE WITH ( HBOR GE 100 OR TBOR GE 100 ) . HVAC. 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. Example: LEVEL ALL STRU. 'ON 55' WITH ( PURP EQ 'ADCA' ) . then no other level switches or rules will apply to items within the backing sheet. 7:25 12. SBFR. Any other pens have no specific levels. a later rule will not affect it. Using the order specified in the above examples. up to pen 20 onto level 40. GRDM. 'ON 22' WITH ( PURP EQ 'MATB' ) . ZONE. therefore. BOUN. REST. if a rule has already been applied for a given element. VNOT. GLAB. 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). pen 11 onto level 31 and so on. PDIM and RDIM. • Level Rules Standard selection syntax is used to define Level Rules. PTRA. DRAFT pens 100 to 200 are put onto level 63. DRAFT elements which can have level rules include: LAYE. These specify how design elements are to be organised onto DGN Levels. OLAY. DRAWI (when owned by a SITE or ZONE) and all Piping Components.0 . Design elements which can have level rules include: SITE. BRAN. a LAYE with PURP ‘ADCA’ will be placed on level 21 not on level 24. • LevelBack This switch can set the level number for the backing sheet and everything contained within it. ADIM. SLAB. LDIM. which are allocated as required. Example: SWITCH LevelBack '63' This uses level 63 for the backing sheet and everything within it. SUBS. a DRAFT Sheet may have several overlays. FRMW. STRU. The default is Off. NOTE. These rules can operate with a level pool. If this option is switched On. 'ON 21' WITH ( PURP EQ 'ADEA' ) . 'ON 44' ) . 'ON 40' WITH :purpose EQ HVAC. This consists of one or more levels. PIPE. For example. EQUI. 'ON 23' . SUBE. 'ON 24' Rules are applied in order. Note that levels set by LevelBack (see LevelBack) or Level Rules (see Level Rules) take priority over this switch.DRAFT User Guide Plotting and Drawing Output This puts lines and text drawn with pen 10 onto level 30. and the default level is used. REST. 6. to use levels 3. into the group. and then put any other sites on level 9.'POOL 6-10' Note: Only the first rule that matches an element is ever considered. For example: GROUP ALL STRU.7 Group Related Options MicroStation groups are also known as anonymous or orphan cells. and 'D integer' to specify a default value when the pool is exhausted (see General Mappings). EQUI. meaning repeat the pool if necessary. Any tags associated with the group will be associated with the first group created. that group will be closed and a new group opened (a message will be written to the log-file. 7. then put any other sites on levels specified by whatever other switches apply. If a group reaches this limit. not the contents of the frame. INCLUDE NAME GROUP ALL BRAN WITH ( HBOR GE 100 ) . They have a limited capacity. do not use either a ‘D’ or an ‘R.'POOL 3. If it is switched On.0 .5. they will be attached to the groups as MicroStation tags. STRU. 5. BRAN. If element attributes are included in group definitions. FRMW. This option puts the line representing the frame itself. SUBS. • GroupSymb The default for this switch is Off. ZONE. if any. 7:26 12. If it is switched On. Note: The groups produced are never nested. PIPE. INCLUDE NAME SPREF Design elements which can have group rules include: SITE. separated by commas. a single group is created for each DRAFT hatch/fill pattern if no other group is active. HVAC. These specify how design elements are to be organised into MicroStation groups. PTRA. SBFR. • Group Rules Standard selection syntax is used to define Group Rules.5-7D9' To use levels 6-10 for all sites. DRAWI (when owned by a SITE or ZONE) and all Piping Components. thus: LEVEL ALL SITE . If it is switched On. reusing them in turn as necessary. • GroupFill The default for this switch is Off. specify the switch setting: LEVEL ALL SITE . and 7 for the first four sites. • GroupFrame The default for this switch is Off. a single group is created for each instanced DRAFT symbol if no other group is active. with the optional characters ‘R’. BOUN. GRDM. each time this occurs). SUBE. specify: LEVEL ALL SITE .DRAFT User Guide Plotting and Drawing Output A level pool consists of one or more integers or integer ranges.'POOL 6-10R ' To use levels 6-10 for the first four sites. For example. a single group is created for each DRAFT view frame if no other group is active. 5.txt' 7. The Validate feature checks the syntax of all switches in a supplied configuration. The default value is ‘%PDMSUSER%\Draft_DGN_LI_log. Example: SWITCH LogFileName '%PDMSUSER%\example27.txt’. Example: LIEXEC /Draft_DGN_LI 'VALIDATE' CHECKLEVELRULE 'POOL 3. CheckLevelRule and CheckGroupRule. Example: LIEXEC /Draft_DGN_LI 'VALIDATE' MapColour 1-256:0-255' It also has extra switches. ADIM. PDIM and RDIM. Example: GROUP ALL GLAB LEVEL ALL GLAB. GLAB. which check that values are valid as the text string for a Level or Group rule.8-10R' LIEXEC /Draft_DGN_LI 'VALIDATE' CHECKGROUPRULE 'INCLUDE NAME' It is expected that the Validate feature will be used mainly by applicationware and macro writers. Group rules specify that one group will be created for each occurrence of an element that fits a given rule.5.8 • Product Support Options LogFileName This switch sets the name used for the log file. The order of the rules is therefore important.9 Validation feature and options It is important to be able to syntax-check switches and rules. ‘ON 25’ places each GLAB in a separate group places the group for each GLAB on Level 25 7. VNOT. respectively. SLAB.DRAFT User Guide Plotting and Drawing Output DRAFT elements which can have group rules include: LAYE. which fit a given rule.0 .5. LDIM. Level rules specify that all elements. Only the first Group rule that matches an element is ever considered. Note: Elements may be both grouped and levelled. NOTE. 7:27 12. OLAY. will be placed on the same level or range of levels. DRAFT Overlays transferred to DGN file. Suppresses transfer to the DGN file of Solid fill Solid fill transferred to DGN file.5. Suppresses transfer of DRAFT Backing Layer to DGN file.0 .0] On [Off] Scaling factor applied to entire DGN file. Vertical shift in Master Units applied to the entire DGN file.0] [0. Suppresses transfer of DRAFT Overlays to DGN file. Suppresses transfer of DRAFT Sheet Frame to DGN file. MicroStation has 32 line weights (0-31). DRAFT Sheet Frames transferred to DGN file.10 Summary of Switches and Rules to Control DGN Export Option name OutPutFileName SeedFileName Units Value [default] [‘output. Ratios of Master Units to Sub-Units and of Units of Resolution (Positional Units) to Sub-Units.DRAFT User Guide Plotting and Drawing Output 7. ExcludeOlay On [Off] ExcludeSheetFrame On [Off] ExcludeFill On [Off] ExcludeSolidFill On [Off] ExcludeArrowFill On [Off] MapLineWeights [1-11:0-10] 7:28 12. DRAFT has 11 line weights (1-11). Pathname for seed file used to create DGN export file. Can also specify descriptions (max. Suppresses transfer to the DGN file of fill for Dimension-line and Leader-line terminators Fill for Terminators transferred to DGN file.dgn’] [internal default seed file] Description Pathname for DGN export file. Horizontal shift in Master Units applied to the entire DGN file. DRAFT Backing Layer transferred to DGN file. ScaleFactor ShiftX ShiftY ExcludeBack [1. Suppresses transfer of Hatching (including solid fill) to the DGN file Hatching and solid fill transferred to DGN file. two characters) for Master Units and Sub-Units.0] [0. ExcludeOlay On [Off] ExcludeSheetFrame On [Off] ExcludeFill On [Off] ExcludeSolidFill On [Off] ExcludeArrowFill On [Off] MapLineWeights [1-11:0-10] 7:29 12. Suppresses transfer to the DGN file of Solid fill Solid fill transferred to DGN file. DRAFT has 11 line weights (1-11). Suppresses transfer of DRAFT Backing Layer to DGN file. Suppresses transfer to the DGN file of fill for Dimension-line and Leader-line terminators Fill for Terminators transferred to DGN file. DRAFT Overlays transferred to DGN file. DRAFT Backing Layer transferred to DGN file. Suppresses transfer of DRAFT Sheet Frame to DGN file.0 .DRAFT User Guide Plotting and Drawing Output ShiftY ExcludeBack [0. DRAFT Sheet Frames transferred to DGN file. Suppresses transfer of DRAFT Overlays to DGN file. Suppresses transfer of Hatching (including solid fill) to the DGN file Hatching and solid fill transferred to DGN file. MicroStation has 32 line weights (0-31).0] On [Off] Vertical shift in Master Units applied to the entire DGN file. Map items associated with specific DRAFT pen numbers to MicroStation levels. GroupFill On [Off] GroupFrame On [Off] Group Rules LogFile On [Off] Creates log file to record error messages generated during creation of DGN file. 31-36.0 . but not frame content. (Group will contain frame line. 41-46. SYMBOL) to MicroStation font numbers. Sets MicroStation level to be used for backing sheet (and items within it).) Does not automatically create group for DRAFT view frame. A set of rules that assign specified PDMS element types to MicroStation levels. A set of rules that assign specified element types to MicroStation groups. SYMBOL:105] [On] Off Description Maps DRAFT font numbers (11-16. Does not automatically create group for DRAFT symbols. Creates single MicroStation group for each DRAFT hatch/fill pattern if no other group is active. Ignores DRAFT font slopes. log. Creates single MicroStation group for each DRAFT view frame if no other group is active. slopes to FontSlopes LevelDefault [1] LevelPen LevelBack Level Rules GroupSymb On [Off] Creates single MicroStation group for each DRAFT symbol if no other group is active. Can use R (repeat) and D (default) syntax to set up level pools.txt] 7:30 12. Log file is not created. Any attributes included in group definitions will be attached to groups as MicroStation tags.DRAFT User Guide Plotting and Drawing Output Option name MapFont Value [default] [11-46:105. Translates DRAFT font MicroStation text slants. LogFileName [%PDMSUSER%\ Pathname for log file (if LogFile is set to DRAFT_DGN_LI_ On). Does not automatically create group for DRAFT hatch/fill patterns. 21-26. Sets default level to be used by MicroStation if no other switches or rules apply. A configuration can be defined which allows DRAFT DGN files to be imported into a freshly installed version of MicroStation/J with correct geometry. in-house and the user community. These notes refer only to MicroStation/J and the DGN files produced from DRAFT. Hatching (fill) is exported as a set of poly-lines. Differentially scaled symbols are not supported.5. it is possible to specify a MicroStation custom line-style for a given DRAFT pen number. However. Individual projects may have different fonts in use. and how to improve other aspects of the translation. Experienced MicroStation users may know alternative ways of doing this.2 Exporting DRAFT Drawings Containing PDMS Fonts The AVEVA product is issued with a very large number of font files (AVEVA fonts) that have been assembled over a long period from the public domain. It is not possible to install a 16 bit font (.shp) and compiled (. and accept some differences in text output.SHX) file into Microstation/J or earlier. 7:31 12. Various switches and rules are available in DRAFT to allow the DGN output to be configured as required. These notes discuss how to install these fonts into MicroStation in line with the original DRAFT drawing. so will require a different font resource file. the fonts are not likely to be correct. These notes contain guidelines on how to produce DGN drawings from DRAFT with the correct fonts.6 7.0 . The supplied font resource file pdmsSamFont. However.6. However. colours and styles.shx) files. The set of PDMS fonts required in MicroStation is project dependent. 7. If you use DRAFT’s alternative character set for characters such as ¥ © ¼ or Ω you will need to install AVEVA’s symbol font.shp versions of the fonts you wish to use in MicroStation Use MicroStation standard fonts similar to the PDMS fonts.DRAFT User Guide Plotting and Drawing Output 7. See Creating a New Font Resource Library for instructions on how to create such resource files.rsc uses the PDMS fonts associated with the SAM project. User-defined glyphs and line pictures are ignored. Two alternative approaches are: • • Use AVEVA’s Fontconverter utilities to create PDMS-compatible versions from .11 Limitations The following limitations apply: • • • • • • DRAFT's intelligent blanking primitives are not exported to the DGN file. they may be grouped.1 Guidelines for Importing DGN Files from DRAFT into MicroStation Introduction DRAFT drawings can be passed into MicroStation as DGN files. Dimensions are not exported as MicroStation dimensions. 7.6. They have all been translated to the AutoCAD standard and take the form of pairs of source (. Multi-byte fonts are not supported with MicroStation/J. When you install additional fonts into MicroStation.dgn (where NNN is a MicroStation font number referred to in the font resources file). This variable OPENDGN_FONT_DIR should be set to %PDMSEXE%\dgndata or wherever the font geometry files have been installed. font numbers may be modified (see Changing MicroStation Font Numbers. These are mapped to DRAFT fonts using the MapFont switch in DRAFT. If this happens. DRAFT needs additional information on the font geometry to export the drawing. These fontNNN. It is possible that these font numbers may clash with fonts in other font resource files in use.)... they may be checked using the element/text menu. typically in . If necessary. The font installation should follow the step-by-step procedure: 7:32 12. fontNNN. Mapping the Installed Fonts discusses how PDMS font numbers are mapped onto font file names. All PDMS fonts are supplied in the %PDMSEXE%\autodraftfonts directory..shx files.0 . 7.shx files as part of AutoDRAFT. Select the Required .dgn files for other fonts.. \bentley\workspace\system\symb MicroStation refers to fonts by a number not by the name. \bentley\workspace\system\symb pdmsSamFont. This is supplied as a set of font geometry files. in AutoCAD format as . Font geometry files are supplied for the fonts used in the SAM project.3 Installing PDMS Fonts into MicroStation To keep them separate the required fonts should be installed into a new font resource library called. see section Changing MicroStation Font Numbers for instructions on how to modify MicroStation font numbers.rsc and are supplied in the directory PDMSEXE%\dgndata.DRAFT User Guide Plotting and Drawing Output Font resource files should be installed alongside the corresponding MicroStation font resource files. or a directory accessed by the environment variable OPENDGN_FONT_DIR.dgn files must be in either the current directory.rsc uses particular MicroStation font numbers (201 to 207 for text fonts and 255 for the symbol font). These are supplied in the directory %PDMSEXE%\autodraftfonts (or another location). Once fonts have been installed. PDMS fonts are supplied as AutoCAD . for example. myfont.rsc. These correspond to pdmsSamFont. which should be placed with the supplied font resource libraries.rsc Library contains instructions as to how to create further fontNNN.6. typically in the directory: . The newly installed fonts should be visible together with the font numbers assigned by MicroStation to the new fonts. select the required source files. Button: Button: Copy Done • Checking the Installation Menu: Element>Text • • Use drop down or View to locate the font name The font number assigned by MicroStation is also visible Select to use for text 7:33 12. \bentley\workspace\system\symb) Select the required font resource library (.shx file area Select the required .shx • • Navigate to a AutoCAD . myfont.rsc • Selecting .. Font details should appear.e.0 .shx Files to Add to Resource Library Menu: Button: Open (Leftmost window) Set Type to .DRAFT User Guide Plotting and Drawing Output • Creating a New Font Resource Library (This step may be skipped if using an existing resource library) Menu: Button: Utilities>Install Fonts New (Rightmost window) • • Button: OK Navigate to the default font library area Enter required library file name .shx files Button: Button: Add Done • Selecting the Library Destination Button: Open (Rightmost window) • • Navigate to default font library area (typically .rsc file) Button: OK • Copying the Fonts into the Library In the leftmost window..g. dgn files are repeated here. We recommended that these fonts are placed in %PDMSEXE%\dgndata. Open this file in MicroStation and type 'mdl load fixrange' (Use Keyin option). These files contain a set of instructions and various other text data. The new name must start with 'font' appended with the font number. This involves using the MicroStation EDG utility to change the font used.0 . (The EDG utility is installed alongside MicroStation. (e. If you need different font resource libraries for different projects we suggest that you create subdirectories and point OPENDGN_FONT_DIR to the appropriate one for the project.DRAFT User Guide Plotting and Drawing Output • Changing MicroStation Font Numbers Menu: Button: Utilities>Install Fonts Open (rightmost window) • Navigate to the default font library area • Select the Required .dgn must then be created to match the font numbers in the resource file.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. since the data in these files is required for DRAFT DGN output to work correctly. font186. One of these files is required for each font used.exe. 7:34 12. In order to create a font geometry file for a new font. (Use Compress on File menu) Place the file in a directory where it can be found by the OpenDGN kernel (which is used by DRAFT DGN output). for example in …\Bentley\Program\Edg\edg. These files should not be modified other than as described below. open an existing font geometry file (a set of these is supplied in %PDMSEXE%\dgndata) and follow the instructions displayed there.g.rsc Library Button: OK • • • Select the font name in the rightmost window Font details appear The font number and the description may be edited here. Font geometry files fontNNN. Compress and close the design 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. The MicroStation font number NNN is included in the name of these files. To create an external font do the following: • • • • • • Make sure you have made a copy of this design file.) The instructions in the fontNNN. Either this is either the current directory or a directory accessed by means of an environment variable called 'OPENDGN_FONT_DIR'. 4 Mapping the Installed Fonts PDMS fonts normally need the DRAFT export to use a font adjustment factor of 1. e.6. but is briefly summarised here. All font-files have an 8-character equivalent short name: Name Latin-1 Latin-2 UK Latin-Cyrillic US Greek Cyrillic SYMBOL IR Number 1 2 4 5 6 7 8 - Encoding (marrr) 01001 01002 01004 09998 Short code L1 L2 LB CL 08901 (or 01006) 81 (or LA) 02018 03537 09999 GG CR OP Name Line Block Serif Italic Script Typewriter Uniform width PDMS Style number 1 2 3 4 5 6 7 Font type (tswuu) 11901 Outline 11203 21191 22191 31191 21902 16901 Bold Font type (tswuu) Filled 11203 21291 22291 31291 - 7:35 12. This is described fully in AVEVA’s fontbuilding utilities. This may be achieved by using the code p when mapping the fonts. ts is the type and sub-type. see Configurable DGN Output. and a special adjustment when aligning text to the top of the body. Font file names are of the form marrrtswuu. where m=0. MAPFONT ‘11-16:201p’ For further details. PDMS font families are defined by their IR (International Registration) number and Style number in the system database.DRAFT User Guide Plotting and Drawing Output 7.0 . a is the alphabet. w is the weight.5 PDMS Font File Names PDMS font file names follow a naming convention. 7. or open (prefix of). PDMS fonts are exported to AutoCAD as either filled (prefix f).g.6.25. rrr is the encoding. and uu is a serial number. Thus IR number 6 Style number 1 is font of0890111901 (short name O8111901).dgn) 11-16 21-23 24-26 31-33 34-36 41-43 44-46 SYMBOL 201 202 203 204 205 206 207 255 O8111901.tbl.shx (shortname FOP11901). To determine the font families used in a AVEVA project.shx US Line UK Block (Outline) UK Block (Filled) UK Serif UK Serif (Bold) UK Hershey Complex Italic UK Hershey Triplex italic PDMS Symbols OLB21291. since these include US characters. \bentley\workspace\system\tables 7:36 12.shx of0100411203. bold version of 0100421291 (OLB21291). and also for the other named DRAFT colours. The following font files are used in the SAM project and are set up in pdmsSamFont. DRAFT uses a Symbol font for special characters (e.shx 7. PDMS uses the 8-bit Latin fonts (08901) instead of US fonts (01006). This may be installed in the MicroStation data directory alongside the Bentleysupplied colour tables.shx OLB21191.shx OLB22191.. font family 2 is a block font. For example.shx f0999911901. The AVEVA SYMBOL font is of0999911901.shx f0100411203. font family 3 contains two font files to set up fonts 31-33 (normal.shx Longname Description of0890111901.shx (shortname OOP11901).0 . Different projects will use different fonts.shx of0100421291. font family 1 is a line font. the following ADMIN command should be used: Q FONTFamily In typical AVEVA projects. typically at: .shx OLB22291.shx OLB11203. The fonts available in DRAFT are organised into four font families.shx FOP11901. forward and back-slant) and the equivalent bold font 34-36.DRAFT User Guide Plotting and Drawing Output Generally. In addition.6.shx of0100421191.g. font family 3 is a serif font and font family 4 an italic or typewriter font.. IR number 4 Style number 3 is of 0100421191 (short name OLB21191).6 Colours We supply a MicroStation colour table pdms_col. Each font family uses up to two font files to set up a range of six font numbers.rsc: Font numbers MicroStation Shortname in Project Font Number SAM (FontNNN. which contains colour definitions matching DRAFT’s default settings for Colours 1 to 16.shx of0100422191.shx of0100422291. ~D gives the degrees symbol). The equivalent filled font is f0999911901.shx FLB11203. 7.0 . attach this colour table to a seed file or design file and set a suitable colour mapping. \bentley\workspace\system\symb 7:37 12..6. if you wish to match DRAFT colours as closely as possible.. typically at: . if you wish. This may be installed in the MicroStation font directory alongside Bentley-supplied font resource files.DRAFT User Guide Plotting and Drawing Output You may.7 Line Styles AVEVA supplies a line style resource file containing definitions of MicroStation custom line styles matching the proportions of DRAFT’s named line patterns. 0 .DRAFT User Guide Plotting and Drawing Output 7:38 12. or to describe a hatching (fill) pattern.DRAFT User Guide Colours and Styles 8 8. Generally. except that there are no style attributes for text primitives – only colour attributes. The full list of colour and style attributes is given below: Attribute type Line Leader-line Label-frame Dimension-line Projection-line Cross-hair Note line Table-row Table-column Front-face Back-face Centre-line Obscured-line LLSTYLE LFSTYLE DLSTYLE PLSTYLE CHSTYLE NLSTYLE ROWSTYLE COLSTYLE FFSTYLE BFSTYLE CLSTYLE OBSTYLE LLCOLOUR LFCOLOUR DLCOLOUR PLCOLOUR CHCOLOUR NLCOLOUR ROWCOLOUR COLCOLOUR FFCOLOUR BFCOLOUR CLCOLOUR OBCOLOUR Style attribute Colour attribute 8:1 12. and can be classified as: • • • • 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) those for text primitives (three colour attributes only). or to describe the size and appearance of markers. The term style is used to describe the overall appearance of a line in terms of its thickness and repeating pattern. determined by the values of the relevant colour and style attributes.0 . there is a style attribute for every colour attribute.1 Colours and Styles Introduction Every graphics primitive in DRAFT is drawn in a specific colour and style. Within the DRAFT database there are 20 different colour attributes and 17 style attributes. In some circumstances linestyle attributes may be set to the special values: OFF. See System-Defined Fill Styles and User-Defined Fill Styles for further details of these. See Marker Styles for further details of these. In some circumstances fillstyle attributes may be set to the special values: OFF. UNCHANGED. DEFAULT.0 . User-defined line and fill styles are defined in the PADD database within a hierarchy headed by a STYLWL element (see DRAFT Database Hierarchy). beneath which the definitions of user-defined Linestyles and Fillstyles are stored. See the relevant sections of this User Guide for details of where these values are allowed. See System-Defined Line Styles and User-Defined Line Styles for further details of these. UNCHANGED. See the relevant sections of this User Guide for details of where these values are allowed. STYLWL. In some circumstances markerstyle attributes may be set to the special values: OFF. The creation and maintenance of STYLWL hierarchies is the responsibility of the DRAFT Administrator. See the relevant sections of this User Guide for details of where these values are allowed. FSTYTB). The fillstyle attribute may be assigned values that describe system-defined or user-defined fill styles.DRAFT User Guide Colours and Styles Attribute type P-line Member-line Outline Text General text Dimension-line text Projection-line text Fill Fill (hatch pattern) Marker Marker symbol Style attribute PLNSTYLE MLNSTYLE OLSTYLE Colour attribute PLNCOLOUR MLNCOLOUR OLCOLOUR - TXCOLOUR DTCOLOUR PTCOLOUR FSTYLE FCOLOUR MSTYLE MCOLOUR The colour attributes may be assigned values by colour table index number or by colour name. DEFAULT. The markerstyle attribute may be assigned values that describe system-defined marker styles. DEFAULT. TEMPLATE. UNCHANGED. See the relevant sections of this User Guide for details of where these values are allowed. See Colours for a listing of the colours available. LSTYTB and FSTYTB are classified as ‘primary’ elements and can therefore be claimed. TEMPLATE. In some circumstances colour attributes may be set to the special values: DEFAULT. The linestyle attributes may be assigned values that describe system-defined or userdefined line styles. STYLWL owns Linestyle and Fillstyle Tables (LSTYTB. 8:2 12. 506 1.DRAFT User Guide Colours and Styles 8.314 0.337 0.000 1.745 0. By default all 272 colour numbers have colour definitions assigned to them: Colour numbers 1 to 16 are assigned by default to the following colours: Colour 1 Colour 2 Colour 3 Colour 4 Colour 5 Colour 6 Colour 7 Colour 8 Grey Red Orange Yellow Green Cyan Blue Violet Colour 9 Colour 10 Colour 11 Colour 12 Colour 13 Colour 14 Colour 15 Colour 16 Brown White Pink Mauve Turquoise Indigo Black Magenta Colour numbers 17 to 272 are mapped to the colours in the standard AutoCAD™ Colour Index (ACI).741 1.208 0.000 0.000 0.741 1.000 0.000 0.000 1.2 Colours DRAFT allows you to draw in up to 272 colours.000 1.000 1.510 0. numbered 1 to 272. 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.494 BLUE 0.000 0.180 0.745 0.000 0.310 0.000 1.314 0.000 0.000 0.510 0.000 1.506 0.498 0.000 0.000 1.247 0.000 1.000 0.667 0.000 0.745 0.000 0. These names (which include the 16 given above) and their ACI (AutoCAD Colour Index) and RGB values are as follows: COLOUR Black White Whitesmoke Ivory Grey Lightgrey Darkgrey Darkslate Red Brightred Coralred Tomato Plum Deeppink Pink ACI 0 7 7 51 253 254 251 129 12 1 22 20 215 230 243 RED 0.510 0.0 .553 8:3 12.000 0.741 GREEN 0.286 0.314 0. 749 0.498 0.000 0.122 0.000 0.749 0.000 1.506 0.506 GREEN 0.741 0.741 0.310 1.000 0.000 0.000 0.000 0.553 0.831 0.000 0.000 1.408 0.000 0.000 1.553 0.000 0.506 0.000 0.506 BLUE 0.000 1.408 1.667 0.494 0.000 0.000 0.918 0.204 0.000 0.741 1.000 0.000 0.000 0.000 1.000 0.000 0.000 1.0 .000 0.337 8:4 12.000 0.000 0.000 0.000 0.000 0.000 0.000 0.749 1.408 0.204 0.000 0.247 0.000 1.667 0.741 1.749 0.369 0.000 0.000 0.000 0.918 0.310 0.000 0.000 0.408 1.741 0.000 0.918 1.075 0.667 0.075 1.667 0.376 1.000 1.553 0.741 0.000 1.667 0.000 0.306 0.741 1.000 0.000 0.DRAFT User Guide Colours and Styles COLOUR Salmon Orange Brightorange Orangered Maroon Yellow Gold Lightyellow Lightgold Yellowgreen Springgreen Green Forestgreen Darkgreen Cyan Turquoise Aquamarine Blue Royalblue Navyblue Powderblue Midnight Steelblue Indigo Mauve Violet Magenta Beige Wheat Tan Sandybrown Brown Khaki ACI 21 40 40 30 226 50 40 51 41 62 110 92 84 108 4 132 120 5 160 176 141 168 142 196 204 221 6 43 31 32 42 36 55 RED 1.667 0.000 0.498 0.000 0.749 1.000 0.678 0.000 0.741 0. ‘orange’) will be returned if available.153 0.0 . 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.180 0. FCONUM/BER etc. 8:5 12. and Orange.741 0. Brightorange and Gold are mapped to ACI 40. The names of these are derived from the normal colour attributes.506 0. e.000 0.310 0. otherwise the colour number will be returned.412 0. Colour definitions can be queried thus: Q COLour 12 Q COLour RGB 55 Colour attributes can be assigned values by number or name.498 0.000 0.498 1.251 0. or an RGB definition.494 1.DRAFT User Guide Colours and Styles COLOUR Chocolate Darkbrown Blueviolet Firebrick Darkorchid Dimgrey Coral Indianred Lightblue Limegreen Mediumaquamarine Sienna Stateblue ACI 38 48 190 30 202 252 22 13 151 80 121 34 173 RED 0.000 0.412 0.310 0.831 1.494 0. LLCONU/MBER.741 Note: the actual RGB definitions of these colours have generally changed at PDMS12 so as to match entries in the ACI.000 0.667 0. If a number is specifically required (regardless of whether a name is available. Typical examples would be: COLour 3 STEELBLUE COLour 12 MIX RED 80 GREen 50 BLUe 50 COLour 14 RGB 0. either specifying a predefined name from the system colour dictionary.000 0. thus: LLCOLOUR 54 TXCOLOUR NAVYBLUE When a colour attribute is queried the name (e.g.g. The redundant colour names have been maintained for compatibility with previous versions of AVEVA Software.918 0.231 0. 141.667 0.247 0.741 0. TXCONU/MBER. This has led to duplication: thus White and Whitesmoke are both mapped to ACI 7.000 0.412 0.494 BLUE 0.741 0.000 0. a special colour-number pseudo-attribute should be used.000 0.553 0.000 0. The syntax can take three forms. or a percentage mixture.000 1. It is possible to change the definitions of colours 1-16 using the COLOUR command.000 0.000 0.495 GREEN 0.000 1. 3. The special colour attribute values of DEFAULT. See the relevant sections of this User Guide for details of where these values are allowed. it is also possible for you to define your own.DRAFT User Guide Colours and Styles It is possible to set all colour attributes on an element to the same value by the ALLCOLOURS command.0 . To set all the text colours and all the line colours separately the TEXTCOLOURS and LINECOLOURS commands should be used. thus. As some DRAFT elements have many such attributes this is a convenient way of changing them to the same colour quickly.3 Line Styles A pre-defined set of line styles is provided. TEMPLATE. Basic User-Defined Line Patterns The line-widths are: • • • THIN MEDIUM THICK single stroke line of minimum thickness 0. and the optional placement of glyphs and/or text strings along it. A line style is defined by the thickness of the line. for example: ALLCOLOURS TEXTCOLOURS LINECOLOURS RED 7 GREEN The list of colour attributes is given in Introduction.1 System-Defined Line Styles A system-defined line style is specified by combining one of ten basic line patterns (see Figure 8:1. 8.: Basic User-Defined Line Patterns) with one of three line widths. SOLID DDASHED DASHED DDOTTED DOTTED FDOTTED CHAINED DCHAINED LDASHED TCHAINED Figure 8:1. 8.4mm approx 8:6 12. its repeating pattern.2mm approx 0. and UNCHANGED can also be specified but these are only valid in particular circumstances. 4mm width gives a dashed line of 0.2mm width BFSTYLE DASHDOTXWide FFSTYLE SOLIDXWIDE gives a dash-dotted line of 0. pattern repeat distance and line width.: Alternative Pre-defined Line Patterns).2mm width gives a double-dotted line of 0. either by specifying an existing system-defined pattern by name or by specifying a sequence of integer numbers that define 8:7 12.4mm width gives a solid line of 0. Figure 8:2. To be valid the definition of a LINEST must include (at the minimum) definitions for dashpattern geometry.0 . 8. For historical reasons an alternative set of line patterns is provided (see Figure 8:2.2 • User-Defined Line Styles Basic Line Style Functionality User-defined Line Styles are defined in the database by LINESTyle elements which are members of a Line Style Table (LSTYTB) element.4mm width Note that for consistency WIDE and XWIDE can be also used with the basic pattern SOLID.DRAFT User Guide Colours and Styles Thus for example: NLSTYLE LDASHED FFSTYLE SOLID OBSTYLE DOTTEDMedium PLSTYLE DDOTTEDMedium CLSTYLE CHAINEDThick BFSTYLE DASHEDThick gives a long-dashed line of minimum thickness gives a solid line of minimum thickness gives a dotted line of 0.2mm width gives a chained line of 0.4mm width Note that for minimum thickness lines the qualifier THIN is omitted. The dash-pattern geometry can be defined in two ways.3. thus for example: NLSTYLE DASHPattern gives an alternative dashed pattern of minimum thickness OBSTYLE SHORTDASHWide gives a short-dashed line of 0. Alternative Pre-defined Line Patterns These alternative line-patterns can be combined with widths named WIDE and XWIDE. The maximum allowed width is 2mm (0. By default PATNAM will be set to SOLID. Dashes and gaps must alternate and we recommend that the pattern sequence starts with a dash. PATNAMe The name of an existing system-defined line pattern (eg LDASHED) to be used as the basis of the user-defined line style. The approximate distance at which the pattern is to be repeated and to which the sum of all the lengths of the dashes and gaps are scaled. Text attribute for descriptive purposes. Value 0 is allowed and means the minimum-allowed line width. It is this number that should be used when the Linestyle is used. When the LINEST element is created a system-defined line style number is allocated automatically.: Basic User-Defined Line Patterns or Figure 8:2.2mm will produce a linestyle similar to the user-defined DCHAINEDMEDIUM style but with a greater repeat distance. This is a unique number in the range 1-255 and is held in the LSTYNO 8:8 12. Element LINEST also has attributes: LSTYNO FUNC ALTDEF This is a system-defined attribute that will have a unique value within the MDB. If set it must refer to another LINEST. (see Figure 8:1. The repeat distance is 30mm and a minimum line width is specified.: Alternative Predefined Line Patterns for the line patterns that can be used). The width of the line (in mm or inches). PATDEFinition LWIDTH PATREPeat Thus for example: NEW LINEST /LS1 PATNAM DCHAINED PATREP 45mm LWIDTH 0.0 . these are mutually exclusive – setting one will unset the other.DRAFT User Guide Colours and Styles 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. If set the referenced LINEST will be used on hard copy output. A series of integers (max 20) that define the relative lengths of the dashes and gaps.078inch). 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. And: NEW LINEST /LS2 PATDEF 10 -3 5 -3 5 -3 10 PATREP 30mm LWIDTH 0 will produce a linestyle of two short dashes inserted between pairs of long dashes. A dash is represented by a positive value and a gap by a negative value. For example: GLYREF /flow-arrow GLYNUM SYSpattern 15 GLYNUM may be set OFF. 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). The size to which the glyph reference size is scaled. One glyph at the start of the line. One glyph at the end of the line. For details of user-defined and system-defined glyphs see Glyphs. A glyph at each end of the line. This is the number to use for a linestyle attribute (eg NLSTYLE) when it is required to use that LINEST. DECMOD 3 is recommended to give the best overall results. Values 1 or 2 may give untidy effects at the ends of spans. DECMOD A code number (1-6) to signify how the glyphs are to be distributed. with its axes reversed.0 . These two attributes are mutually exclusive – setting one will unset the other. 4 5 6 DECSIZ 8:9 12. the first having its axes reversed. Alternatively. In subsequent sessions it will be automatically defined during module entry. The default value is 3. If a repeated glyph is required the following attributes have to be defined: GLYREF GLYNUM The reference of the user-defined glyph The user-defined glyph number. The code number is interpreted as follows: 1-3 Glyphs spaced along the line. This will cause both GLYNUM and GLYREF to be unset. • 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). it is usually more convenient to specify a name for the LINEST.DRAFT User Guide Colours and Styles attribute of the LNEST element. 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. 5 or 6 will cause them to be centred upon the end(s) of the line. The default value is 0. and you can also define your own. The first glyph has its origin at half the repeat distance from the start of the line. This is generally satisfactory for balloons. 11 and 20) have their origins at their centres and thus a repeat distance of 0 with DECMOD = 4. With DECMOD = 2 or 3 DRAFT will adjust the specified repeat distance so as to give an integer number of repeats. the size and frequency of the glyphs and texts will be affected by the scale of the Symbol. To avoid this the repeat distance should be equal to the DECSIZ value. DECREP and DECGAP must be set as described above. TOP. 5 or 6 the repeat distance may be 0. attributes DECMOD. 8. This will cause the origin of each glyph to be positioned at half the repeat distance from the end of the line. Users should note that the DECSIZ. With DECMOD = 4. This functionality is not available for use with native PDMS fonts. This must be a TrueType font. dots. and DECGAP parameters are affect by scale.3. otherwise it must be greater than 0. DECSIZ. • Pre-defined Glyphs 25 pre-defined Glyphs are provided.DRAFT User Guide Colours and Styles DECREP The approximate repeat distance between glyphs. With DECMOD = 4. Text strings and glyphs can both be defined but they have to have common values for DECMOD. 5 or 6 the glyphs will be placed with their origins at half the repeat distance from the appropriate ends. For text strings DECSIZ specifies the character height. This means that if a linestyle with these parameters set is used: • • to define a Symbol Template then. see Figure 8:3. CENTRE. A set of pre-defined Glyphs is provided. DECREP. DECREP. to define 3D design graphics then the size and frequency of the glyphs and texts will be reduced by the View scale. which will be stored in the database. If it exceeds the glyph repeat distance then the path itself will be completely omitted – only the glyphs will be drawn.3 Glyphs Glyphs are used in conjunction with user-defined Linestyles to produce special effects. and DECGAP. DECGAP Note: All DRAFT’s pre-defined glyphs (except numbers 10. Permitted values are BOTTOM (the default).: Pre-Defined Glyphs 8:10 12. DECSIZ. If a repeated text string is required. The length of each gap left in the path. This may be 0 if no gaps are required. The font to be used.0 . for example: symbols at the ends of lines or symbols drawn at regular intervals along the line. In addition the following attributes must be set: TXSTRI TXALIG FONT The text string required (32 characters maximum) The vertical alignment. when that template is instanced by a Symbol. etc but with arrowheads it will cause the line to appear longer than defined. filled Figure 8:3. filled Circle. backward pointing Circle.0 . unfilled Diamond. filled Broad arrowhead. filled Star Thick bar Circle. backward pointing.DRAFT User Guide Colours and Styles System Glyph 1 System Glyph 2 System Glyph 3 System Glyph 4 System Glyph 5 System Glyph 6 System Glyph 7 System Glyph 8 System Glyph 9 System Glyph 10 System Glyph 11 System Glyph 12 System Glyph 13 System Glyph 14 System Glyph 15 System Glyph 16 System Glyph 17 System Glyph 18 System Glyph 19 System Glyph 20 System Glyph 21 System Glyph 22 System Glyph 23 System Glyph 24 System Glyph 25 Double slash L Cross Zigzag 1 Zigzag 2 Break symbol Transverse bar Arrowhead. forward pointing. filled Waveform Square. forward pointing. backward pointing. forward pointing Open arrowhead. filled. Pre-Defined Glyphs 8:11 12. unfilled Square. unfilled Hexagon. unfilled Arrowhead. forward pointing. unfilled Open arrowhead. unfilled Arrowhead. filled Arrowhead. with X overlaid Diamond. and outlines. and GLYOUT elements that represent circles.0 . rectangles. In addition to the basic attribute(s) that define their dimensions these glyph-primitive elements may be rotated and offset from the glyph origin. By default this will be FALSE. • Element GLYRECtangle has attributes: GXLENgth: GYLENgth: GANGLE: GOFFSet: GFILLD: (Integer) The length of the X-side of the Rectangle (Integer) The length of the Y-side of the Rectangle. • Element GLYCIRcle has attributes: GDIAMeter: GOFFSet: GFILLD: (Integer) The diameter of the Circle. Text attribute for descriptive purposes REFSIZe: FUNCtion: GLYPH elements may own GLYCIR. The database default value is 100. and may be solid-filled. It is this number that should be used when the Glyph is used in conjunction with a user-defined Linestyle. 8:12 12. If set TRUE will cause the Circle to be solid-filled. If set TRUE will cause the Rectangle to be solid-filled. Thus if a Glyph with REFSIZ 2000 consisting of a circle of diameter 1000 is used in conjunction with a LINEST with DECSIZ 6mm the result will be a line with 3mm diameter circles. (Degrees) The rotation of the Rectangle about its centre point. GLYREC. (2 Integers) The X & Y offsets of the Rectangle centre point from the Glyph origin. By default this will be FALSE.DRAFT User Guide Colours and Styles • User-Defined Glyphs User-defined Glyphs are defined in the database by GLYPH elements which are members of a Glyph Table (GLYTB) element. (2 Integers) The X & Y offsets of the Circle centre point from the Glyph origin. (Integer) The value that will be mapped to the DECSIZ attribute value of the LINEST when the Glyph is used. GLYPHs have the following attributes: GLYNO: This is a system defined attribute that will have a unique value within the Multiple Database (MDB). The geometry of these is created using the syntax of the <GDEFIN> graph and stored in the GDEFIN attribute. This defines the start point of the Outline. If set TRUE will cause the Outline to be solid-filled.0 .ANG/TO -. 8:13 12.L/TO | | | |-.ANG/TO | | | `--> | | `-. This must be followed by the LTO (LineTo) or ANGTO (AngleTo) keyword and then two or three integers respectively to define the first span. The sequence must start with the MTO (MoveTo) keyword followed by two integers.M/TO | | | |-. The syntax is: GDEFIN -.L/TO -. A GLYOUT is a series of spans that may be straight lines or circular arcs.DRAFT User Guide Colours and Styles • Element GLYOUTline has attributes: GDEFINition: GANGLE: GOFFSet: GFILLD: (Integer array). (Degrees) The rotation of the Outline about its origin.<int2> --|-.M/TO -. a negative angle denotes a clockwise arc. (2 Integers) The X & Y offsets of the Outline origin from the Glyph origin.etc etc etc . They may be continuous or discontinuous. The syntax is given below.<int3> | |. A series of XY coordinates describing the Outline. represents the input of 3 integers defining the angle subtended by a circular arc plus the coordinates of the end point of the arc.ANG/TO | `--> -. By default this will be FALSE.<int3> -|.M/TO | |.etc etc etc .etc .etc Where <int2> <int3> represents the input of 2 integers to define the coordinates of the end point of a straight-line span.<int2> | | | |-.<int2> --|-. A positive angle denotes a counter-clockwise arc.L/TO | |. DRAFT User Guide Colours and Styles 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.3. 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 GDEFINE MTO 10 0 NEW GLYOUT GANGLE 45 GFILLD TRUE NEW GLYOUT GANGLE 90 NEW GLYOUT COPY GLYPH 1 GANGLE 135 GFILLD TRUE NEW GLYOUT NEW GLYOUT COPY GLYPH 1 COPY GLYPH 1 GANGLE 180 GANGLE 225 GFILLD TRUE NEW GLYOUT NEW GLYOUT COPY GLYPH 1 COPY GLYPH 1 GANGLE 270 GANGLE 315 GFILLD TRUE NEW GLYOUT NEW GLYCIR GDIAM 15 GFILLD TRUE COPY GLYPH 1 GANGLE 180 COPY GLYPH 1 LTO 50 -17 ANG 45 50 17 LTO 10 0 COPY GLYPH 1 8.0 . For example. This may be set as follows: GLYNUM/ber OFF GLYNUM SYS/temglyph 10 (the default value) (in the range 1-25) 8:14 12.4 Using Glyphs Glyphs are used in conjunction with LINEStyle elements. The LINEST's GLYNUM attribute defines the glyph to be used. 0 . the spacing between the hatch lines. -30.4. System styles 1 to 10 are defined by a single hatch pattern. 8:15 12.DRAFT User Guide Colours and Styles GLYNUM 3 GLYNUM /My-Glyph (the GLYNO value of the required GLYPH) The LINEST's DECSIZ attribute should be set to define the size to which the Glyphs REFSIZ value is to scaled. 45. It is only of real use when two hatchpatterns with the same angle and separation are combined together. 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. These provide two separations (2mm and 4mm) and six angles (30. The value specified must lie in the range -360 to 360. this is the offset of the hatch-pattern from the bottom left-hand corner of the picture. If no value is given. If 0 then a solid fill is achieved. 8.1 System-Defined Fill Styles Eighteen system-defined fill styles plus a solid-fill capability are provided. on terminals the spacing will be device-dependent but it will be related to the specified value. If not specified a value of 45 will be assumed.: Hatch Patterns 1-10. -45. A Hatch Pattern is defined in terms of three parameters: Angle (HANGLE): the slope of the hatch lines in degrees measured in a counterclockwise direction from the horizontal. 0. 90 deg). 3 mm will be assumed. If they have different offsets double-line hatching can be achieved. The specified value will always be used in plot files. and are shown (within square RECT primitives) in Figure 8:4. A Fill Style is defined either as 'Solid Fill' or by 1 or 2 Hatch Patterns. If no value is given 0 is assumed. Separation (HSEPAR): Offset (HOFFSE): 8.4 Fill Styles Fill Styles are used whenever it is required to hatch an area on a drawing. The offset value for all of these settings is zero. double-line hatching. 2mm separation 90 deg. cross-hatching. 4mm separation 8:16 12. 4mm separation 45 deg. double-line hatching. 4mm separation 45 deg. cross-hatching.0 . cross-hatching.DRAFT User Guide Colours and Styles HPATTERN 1 Angle 30° Gap 4mm HPATTERN 6 Angle 90° Gap 2mm HPATTERN 2 Angle -30° Gap 4mm HPATTERN 7 Angle 30° Gap 2mm HPATTERN 3 Angle 45° Gap 4mm HPATTERN 8 Angle -30° Gap 2mm HPATTERN 4 Angle -45° Gap 4mm HPATTERN 9 Angle 45° Gap 2mm HPATTERN 5 Angle 0° Gap 2mm HPATTERN 10 Angle -45° Gap 2mm Figure 8:4. Hatch Patterns 1-10 Patterns 11-18 are combinations or variants of hatch patterns 1-10. 2mm separation 30 deg. and are defined as: Pattern 11: Pattern 12: Pattern 13: Pattern 14: Pattern 15: 45 deg. single-line hatching. 1mm separation -45 deg. for example. 6mm separation Patterns 11-18 are illustrated in Figure 8:5.0 . the fill style attribute of the primitives is set using the command: FSTYLE SYStempattern integer To fill an area with system-defined hatch pattern 12. Figure 8:5. single-line hatching. Hatch Patterns 11-18 To fill an area of a primitive with a system-defined hatch pattern. single-line hatching.DRAFT User Guide Colours and Styles Pattern 16: Pattern 17: Pattern 18: 30 deg. the following would be used: 8:17 12. 1mm separation 45 deg.: Hatch Patterns 11-18. If set it must refer to another FILLST. Thus if at /My-Fillstyle: ALTDEF is set to /My-Plot-Fillstyle it is /My-Plot-Fillstyle that will be used on hardcopy output in place of /My-Fillstyle.5mm will create a Fillstyle composed of parallel lines 3. Adding a second HPATTE thus: NEW HPATTE HANGLE 35 HSEPAR 3.DRAFT User Guide Colours and Styles FSTYLE SYS 12 To solid fill an area. The default setting is unset. The default setting is FALSE. If set TRUE will cause the Fillstyle to provide solidfill.5mm Adding additional HPATTEs will have no effect . Element FILLST also has attributes: FSTYNO: This is a system defined attribute that will have a unique value within the MDB. use the command: FSTYLE SOL 8.the third and subsequent ones (in database list order) will be ignored.5mm HOFFSE 1mm will convert /My-Fillstyle into a double-line Fill Style with double lines (1mm between them) repeated every 3.2 User-Defined Fill Styles User-defined Fill Styles are defined in the database by FILLSTyle elements which are members of a Fill Style Table (FSTYTB) element. It is this number that should be used when the Fillstyle is used. Text attribute for descriptive purposes. Thus the commands: NEW FILLST /My-Fillstyle NEW HPATTE HANGLE 35 HSEPAR 3. If set the referenced FILLST will be used on hard copy output. When the FILLST element is created a system-defined fill style number is allocated automatically.5mm apart at an angle of 35deg. They own HPATTErn elements.0 . 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. SOLFILled: FUNCtion: ALTDEF 8:18 12.4. (thus CIRCles. it is usually more convenient to specify a name for the FILLST. 8.5 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. UNC/hanged. ACSTYL. DEF/ault. used during the Update Design process. X + * O (STOP) (CROSS) (PLUS) (STAR) (RING) To set the marker style attribute (MSTYLE). etc). The FSTYLE attribute can be set to: a System Fillstyle. and this is then used to set the FSTYLE attribute (although it is the FSTNO value that will be assigned to the FSTYLE attribute). This occurs at: Annotation elements: Style elements: High-level elements: where the hatching of an area is feasible.DRAFT User Guide Colours and Styles Alternatively. The five marker types are: . 8.4. use the command: MSTYLE marker-type SCAle integer 8:19 12. thus: FSTYLE SYS/temstyle 10 FSTYLE SOL/idfilled a User-defined Fillstyle. OUTLines. These are not all valid in all circumstances. 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. (thus HSTYL.0 . thus: FSTYLE 3 (the FSTYNO value of the required FILLST) (in the range 1-18) FSTYLE /My-FillStyle Various special values: OFF.3 Using Fillstyles The only attribute within the DRAFT database that uses Fillstyles is FSTYLE. and DCSTYL) to allow the FSTYLE value to be cascaded down the database hierarchy as it is created. In subsequent sessions it will be automatically defined during module entry. Example: SETFEED COL 15 Set rubber banding colour to colour 15 SETFEED COL BRIGHTORANGE SETFEED COL DEF Set rubber banding colour to magenta The SETFEEDBACK command also controls the appearance of displayed p-points. in the current feedback colour.DRAFT User Guide Colours and Styles For example. when p-points are displayed (see Picking P-points and Nodes) they appear as ‘star’ markers. but can be changed by the SETFEEDBACK command.keeping the left-hand mouse button held down enables an appropriate shape to be dragged out to the required extent. DIAMETER etc) incorporate a ‘rubber banding’ feature . The colour of this ‘graphical feedback’ feature is magenta by default.g. the following command could be used: MSTYLE PLUS SCA 6 8. By default. scale 2. scale 3 8:20 12.6 Graphical Feedback Style and Colour The cursor size/resize commands (e. VREGION. to mark the centre of a circle. scale 2 SETFEED PPO RING SCALE 3 Set p-point symbol to ‘o’.0 . The marker type and scale can be changed by: SETFEEDBACK PPOINTS marker_type SCALE int Example: SETFEED PPO PLUS SCA 2 Set p-point symbol to ‘+’. DEFINE. 9. See Circulation List. The name of the macro which generated the report Originator (ORNA.DRAFT User Guide Reports. The relevant part of the DRAFT database is shown in Figure 9:1. The revision number of the report A typical creation sequence for a REPO might be: NEW REPO TITL ’REPORT ON VALVES IN ZONE 2’ FLEN ’/REP-A-V’ CLRF /PURCHASING 9:1 12. A description of the report Revision (RVSN). as a text string Title (TITL). Circulation Lists and Revisions This Section describes how to create the drawing office administrative elements of reports and circulation lists.0 .: Report Database Hierarchy. Circulation Lists and Revisions 9 Reports. The report creation date Source. Report Database Hierarchy A Report has the attributes: • • • • • • • Circulation List Reference (CLRF). and how DRAFT handles revision numbers.1 Report The Report (REPO) element may be used to contain brief textual information relating to a full report (which would exist outside Plant/Marine) on the owning drawing registry. Date. The name of the file containing the report. REGI REPO TEXT Figure 9:1. Text to describe the originator of the report Filename (FLEN). A reference to a circulation list element. Circulation Lists and Revisions 9.: Circulation List Database Hierarchy.0 .2 Circulation List DRAFT gives you the ability to store Drawing Circulation Lists. Circulation List Database Hierarchy 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. The relevant part of the DRAFT database is shown in Figure 9:2. Each CIRL may contain other CIRL elements and/or Recipient (RECI) elements. A RECI has the attributes: • • • Recipient Name (RNAM) Location (LOCA) Number of Copies (COPI) 9:2 12. Library DRWG CLRF REPO CLRF CLLB CIRL CIRL RECI RECI Figure 9:2.DRAFT User Guide Reports. : Revision Element. Revision Element A REVI has the attributes: • • • • • • Approver (APPR) Date of Approval (APDT) Revision (RVSN) Revision text (STEXT) Date of Revision (RVDT) Revision Author (RVAU) 9:3 12.DRAFT User Guide Reports.3 Drawing Revisions The Revision (REVI) element enables you to store drawing revision data. Circulation Lists and Revisions An example of setting up a Circulation List hierarchy might be: Example: NEW CLLB Create Circulation List Library (at Library level) NEW CIRL /CL1 Create Circulation List NEW RECI /RC1 Create Recipients RNAM ’Tom’ LOCA ’Room F21’ NEW RECI /RC2 RNAM ’Dick’ LOCA ’Room G24’ COPI 2 /DRWG DR1 Set Circulation List Reference CLRF /CL1 9. DRWG SHEE REVI CIRL REVI CLRF Figure 9:3.0 . A REVI may be a member of a Drawing element or of a Sheet element. see Figure 9:3. 0 .revision letter.4 9. . The attributes are valid at any element of or below a Sheet or Drawing respectively. APPR text APDT text RVSN [text] RVAU [text] CLRF name . They have been created primarily for use with hash codewords to generate revision data on drawings.4.set location of recipient .set approval date .4. Automatically set. . but may be overridden . Part 2.set name of approver . The maximum array size is 50. but they can then be edited.DRAFT User Guide Reports. Circulation Lists and Revisions • Circulation List Reference (CLRF) RVSN.set name of recipient .1 Summary of Commands At Circulation List .set number of copies 9. Drawing Annotation. Automatically set.revision author. RVDT and RVAU are all automatically set on REVI creation. but may be overridden . 9. see Accessing Data from the DRAFT Database. RNAM text LOCA text COPI integer . . 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.set Circulation List (CIRL) reference 9:4 12. . The format of the date assigned to RVDT is controlled by the value of the DATEFOrmat attribute of the relevant DEPT.2 At Revision . 0 . When a VIEW references a CRST. In order to determine whether Design and Annotation elements have changed. or named elements. be underlined. Change Rules Database Hierarchy 10:1 12. either Design Change Styles or Annotation Change Styles. the reference is made by its CRSF attribute. The other point used is a Comparison Date.1 Change Highlighting Introduction Change Rules control how Design and Annotation elements that have been changed are drawn on a DRAFT View and are similar to Representation Rules.DRAFT User Guide Change Highlighting 10 10. and the reference from an ACRULE to an ACSTYL is made by its ACSTYF attribute. Pieces of text may also have their font changed. RPLB RPLB VIEW crsf CRST DCSTYL ACSTYL dcstyf ACRULE DCRULE acstyf Figure 10:1. Design Change Rules (DCRULE) and Annotation Change Rules (ACRULE) are stored in Change Rulesets (CRST). The concept of Comparison Dates is discussed in Comparison Date. Each Change Rule can be specific to a given type or types of element. it is necessary to compare the relevant databases at two points in time. The reference from a DCRULE to a DCSTYL is made by its DCSTYF attribute. The attributes of the Change Styles define the way in which changed elements will be drawn. For more information about styles and colours see Colours and Styles. or be enclosed within a specified style of parentheses. One of these two points is always the current time. Generally this will be by altering the drawing styles and colours used. Change Rules refer to Change Styles. For information about Representation Rules see Graphical Representation. which in turn are owned by Representation Libraries (RPLB). RPLBs are also used to store Design Change Styles (DCSTYL) and Annotation Change Styles (ACSTYL). depending on whether the changed element is a Design element or an Annotation element. Design elements that have no DCSTYL assigned to them will not have any changes that are made to them marked. Drawing Level (DLEV). etc. The DCSTYL only defines which. but ignore changes made to steelwork. Dimension or 2D Primitives) specified by an ACRULE that references it. The values of these attributes are determined from the relevant Representation Styles. SHOW CHANGES Option and Error Messages). and two other attributes that will be used 10:2 12. for example. Once the Rulesets and Styles have been set up. 10. These are equivalent to the six styles/ colours of a Representation Style plus the two styles/colours (Outline and Fill) of a Hatching Style.DRAFT User Guide Change Highlighting 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. and issuing an UPDATE command with the SHOW CHAnges option (see UPDATE Command. if any. Within a VIEW.3 Annotation Change Styles An Annotation Change Style (ACSTYL) defines the appearance of changed annotation elements (Label.2 Design Change Styles The Design Change Style (DCSTYL) defines the appearance of changed design elements specified by a DCRULE that references it. it is just a matter of setting the VIEW attribute CRSF to point to the Ruleset that you wish to use. All eight styles/colours may be set to specific values.0 . defining a Comparison Date. Each ACSTYL defines three styles/colours. If any of the Representation or Hatching styles are set to OFF they will not be overridden by the Design Change Style style/colour. it is therefore possible to mark changes made to pipework. Alternatively. The DCSTYL attributes. 10. they do not have Tubing Flag (TUBEF). the relevant Representation or Hatching style/colour will be used. If set to UNCHANGED. are as follows: Frontface Style/Colour Backface Style/Colour Obscured Line Style/Colour Centreline Style/Colour P-line Style/Colour Member Line Style/Colour Outline Style/Colour Fill Style/Colour FFSTYLE/FFCOLOUR BFSTYLE/BFCOLOUR OBSTYLE/OBCOLOUR CLSTYLE/CLCOLOUR PLNSTYLE/PLNCOLOUR MLNSTYLE/MLNCOLOUR OLSTYLE/OLCOLOUR FSTYLE/FCOLOUR SOLIDTHICK/8 DOTTEDTHICK/8 LDASHTHICK/8 CHAINEDTHICK/8 DASHEDTHICK/8 CHAINEDTHICK/8 SOLIDTHICK/8 SYSTEMPATTERN1/8 Note that DCSTYLs are not exact equivalents of Representation Styles. of the standard style/colour values should be overridden in order that changed Design elements are marked. a style can be set to OFF or UNCHANGED. and a colour may be set to UNCHANGED. However. a font. attributes. with their defaults. Change Rules cannot be owned directly by a VIEW and there are therefore no local change rules. Each DCSTYL defines eight styles/colours that will be used to draw changed design elements. unlike Representation and Hatching Rules. CREATED and MODIFIED. For changes to be highlighted properly the Selection Criterion should use one of the functions that make use of the current Comparison Date.DRAFT User Guide Change Highlighting to draw changed annotation elements. These are. Part 1 General Commands.4. It is therefore possible to mark different types of elements in different ways. For example: CRIT ALL BRAN MEM WITH (MODIFIED (GEOM)) CRIT ALL SCTN WITH (MODIFIED (LENGTH)) CRIT ALL EQUI WITH (CREATED ()) CRIT ALL WITH (CREATED ()) 10:3 12. The two other attributes define whether changed text is to be underlined or enclosed in brackets. The three styles/colours are used for drawing text. with their defaults. 10. If any of these four attributes are set to UNCHANGED.4 Change Rules The Change Ruleset (CRST) owns both Design Change Rules (DCRULEs) and Annotation Change Rules (ACRULEs). are as follows: Text Colour Note Line Style/Colour Fill Style/Colour Font Number Brackets Underline TXCOLOUR NLSTYLE/NLCOLOUR FSTYLE/FCOLOUR FONT BRACKE UNDERL 8 SOLID/8 SYSTEMPATTERN1/8 UNCHANGED NONE OFF Alternative values for BRACKE are: ROUnd. The manner in which each changed design element is marked is defined by the referenced Design Change Style. The ACSTYL attributes. or not at all.1 Design Change Rules Design Change Rules use Selection Criteria to define the changed design elements to which the rule is to apply. Design Change Rules reference Design Change Styles and Annotation Change Rules reference Annotation Change Styles. are as follows: Design Change Style Reference Selection Criterion DCSTYF CRIT unset unset For more information on using Selection Criteria refer to DESIGN Reference Manual. 10. the relevant Label/Dimension/2D Primitives attribute will be used.0 . linear graphics and hatched areas of annotations. in a similar manner to Representation and Hatching Rules. The DCRULE attributes. with their defaults. All three styles/colours may be set to specific values or to UNCHANGED. CURly. SQUare. The font attribute may be set to a standard font number or to UNCHANGED. ANGle. projection lines. CHANgedanno. 10. that is. dimension lines. Associated leader lines. all elements associated with the annotation will be marked. if its BTEX was '#NAME at #POS' then the text string would be marked as changed.5 Attribute Setting The following attributes: FFSTYLE/FFCOLOUR BFSTYLE/BFCOLOUR CLSTYLE/CLCOLOUR OBSTYLE/OBCOLOUR PLNSTYLE/PLNCOLOUR MLNSTYLE/MLNCOLOUR OLSTYLE/OLCOLOUR NLSTYLE/NLCOLOUR FSTYLE/FCOLOUR TXCOLOUR FONT 10:4 12.4. If more than one ACRULE is referenced for a type of changed annotation. The syntax for the Annotation Change Rule Application attribute is: ASCODE ADDedanno.0 . Annotation Change Rules have an attribute to determine whether they should be applied to Changed Annotations. For example. one applicable to Changed Annotations. Added Annotations. ADDed AND CHANged 10. is not relevant here. or both. deleted design elements will not be shown on DRAFT drawings and hence cannot be highlighted. a repositioned GLAB with BTEX '#NAME' that has moved because its referenced design element has moved will not be marked as changed. only changes in expanded text strings will be marked. are as follows: Annotation Change Style Reference Annotation Code ACSTYF ASCODE unset Changed Each CRST therefore only needs to reference one or two ACRULES. For Changed Annotations.DRAFT User Guide Change Highlighting For more information on the CREATED() and MODIFIED() functions and their use in AVEVA Plant/Marine expressions refer to DESIGN Reference Manual. The whole expanded text string would be drawn in accordance with the referenced ACSTYL. in database order. DELETED(). the expanded text string and all graphic elements. will be applied. Part 1 General Commands. would not be marked as changed.2 Annotation Change Rules Changes to annotation graphics are treated in a simpler manner than changes to design graphics. only the first. However. The ACRULE attributes. For Added Annotations. or any other graphic elements. Note that a third function associated with the Comparison Date. with their defaults. one applicable to Added Annotations. The Comparison Date can be set in one of two ways: • • By specifying an actual time and date.0 . This is valid at DCSTYL and ACSTYL elements only. For more information on Stamps and how they are created and used refer to the ADMIN Command Reference Manual and the ADMIN User Guide.For example: Example: SETCOMPDATE 31 March 2002 SETCOMPDATE STAMP /Prelim-Milestone The current Comparison Date can be queried by: Q COMPDATE DATE Q COMPDATE STAMP A Stamp is a way of referencing combinations of databases and sessions at specified instances. Assigning UNChanged to these attributes at any other element will generate the following error message: 64. that is.275: UNCHANGED is not valid at <type> elements The syntax for the Change Highlighting Referencing attributes is: DCSTYF ACSTYF CRSF UNSET or any DCSTYL UNSET or any ACSTYL UNSET or any CRST Change Rules can also be defined with the USE command. 10. We do this by specifying a Comparison Date (COMPDATE). Example: USE /anno-change-style-01 FOR CHANGEDANNO USE /anno-change-style-04 FOR ADDEDANNO USE /des-change-style-A FOR ALL EQUI WITH MODIFIED (GEOM HIER) USE /des-change-style-B FOR ALL WITH MODIFIED() For full details of using expressions refer to DESIGN Reference Manual. By referencing a Stamp.DRAFT User Guide Change Highlighting all have the option of UNChanged. Using the current state of the drawing as one state we must then reference an earlier state in order to make the comparison. Part 1 General Commands. the drawing state at a time that we wish to use as a baseline or datum. Stamps are created by the PDMS Administrator. 10:5 12.6 Comparison Date It is only by comparing a drawing at two states or sessions that it is possible to determine what has changed. • If the View's CRSF attribute is invalid. 10.DRAFT User Guide Change Highlighting The Comparison Date can be used in queries on any attributes. SHOW CHANGES Option and Error Messages The commands UPDATE DESIgn.64: <view-name>:CRSF attribute value is invalid followed by the error message: 64. updating will be abandoned and the following error message will be displayed: 64. updating will be abandoned and the following error message will be displayed: 64. This option is only valid at View elements or above. it is assumed that default Design and Annotation Change Rules are to be applied. In each case this option will update the picture to the latest relevant data and VIEW attributes. using the syntax OLD. These are equivalent to the following: USE /default-design-change-style FOR ALL WITH MODIFIED()) USE /default-anno-change-style FOR ADDED AND CHANGED ANNO where the defaults are listed in Design Change Styles and Annotation Change Styles. The following error conditions may be encountered when using the SHOW CHAnges option: • If the SHOW CHAnges option is given below View level.7 UPDATE Command.0 .445: <CRST-name>: No DCRULEs (or ACRULEs or Change Rules) defined followed by the error message: 10:6 12. If no changes are found on the View. updating will proceed and the following error message will be displayed: 64. Q OLD REF OF /OLDPIPE will output the reference of deleted element /OLDPIPE at the Comparison Date.446: No current Comparison Date or Stamp defined.444: The SHOW CHANGES option will be ignored when issu ed below a View • If no Comparison Date or Stamp is specified.153: <view-name>:Generation of Design (or Annotation or All) graphics abandoned • If the CRSF references a CRST that contains no rules. a message will be output to reassure the user that the SHOW CHAnges option has been properly evaluated. For more information on the Comparison Date functionality refer to the ADMIN User Guide. updating will be abandoned and the following error message will be displayed: 64. For example: Q OLD XLEN will output the value of attribute XLEN of the current element at the Comparison Date. • If the View's CRSF attribute is unset. including changes. UPDA TE SHOW CHANGES abandoned. UPDATE ANNOtation and UPDATE ALL have the option SHOW CHAnges. 445: <CRST-name>: No DCRULEs (or ACRULEs) defined followed by the error message: 64.one for each of its DCRULEs and ACRULEs.153: <view-name>:Generation of Design (or Annotation or All) graphics abandoned • If the CRSF references a CRST that contains no DCRULEs (with reference to an UPDATE DESI command).DRAFT User Guide Change Highlighting 64. the following error message will be displayed: 64.296: Warning: <rule-name>: is invalid and will be ignored 10. 10:7 12. • If the DCSTYF or ACSTYF attribute of a Change Rule is unset or invalid.0 . at a DCRULE or an ACRULE: Q DESCription will output a description for that rule with the format: USE desi-change-style FOR criteria USE anno-change-style FOR ascode-value At a CRST: Q DESCription will output an ordered list of descriptions .8. updating will be abandoned and the following error message will be displayed: 64.64: <rule-name>:DCSTYF (or ACSTYF) attribute value is invalid 64. then it is assumed that the user wants to produce a drawing on which only annotation changes are marked.153: <view-name>:Generation of Design (or Annotation or All) graphics abandoned • If the CRIT attribute of a DCRULE is unset (with reference to an UPDATE DESI and an UPDATE ALL command). Thus.153: <view-name>:Generation of Design (or Annotation or All) graphics abandoned In this case if the command was UPDATE ALL and the CRST contains ACRULES but no DCRULEs (for example).8 10. updating will be abandoned and one of the following error messages will be displayed: 64.65: <rule-name>:DCSTYF (or ACSTYF) attribute value unset followed by the error message: 64.1 Querying Commands Querying Change Rulesets and Design or Annotation Styles The querying facilities are similar to those provided for RRULs. or no ACRULEs (with reference to an UPDATE ANNO command). BFSTYLE integer/line_pattern. one for each owned by its referenced CRST. OBCOLOUR integer/colour_name OBSTYLE OFF OBSTYLE UNCHANGED OBCOLOUR UNCHANGED . . .Controls style and colour for drawing rear face edges. .Controls style and colour for drawing front face edges.DRAFT User Guide Change Highlighting At a VIEW: Q CRSF DESCription will output an ordered list of rule descriptions.Controls style and colour or drawing front-facing edges of Items that would otherwise be obscured by other objects 10:8 12. FFSTYLE integer/line_pattern.1 Summary of Commands At Design Change Rule . . USE stylename FOR crit CRITeria crit .0 .Set the CRIT attribute for the current rule. At a VIEW or CRST: Q DCSTYF FOR design-id will return the DCRULE that is relevant for the specified design item.9. 10.9. FFCOLOUR integer/colour_name FFSTYLE OFF FFSTYLE UNCHANGED FFCOLOUR UNCHANGED .9 10.Set drawing style for Design generic types.2 At Design Change Style . . 10. OBSTYLE integer/line_pattern. BFCOLOUR integer/colour_name BFSTYLE OFF BFSTYLE UNCHANGED BFCOLOUR UNCHANGED . FCOLOUR integer/colour_name FSTYLE OFF FSTYLE UNCHANGED FCOLOUR UNCHANGED .0 . USE stylename FOR ADDED .3 At Annotation Change Rule .Controls style and colour for drawing p-lines.Controls style and colour for hatching selected faces. 10:9 12. OLCOLOUR integer/colour_name OLSTYLE OFF OLSTYLE UNCHANGED OLCOLOUR UNCHANGED .Controls style and colour for drawing member lines. MLNCOLOUR integer/colour_name MLNSTYLE OFF MLNSTYLE UNCHANGED MLNCOLOUR UNCHANGED .Controls style and colour for drawing centrelines.Set drawing style for changed Annotations. . CLCOLOUR integer/colour_name CLSTYLE OFF CLSTYLE UNCHANGED CLCOLOUR UNCHANGED .9. FSTYLE integer/line_pattern. .Controls style and colour for drawing outline of selected faces.DRAFT User Guide Change Highlighting CLSTYLE integer/line_pattern. 10. PLNSTYLE integer/line_pattern. OLSTYLE integer/line_pattern. MLNSTYLE integer/line_pattern. PLNCOLOUR integer/colour_name PLNSTYLE OFF PLNSTYLE UNCHANGED PLNCOLOUR UNCHANGED . NLSTYLE integer/line_pattern.4 At Annotation Change Style .Controls colour for annotation text. TXCOLOUR integer/colour_name TXCOLOUR UNCHANGED .Controls style and colour for drawing annotation linear graphics. NLCOLOUR integer/colour_name NLSTYLE UNCHANGED NLCOLOUR UNCHANGED .Set bracket style for enclosing text. . FCOLOUR integer/colour_name FSTYLE UNCHANGED FCOLOUR UNCHANGED .DRAFT User Guide Change Highlighting 10.Set Underline ON for annotation text.9. FONT integer FONT UNCHANGED . FSTYLE integer/hatch_pattern.0 . 10:10 12. UNDERL ON .Controls style and colour for drawing annotation hatched areas. BRACKE SQUARE BRACKE NONE . .Set annotation font. that is dimensioning elements. geometric primitives. symbols. and 2D drafting elements (i. labelling elements. and text). Other text. Annotation Elements Dimensioning and Labelling elements are owned by Layers.e.0 . This part of the DRAFT database hierarchy (see DRAFT Database Hierarchy) is shown below: Figure 11:1.DRAFT User Guide Introduction to Annotation 11 Introduction to Annotation This Chapter describes the part of the DRAFT database used to store annotation elements. 11:1 12. symbols and graphics are owned by Notes. There are two types of Note: • • Sheet Notes (NOTEs) owned by Sheets View Notes (VNOTs) owned by Views. The PCOD (Precision Code) attribute controls the precision of output used with Dimensions and Labels.0 .13/16 The default is mm for distances and bores. #PKNA^POSS).g. and the function of a Layer is defined by its PURPose attribute.g. The LVIS attribute controls the visibility of a Layer. #POS.1. The PURP attribute is used to control the types of element that the Layer can own.DRAFT User Guide Introduction to Annotation 11.1 Layers Layers (LAYE) are owned by VIEWs and are administrative elements used to group together annotation elements. different Layers are used for different functions. #P2POS. Example: UCOD FINCH DIST set distance units to feet and inches. Usually.1. See Distance. e. Position and Bore Data Output for full details of UCOD. as an absolute position (XYZ). Note: Where Layers and Layer members have common attributes. These attributes are described in more detail in Position Output Formats. The setting of these attributes determine the output format used by the positional code words. 11. To accomplish this two attributes. See Controlling the Precision of the Generated Output. They expand to a string providing the location expressed in either the ENU (East North Up) coordinate system. the values of those attributes are cascaded down from the Layer. The same output format is used throughout a given layer. POSFOR and GRSYS are provided for a number of elements in the PADD database. This enables different types of annotation to be switched on and off.1 Dimension and Label Attributes The UCOD (Units Code) Layer attribute controls the display of units used for dimensions and labels. Layers may own Dimension elements.2 Intelligent Text Attributes In the Intelligent Text System there are code words that are used to request the position of certain elements (e. Label elements and View Note elements. in the Ship Reference System or as a purely numerical output. see Highlighting Displayed Elements. for example: PURP DIMS The PURP attribute may also be used to identify the Layer in other commands. The PURP (Purpose) attribute of a Layer is set to a (four character) word. Example: UPDATE LAYE DIMS HIGhlight PURPose DIMS highlight the Layer in the current view with its PURP attribute set to DIMS For more information on the HIGHLIGHT command. 11. 5’5. It can be set to TRUE or FALSE. 11:2 12. 11:3 12.DRAFT User Guide Introduction to Annotation 11. For more information on 2D Symbology. When autoblanking is switched off. The geometry of the blanked areas is defined by the geometry of the annotation element. PDIM. The main purpose is to allow annotation to be shown clearly in crowded parts of a drawing. for example. a circular annotation element can define a circular blanked area where no 3D design graphics will appear.2 Autoblanking You can use autoblanking to remove an area of graphics from a drawing and leave a clear area.0 then a blanked region will be drawn with no blanking margin. If BMAR is set to 0. The attribute BLNK specifies whether autoblanking is required. but switching autoblanking on will generate all blanks immediately. ADIM.3 Design Symbol Layers The Design Symbol Layer (DSLAYE) is a particular type of LAYE element that is used to contain Design Symbol (DESSYM) database elements. The advantage of working with Autoblanking switched off is that view control operations such as zooming and panning will be slightly faster. VNOT.0. RDIM. graphics added later will be drawn in this clear area. 11. SLAB. Blanks will always be generated in plot files generated from DRAFT.0 . 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. Overlapping 2D. even when Autoblanking is off. the blanks will not be generated on the screen. GLAB. Generally. text and other annotation graphics will not be hidden by blanking. When autoblanking is switched on. The DESSYM elements enable design elements to be represented symbolically on a 2D View. BLNK TRUE/FALSE BMAR value where value is a real value that is greater than or equal to 0. and NOTE. There can be only one occurrence of a DSLAYE per View. the geometry will be hidden in the blanked areas immediately the annotation that defines them is drawn or modified. and attribute BMAR specifies the blanking margin to be applied. refer to 2D Symbolic Representation and Representation Rules.1. DRAFT User Guide Introduction to Annotation 11:4 12.0 . A simplified view of that part of the DRAFT Database hierarchy (see DRAFT Database Hierarchy) that relates to dimensioning is shown below. Hierarchy of Dimension and Related Elements DRAFT allows dimensions to be created quickly and easily (using the cursor).DRAFT User Guide Dimensioning 12 12. with many attributes of the dimension elements being set automatically by cascading values from the owning LAYE element.0 . which specify the points between which dimensions are drawn. VIEW LAYE LDIM RDIM PDIM ADIM (Dimension Directions) (Dimension Points) (Dimension Points) Figure 12:1. radial (two types) or angular. Two other types of linear dimension are: 12:1 12.1 Dimensioning Introduction DRAFT dimensions are a form of drawing annotation consisting of both text and geometric elements. 12. Linear and radial dimensions show the distances between particular points in the design model whilst angular dimensions show the angles between directions. they may be linear. LDIM elements own Dimension Point elements.2 Dimension Element Types Linear Dimension (LDIM) elements (see Linear Dimensions) exist for each linear dimension that appears on a drawing. 3 12. PDIM elements own Dimension Point elements. being defined by a database element and an attribute (e.3. dimension lines are drawn. each of which relates to a point in the Design model. Each dimension and projection line may have text associated with it. ADIM elements own Dimension Direction elements. 12. then the position of the HEAD of the first Branch is used.0 . which specify the points between which dimensions are drawn. An illustration of a simple linear dimension between two Equipments is shown in Figure 12:2. if any. If no Branch HEADs are visible in the VIEW region. Note: When a Pipe element is dimensioned directly. Pitch Circle Dimension (PDIM) elements (see Pitch Circle Dimensions) exist for each pitch circle dimension that appears on a drawing. From each of these Dimension Points on the drawing. a projection line is drawn in a user-definable direction. Angular Dimension (ADIM) elements (see Angular Dimensions) exist for each angular dimension that appears on a drawing. the Pipe origin is assumed to be the position of the HEAD of the first Branch visible in the VIEW region.g. The graphics for a PDIM are similar to those for an RDIM. between these parallel projection lines. Figure 12:2.DRAFT User Guide Dimensioning Radial Dimension (RDIM) elements (see Radial Dimensions) exist for each radial dimension that appears on a drawing. Single Value Linear Dimension 12:2 12. DIAM of a CYLI).1 Linear Dimensions Linear Dimensions and How to Create Them The simplest kind of Linear Dimension consists of a pair of points on a drawing. which specify the end points of the dimension arc and its origin.: Single Value Linear Dimension. in this case the origin. DRAFT will ignore those primitives with OBST (obstruction level) set to 0 or 1. with the last point becoming the current element.allows you to dimension to/from any given 3D positions DPBA. STRU or SUBS. Figure 12:3.0 .: Single Value ‘Before/After’ Linear Dimensions shows an example of such a linear dimension.01 mm. 12:3 12. its OBST value will be ignored.: Single Value Linear Dimension) will be suppressed.Use cursor to nominate (three) items to dimension from/to The Dimension will appear on the display.Create new linear dimension element . DPOI elements would be created by a sequence such as: 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 . Note: In cases where the dimension value is less than 0. starting at Layer level: NEW LDIM FROM ID @ TO ID @ TO ID @ .see Principal Attributes of Angular Dimensions. Constructed points (see Point and Line Construction) may also be used to create Dimension Points. produced by the same command but with different dimension directions.the Dimension Point is defined by a p-point of the Design element. If only two elements are hit a pair of Dimension Point elements will have been automatically created.allows you to dimension to/from ‘before’ or ‘after’ a Design element (in the Dimension direction). In the above example the Dimension Points will be DPPT elements . Any p-point can be nominated as a dimension point by replacing the FROM ID @ syntax above by FROM IDP @/TO IDP @.DRAFT User Guide Dimensioning Such a dimension could be produced by typing the following commands. When dimensioning BEFORE or AFTER elements such as EQUI. When dimensioning BEFORE or AFTER a primitive. The Dimension may also be defined explicitly: Example: FROM /1501A TO /1501B The other two types of Dimension Point that may be owned by an LDIM element are: • • DPOI. the display of all dimension point graphics (see Figure 12:2. (See Principal Attributes of Linear Dimensions for details of DOFF and OSHT.: Before/After’ Linear Dimensions on a Single Element shows examples of using ‘before/after’ linear Dimensions with a single element. 12:4 12.) 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.DRAFT User Guide Dimensioning Figure 12:3.0 . Single Value ‘Before/After’ Linear Dimensions Figure 12:4. the Dimension will still be drawn.0 . If the DDNM is set to refer to an element.: Before/After’ Linear Dimensions on a Single Element . Before/After’ Linear Dimensions on a Single Element 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. Note: Any combination of the above three Dimension-creating commands is permissible.see Radial Dimensions.DRAFT User Guide Dimensioning Figure 12:4. Example: FROM ID @ TO BEFORE ID @ FROM POS @ TO ID @ FR AFT ID @ TO POS @ Each FROM command sets the Dimension Point’s DDNM (Design Data Name) attribute to the Name of the Design element. The command: CHECK REFS WARN will cause a warning to be output in this situation. The DDNM attribute may be reset immediately to define a new Dimension Point. which is not in the Id List referenced from the current VIEW. and the command 12:5 12. Two classes of multi-valued Dimensions exist. Figure 12:5. The default reference-checking mode (i. the Dimension is said to be multi-valued. moving the cursor crosshairs to each Dimension Point in turn. This is done simply by typing: INSERT ID @ and using the cursor to nominate the link element. where more than two Dimension Points are involved.2 Multi-valued Dimensions The preceding examples have dealt with single-valued dimensions. 12. The example shown in Figure 12:4. The Dimension is now treated as only containing the significant Dimension Points for both drawing the Dimension and for commands which rely on the drawn dimension (such as PLCL @ (see Figure 12:9.: Before/After’ Linear Dimensions on a Single Element would have been created by a command sequence such as: 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. TO command line.DRAFT User Guide Dimensioning CHECK REFS FULL will result in such Dimensions not being drawn. no checking) is given by CHECK REFS OFF Reference checking is also available for Labels . .0 . namely chained and parallel.: Key Attributes of a Linear Dimension) and DTOF @ (see Detail Attributes of Linear Dimensions). An example of a chained Dimension is shown in Figure 12:5.see Labelling.e.3. a DPPT with an unset/illegal DDNM). dimension points or 3D points may also be used as links using: INSE INSE INSE INSE IDP @ IDPL @ IDPD @ or POS @ 12:6 12. It is possible to draw a Dimension that contains Dimension Points that are incompletely defined (for example. Chained Linear Dimension Such a dimension (which is still represented by a single LDIM element) is created by repeating the TO part of the FROM . . P-points.: Chained Linear Dimension. p-lines. Figure 12:6. it is a DPOI) but will not be associated with the identified Design element. Parallel (or Tail) Linear Dimension 12:7 12. Figure 12:6. The effect of the command is shown in Figure 12:7.DRAFT User Guide Dimensioning A Dimension Point may be constructed using DRAFT’s point construction facilities (see Point and Line Construction).: Parallel (or Tail) Linear Dimension.: Use of the INSERT Command illustrates the use of the INSERT command. Figure 12:7. INSERT can be used at Dimension Point or LDIM level. The constructed Dimension Point will have a 3D position (i.e. For example: INSE POS OF @ INSE POS OF ENDP OF @ Other constructions such as INTERSECTION and MIDPOINT can be used.: Use of the SORT DIM Command. 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.0 . Figure 12:8. which can be used at Dimension or Dimension Point level. 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). The effect of the INSERT command is to create a new Dimension Point of the appropriate type at the correct position in the owning LDIM’s member list. Use of the SORT DIM Command An example of a parallel Dimension is shown in Figure 12:8. Use of the INSERT Command Dimensions will be drawn in the same order as the LDIM’s member list order. chained dimension 12.DRAFT User Guide Dimensioning A parallel Dimension can be produced simply by setting the LCHA attribute of an LDIM as appropriate: LCHA PARA LCHA CHA .3. The Projection Line Clearance (PLCL) is the distance between the dimension point and the projection line at the dimension point end.) Figure 12:9.set using cursor . These comments also apply to the OSHT attribute (see below).parallel dimension . Following this initial setting. These values are cascaded down to Dimension level when those elements are created subsequently. not from Dimension level. When setting PLCL with the cursor. PLCL and DOFF are given initial default values at Layer level when the Layer is created.0 . the resulting (paper) coordinate that does not lie in the same axis direction as the projection line is ignored. Key Attributes of a Linear Dimension Note that OSHT.(at Dimension Point level): set to owning Dimension PLCL value PLCL may be set at Dimension or Dimension Point level. an attribute set to ‘default’ at Dimension Point level will take its value from the same attribute of its owning Dimension element (if appropriate). 12:8 12. PLCL set at Dimension level (which becomes the ‘default’ PLCL) will apply to all subsequently created Dimension Points. Examples of setting this attribute are: PLCL 5 PLCL @ PLCL DEF .3 Principal Attributes of Linear Dimensions Those attributes of a linear Dimension that most affect its general appearance are shown in Figure 12:9. PLCL set at Dimension Point level can only be reset from the same Dimension Point.: Key Attributes of a Linear Dimension.set PLCL to 5mm . (Default values are shown in brackets. Negative clearances may be specified. the dimension line position.at Dimension Point level): set to owning Dimension OSHT value (See PLCL description for further comments relating to OSHT.DRAFT User Guide Dimensioning The Projection Line Overshoot (OSHT) is the distance by which the projection line ‘overshoots’ the end of the dimension line. DOFF has a related attribute DPOS . Examples of the relevant commands are: DOFF 20 DPOS @ DIM ABSOLUTE DIM OFFS . . Negative overshoots may not be specified.: Key Attributes of a Linear Dimension are: Dimension Line Offset (DOFF) Projection Line Direction (PLDI) Dimension Line Direction (DIR) .convert DOFF to DPOS .0 .setting one will unset the other. p-point or p-line direction).set DOFF to 20mm .set OSHT to 5mm . removing the need to move back up the hierarchy having just created a new LDIM. DOFF and DPOS both control the position of the dimension line and so are mutually exclusive . Default East.OSHT defined by a ‘constructed point’ see Point and Line Construction.convert DPOS to DOFF When setting DPOS.) The other three attributes shown on Figure 12:9. If a dimensioned element is moved. then if DOFF is used the whole Dimension will also move.the distance by which the dimension line is offset (in the projection line direction) from the 2D position of the first dimension point. Examples of setting this attribute are: OSHT 5 OSHT @ OSHT @ OSHT TOP /CIRCLE1 OSHT DEF .set DPOS using cursor . . . 12:9 12.set using cursor .the angle between the projection line and the dimension line. the resulting (paper) coordinate that does not lie in the same axis direction as the required offset is ignored.the direction of the dimension line (an explicit compass direction. DPOS is a fixed 2D paper coordinate through which the dimension line will pass. if DPOS is used then the dimension line will still pass through the same point (but the projection lines will be adjusted to suit).set using cursor . An important feature of the above attributes is that they can be set at Dimension Point level. set PLDI with cursor . This avoids an unexpected flip in the projection line text orientation.set PLDI to explicit compass direction .set PLDI to 75 degrees .: Definition of ‘True Length’ and Figure 12:11. Definition of ‘True Length’ 12:10 12.: Effect of True Length Attribute Settings. P2 DOWN P2 P1 P1 (i) (ii) DIR TRUE gives distance as in (i) not as in (ii) Figure 12:10.set PLDI to nominated p-point direction Note: Projection line direction is treated as 90 degrees when it is nearly but not quite 90 degrees. See Figure 12:10.0 .DRAFT User Guide Dimensioning The projection line direction is set by commands such as: PLDI 75 PLDI N10W PLDI @ PLDI @ . 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). Points to note about the true length facility are: • • The true length is 2D. which turns out to be inappropriate. 12:11 12.e.‘uppings’ are ignored. unless the points are in line. True length is meaningless for a Dimension with more than two points.DRAFT User Guide Dimensioning Figure 12:11.0 . i.: Effect of True Length Attribute Settings has been created without regard for the Dimension direction. Effect of True Length Attribute Settings The true length facility can be useful when it is not clear what explicit direction to set in order to achieve the desired result. Setting TLIN TRUE produces the desired picture. The bottom left-hand dimension in Figure 12:11. not a slope length . the length is orthographic. using the command: DIR IDP @ (This command will set the DDNM attribute to the name or reference number of the primitive concerned.0 . Figure 12:12.3. a parallel dimensions may be produced in a truncated form. such a point cannot be used as one of the first two points of a true length.4 Detail Attributes of Linear Dimensions To save space on the paper. 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).: Parallel Dimension Line Spacing shows the effect of varying the spacing. Figure 12:12.turn off truncation For non-truncated parallel dimensions. which has two forms as shown in the examples below.the calculated spacing cannot be less than this minimum.: Parallel (or Tail) Linear Dimension.set separation with cursor In a macro. Note that the minimum separation is governed by the DMSP attribute . 12:12 12.) 12. Truncated Parallel Dimension The truncation is produced by the TRUNCATE command.truncate affected dimension lines by 5% .set separation to 30mm . DIR will be unset and TLIN set to FALSE.DRAFT User Guide Dimensioning • Since a DPBA Dimension Point relies on the existence of a predefined dimension direction. and the PPDI attribute to the appropriate p-point number. It is possible to set the dimension direction to that of a p-point.truncate dimension lines to 10mm from nearest dimension point . Example: DMSP 30 DMSP @ . The spacing is controlled by the Dimension Line Separator Attribute (DMSP). TRUNCATE BY 5 TRUN TO 10 TRUN OFF .: Truncated Parallel Dimension shows the truncated form of the dimension shown in Figure 12:8. Figure 12:13. the separation can also be set in terms of Sheet or screen coordinates. the dimension line spacing will automatically be adjusted to accommodate two or more lines of text if these are input.: Dimension Line Text. left hand) DMTX ’ACCESS SPACE #/#DIM’ (see Figure 12:14.: Dimension Line Text. although in the latter case the text input will attached to all the dimension lines involved. Dimension Line Text #DIM in the example above takes the value of the dimension.0 . Dimension line text may be set at Dimension Point or Dimension level.see Intelligent Text.DRAFT User Guide Dimensioning Figure 12:13. right hand) Figure 12:14. #DIM is a simple case of intelligent text .(at Dimension Point level): set dimension text to that of owning Dimension 12:13 12. Note that in the case of non-truncated parallel dimensions. Associated commands are: DMTX DEFAULT . Parallel Dimension Line Spacing The initial value of DMSP is cascaded down from LAYE level Dimension line text (DMTX) is set by a command of the form: DMTX ’text’ Example: DMTX ’ACCESS SPACE’ (see Figure 12:14. 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. Dimension text angle can be controlled using the DTANGLE attribute.DTOF defined by a ‘constructed point’ . By default the text is centred on middle of the dimension line. If the text is not external.move dimension text origin 5mm along axis parallel to projection line in text up vector direction (= perpendicular to dimension line in most cases) .move dimension text origin to cursor position . STANDARD is the default setting for Dimension elements. external dimension line text. not Dimension Point value .equivalent to DTOF 0 0. Reducing the text character size (see below) may result in their being enough room to display the text parallel to the dimension line. Note that if there is insufficient space between the ends of two projection lines to enable the dimension line text to be fitted in parallel to the dimension line it will be automatically rotated by 90 degrees.i. the standard position .move x coordinate of dimension text origin to cursor position (y coordinate not changed) . The dimension text origin is at the centre of and approximately half a character height ‘below’ the text.0 . when it is drawn parallel to the projection-line . For example: DTOF 0 5 . Possible settings are: 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. This is available both at dimension and dimension point level.e. The HORIZONTAL and VERTICAL settings cause the dimension line text to be drawn respectively horizontally or vertically in the VIEW. but its position relative to the dimension line may be varied by changing the setting of the dimension text offset (DTOF) attribute. 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.DRAFT User Guide Dimensioning Dimension text is automatically centre-justified. then its position is constrained to lie between the projection lines. By default the 12:14 12.use default Dimension offset value.change y coordinate of dimension text origin by 5mm (x coordinate not changed) DTOF @ DTOF N 1 @ DTOF N 2 5 Note also: DTOF DEF DTOF STAN .see Point and DTOF ENDP OF /LINE1 QUAL X500 Y500 Line Construction. 0 . 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.: Projection Line Text. Otherwise the setting at the Dimension Point is used. If the text would not be external in the STANDARD case. 12:15 12. This is the default setting for Dimension Points. By default the text is positioned just above the middle of the dimension line. This allows the DTANGLE value to be taken from the Dimension element (LDIM or ADIM). then its position is constrained to lie between the projection lines. Dimension Line Text Angle Projection line text (PLTX) is set and manipulated in a similar way. Figure 12:15. then its position is constrained to lie between the projection lines. For example. The DEFAULT setting is only available at Dimension Points. If the text would not be external in the STANDARD case.DRAFT User Guide Dimensioning text is centred on middle of the dimension line. the commands: PLTX ’PUMP /1501A’ PLTX ’PUMP /1501B’ (each at the appropriate dimension point level) could be used to give the text shown in Figure 12:16. DRAFT User Guide Dimensioning Figure 12:16. not Dimension Point setting Projection line text axes are oriented relative to the projection line. 12:16 12. The orientation is controlled by setting the PTOF attribute.0 .use default Dimension setting.no projection line text (the standard option) . Projection Line Text Note also: PLTX STAN PLTX DEF .: Projection Line Text Offset for an example of changing the projection line text offset. Example: PTOF -5 -5 See Figure 12:17. using the commands: PJUST AWAY PJUST CENTRE 12:17 12. .Change y coordinate of projection line text origin by 5mm (x coordinate not changed) Projection line text is justified ‘towards’ the appropriate dimension point by default.DRAFT User Guide Dimensioning Figure 12:17.PTOF defined by a constructed point.Set PTOF by cursor . the standard position . not Dimension Point value .0 .Use default Dimension value.Equivalent to PTOF 0 0.Move x coordinate of projection line text origin to cursor position (y coordinate not changed) . See Miscellaneous Text Facilities. Projection Line Text Offset Other options are: PTOF @ PTOF STAN PTOF DEF PTOF CENTRE OF /CIRCLE1 PTOF N 1 @ PTOF N 2 5 . but may be justified ‘away’ from the dimension point or may be centred on the projection line. Projection text angle can be controlled using the PTANGLE attribute. This allows the PTANG setting to be taken from the Dimension element (LDIM or ADIM). This is the default value for Dimension elements. This is available both at dimension and dimension point level. Possible settings are: 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. 12:18 12. This is the default setting for Dimension Points. The DEFAULT setting is only available at Dimension Points.0 . In these cases. Projection Line Text Justification The initial value of PJUS is cascaded down from LAYE level. otherwise the setting at the Dimension Point is used.DRAFT User Guide Dimensioning Figure 12:18. 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. Projection Line Text Angle The standard character height for dimension line and projection line text is 4mm (cascaded from LAYE level).set dimension line text character height (DTCH) to 2mm .Projection text Font .Dimension text Font .8* character height) Initial settings of these attributes are cascaded down from LAYE level.0 .Dimension text letter height (0.DRAFT User Guide Dimensioning Figure 12:19.Projection line text colour (cascaded down from LAYE’s TX COLOUR) . Other text attributes (present at Dimension and Dimension Point level) are: PLSP PFON DFON DT COLOUR PT COLOUR PTLH DTLH .Projection text letter height (0. See Miscellaneous Text Facilities for details of letter height and text fonts. 12:19 12.Dimension line text colour (cascaded down from LAYE’s TX COLOUR) .set projection line text character height (PTCH) to 2mm Initial settings of these attributes are cascaded down from LAYE level.8* character height) .Projection text line-spacing . but this may be varied by commands such as: DTCH 2 PTCH 2 . in which case its setting will be cascaded down to newly-created dimensions.Change dimension line text to ‘ACCESS SPACE’ EDTEXT PLTX ’DPACE’ ’SPACE’ .: Dimension Line Terminators. Dimension Line Terminators The terminators (DTER attribute) are set by the commands: DTER ARROWS DTER OBLIQUES DTER DOTS DTER OFF Note: The first terminator of a truncated dimension (see Figure 12:12. the target string is ‘ACCESS DPACE’.Change projection line text to 'ACCESS SPACE Note: When editing intelligent text the intelligent text code itself must be specified. or can be DEFAULT. Dimension line terminators are arrowheads by default. dots. not the resultant text. in which case FTER assumes the same setting as DTER. The first terminator will be drawn 25% larger than the remainder. Figure 12:20. 12:20 12. but may be obliques. In the following examples. = ‘ACCESS SPACE’ mistyped: EDTEXT DMTX ’DPACE’ ’SPACE’ .see Figure 12:20. FTER can have any of the same settings as DTER. or can be set at LAYE level.0 . See Miscellaneous Text Facilities for full details of the EDTEXT command. FTER is applicable to LDIMs and ADIMs.DRAFT User Guide Dimensioning Dimension line and projection line text can be edited through use of the EDTEXT command. or absent altogether .: Truncated Parallel Dimension) can be set independently using the FTER attribute. Gaps in projection lines are most easily defined using the cursor.Set default gap length to be 15mm . 12. Either of the above commands may have an element name after the main command if the required element is not the current element. 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. i.set size to 4mm (default 3mm The initial settings of DTER and TSIZ are cascaded down from LAYE level.e.4 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.Delete gap specified by cursor . At dimension point level their initial values will be DEFAULT.Specify a default length gap (2mm) centred on given point . Gaps may be highlighted by giving the command: SKETCH GAPS at any element that contains gaps. centred on the gap centre. they use the values from the owning LDIM. A circle will be drawn with diameter equal to the gap length.Delete all gaps on the current projection line or dimension line Up to ten gaps may be inserted in the projection line.0 .DRAFT User Guide Dimensioning The size of the terminator is controlled by the TSIZ attribute: TSIZ 4 . The line styles and colours used for dimension and projection lines may be set by DLSTYLE integer/line_pattern. 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. The command: ERASE GAPS will remove the circles.Specify a 10mm gap centred on given point . and delete all other gaps in line . A Radial Dimension does not own Dimension Point elements. See Colours and Styles for details of colours and line styles. 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.Specify gap by giving start and end points . Examples of the relevant commands are: GAP @ GAP AT @ SETDEF GAP 15 GAP AT @ L 10 GAP OVER @ GAP DELETE @ GAP DELETE ALL .Specify gap start and end points with cursor. with either the start and end points or a mid point and a length being specified. Principal Features shows the principal features of an RDIM and Figure 12:22. An example is DIAM of a CYLI (the diameter of a cylinder) or FRAD of a PAVE (fillet radius of a Panel Vertex). with leader lines Figure 12:22.Examples 12:22 12.Principal Features Diameter dimension on a CYLI. no leader line Radius dimension on a CYLI.see Pitch Circle Dimensions. Dimension Text Dimension Origin Leader Line (optional) Dimension Line Terminator Figure 12:21.0 .: Radial Dimension . Figure 12:21. A Pitch Circle Dimension (PDIM) is another form of radial dimension . Radial Dimension . no leader line Diameter dimensions on filleted Panel Vertex (PAVE) elements.: Radial Dimensions Examples shows examples of types of RDIM.DRAFT User Guide Dimensioning a radius is to be drawn. Radial Dimensions . The default value of AKEY is DIAM. SLCY. NCTO). This is an attribute of the RDIM itself. This is a word attribute that stores the code of a dimensional attribute of the DESIGN element type that is to be dimensioned. CTOR. The following table shows which attributes of which DESIGN element types may be dimensioned using an RDIM.) This could be (for example) the origin of a CYLI or of a (filleted) PAVE (Panel Vertex). Most of the AKEY settings allowed above are genuine database attributes. Attributes DIAM DIAM DIAM DIAM DIAM DIAM DIAM DIAM DIAM DIAM DIAM DIAM DIAM DIAM DIAM DIAM DIAM RADI RADI RINS RINS RINS RINS DTOP DTOP DTOP DTOP FRAD FRAD FRAD CRAD CRAD ROUT ROUT ROUT ROUT DBOT DBOT DBOT DBOT 12:23 12. defined by the DDNM (Design Data Name) attribute.DRAFT User Guide Dimensioning Radial Dimensions have a dimension centre.i. For a Torus (RTOR. Element Type CYLI NCYL SLCY NSLC DISH NDIS RTOR NRTO CTOR NCTO SNOU NSNO CONE NCON VERT PAVE SEVE The command: Q AKEYLIST (at a Design element) returns the list of possible AKEY settings.e. The other principal attribute of an RDIM is the dimension attribute key. NRTO. (See Radial Dimensions for exceptions to this. and is normally defined by the origin of the element dimensioned. AKEY. For some Design elements it is a genuine attribute. NDIS) and all Cylinders (CYLI. DIAM give the centreline diameter of the element . however. for others it is derived: • • DIAM is a genuine attribute of Dishes (DISH. NSLC). twice the average of RINS and ROUT. the DIAM keyword has different meanings at different elements.0 . NCYL. SEVE).change AKEY to give a radius dimension In many cases it will be unnecessary to define AKEY explicitly. The origin is normally the position of p9 of the vertex. For example for AKEY RINS and DFLAG DIAM. #DIM is a simple case of intelligent text . 12. NDIS) is the knuckle radius. 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. the bottom diameter. 12. DIAM is taken to be DBOT. Both these AKEY settings are only sensible for a sideways view of a tori-spherical dish. the centre of the fillet radius is defined by one of the many p-points of the Vertex (p8 or p9). The default setting is RADIUS. for example: NEW RDIM ON ID @ AKEY RADI .4. The centre of a Radial Dimension is normally defined by the origin of the element dimensioned. The CRAD attribute of a dish is the cap radius.2 Appearance of Radial Dimensions . except for the following AKEY settings: • • • For DTOP and DBOT. For FRAD. For Structural Vertices (VERT. Radial Dimensions .DFLAG Setting The Dimension Text (DMTX) attribute has the initial setting #DIM.Specific Attributes The Radius/Diameter flag (DFLAG) attribute controls whether the RADIUS or DIAMETER is evaluated by the AKEY attribute as well as whether the dimension line is drawn from the centre (Radius) or across the diameter (Diameter). This also applies to DIAM for Snouts and Cones. This also applies to DIAM if the FRAD value is being used. DIAM is taken to be twice the fillet radius (FRAD) if it is set. since the DIAM setting will give a sensible result. 120 240 DFLAG RADI DFLAG DIAM Figure 12:23. However.0 . the Design element can be picked using the IDP @ command.4. SEVE. PAVE. The resulting value will be output on the drawing in place of this codeword.use cursor to define dimension centre .DRAFT User Guide Dimensioning • • For Snouts (SNOU.1 Creating Radial Dimensions The RDIM is defined by the ON command plus optional AKEY syntax.create RDIM element . The centres of these radii are derived. NSNO) and Cones (CONE. the text ’#DIM’ will be evaluated as the inside diameter of the element identified. PAVE) that cannot be picked directly by cursor. which gives the value of the dimension controlled by DLFAG.see Intelligent Text. NCON). This is necessary for vertices (VERT. The RADI attribute of a dish (DISH. 12:24 12. the dimension centre will be the centre of the appropriate end of the primitive. 240 240 DTRA 0 DTFLA CENTRE DTRA 0 DTFLA CIRCUM 240 240 DTRA -10 DTFLA CIRCUM DTRA 10 DTFLA CIRCUM 240 240 DTRA 10 DTFLA CENTRE DTRA -10 DTFLA CENTRE 240 120 DFLAG DIAM DTFLA MIDPOINT DFLAG RADIUS DTFLA MIDPOINT Figure 12:24. for diameter dimensions MIDPOINT is the same as CENTRE.0 . DTRA= 0 (the default value) means that the text origin is positioned at the 2D projection of the circumference of the object dimensioned. MIDPOINT is the midpoint between centre and circumference. the justification is towards the circumference. 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. If the text lies inside the circumference then the text is centre justified unless the DSTYL is LEADER. Text radius can be negative. In the latter case. DDEG @). For DTFLAG CIRCUMFERENCE. 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. The Text Radius Flag (DTFLAG) attribute controls whether the text radius DTRAD (see below) is measured from the CENTRE. For radius dimensions. If the text origin lies outside the circumference then the text is justified towards the centre of the circle.e. The default setting is CENTRE. MIDPOINT or CIRCUMFERENCE of the radial dimension. For DTFLAG CENTRE. a negative value places the text on the opposite side of the centre to its usual position. a negative value means inside the circumference.DTRA Setting 12:25 12. The default value is 0 (horizontal in the VIEW).DRAFT User Guide Dimensioning The Dimension Line Angle (DDEG) attribute controls the angle at which the dimension line is shown. In this last case. This is equivalent to reversing DDEG with a positive DTRA value. relative to the 2D coordinate system of the VIEW. Radial Dimensions . DTOF is a 2-dimensional array attribute.: Radial Dimensions . Horizontal or Vertical depending on the DTANG setting).DTANG Setting for the effects produced by changing DTANG. Further control of the text position in the upvector direction is given by use of the vertical alignment attribute ALIG.: Radial Dimensions . This allows you to align text independently of the character height DTCH.DTANG Setting The Dimension Text Offset (DTOF) attribute defines the displacement of the text position from the text radial position. 12:26 12. The actual position of the text for DTOF(2)=0 will depend on the value of ALIG. The default/initial value of DTOF is (0. Radial. Radial Dimensions . As an alternative to entering two values. DTOF(2).0 .e. DTOF may be set using the cursor. See Figure 12:25. See Figure 12:26. Possible settings are: DTANGLE STANDARD DTANG HORIZ DTANG VERT The default setting of DTANG is STANDARD. See Label Text Manipulation for further details of ALIG.e.DTOF(2) Setting. DTOF @ Note: In Figure 12:26. ALIG=BBODY unless otherwise indicated. In this case the text is orientated radially. i.0). and DTOF(2) in the text ‘upvector’ direction. zero or negative. is always applied in the upvector direction.: Radial Dimensions DTOF(2) Setting for the effects produced by changing DTOF(2).DRAFT User Guide Dimensioning The Dimension Text Angle (DTANGLE) attribute controls the Dimension text angle. Its value may be positive. DTANG STAN DTANG HORIZ DTANG VERT Figure 12:25. DTOF(1) defines the displacement along the text path direction (i. The second component of text offset. 12:27 12. Similarly. for DTANG VERTICAL and text outside the circumference.0 .DRAFT User Guide Dimensioning 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 Figure 12:26. it is preferable to modify the text radius (DTRAD) rather than DTOF(1). positive DTOF(2) adjusts the text position to the left. DTOF(1) is in the direction of the radial displacement outwards from the text radial position. positive DTRAD). DTOF(1) is best left set to zero).DTOF(2) Setting The definition of the direction of application of the first component. for DDEG between -90 and +90. (In this case. Radial Dimensions . the sign of DTOF(1) is determined by the DDEG attribute.e. DTOF(1). for DDEG between 90 and 270. DTOF(1) moves the text up for DDEG between 0 and 180. See Figure 12:27.: Radial Dimensions DTOF(1) Setting . In this case. DTOF(1) is horizontal from the text radial position.Text Outside Circumference. and down for DDEG greater than 180 and less than 360. positive DTOF(1) adjusts the text position to the right of the radial position of the dimension text. DTFLAG CIRCUM. is more complex: For DTANG STANDARD and text outside the circumference (i. For DTANG HORIZONTAL and text outside the circumference. For DTANG Standard. the direction in which DTOF(1) is applied is reversed.DTOF(1) Setting .: Radial Dimensions . Thus for DTANG Horizontal and DDEG=45. when the text is outside the circumference then DTOF(1) adjusts text to the right. and inwards for text inside the circumference. if the text lies inside the circumference. DTOF(1) is always applied in the direction away from the Circumference.Text Outside Circumference In all three DTANG cases.DTOF(1) Setting . However when text is inside the circumference.DRAFT User Guide Dimensioning 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 Figure 12:27. Radial Dimensions . See Figure 12:28. However in this case it is better to leave DTOF(1) set to zero and modify the text radial position DTRAD.0 . then DTOF(1) would move text radially outwards for text outside the circumference. then DTOF(1) adjusts text to the left.Text Inside Circumference. 12:28 12. The default setting will be OFF. If the text is horizontal.DFLAG Setting. the line will be extended to underline the text if indicated by the DTUL attribute (see below). If DTUL is ON. 12:29 12. then a horizontal line will be drawn from the radial dimension line to the actual text position. Whatever the text orientation. the leaderline will always be extended to underline the text even if this causes it to pass through the text string. The position of dimension text is controlled by the Dimension Text Offset (DTOFF) attribute .: Example RDIMs in LEADERLINE Style for examples of the LEADERLINE style (all shown with DTUL ON). Radial Dimensions . The LEADERLINE style shows a radial leaderline from the circumference to the text radial position.) If the dimension text lies inside the circumference. No dimension-line will be drawn. This indicates whether the leaderline is extended to underline the text or not. (See Figure 12:23. This style shows a radial dimension line with terminators. Possible settings are: DSTYLE DIMLINE DSTYLE LEADERLINE DSTYLE EXTERNAL The default setting of DSTY is DIMLINE.see earlier in this Section.DTOF(1) Setting . controls the overall dimension style. then the leaderline will be extended horizontally to the text offset position. DTUL is ignored for DSTYL DIMLINE unless the text radial position is outside the circumference.0 . The line will be drawn through the text offset position . DTUL. See Figure 12:29. combined with DTANG.Text Inside Circumference The Dimension Style (DSTYLE) attribute. The dimension line will be extended beyond the circumference of the object dimensioned if the text radial position (DTRAD attribute . Text underlining will be controlled by the Dimension Text Underlining attribute.see earlier in this Section) lies outside the circumference.: Radial Dimensions . For DFLAG DIAM this is drawn across the diameter with two terminators.thus there will be overlining for ALIG TBODY. then the dimension line will be gapped if the text crosses it. for DFLAG RADI this is drawn from the centre to the circumference with a single terminator. If the text is horizontal.DRAFT User Guide Dimensioning 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 Figure 12:28. The general attributes are: The Dimension Terminator attribute DTER . two short radial lines are drawn outwards from the circumference with terminators on the circumference. Example RDIMs in EXTERNAL Style 12. The Terminator Size attribute TSIZ . These attributes will be cascaded down from the owning LAYE.3 Appearance of Radial Dimensions .: Example RDIMs in EXTERNAL Style for examples of the EXTERNAL style (all shown with DTUL ON). For Radius dimensions with EXTERNAL style the appearance depends on the text radial position.see Detail Attributes of Linear Dimensions for details. See Figure 12:30. If the text radial position lies outside the circumference.4. which are also used by Linear and Angular Dimensions (see Angular Dimensions) and Dimension Points.0 . Example RDIMs in LEADERLINE Style The EXTERNAL style is a variant on the Dimline style.DRAFT User Guide Dimensioning 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 Figure 12:29. If it lies inside the circumference.see Detail Attributes of Linear Dimensions for details. For Diameter dimensions. The attribute setting DEFAULT is not available for Radial Dimensions. then a single short radial line is drawn outwards from the circumference with a terminator on the circumference.General Attributes In addition to the attributes described in the previous section there are further attributes which control the appearance of the dimension. 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. 12:30 12. then one line is extended to the text offset position (with optional text underlining). If the text radial position lies outside the circumference. 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 Figure 12:30. for DFLAG RADIUS only one arc is drawn. This controls the distance by which the crosshairs overshoot the circle circumference.DRAFT User Guide Dimensioning The Dimension Line Style and Colour attributes (DLSTYLE. .cascaded from CHEI on LAYE . i. The command: GAP TIDY deletes unused gaps. Dimension Text will also have the following attributes. using the command: CHOSHT @ Angle Subtended ASUB .Ancillary Graphics Attributes Additional attributes are provided to control ancillary graphics as follows: Marker Style/Colour (MSTYLE/MCOLOUR). This is in addition to the gap under the dimension text that is inserted automatically in the dimension line. Note that ASUB=180 generates a circle for a diameter dimension. See Detail Attributes of Linear Dimensions for details. See Miscellaneous Text Facilities for details of text fonts. See Colours and Styles for details of colours and line styles. 12:31 12. These control the appearance of the optional horizontal and vertical fixed crosshairs that mark the centre of the circle/arc being dimensioned.attribute derived from DTCH.4 Appearance of Radial Dimensions . MSTYLE may be set to OFF to suppress the marker. no gaps by default. For DFLAG DIAMETER two arcs are drawn. DLCOLOUR) control the appearance of the dimension and leader lines.4. CHSTYLE may be set to OFF to suppress the crosshairs.e.an array of user-defined gaps. similar to those in use for LDIMs and ADIMs: Vertical Alignment ALIG Font DFONT Dimension Text Colour DTCOLOUR Character Height DTCH Letter height DTLH . one at each end of the dimension-line.see Detail Attributes of Linear Dimensions for details. 12. CHOSHT can be set using the cursor. .cascaded from TXCOLOUR on LAYE. Crosshairs Line Style/Colour (CHSTYLE/CHCOLOUR). For details of setting colour and style attribute values see Colours and Styles.cascaded from the LAYE. These control the appearance of the optional marker at the circle/arc centre. These control the appearance of projection arcs. The gaps defined in this array will be applied to the dimension. The midpoint of these arcs will intersect the dimension-line.cascaded from FONT on LAYE. This controls the angle subtended by the optional projection arcs at the circle circumference. .default 0. The Gaps array attribute GAPS . Crosshairs Overshoot distance CHOSHT .default value 6. The initial values are cascaded down from LAYE level.0 .and leader lines of the Radial Dimension. See Label Text Manipulation for further details of ALIG . This value can be negative. Projection Line Style/Colour (PLSTYLE/PLCOLOUR). 5 Creating Radial Dimensions using the Cursor Note: The creation methods given here are applicable to RDIMs and PDIMs (Pitch Circle Dimensions) . In addition. Reset causes the position of the current ‘hot spot’ to be reset to its database position. the second will define the circumference of the dimension. RPPT element) or 3D positions (Radial Dimension Position Point.) The form also contains the point construction Option list button that allows positions to be defined in terms of end-points. A PDIM will be drawn when two significant dimension points are defined. etc.4. As with RDIMs.5 Pitch Circle Dimensions A Pitch Circle Dimension (PDIM) is a form of radial dimension. not the true 3D distance between these points. which will move as the mouse is moved). The first dimension point will be at the centre of the dimension. In addition to the basic creation method given in Creating Radial Dimensions. These in turn are defined by p-points/p-lines (Radial Dimension P-Point. As with Linear Dimension Points.: Pitch Circle Dimension . and the selected dimension is highlighted with four pickable ‘hot spots’ that allow modification of the DDEG. This projected distance 12:32 12. it is possible to use a RULE to parameterise 3D positions. click on the new position (a transient image of the dimension will appear.other dimensions are RDIMs).0 . (The dimension text origin will be at the cursor crosshair position. then click on OK on the form. giving this command causes the Dimension Modification Form to appear. It is not normally necessary to navigate to the two individual Dimension Points. (Cancel allows the command to be aborted with no change to the dimension. Having created the RDIM/PDIM and defined its position. The dimension points contain no style attributes. some style attributes may be defined by cursor interaction.DRAFT User Guide Dimensioning 12. Delete causes the current ‘hot-spot’ to be deleted or set to a default position. A PDIM is defined by two Dimension Point elements that are owned by the PDIM. The dimension radius will be the distance between the two dimension points as projected into the VIEW. click on the ‘hot spot(s)’ that you wish to move.) It will not modify DTOF. A PDIM contains the same style attributes as an RDIM (see Appearance of Radial Dimensions . DTANG can be modified using the Text angle option button.4. 12.6 Modifying Radial Dimensions through Graphical Interaction A powerful facility for modifying an existing radial dimension is provided by the command MODIFY @ Having made the dimension you wish to modify the current element.Specific Attributes. but does not have DDNM/ DDNX and AKEY attributes. To modify the dimension. DTRA and DTOF attributes of the dimension. 12. RPOI element).example shows a simple example PDIM (bold line . DIM @ will cause both dimension angle DDEG and text radius DTRAD to be defined in one go. Figure 12:31. which may be used to draw radius. It is not possible to create more than two Radial Dimension Points. and diameter dimensions between two independently definable points. intersection points.see Pitch Circle Dimensions. the meaning of the ’#DIM’ dimension text is defined by the DFLAG attribute. creates an RPPT Position centre point on p-line (start) .creates an RPOI Position centre point on p-point position .0 .example 12. Pitch Circle Dimension . For example: PCEN IDP @ PCEN IDPL @ PCEN IDPD @ PCEN POS @ PCEN POS IDP @ PCEN POS IDPL @ Position centre point on p-point .creates an RPOI 12:33 12.DRAFT User Guide Dimensioning defines the value reported in the dimension text.1 Creating Pitch Circle Dimensions The PDIM position is defined by two p-points.5. p-lines or positions.creates an RPOI Position centre point on p-line (start) position . for example: NEW PDIM PCEN IDP @ PCIRC IDP @ NEW PDIM PCEN POS @ PCIRC IDP @ Create PDIM Define centre point as p-point position Define circumference point as p-point position Define centre point as 3D position The PCENTRE command defines or redefines the centre point of a PDIM.creates an RPPT Position centre point at a 3D position . This is consistent with the functionality for Linear Dimensions (LDIMs) with Direction TRUE (see Principal Attributes of Linear Dimensions). Figure 12:31.creates an RPPT Position centre point at a distance along a p-line . These define the Dimension Points and set DDEG for a PDIM but do not set DTRAD. DDEG normally remains unchanged.6.1 Angular Dimensions Angular Dimensions and How to Create Them This section concentrates on those features that are unique to angular dimensions. Each dimension arc and projection line may have a piece of text associated with it.creates an RPOI This creates or redefines the circumference point of the PDIM. Between these lines a dimension arc is drawn centred upon the dimension origin. the command: DDEG TRUE will change DDEG so that the dimension line passes through the circumference point.0 . an RPPT or RPOI element is created as appropriate. then this must be set or deleted explicitly at the RPOI. then this command will delete it and create a point of the correct type. These directions are projected onto the drawing and are represented by projection lines.: Single Value Angular Dimension shows a simple angular dimension. If a RULE is required to parameterise the 3D position. Figure 12:32. Example: NEW PDIM PCEN IDP @ PCIRC @ Individual RPPT Dimension Points may be redefined using the ON command. If necessary the existing circumference point is deleted.creates an RPPT Position circumference point at a distance along a p-line creates an RPPT Position circumference point at a 3D position .creates an RPPT Position circumference point on p-line (start) .DRAFT User Guide Dimensioning PCEN POS IDPD @ PCEN @ Position centre point at a distance along a p-line . 12:34 12. The PCIRCUMFERENCE command defines or redefines the Circumference point of a PDIM: PCIRC IDP @ PCIRC IDPL @ PCIRC IDPD @ PCIRC POS @ etc (as for PCEN) Position circumference point on p-point . Individual RPOI Dimension Points may be modified by the POS command. 12. The simplest type of Angular Dimension consists of a pair of directions in the Design model (the dimension directions) that radiate out from the dimension origin. However.6 12. As with the PCEN command. A PDIM may be defined using two cursor hits.creates an RPOI Position centre point on a p-point (and set DDEG if possible) If the existing centre point is the wrong database type. the Dimension will appear on the display. with the last direction becoming the current element. Figure 12:32. NPPT being the specific p-point within the Design element (the origin by default). A pair of Dimension Direction elements will have been automatically created. and if parallel the dimension arcs may be truncated. Any p-point can be nominated to define a Dimension Direction by replacing the FROM @ command above by FROM IDP @.Use cursor to nominate items defining first and second Dimension Directions Having pressed Enter when the confirmation command line appears. The DPPT also has DDNM and NPPT attributes.Use cursor to nominate Dimension origin . NPPT will be set to a default value that equates to the origin of the element named by the DDNM. This could be done by typing the following commands. chained or parallel. starting at Layer level: NEW ADIM ON ID @ FROM @ TO ID @ . In the example above. In this example the Dimension Directions will be DPPT elements .0 . Single Value Angular Dimension An Angular Dimension cannot be drawn until its origin and dimension have been properly defined. 12:35 12. The NPPT attribute of the ADIM is set to the p-point that is the origin position.DRAFT User Guide Dimensioning Angular Dimensions share many of the properties of Linear Dimensions. In the case of parallel dimensions the projection lines will be automatically ‘gapped’ if their overshoot is sufficiently large (for instance where there is projection line text) to cause them to cross dimension arcs. In this case DDNM is set by the FROM or TO keyword to the name of the Design element which defines the Direction. The ON command sets the DDNM attribute of the ADIM to the name of the element at the Dimension origin. they may be single or multi-valued.Create new Angular Dimension element .the directions are defined by lines drawn from the origin of the ADIM to the specified p-points (in this case the origins of the specified nozzles). An example of a chained Angular Dimension is in Figure 12:33. the projection line direction (as specified by DIR) will appear as projection line text. The above examples show the easiest way of creating ADIM elements. similar considerations also apply when defining the Direction elements. The dimension origin can be defined explicitly as a 3D point.: Chained Angular Dimension. If the PLTX attribute is set to ’#DIR’. 12:36 12. The Directions will be drawn in the order in which they appear in the list.0 . but many other methods are available. APPT elements would be created by a sequence such as: NEW ADIM ON ID @ FR DIR IDP @ TO DIR IDP @ Here the PPDI attribute of each APPT will be set to the number of the p-point of the nominated element that defines the Dimension Direction. #DIR is an example of intelligent text . In each example above. and the rotational direction between the Directions is determined by the minor arc between the first two Directions. 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. TO defines a Direction after the last item in the list.see Intelligent Text. the FROM keyword defines the Direction at the start of the Dimension’s member list. as a ppoint. as a Branch Head or Tail or as (the origin of) any Design element.DRAFT User Guide Dimensioning The other types of Dimension Direction that may be owned by an ADIM element are: • • • DPOI ADIR APPT allows the direction to be defined by any given 3D position allows the direction to be defined by any given 3D direction allows the direction to be defined by any given p-point direction DPOI elements would be created by a sequence such as: 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. : Parallel Angular 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. The SORT DIM command can also be used with Angular Dimensions to reorder any incorrectly ordered Directions. Chained Angular Dimension Such a dimension is created in a similar way to a chained Linear Dimension.0 . 12:37 12. An example of a parallel Angular Dimension is shown in Figure 12:34. 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 with Linear Dimensions.DRAFT User Guide Dimensioning Figure 12:33. the PLDI (projection line direction). 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. DIR (projection line direction) and TLIN (true length) attributes do not apply to Angular Dimensions. 12.namely DOFF.are all the same as or similar to those for Linear Dimensions. OSHT and PLCL .0 .2 Principal Attributes of Angular Dimensions Those attributes of a linear Dimension which most affect its general appearance . Those attributes that relate to the dimension line of a Linear Dimension relate to the dimension arc of an angular dimension. DOFF for an Angular Dimension is the radius of the dimension arc and is set by the DIM RAD command (cf DIM OFFS). Clearly. 12:38 12. and are set in the same way.6.DRAFT User Guide Dimensioning Figure 12:34. The standard value is that given by the minor arc from the first to the second dimension point. DPOS. The SENSE attribute enables the rotational direction of the Dimension to be changed. LCHA. 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. and those attributes that relate to the projection line of a linear dimension relate to the dimension radius of an Angular Dimension. Parallel Angular Dimension A parallel Dimension can be produced simply by setting the LCHA attribute of an ADIM to PARA (a chained dimension has LCHA CHAI). The default setting.all dimensions are treated as chained. However. At ADIMs the default setting of attribute DMTX is ’#DIM~0’.identify Dimension nominated by cursor .7 Identifying Dimensions The cursor may be used to identify Dimensions and Dimension Points/Directions as follows: ID LDIM @ ID ADIM @ ID @ . The setting of the LCHAIN attribute is ignored in this case . (See Intelligent Text for details of ‘hash codes’. which is output to one decimal place. 12.with the coordinate reported in the projection-line text. This produces a degree symbol after the angle value.6.g. standard or reverse sense should be used with parallel dimensions. Dimension arc and projection line (dimension radius line) text is set and positioned in the same way as for linear dimensions.3 Detail Attributes of Angular Dimensions Angular Dimensions have the same TRUN and DMSP attributes as Linear Dimensions.0 .identify Dimension Point/Direction nominated by cursor Dimensions can also be highlighted . 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.DRAFT User Guide Dimensioning It is also possible to specify an explicit rotational sense: SENSe CLOCkwise or SENSe ANTIclockwise However. causes both dimension.8 Suppressing the Display of Dimension and Projection Lines The display of either the dimension or projection lines of a Linear or Angular Dimension may be suppressed using the DLFG attribute of the LDIM: DLFG PROJ causes only the projection lines of a Dimension to be drawn. 12. DLFG DIM causes only the dimension lines of a Dimension to be drawn. Projection line gaps are also handled in the same way. e.and projection lines to be drawn: DLFG ALL 12:39 12.) The DTANGLE (Dimension text angle) attribute is available for Angular Dimensions and their Dimension Points. This enables coordinate dimensions to be output . #DIM.see Highlighting Displayed Elements. See the manual AVEVA DRAFT Administrator Application User Guide for more details about rule sets. an elevation Dimension is required between a Valve and an Elbow in skewed pipe. For example. Sensible graphics can be achieved by the following: NEW LDIM FROM valve_id NEW DPOI RULE SET POS (E (POS(1) OF <valve_id> WRT /* ) $ (N (POS(2) OF <valve_id> WRT /* ) $ (U (POS(3) OF <elbow_id> WRT /* ) RULE EXEC POS A copy of this Dimension Point can be used in other Dimensions to dimension between the Elbow and the Easting/Northing of the Valve. be given from any position in the hierarchy. LDIM. where element_identifier would typically be a DRWG. VIEW or LAYE. 12. The above command will affect the current element (and elements below it).10 Updating Dimensions If the VIEW XYPS is changed. Such a command can. or if the positions of Design elements are changed. for example.DRAFT User Guide Dimensioning 12. This can be avoided by using a constructed Dimension Point. of course. The ANNO keyword can be omitted if element_identifier defines a piece of annotation only. This constructed Dimension Point can then be used with either Component to draw Dimensions with sensible graphics.0 . the positions of Dimensions on the Sheet will not change automatically. only annotation relating to the named element will be updated. whose position is defined by a RULE set which gets one coordinate of position from one Component and the remainder from another. Commands of the form: UPDATE element_identifier ANNO are also valid. SHEE.9 Dimensioning Skewed Pipe in Isometric Views Dimensions on skewed Pipe in isometric views can have misleading graphics. For the necessary repositioning to occur the command: UPDATE ANNO must be given. 12:40 12. .11.3 Setting Dimension Directions .create a Dimension start point .sets DIR .create a dimension Point at a p-line 12.0 .create a dimension Point at a p-point . SORT DIM DIR value PLDI value DIR TRUE .DRAFT User Guide Dimensioning 12.create a Dimension Point in order .create a dimension Point at a 3D Design World coordinate .sets TLIN true 12:41 12.11.create subsequent Dimension Points .convert a DOFF attribute to DPOS (absolute paper coordinate) 12. .11 Summary of Commands 12.1 Creating Linear Dimensions . DPOS @ DOFF value DIM OFFS DIM ABS .sets PLDI .set Dimension line position through a paper position (DPOS) .set projection line direction via a direction or angle . . . or you can use a design p-point direction .rearrange Dimension Points into a logical sequence .convert a DPOS attribute to DOFF (offset distance from the first dimension point) .create a Dimension Point ‘after’ (with respect to dimension direction) nominated Design item .2 Positioning the Dimension Line . FROM ID @ TO ID @INSERT ID @ TO AFT ID @ TO BEF ID @ TO POS @ TO IDP @ TO IDPL @ . .set dimension line direction to be that calculated from the first & second p-points .sets Dimension direction & uses standard PDMS direction syntax.11.create a Dimension Point ‘before’ (with respect to dimension direction) nominated Design item .set a Dimension line position as an offset from the first Dimension Point explicitly . . creates an RPPT .creates an RPPT .4 Creating and Modifying Radial Dimensions .defines centre point as p-point position .defines Dimension Points and sets DDEG 12:42 12. .11.modifies DDEG.positions centre point at a 3D position .defines centre point as 3D position .position centre point on p-line (start) . NEW PDIM PCEN IDP @ PCIRC IDP @ NEW PDIM PCEN POS @ PCIRC IDP @ PCEN IDP @ PCEN IDPL @ PCEN IDPD @ PCEN POS @ PCEN POS IDP @ PCEN POS IDPL @ PCEN POS IDPD @ PCIRC IDP @ PCIRC IDPL @ PCIRC IDPD @ PCIRC POS @ NEW PDIM PCEN IDP @ PCIRC IDP @ .11. .0 .creates an RPPT .position centre point at a 3D position .position centre point on p-point .creates an RPOI .creates an RPOI .positions centre point at a distance along a p-line .creates an RPPT .positions centre point on p-line (start) position .creates an RPOI : etc .creates RDIM element . NEW RDIM ON ID @ AKEY word DIM @ MODIFY @ .positions centre point at a distance along a p-line .defines circumference point as p-point position .creates an RPOI .creates an RPPT .position centre point at a distance along a p-line . .use cursor to define dimension centre .sets AKEY to give a diameter or radius dimension as required (default DIAM) . .creates an RPPT .defines both dimension angle DDEG and text radius DTRAD in one go.creates an RPOI . (Dimension text origin will be at cursor crosshair position.5 Creating Pitch Circle Dimensions .) .DRAFT User Guide Dimensioning 12.creates PDIM .positions centre point on p-line (start) . DTRA or DTOF attributes by cursor interaction 12.positions centre point on p-point position .positions centre point on p-point . #DIM) . . or if direction specified .sets DDNM & PPDI. . PPoint.changes rotational sense of angular dimensions 12.change y coordinate of dimension text origin by 5mm (x coordinate not changed) . PH.sets DDNM . Y.set dimension text as text string.6 Creating Angular Dimensions .sets text letter height in mm (=0.sets dimension line colour . e.7 Setting Dimension Line and Dimension Line Text .sets to Dimension default value . options: PA. HT . PL.11.8 * character height) .sets dimension line style to Dimension default value .e.specify the Design item which will be referenced for an Angular Dimension .sets DIR.sets to 0 0 . D. ON ID @ FROM DIR option . . W. DTOF option STAN 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 . DTOF ENDP OF /LINE1 QUAL X500 Y500 . . PT. or if direction specified .0 . HH.sets dimension line colour to Dimension default value . X.move x coordinate of dimension text origin to cursor position (y coordinate not changed) .sets the dimension line position as an offset radius from the Dimension Point .set via cursor-constructed point. Options: .DRAFT User Guide Dimensioning 12.sets dimension text colour to Dimension default value 12:43 12.set dimension text offset distance from origin.sets DOFF first TO DIR option DIM RAD value SENSE REV SENSE STAN .sets DIR . E. Unsets from #DEF (i. X.g.sets text character height in mm .sets DDNM & PPDI.sets dimension text colour .11. N.creates subsequent dimension Point with direction set as p-point specified .creates a Dimension start point with the direction set as the ppoint specified .sets dimension line style . IDP. S. . move x coordinate of projection line text origin to cursor position (y coordinate not changed) .set projection text offset distance from origin.sets projection line text colour . Unsets from #DEF (i.sets projection line style to Dimension default value .sets dimension text angle to HORIZONTAL .sets to Dimension default value .sets projection text character height to Dimension default value . Options: .sets text character height in mm .sets projection text angle to HORIZONTAL 12:44 12.sets text letter height in mm (=0. PTOF option STAN DEF @ PTOF N 1 @ PTOF N 2 5 PLTX ’text’ 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 .sets dimension text angle to STANDARD .sets to 0 0 .set projection text as text string.sets projection text justification .11.sets projection line colour .sets projection line text colour to Dimension default value .sets via cursor-constructed point. Options: . CENTRE OF /CIRCLE1 . .g.8 * character height) .sets dimension text angle to DEFAULT 12.8 Setting Projection Line and Projection Line Text .sets dimension text angle to VERTICAL .sets dimension text angle to EXTERNAL .DRAFT User Guide Dimensioning DTANGLE STAN DTANG HORIZ DTANG VERT DTANG EXTERN DTANG PARA PTANG DEF .e.change y coordinate of projection line text origin by 5mm (x coordinate not changed) .sets dimension text angle to PARALLEL . e.sets projection line colour to Dimension default value .0 .sets projection line style . #DIM) . projection line overshoot defined by a constructed point .for Parallel Dimensions.for Parallel Dimensions.11. LCHA PARA LCHA CHAI DMSP value DMSP @ TRUN BY value TRUN TO value DTER option FTER option TSIZ 4 OSHT value OSHT @ OSHT TOP /CIRC1 PLCL value PLCL @ . DOT.specifies a gap by giving a single point .11.set terminator size to 4mm (default 3mm) .10 Miscellaneous Operations on Dimensions .deletes a gap identified by cursor .sets projection line clearance explicitly .specifies a default length gap of 2mm in a projection line by a single point .sets projection line overshoot using cursor .sets default gap length . . Options: ARR. GAP @ GAP AT @ SETDEF GAP value GAP AT @ L value GAP DELETE @ GAP DELETE ALL GAP TIDY .sets projection line clearance using cursor 12:45 12.deletes all unused gaps (Radial Dimensions only) 12. .sets projection text angle to VERTICAL .specifies a gap in a projection line by giving start & finish points .sets dimension type to Chained .for Parallel Dimensions truncates dimension lines to a specified value in mm . OFF. OBL. OFF .set dimension line terminator. sets separation spacing using cursor . .sets projection text angle to STANDARD . sets separation spacing explicitly . . DEFAULT . Options: ARR.sets projection text angle to DEFAULT 12.deletes all gaps on the current projection line or dimension line . DOT.9 Setting Gaps .sets dimension type to Parallel .0 .for Parallel Dimensions truncates dimension lines by a percentage specified .DRAFT User Guide Dimensioning PTANG VERT PTANG STAN PTANG DEF .set first dimension line terminator. OBL.sets projection line overshoot explicitly . VERT.11 Radial Dimensions . default 6. . .combined with DTAN. value can be negative. AKEY option .stores the code of a dimensional attribute of the Design element type that is to be dimensioned.controls angle at which dimension line is shown. HORIZ. EXTERNAL. . Value can be a colour number or pre-defined colour name. .(according to the DTFL setting) of the dimensioned object.controls the drawing colour for the above. controls the overall dimension style.controls whether the text radius DTRAD is measured from the CENTRE. Default DIAM. . default STANDARD. option = OFF (default). . option = CENTRE. Option dependent on Design element type. MIDPOINT or CIRCUMFERENCE. MIDPOINT or CIRCUMFERENCE of the radial dimension.coordinate system of the VIEW. default RADIUS.modifies DTFL and recalculates DTRA to keep same visual appearance. LEADERLINE. Default 0 (horizontal in the VIEW).draw dimension lines only . relative to 2D the DFLA option DDEG value DDEG @ DTFL option . option = DIAMETER or RADIUS. . . Option = DIMLINE.draw projection and dimension lines (default) 12.controls the drawing style used for the optional horizontal and vertical fixed crosshair markers that mark the centre of the circle/ arc being dimensioned. default DIMLINE.draw projection lines only .controls whether the dimension line is drawn from the centre (Radius) or across the diameter (Diameter).radial position of the dimension text origin from the centre or circumference . option = STANDARD. . .11.controls the distance by which the crosshairs overshoot the circle/ arc circumference. DTRA value DTRA @ DTRA FLAG option DTAN option DSTY option CHSTYLE option CHCOLOUR value CHOS value CHOS @ 12:46 12.controls the Dimension text angle. . integer or line pattern.0 .DRAFT User Guide Dimensioning DLFG PROJ DLFG DIM DLFG ALL . Default CENTRE . gives the X and/or Y Sheet coordinate(s) of the 3D position of either the p-point specified by the NPPT attribute or the position specified by the PKEY and PKDI attributes. .(at a PDIM) .(at Dimension or Dimension Point) • • • • • gives dimension direction and Dimension Points (Linear Dimensions) gives dimension origin and Dimension Points (Angular Dimensions) reports whether a Radius or Diameter dimension is required (Radial Dimensions) names the Design element and attribute dimensioned (RDIMs) gives the Radial Dimension Points (PDIMs) Q SETDEF Q DDNM X coord Q DDNM Y coord Q DDNM X coord Y coord . Q DESC .(at a Design element) .(at Dimension Point) • • Q PCENTRE Q PCIRC Q AKEYLIST gives Sheet area occupied by Dimension Text/Projection Line Text . . ASUB 180 generates a circle for a diameter dimension.(at Dimension or Dimension Point) .gives default gap length and PKDI setting .controls the angle subtended by the optional projection arcs at the circle/arc circumference.allows interactive modification of Dimension.11.lists possible AKEY settings for element type 12:47 12.12 Querying . These values may be useful when attempting to position GLABs and SLABs neatly. for DFLAG RADIUS only one arc is drawn. The midpoint of these arcs will intersect the dimension line. .gives circumference point of dimension . For DFLAG DIAMETER two arcs are drawn. with graphical feedback.gives centre point of dimension .DRAFT User Guide Dimensioning ASUB value .(at a PDIM) .0 . MODIFY @ 12. Q EXTENT DMTX Q EXTENT PLTX . one at each end of the dimension line. DPPT. 12:48 12.0 . DELETE NULL ANNO .deletes all RDIM. leaving the PDIM and its centre point still defined. . then only that dimension point will be deleted. if only the second dimension point (RPOI element) is inaccessible. if the first dimension point (RPPT element) is inaccessible.13 Deleting Unwanted Dimension Points .DRAFT User Guide Dimensioning 12. For PDIMs. DPBA and APPT elements with DDNM set to NULREF.11. . then the entire PDIM will be deleted. The Label elements are the General Label (GLAB). or automatically following the definition of a set of rules controlling the elements to which the Labels are to be applied (see Autotagging). Label elements are owned by Layers or Views. showing its principal features and attributes.Label Elements Labels may be created individually. and the Special Label (SLAB). Figure 13:2.DRAFT User Guide Labelling 13 13.: A Typical Label Element illustrates a typical Label. (TXTMs)) exist as members of Label Libraries (LALBs). associated with Design items or Views.1 Labelling Introduction Labels are a form of drawing annotation. SLAB templates (Text Label Templates. comprising text and/or graphics.0 . 13:1 12. SLABs are similar to GLABs except that they are generated from templates rather than individually. DRAFT Database Hierarchy . 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 Figure 13:1. • • • • 13. defined relative to the Label origin.0 . Label Origin. A Typical Label Element The main features of a Label are: • Label Attachment Point. Label Position. Leader Line. Leader Line Connection Point. A position.: A Typical Label Element could be created simply by typing the following (starting at LAYE) level: 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. to which the leader line is drawn. A 2D position within the VIEW at which the Label’s origin is placed. The 2D VIEW position equivalent to a user-specified p-point or distance along a p-line or (by default) the origin of the Design item with which the Label is associated. A position within the body of the Label that is used to position it.1 Creating and Manipulating Labels Creating Labels and Label Text The example Label shown in Figure 13:2.DRAFT User Guide Labelling Figure 13:2. this may be an absolute VIEW position or a position relative to the Label’s attachment point.2.2 13. A line from the connection point to the Label attachment point. DRAFT User Guide Labelling 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 Label’s 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: ON PPLIN TOS OF /SCTN4 2500 FROM START ON PPLIN BOS OF /SCTN5 1000 FROM END If the FROM keyword is omitted then FROM START is assumed. When using the ON command if values for NPPT, PKEY and PKDI are not specified then the defaults will be used - any existing values may be overwritten. The Label attachment point can be offset from the DDNM using the APOF (Attachment Point Offset) attribute. This defines an offset position (in VIEW coordinates) measured from the p-point/p-line distance referenced by the Label. The leader line will be attached to this 13:3 12.0 DRAFT User Guide Labelling 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: LEAD ATTA X455 Y677 LEAD ATTA @ The offset may be removed by: LEAD ATTA DELETE (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 LAYE’s 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 BTEX ’NOZZLE 2#/#NAME’ would produce the Label shown in Figure 13:3.: Label Text. Note how the size of the Label frame automatically adjusts to accommodate the specified text. Figure 13:3. Label Text 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’: EDTEXT ’NOZZLE 2’ ’NOZZ 1-2’ change Label text to ‘NOZZ 1-2’ Note: When editing intelligent text the intelligent text code itself must be specified, not the resultant text. See Editing Text for full details of the EDTEXT command. 13:4 12.0 DRAFT User Guide Labelling 13.2.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.2.3 Positioning and Orienting Labels When a Label is created, its origin (held as the XYPS attribute) is placed at a fixed offset (default x 25mm, y 25mm) from its attachment point. The Label origin (and hence the Label) may be moved by the AT @ command, which resets XYPS to the position specified by the cursor. This command calls up the Point Construction Option form, which contains the point construction Option list button which allows positions to be defined in terms of end-points, intersection points, etc. If the Label’s OSET attribute is TRUE then the origin is held as an offset from the attachment point; if OSET is FALSE then the Label origin is held as an absolute Sheet coordinate. Note that the coordinates specified with the AT command (whether explicit or from cursor input) are always taken to be absolute coordinates, irrespective of the OSET setting. To avoid any potential confusion when positioning labels explicitly, several alternatives are available. For example: OFFS X45 Y45 OFFSET ABSOLUTE AT X300 Y200 ABS AT X300 Y200 XYPS 20 20 Set Label origin to given offset coordinates. XYPS set to offset coordinates (from Label attachment point) Convert XYPS (absolute coordinates) to offset coordinates (Label will not move). This is equivalent to OSET TRUE. Convert XYPS (offset coordinates) to absolute coordinates (Label will not move). This is equivalent to OSET FALSE. Set Label origin to given absolute coordinates. XYPS set to absolute coordinates. Set Label origin to given absolute coordinates. XYPS set to offset coordinates (from Label attachment point) Set Label origin as given coordinates, taken as offset if OSET TRUE, absolute if OSET false. (XYPS @ is also available). 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.0 DRAFT User Guide Labelling Labels may be oriented by the ANGLE command, which sets the Label’s 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 Label’s attachment point). For example: ANGLE 30 ANGLE IDP @ ANGLE P2 OF BOX 1 OF /1502B ANGLE PPLIN NA OF /SJ1-1 Set angle of turn to 30 degrees Specify orientation as p-point direction using cursor Specify p-point direction explicitly Specify orientation as p-line direction (of secondary joint) Figure 13:4. Label Orientation 13.2.4 Label Frame Manipulation The Label frame may be drawn or omitted. This is controlled by the LFRAme attribute: LFRA ON LFRA OFF The appearance of the frame is controlled by the LFSTYLe and LFCOLOur attributes. For example: LFSTYL DASHEDMED LFCOLO 4 sets the frame linestyle to DASHEDMEDIUM draws the frame in colour 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.0 DRAFT User Guide Labelling Figure 13:5. Frame Clearance 13.2.5 Hiding Labels A Label’s visibility is controlled by its LVIS attribute: LVIS TRUE LVIS FALSE the label is visible (the default) the label is invisible This facility could be used to hide labels attached to obscured Design elements. 13.2.6 Label Text Manipulation Character height and spacing, and line spacing are all definable, as is the text justification. The set of attributes that control the appearance of a Label text is: CHEI LHEI CSPA LSPA character height (default 4 mm) letter height (0.8* character height) character spacing factor (default 0) text line spacing factor (default 0) 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 (LHEI automatically set to 4.8) 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.0 DRAFT User Guide Labelling Figure 13:6.: Label Text - Character Spacing and Line Spacing illustrates the effects of varying the character spacing and line spacing. Figure 13:6. Label Text - 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 left justified (default) Text centre justified Text right justified right Text aligned with bottom of body (default) Text aligned halfway up body Text aligned with top of body 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.0 DRAFT User Guide Labelling Figure 13:7. Horizontal Justification and Vertical Alignment In Figure 13:8.: Text Base/Body Alignments, the symbol shows the text string origins for BBODY and BASE alignments. For a multi-line text string (as shown), the origin is at the baseline of the first line of text. ALIG BBODY ALIG BASE Figure 13:8. Text Base/Body Alignments 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.0 with the results of the commands being shown in Figure 13:9. the 3D World position specified will be used as the leader-line attachment point (rather than the DDNM and NPPT or DDNM. 13:10 12. or implicitly by specifying that the leader line is to contain a vertical or horizontal portion. A DDNM attribute still has to be specified for the label to be properly defined. The leader line clearance (attribute LLCL. The size of the terminator is controlled by the TSIZ attribute: TSIZ 4 set size to 4mm (default 3mm) The initial settings of LTER and TSIZ are cascaded down from LAYE level.0 . The leader line may be straight or bent. 0mm by default) is set as follows: LLCL 4 clearance 4mm The attachment point offset (APOF). The terminator is controlled by the LTER attribute: LTER ARROWS LTER DOTS LTER OBLIQUE LTER OFF These commands set the Label’s LTER attribute. unset by default.2. If the POS attribute is set.: Bending the Leader Line. This allows labels to be positioned at a calculated position (for example. is set by commands such as: APOF 3 0 sets attachment point offset to be X3 Y0 Labels also have a POS attribute. a dot or nothing. which is set to ‘no terminators’ by default. at a definable distance from the attachment point. 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). PKEY. this distance may be specified by setting either the leader line clearance attribute (LLCL) or the attachment point offset (APOF) a position. which by default is unset. For example: LLEA OFF LLEA ON The leader line may terminate with an arrow.7 Leader Lines The label leader line may be drawn or omitted. This is controlled by the LLEAder attribute. and PKDI attributes).DRAFT User Guide Labelling 13. 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. Examples of commands used to specify the bend point explicitly are shown below. 0 . Bending the Leader Line 13:11 12.DRAFT User Guide Labelling Figure 13:9. See Figure 13:10. bend-point 1 will be set to Offset X0 Y0 if it does not already exist.0 . 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 leader line connection point may change see the bottom illustration of Figure 13:9. In the case of a bent leader line specified as having a horizontal or bent portion.: Bending the Leader Line .: Bending the Leader Line for an example.Horizontal/Vertical Portions for examples of the commands involved and their results. 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. the first point to be defined should be the one nearest the 3D item labelled. When defining two bend-points using a single command. Depending on the position of the bend point. The LSHA attribute defines how the values stored in BPOF are to be interpreted. 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. 13:12 12.DRAFT User Guide Labelling LEAD BENT OFFS X7 LEAD BENT OFFS X0 Y-60 X100 Y-60 LEAD BENT @ LEAD BENT PT 2 @ LEAD BENT PT 2 X722 Y40 LEAD BENT PT 1 OFF X15 LEAD BENT PT 1 DEL LEAD BENT @ @ LEAD STRAIGHT Specify bend point as offset from Label attachment point Specify two bend points Specify bend point using cursor Specify second of two bend points using the cursor Specify second of two bend points explicitly Specify first of two bend points as offsets from Label attachment point Delete first of two bend points Specify two bend points using cursor Return to straight leader line The above commands set the Label’s LSHA (Leader Line Shape) and BPOF (Bend-Point Offset) attributes. The first of these two portions to be specified will be at the end nearest to the attachment point. 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. or to the middle of a box line if the horizontal/vertical portion is specified last. bend-point 2 (if it exists) will be made the new bend-point 1. When deleting bend point 1. will always be drawn specially .0 . Varying the Leader Line Connection Point 13:13 12. Bending the Leader Line .: Varying the Leader Line Connection Point.2. which causes DRAFT to determine the actual leaderline connection point. 13.Horizontal/Vertical Portions If a Label’s position relative to its attachment point is changed then on Drawing regeneration the leader line. or an explicit 2D value. Other settings are ORIGIN. ABC ABC ABC CPOF STAN CPOF ORIG CPOF -3 0 Figure 13:11.8 Varying the Leader Line Connection Point The Leader Line connection point can be offset from its standard position using the CPOF (Connection Point Offset) attribute. which offsets the connection point relative to the Label origin.DRAFT User Guide Labelling Figure 13:10. This is STANDARD by default.you don’t necessarily have to redefine the bend point position. if bent. which puts the connection point at the Label origin. See Figure 13:11. with either the start and end points or a mid-point and a length being specified. Note: For this functionality to be available the Annotation Modification form must be loaded. Delete causes the current hot-spot to be deleted or set to a default position: • • • • • A bend point will be deleted The attachment point will be set to the p-point (i. Cancel allows the command to be aborted with no change to the Label.0 .see Detail Attributes of Linear Dimensions. You can then do one of the following: Click on OK on the form. CPOF STANDARD) The angle of the label will be set to 0.e. A transient image of the Label will appear. APOF 0 0) The connection point will be set to its default value (i. and ADEG attributes of the Label to be modified interactively. CPOF.e. etc. (In the latter case a default gap length will be assumed if a value is not specified. intersection points. and the selected Label is highlighted with pickable hot spots.DRAFT User Guide Labelling 13.10 Modifying Labels through Graphical Interaction You can modify a label graphically by making it the current element and giving the command MODIFY @ The Annotation Modification Form will appear. and click on the new position. 13.2. The form contains the point construction Option list button that allows positions to be defined in terms of end-points. to accept the changes you have made. Reset causes the position of the current hot-spot to be reset to its database position.2. XYPS. 13:14 12. BPOF. click on the hot spot that you wish to move. The Label position will not be affected.) Examples of the relevant commands are: GAP @ GAP AT @ GAP AT @ L 5 GAP OVER @ GAP DELETE @ GAP DEL ALL GAP TIDY Insert gap by specifying start and finish points with cursor Insert gap of default length centred on cursor position Insert 5mm gap centred on cursor position Insert gap by specifying start and finish points with cursor. which will move as the mouse is moved.9 Leader Line Gaps A leader line may have up to 10 gaps in it. These are most easily defined using the cursor. These enable the APOF. To modify the Label. for example: SETDEF GAP 5 Set default gap length to be 5mm Gaps in Label leader lines can be sketched and erased in the same way as Dimension projection line gaps . and delete all other gaps in line Delete gap specified by cursor Delete all gaps on current Sheet Deletes all unused gaps from Label The default gap length may be set by using the SETDEFAULT GAP command. but in the latter case the expanded result cannot be shown on the library Sheet (ie LALB). for example. See Figure 13:1. a description of the template. but without a leader line. like a SHEE. The templates can be picked to be used to define SLABs. The attributes that appear at both TXTM and SLAB are: FONT CHEIGHT ALIGNMENT JUSTIFICATION TXCOLOUR LFSTYLE LFCOLOUR Font Character height Text vertical alignment Text justification Text colour Frame linestyle (NLSTYLE at the TXTM) Frame colour (NLCOLOUR at the TXTM) The initial values for these attributes on a newly created SLAB are cascaded from the owning Layer. If the TXTM does not use ‘#ATEX’ the SLAB’s ATEX attribute has no effect. can be displayed in an area view. See Colours and Styles for more information on colours and line styles. use the value obtained from the TXTM.2 Special Labels and Text Label Templates The Text Template element (TXTM) is similar to a GLAB.3 13. thus allowing the definition provided by the TXTM to be overwritten. The appearance of the text and frame of the SLAB is (by default) controlled by attributes of the referenced TXTM. There are two types of templates: Text Templates (TXTM) and Symbol Templates (SYTM).e. 13.0 . if they are set to explicit values these will be used rather than the values of the TXTM.3. i. The Example Text attribute (ETEX) of a TXTM is a documentary attribute to allow. However.Label Elements. Thus for example if TXTM /TEMPLATE has: BTEX ‘Number #ATEX’ 13:15 12. When the BTEX attribute of the referenced TXTM contains the hashcode ‘#ATEX’ it will be replaced by the ATEX value. TXTM and SYTM have an XYPS attribute which defines their position on the Library Sheet and allows them to be laid out in a logical fashion.DRAFT User Guide Labelling 13. It can only be evaluated at the SLAB because it will depend upon the SLAB’s DDNM attribute. Some of the attributes of the TXTM are duplicated at the SLAB.1 Special Labels and Label Templates Introduction The appearance and text contents of a Special Label (SLAB) are defined by the Label Template that it references by its Template Reference attribute (TMRF). Both types are owned by a Label Library (LALB) which. The appearance of the leader line is controlled by attributes of the SLAB. The text attribute of a TXTM (ie BTEX) can be an explicit or intelligent text string.: DRAFT Database Hierarchy .3. By default their values at the SLAB will be ‘TEMPLATE’. The ATEX attribute of a SLAB has a special purpose. The appearance of SYTMs is completely user-definable. As with ‘textual’ SLABs the appearance of the text and graphics of a ‘symbolic’ SLAB is (by default) controlled by attributes of the referenced SYTM.3.DRAFT User Guide Labelling 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. SYTMs are generated using DRAFT’s 2D drafting facilities . The initial values for these attributes on a newly created SLAB are cascaded from the Layer. The appearance of the leader line is controlled by attributes of the SLAB. and may consist of any size and combination of basic geometrical shapes (squares. (Note also that Point Construction (see Point and Line Construction) can also be used to create SYTMs.4 Scaling and Mirroring Special Labels The XYSCALE attribute of a SLAB allows independent scale control in the X and Y directions.3 Special Labels and Symbol Templates SLABs may also reference Symbol Templates (SYTMs). 13. A negative Y value will rotate the entire text to be upside-down.3. Instanced text is only affected by its scale in Y direction. as well as text (which may be ‘intelligent’). 13. SYTMs are members of LALBs or SYLBs (Symbol Libraries). for example SYSZ 2 is equivalent to XYSCALE 2 2 13:16 12. Either or both values assigned to XYSCALE may be negative. At a SLAB the following three attributes may be set to overwrite the values provided by the SYTM: TXCOLOUR LFSTYLE LFCOLOUR Text colour Graphics linestyle Graphics colour Note that a SYTM may be composed of several graphics primitives each drawn in a different style or colour. It is not possible to produce backwards or distorted text. See Colours and Styles for more information on styles and colour. Overwriting the SYTM attribute values will cause all the graphics primitives to adopt the single linestyle or colour specified.0 . The Y scale affects the overall size of the text string. circles etc). which allows the SLAB to be ‘mirrored’.) SYTMs are used in the same way as TXTMs. It is recommended that JUSTIFICATION CENTRE be used for text. This will keep the text position unchanged with respect to the rest of the symbol when the symbol is mirrored. The SYSZ attribute may be used to change the scale uniformly in both directions.see 2D Drafting. also have the XYSCALE attribute and may be manipulated in the same way. then the leader line will terminate at the opposite corner of the test box. Generally.e.5 SLAB Leaderline Connection Points The leaderline connection point for SLABs is determined by the setting of its CPOF attribute. Note: Symbols (SYMB). which causes DRAFT to determine the actual leaderline connection point. as occurs with GLABS. its XYSC values are equal) then the leaderline will terminate at the CIRC An MRKP primitive.: Varying the SLAB XYSCALE attribute illustrates the effects of varying XYSCALE.DRAFT User Guide Labelling Another variation is: SYSZ @ @ resize SLAB using the cursor Figure 13:12. and the SLAB is drawn undistorted (i. A TEXP primitive. This is STANDARD by default. see 2D Drafting. when the SLAB references a SYTM. For example: LEAD CONN @ LEAD CONN X30 Y35 LEAD CONN OFFS X10 Y-10 allows the point to be defined by cursor allows an explicit Sheet position to be specified allows a relative position to be specified 13:17 12.0 . XYSCALE 1 1 XYSCALE 1 2 XYSCALE 2 1 XYSCALE -1 1 XYSCALE -1 1 XYSCALE -1 -1 Figure 13:12.3. this will be at its origin. However if the first member of the SYTM’s list is: • • • A CIRC primitive. XYSCALE is also settable at LAYE level. Varying the SLAB XYSCALE attribute 13. then the leaderline will terminate at the MRKP. The CPOF attribute can be set explicitly or by using the LEADERLINE CONNECTION syntax. it may be necessary to reposition a label or to modify its leader line. this is defined by the JUST and ALIG attributes of the TXTM. For a SLAB that references a TXTM.0 . All automatically generated Labels will be owned by a Layer.4 13. A Tag Rule exists as a member of a Layer (LAYE) or of a Tag Ruleset (TRST).4.0 The last three examples are equivalent to: CPOF 10 -10 CPOF STAN CPOF ORIG The values stored in CPOF define the coordinates of the connection point relative to the template’s origin and they are in the axis system of the template. Tag Rulesets are owned by Tag Rule Libraries (TRLB). using a macro such as: VAR !A COLLECT ALL SLAB WITH (TMRF EQ template_id ) FOR SHEE DO !B VALUES !A $!B CPOF -5 10 ENDDO Note: Where the CPOF setting defines an offset from the new Label origin and template_id is the TXTM name (which must be followed by a space). Note: The CPOF attribute for a SLAB is an offset from the Label origin. Those Labels within a 13:18 12. 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. The autotagging process is under the control of a Tag Rule (TAGR) element.DRAFT User Guide Labelling LEAD CONN STAN LEAD CONN ORIG resets CPOF to its default value sets CPOF to 0. The selection system makes it possible to do a global change on the CPOF attribute of all SLABS that use a given TXTM. having defined a set of rules to control those elements that are to be labelled and the (common) appearance of the labels.1 Autotagging Introduction DRAFT’s ‘autotagging’ facility enables you to generate automatically a series of Labels in one or more VIEWS of a Drawing. For example. The Layer element has a Tag Ruleset Reference attribute (TRSF). Hence if the SLAB’s orientation is changed the connection point will rotate with it. Hence if the JUST or ALIG components of a TXTM are modified the leaderline will be connected to a different part of the Label. 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 SLAB’s CPOF attribute defines a specific leader-line connection point. 13. The relevant part of the DRAFT database hierarchy is shown overleaf. The automatically generated labels (which may be GLABs or SLABs) can then be individually edited. which if set will refer to a TRST. 2 Defining the Autotagging Hierarchy and Rules A typical sequence of commands for setting up an autotagging hierarchy would be: NEW TRLB NEW TRST NEW TAGR /TR1 TMRF /LAB1 IDLN /ID6 define Label appearance by setting template reference attribute to point to existing GLAB.4. SLAB or template element IDLN Id List or DESIGN element Figure 13:13.DRAFT User Guide Labelling given Layer will have been generated either from TAGRs owned by that Layer or from TAGRs referenced by the Layer via its TRSF attribute. DRAFT Database Hierarchy . [Set to /* by default. SLAB or template element IDLN GLAB/SLAB I d List or DESIGN element SORF GLAB/SLAB TAGR TMRF SORF GLAB.] 13:19 12. Having defined a TAGR element. SLAB. 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). SYTM or TXTM define elements to be labelled by setting Id List name attribute to point to existing Id List [or Design] element.Autotagging Elements 13. or if the TAGR itself changes. LIBY TRLB VIEW TRST LAYE TAGR TRSF TMRF GLAB.0 . but detail appearance attributes will be cascaded down from the owning LAYE. Example: CRIT ALL BRAN WI (HBOR LE 80 OR TBOR LE 80) 13. Attributes CHEI. 13:20 12. See Representation Rules and Creating Labels and Label Text in Part 1. The GLAB or SLAB need not be in the current Drawing.3 • Controlling Label Appearance and Elements to be Tagged Label Appearance This is defined by the element referenced by the TAGR’s TMRF attribute. By default. other LAYE members. only those elements common to this element and the VIEW’s Id List will be considered for tagging.) • Elements to be Tagged These are defined by the element referenced by the TAGR’s IDLN attribute. 1. the basic style of the generated SLABs will be defined by the referenced template. With a TAGR as current element.DRAFT User Guide Labelling 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. which applies to those elements defined by the IDLN setting. in which case all elements included in the owning VIEW’s Id List will be considered for tagging.4 Querying TMRF and IDLN are queryable in the usual way. for which the ‘TEMPLATE’ setting would be meaningless. The CRIT attribute for the current tag rule can be set explicitly.4. (This applies only to SLABs. FONT. this is set to reference the WORLD. If the IDLN attribute is set to refer to an Id List. If the referenced element is a GLAB or a SLAB. Basic Drawing Creation & Output for more examples. LFSTYLE/LFCOLOUR and TXCOLOUR may be set at LAYE level to ‘TEMPLATE’.0 . If the referenced element is a TXTM or SYTM. 13.4. 1 and 1 (respectively) for these attributes. only those elements common to this Id List and the VIEW’s Id List will be considered for tagging. if the IDLN attribute is set to refer to a Design element. which means that these attributes will take their values from the template referenced by the TAGR. the query command Q DESC will output the tagging rule used. Similarly. Examples of the use of the TAG command are: TAG ALL NOZZ TAG ALL BRAN MEM TAG (ALL VTWA ALL VFWA ALL VALVE) WI (STYP EQ ’GATE’ AND ABORE GE 80) TAG ALL WI (CREF NE =0) The TAG command has the same syntax as the USE style_name FOR command. would be created with values of 4mm. the items to be tagged are defined by the TAG command. Having constructed the hierarchy and set up the necessary references. the generated labels will be identical to it except for attributes DDNM and LVIS (which will be set TRUE). This is of the form: UPDATE element_identifier TAGG If element_identifier refers to a TAGR owned by a LAYE. Note that Labels will be created for elements that are not drawn because they are obscured by others.e. new Labels will only be created for those Design elements found without Labels with correctly set SORF attributes. then all Labels defined by the given Tag Rule will be generated. If element_identifier is omitted then the current element is assumed and one of the three previous conditions will apply. If a LAYE element is LOCKed then none of its TAGRs will be updated. Each Label will have its SORF (source reference) attribute set to refer back to the TAGR.e. SHEE or DRWG then this is equivalent to giving an UPDATE TAGG command for each Layer beneath them in the hierarchy. Not using OVERWRITE will cause existing Labels to be updated so as to reflect any changes that may have occurred in the Design database.4. which needs to be modified or deleted. 13:21 12. UPDATE TAGG OVERWRITE (or UPDATE element_identifier TAGG OVERWRITE) Using OVERWRITE will destroy any editing of individual Labels that may have been done. Tag Rules will also be updated by UPDATE ALL. is LOCKed then it will be UNLOCKed and the modification or deletion carried out. When a Tag Rule is updated for the first time a set of Labels will be created and drawn which can then be edited if required .5 Label Generation Having set up a TAGR element and its associated autotagging rules. An UPDATE ALL command will still cause the annotation of that Layer to be updated. i. If these Labels are not required it is recommended that they are made invisible by setting LVIS FALSE. If element_identifier refers to a VIEW. whether or not an element is excluded depends upon the position of the p-point to which the Label is to be attached. then all Labels defined by all of the member Tag Rules of the Layer.0 . If a GLAB or SLAB. the Labels are generated by UPDATE TAGGING command.see Label Editing and Copying. plus those owned by the TRST referenced by the Layer’s TRSF attribute will be generated. Labels will not be created for any element that is not drawn because • • • It is not included in the VIEW’s Id List It falls outside the VIEW rectangle It is excluded by the action of a Section Plane In the latter two cases. Deleting them will only cause replacements to be generated on the next UPDATE TAGG command. those owned by it and those owned by the TRST it references) may be output by: Q TRSF DESC (at LAYE) 13. existing Labels will not be deleted and recreated from scratch unless the OVERWRITE option is used.DRAFT User Guide Labelling A description of all tag rules relevant to a Layer (i. When a Tag Rule is updated a second (or subsequent) time. 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. If element_identifier refers to a LAYE. i.new Label. 13:22 12. Other options are: TAGG MESS ON FILE /filename TAGG MESS ON FILE /filename OVER TAGG MESS ON FILE /filename APPE TAGG MESS ON FILE EN TAGG MESS OFF output messages to file as above.moved by W2500 /VESS3 . created on /VESS5 When /TR1 is subsequently updated the Labels change as follows: 13.updated. / VESS3 and /VESS4.deleted /VESS4 . but no changes /LAB2 . messages will not be output.6 Tracking the Autotagging Process The command TAGGING MESSAGES ON will result in messages being output during a tagging update operation advising of Label creation and deletion. one on each of / VESS1. When /TR1 is updated for the first time four Labels are created in /VIEW1.updated.e. /VIEW1/LAYE1 owns Tag Rule /TR1 which is simply defined as ‘TAG ALL EQUI’. but overwrite existing file as above. /VESS1.removed from /LIST1 /VESS5 . although the autotagging process would not actually give them names. and moved to reflect new position of /VESS2 /LAB3 . /VESS3 and /VESS4. The IDLN attribute of /TR1 is set to /*. For the sake of convenience we shall refer to these Labels as /LAB1. The following DESIGN and DRAFT database changes are then made: • • • • • • • • • • /VESS1 .0 .deleted /LAB5 .DRAFT User Guide Labelling 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.added to /LIST1 /LAB1 .unaltered /VESS2 . the whole of /LIST1 is to be scanned and all EQUIs tagged. /VESS2. /LAB2.deleted /LAB4 . /LAB3 and /LAB4. but append messages to existing file close message file turn message output off By default.4. /VESS2. If changes are made to a TAGR or TRST that potentially cause database inconsistencies then a warning message will be output. SORF may be unset by SORF =0 SORF NULREF or 13.DRAFT User Guide Labelling 13. RECONFIGURER must be used for correct transfer of data between databases.9 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. which will ensure that the correct appearance of existing labels is maintained.4. If the TMRF is changed in a different way (e. GLABs or SLABs generated by the autotagging process can be edited.g. 13:23 12. thus breaking the link between the Label and the TAGR. TRST and TAGR elements may all be modified in the usual way by changing their attribute settings (although with TRLB and TRST elements only the standard attributes. but it may not be set to point to another TAGR (or to any other value). GLAB to GLAB or SYTM to SLAB) then existing Label edits will be lost.7 Label Editing and Copying A GLAB or SLAB generated by the autotagging process will be the same as a conventionally created Label except that its SORF attribute (set to Nulref in the ‘manual’ case) will be set to refer back to the controlling TAGR. If a TAGR owned by a LAYE is deleted or included in another LAYE then the SORF attribute of all labels generated from it will be set to Nulref. SORF may be set to Nulref. at the next UPDATE TAGG command. that editing these elements could cause existing Labels to no longer represent the TAGR definition.0 . It is not feasible to do this for TAGRs owned by TRSTs (because many labels in several databases may be affected) or to set to Nulref SORF attributes for any other changes to TAGRs (because a change may broaden the scope of the TAGR so that existing Labels are still valid). Note. an implicit UPDATE TAGGING OVERWRITE operation will be performed. Name. a subsequent UPDATE TAGGING command will create another Label on the labelled Design element.8 Tag Rule Editing TRLB.g. If the TMRF is changed from one TXTM or SYTM to another TXTM or SYTM then existing label edits will be kept. If a TAGR’s TMRF attribute is changed then.4. are settable). the new Label will have its SORF attribute set to Nulref. but the following safeguards are applied to ensure that the Labels will always comply with the definition set up by the TAGR: • • • • • The DDNM attribute cannot be changed The BTEX attribute cannot be changed (GLABs) The TMRF attribute cannot be changed (SLABs) The Label cannot be INCLUDED in another Layer The Label cannot be deleted If a Label with its SORF attribute set is copied. however. e.4. Having broken the link. 13. The Tag Rule’s TMRF attribute should reference a GLAB that has been positioned absolutely (e.5 Intelligent Label Placement A facility is provided to ‘tidy up’ crowded labelling. styles 6 or 7). and the PDMS Programmable Macro Language (PML) it is possible to generate schedules on drawings easily. When the Tag Rule is updated all the GLABs generated will be in the same position. AT X1000 Y800 ABS) at the top or bottom of the required schedule’s position.: Poorly positioned Labels and Figure 13:15. and the definition of leader-line shapes and bend-points. as far as possible. The size of the move should be calculated from the character height of the GLAB and its number in the scan.g. If they are moved then.0 . The GLAB’s FONT attribute should point to a font set up with fixed-width characters (i. 13:24 12. text justifications and alignments. The second field will start at character column 15 and the third at column 25. 13. which may be used to position Labels locally or remotely. Labels will be positioned around their significant design elements in such a way as to minimise Label overlap and leader-line crossing. a TEXP element to define the field headings. An example of 'local spreading' is shown in Figure 13:14. The width of the fields should be made sufficient to accommodate the expanded codewords. 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 macro should also create a TABL element to provide the frame of the schedule and its horizontal lines. With local positioning. The GLAB’s BTEX attribute should contain a number of code-words separated by tabbing codes (see Tab Generator Codeword). As well as changing label positions the facility may also change Label orientations. 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.10 Schedule Generation Using Autotagging.DRAFT User Guide Labelling 13. bore.4. and connection reference. A macro should be written that scans around the Layer looking for GLABs with their SORF attribute referencing the Tag Rule.e. The facility uses two versions of the SPREAD command. tabbing in intelligent text. so as to minimise Label overlap and leader-line crossing. and its leader line and text frame suppressed.: Result of SPREAD command on Labels shown in Figure 4-16. This will create a schedule of three fields giving nozzle name. Labels will not be moved from their initial positions unless it is necessary. its CHEI set to an appropriate value. leader lines will be straight and at ± 45° to the VIEW axis. For instance for a nozzle schedule the BTEX may be ’#NAME#15#P1BOR#25#CREF’. Poorly positioned Labels Figure 13:15. the command SPREAD LOCAL SELECT INSIDE @ @ 13:25 12.DRAFT User Guide Labelling Figure 13:14.0 . Result of SPREAD command on Labels shown in Figure 4-16 In the above example. Use cursor to specify corners of rectangle around which Labels are to be repositioned (could be outside or inside of VIEW border). labels will be positioned around the VIEW border. and the minimum permissible gap between any two Labels can also be specified. Other variations of the SPREAD LOCAL command are: SPREAD LOCAL SELECT ID @ ID @ SPREAD LOCAL OFFSET 10 SPREAD LOCAL XOFFSET 15 SPREAD LOCAL RADIUS 20 Use cursor to identify (two) Labels to be spread. To avoid overlapping. Change Label spread offset to 10mm (X and Y directions) Change Label spread offset to 10mm (X direction only) Specify Label spread offset indirectly by giving a diagonal length With remote positioning. the previous SPREAD parameter settings will not be remembered. Prevent Labels from being rotated by 90°. Use cursor to specify corners of window enclosing Labels to be spread. the Labels will be offset by 25mm (in the X and Y directions) from the Label attachment point.0 . It is also possible to define a side of the VIEW frame alongside of which repositioned Labels will not be placed. some leader lines will be doglegged at 45°. SPREAD REMOTE GAP 5 SPREAD REMOTE NOROT Note: All options must be specified on the same command line. Specify 5mm as minimum gap between any two Labels. By default. Part 2).DRAFT User Guide Labelling was used to define a window within which the labels to be repositioned lie. Reposition Labels within 10mm of VIEW border Prevent Labels being placed alongside the top side of the rectangle around which they are to be repositioned. The SPREAD LOCAL command can be used with the PDMS general selection syntax (see the DESIGN Reference Manual. Examples of the SPREAD REMOTE command are: SPREAD REMOTE SELECT ID @ ID @ SPREAD REMOTE SELECT INSIDE @ @ SPREAD REMOTE REPOSITION @ @ SPREAD REMOTE MARGIN 10 SPREAD REMOTE OMIT TOP Use cursor to identify (two) Labels to be spread. It is possible to define a margin outside the VIEW frame that will define the positioning of the Labels. Labels along the top and bottom sides will be rotated through 90° (readable from the righthand side) unless otherwise specified. 13:26 12. Labels will be repositioned at the (allowed) VIEW side nearest to their attachment points. sets ADEG set Label frame visibility .sets DDNM offset the Label from the default using the cursor . OSET turn the Label through an anticlockwise angle . . . .2 Aligning the Label Text . ON ID @ AT @ AT @ ABS ANG value FRA option specify the Design element for the label attachment . .sets XYPS.6 13.sets GBOX 13. LFSTYLE value LFCOLOUR value LLSTYLE value LLCOLOUR value set frame drawing style set frame drawing colour set leader line drawing style set leader line drawing colour 13:27 12.6. OSET absolute position for the Label using the cursor . .sets XYPS.6.1 Summary of Commands Setting Label Attributes .set Label frame clearance .3 Setting Label Frame Attributes .6.0 .sets LFRA options: • • ON OFF FRA CLEA value . JUST option justify text options: • • • L C R ALIG option set text alignment options: • • • • BB HB TB BA 13. .DRAFT User Guide Labelling 13. .set text height to that of Template (TXTM) element specify character spacing factor specify text line spacing set text position as an offset from the p-point . . BTEX ’text’ CHEI value LHEI value CHEI TEM CSPA value LSPA value OFFS ABS specify text string specify text height specify letter height (=0.sets OSET FALSE 13:28 12. prevent Labels from being rotated by 90°.0 . 13.6. .4 Spreading Label Positions .6. specify minimum gap distance between any two Labels. .5 Setting Label Text Attributes .sets OSET TRUE (default) set text position as a specific position on the Sheet . SPREAD LOCAL SELECT selection_option SPREAD LOCAL SELECT INSIDE position_options SPREAD LOCAL OFFSET distance SPREAD LOCAL XOFFSET distance SPREAD LOCAL YOFFSET distance SPREAD LOCAL RADIUS distance SPREAD REMOTE SELECT selection_option select Labels to be spread (locally) spread Labels inside specified window specify Label spread offset (X and Y directions) specify Label spread offset (X direction only) specify Label spread offset (Y direction only) specify Label spread offset indirectly by giving a diagonal length select Labels to be spread (remotely) SPREAD REMOTE SELECT INSIDE p spread Labels inside specified window osition_options SPREAD REMOTE REPOSITION position_options SPREAD REMOTE MARGIN distance SPREAD REMOTE OMIT (top/bottom/left/right) SPREAD REMOTE GAP distance SPREAD REMOTE NOROT spread Labels around specified rectangle spread Labels within given distance of VIEW border prevent Labels being placed alongside the specified side of the rectangle around which they are to be repositioned.8*character height) (Special Labels only) .DRAFT User Guide Labelling 13. option = HORI or VERT bend a leader line horizontal or vertical then at an angle option = HORI or VERT sets leader line clearance using a constructed point offsets attachment point from DDNM (Sheet units) specify attachment point offset explicitly remove attachment point offset places leader line connection point at standard position places leader line connection point at Label origin allows a relative position to be specified 13:29 12. sets leader line terminator. LEAD option LTER option LEAD STRA TSIZ 4 LEAD BENT @ LEAD BENT AT @ OFFSET Y50 LEAD BENT CENTRE OF /CIRC1 LEAD BENT OFFS X value Y value LEAD BENT PT 2 @ LEAD BENT PT 2 X722 Y40 LEAD BENT PT 1 OFF X15 LEAD BENT PT 1 DEL LEAD value option LEAD option value LEAD CLEA ENDP OF /LINE1 QUAL X500 Y500 APOF value value LEAD ATTA X value Y value LEAD ATTA @ LEAD ATTA DELETE APOF 0 0 APOF UNSET CPOF STAN CPOF ORIG CPOF value value set leader line visibility . OBLIQUE sets a bent leader line to straight set terminator size to 4mm (default 3mm) bend a leader line at a position set by cursor (@ @ for two bend points) bend leader line at an offset from a position set by the cursor bend a leader line at the centre of the named circle bend a leader line at a position explicitly (repeat X value Y value for two bend points) specify 2nd of two bend points using cursor specify 2nd of two bend points explicitly specify 1st of two bend points as offsets from Label attachment point delete 1st of two bend points bend a leader line at an angle then horizontal or vertical.6. ARR. DOT. options: OFF.0 .6 Setting Leader Line Attributes (GLABs) . .DRAFT User Guide Labelling 13. .sets LEAD TRUE/FALSE. option = ON or OFF. . .0 offsets attachment point from DDNM (Sheet units) specify attachment point offset explicitly remove attachment point offset 13.DRAFT User Guide Labelling 13.7 Setting Leader Line Attributes (SLABs) . Q LAB option query specified label attributes options: LEA POS leader line position.6. .0 .6. . GAP @ GAP AT @ GAP AT @ L value GAP DELETE @ GAP DELETE ALL GAP TIDY SETDEF GAP value specify a gap in a leader line by giving start & finish points specify a default length gap of 2mm in a leader line by a single point specify a gap of a specified length by giving a single point delete a gap identified by cursor delete all gaps on the current Sheet deletes all unused gaps from current Label set default gap length 13.6. .8 Setting Gaps . rotation and p-line attributes (latter only relevant if Structural element is being labelled) origin ORIG 13:30 12. .9 Querying . LEAD CON @ LEAD CONN X value Y value LEAD CONN OFFS X value Y value CPOF value value LEAD CONN STAN CPOF STAN LEAD CONN ORIG CPOF ORIG APOF value value LEAD ATTA X value Y value LEAD ATTA @ LEAD ATTA DELETE APOF 0 0 APOF UNSET sets leader line connection point by cursor (sets CPOF) allows an explicit Sheet position to be specified allows a relative position to be specified resets CPOF to its default value sets CPOF to 0. . Sheet position. TAG selection_option sets up elements specified by selection_option to be tagged.6. but deleted (and unrecognised) Design elements referenced in the Idlist are ignored.11 Autotagging . offset and angle of turn. without the UPDATE process being aborted as UPDATE TAGG.(at SLAB) Q TRSF DESC . but all labels recreated from scratch as UPDATE element_identifier TAGG. .6. without the UPDATE process being aborted generates Labels down from element_identifier as above.(at GLAB) .DRAFT User Guide Labelling ATTA TEX STY Q DESC option .0 . but deleted (and unrecognised) Design elements referenced in the Idlist are ignored. Sheet position. DELETE NULL ANNO deletes all GLAB and SLAB elements with DDNM set to NULREF 13. Selection rule syntax same as USE . FOR command sets the CRIT attribute for the current tag rule explicitly output tagging messages to screen output tagging messages to file causes Tag Rules to be evaluated and generates Labels down from current element as above. gives template type. .(at LAYE) point annotated text text style gives Label attachment point.. but all labels recreated from scratch CRIT ALL BRAN WI (HBOR LE 80 OR TBOR LE 80) TAGG MESS ON TAGG MESS ON /filename UPDATE TAGG UPDATE TAGG IGNORE UPDATE element_identifier TAGG UPDATE element_identifier TAGG IGNORE UPDATE TAGG OVERWRITE UPDATE element_identifier TAGG OVERWRITE 13:31 12. . gives description of all relevant tag rules 13. offset and angle of turn. .10 Deleting unwanted Labels . 0 .DRAFT User Guide Labelling 13:32 12. Codewords that access data associated with the Drawing database element that owns the text string. DPOI. DPBA) general text string of General Labels (GLAB) and Template (TXTM). projection line text (i. ADIR. The text strings where you can use intelligent text are: DMTX PLTX BTEX dimension line text (of Dimension Points and Directions. retrieve the data. You do not have to navigate through the relevant database. 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. Example: ’Standby pump #NAME’ The advantages of intelligent text are: • • • 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. Codewords that access UDA data. See Accessing Data from the DESIGN or Catalogue Databases. Accessing Data from the DRAFT Database. Codewords with special functions. (See also Text Strings) 14. See Codewords with Special Functions.0 . See Accessing UDA Data.1 Intelligent Text Introduction Intelligent text allows data to be automatically extracted from the Design.DRAFT User Guide Intelligent Text 14 14.2 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.e. Codewords that access dimensioning data. DPPT. which all begin with a # character. Codewords that access administrative data. return to the DRAFT database and enter the data manually. Catalogue or Drawing databases and entered on a Drawing. • • • • • 14:1 12. Intelligent text uses codewords. See Accessing Administrative Data. APPT. See Accessing Dimensioning Data. The codewords for position attributes can be modified so as to provide only one of the coordinates. BOP or TOP only) 14:2 12. W12250 N7890 U3120 Easting coordinate only. E12250. e. S22150 Upping coordinate only.1 P-point Data P-point data can be obtained by a codeword of the form: #Pnxa Data from p-point n of element where n = p-point number. Note that the codeword #POSE can have two meanings.0 .g. In addition. e. The position codewords generate values in World coordinates. BOP. HPOS. U3120. DRPS and DELP.DRAFT User Guide Intelligent Text 14. BOR.see Transforming Position/Direction Data. W12250 N7890 U3120 would give -12250 +7890 +3120 14. D250 All DESIGN database position attributes can be modified in this way. NPOS.3 Accessing Data from the DESIGN or Catalogue Databases All DESIGN and Catalogue database attributes are accessible.g. For example: #POS #POS+ full 3D position. It is possible to generate values in the coordinate systems of other elements by the use of transform keywords . TPOS. For example: #SITE #BRAN Name of site owning the referenced element Name of Branch owning the referenced element PDMS pseudo-attributes may be accessed in the same manner.3. positions can be output with +/ . POSE. any Design element can be accessed. Note: As an alternative to the standard ENU position format. or ‘L’ for leave p-point or ‘A’ for arrive p-point x = POS. TOP or CON a = blank. These are POS. e.g. N or U (valid for x = POS. POSS. For example: #POS #POSE #POSN #POSU full 3D position.format by appending ‘+’ to the codeword. E. e. For example.g. attribute ABCD would be accessed by code #ABCD (or #abcd). in other cases it means the Easting of the POS attribute.g. DIR. e. W9675 Northing coordinate only. N7890. depending on the context: for SCTNs it means the POSE attribute (Section End Position). #PK may optionally be followed by the p-line name. The syntax for p-lines is #PK (for PKEY). direction and offset.DRAFT User Guide Intelligent Text For example: #P3BOR #PLBOPU #P1POS bore at p-point 3 Upping of leave p-point BOP position position of p-point 1 Ppoint codewords can have an optional ^ delimiter between the p-point number and the attribute. Spaces are not permitted between the codeword and sub-codeword. The following sub-codewords may follow the p-line codeword #PK or #PKname: ^DIR ^POSS ^POSSE ^POSSN ^POSSU ^POSE p-line direction p-line start position Easting of p-line start position Northing of p-line start position Upping of p-line start position line end position 14:3 12. #PK may also be followed by MEML (i. for example: #P^POS in which case the value from the NPPT attribute of the relevant piece of annotation will be used. Names such as these would be impossible to separate from the p-line sub-codeword without this delimiter.2 P-line Data The P-line syntax may refer to the p-line used for annotation (i. A specific codeword defining the p-line precedes strings requesting position.e. This syntax on its own is a request for the p-line name (e.e. for example #PKNA for p-line neutral axis. that defined by the PKEY attribute) or to a specified p-line. #PKMEML) if data for the Section’s member-line is required.0 . stored as the PKEY attribute). The p-line name (if present) may be 1-4 characters long. There is nothing to stop you from having p-line names such as NAPO or even DIR. but it must be used when the number is omitted. NA or TOS. for example: #P2^POS The delimiter is optional. The internal delimiter ^ is necessary to separate the p-line attribute from the p-line name.3.g. (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’. 14. U for Upping (optional) 14. Note: In DRAFT p-lines are always cut back by SCTN end-preparations and member-lines are always extended to the ‘working point’. The transform qualifier (see Transforming Position/Direction Data) may be used with any of these sub-codewords.3. DPPT.5 it will be at the p-line’s mid-point and its midpoint position generated. but not for p-line name. For example: #PKTOS^POSEU<WRT /DATUM> #PKTOS^POSEU+<WRT /DATUM> #DERPOS[a] Gives the upping with respect to /DATUM of the end position of the TOS p-line As above. 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. Fitting or Secondary Node. This will generate the position defined by the PKDI attribute of the label. RPPT and PPPT elements also possess the PKDI attribute.DRAFT User Guide Intelligent Text ^POSEE ^POSEN ^POSEU ^PKDI ^PKDIE ^PKDIN ^PKDIU For example: Easting of p-line end position Northing of p-line end position Upping of p-line end position position of point along p line defined by PKDI attribute Easting of point along p-line defined by PKDI attribute Northing of point along p-line defined by PKDI attribute Upping of point along p-line defined by PKDI attribute #PKNA^POSS #PK^DIR gives the start position of the NA p-line gives the direction of the p-line given by the PKEY attribute The #PK^PKDI keyword will extract the position along a p-line at which a Label is attached. ADIM. E for Easting.3 Accessing Data in Catalogue Datasets Data in a Catalogue Dataset is obtained by a two-part codeword of the general form: #attribute^qualifier For example: #PROPERTY^WIDTH #PRTITLE^WIDTH obtain Property value of WIDTH dataset entry obtain Property Title of WIDTH dataset entry 14:4 12. The positions generated by these codewords reflect this functionality. where a = N for Northing.0 . the VNOT. If PKDI = 0. Besides GLABs and SLABs. but gives upping in ‘+/-’ format Derived position of a Joint. In addition the name of any DRAFT element can be accessed. See Extracting Attribute Data from any Specified Element for full details of the FROM qualifier. 14. The following special codewords are also available: #DTITL #STITL #VTITL Drawing title. equivalent to #TITL<FR DRWG> Sheet title.e. attribute ABCD of the current annotation element would be accessed by code #ABCD. The REVI element can be specified by name. For example: #VIEW #DRWG The name of the View owning the annotation element The name of the Drawing owning the annotation element Attributes of other DRAFT elements can be accessed using the FROM qualifier. For example. For example: #AUTH<FROM DRWG> Generates the Author of the Drawing owning the annotation elements.4 Accessing Data from the DRAFT Database All DRAFT (PADD) attributes are accessible. 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.0 . If the qualifier <FR DRWG> is appended then data will be extracted from the first REVI element in the Drawing’s list. equivalent to #TITL<FR SHEE> VIEW title. To extract data from a specific REVI element a qualifier should be used. PROPERTY etc) can be abbreviated to four characters. equivalent to #TITL<FR VIEW> Special functionality is provided for the following codewords that extract revision data: #APPR #APDT #RVSN #RVDT #RVAU Approve Approval date Revision Revision date Revision author These codewords extract their data from the first REVI element in the Sheet’s list. for example: #RVAU<FR/REV3> 14:5 12.DRAFT User Guide Intelligent Text 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. 14. the Northing of the Dimension Position will be output .g BTEX ’#DEF’ is valid. #DIMPOSU #DIMPOSDD 3D position Easting. For details of the FROM qualifier see Extracting Attribute Data from any Specified Element. DPOI. as would be generated by #DIMPOS) together with error message 64. ’name #DEF’ is not. e. APPT. For example: #RVDT<FR SREVAY[2]> #APPR<FR DREVAY[3]> Generates the revision date from the sheet's second revision Generates the approver from the drawing's third revision For details of the SREVAY and DREVAY attributes see Drawing Revisions. exactly the same result as #DIMPOSN. #DIMPOSN. #DIMPOS #DIMPOSE.5 Accessing Dimensioning Data Codewords that are allowed values for the Dimension Line Text (DMTX) and Projection Line Text (PLTX) of Angular and Linear Dimensions (ADIM and LDIM) and Dimension Points/ Directions (ADIR. At a DPOI which has POS and optionally DDNM attributes set.i. DPPT. and cause the 3D Dimension Point position to be generated in World coordinates. 14. Upping.DRAFT User Guide Intelligent Text or the pseudo-reference array attributes SREVAY and DREVAY can be used. DPBA) and have special meanings: #DIM #DEF #DIR Calculated dimension value (DMTX or PLTX) Use default text string supplied by owning ADIM or LDIM (Must appear alone in a text attribute.e. 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. The codewords to access Userdefined attribute (UDA) data have the format 14:6 12.) Projection line direction (of ADIR) The following codewords are valid in the PLTX of LDIMs and their members. Northing. #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. #POS will always obtain data from the element referenced by DDNM.e. if the Dimension Direction is North.399: /ldim-name: Dimension direction not orthogonal.6 Accessing UDA Data For those that extract (UDA) data from the database. respectively Coordinate in the Dimension Direction of the 3D Dimension Point position For example.0 . If the Dimension Direction is not orthogonal. the full 3D position will be output (i. Extracting Attribute Data from any Specified Element) that apply to ordinary codewords may also be applied to UDAs.g. System time: format hh:mm:ss. 09/30/98 Date: format dd/mm/yy. e. DATEFOrmat may be set to: DDMMYYYY DDMMYY MMDDYYYY MMDDYY which gives a format equivalent to ADATE which gives a format equivalent to ADATEX which gives a format equivalent to BDATE which gives a format equivalent to BDATEX 14:7 12. 09:07:57 current user’s System Name Project number Project name Project description Project message Project code DEPT and LIBY elements have a DATEFOrmat attribute. e. e. 14. 30 Sep 1998 Date: format mm/dd/yy. e.g.g. The output of data follows a format similar to that used by existing UDA queries. 30 Sep 98 Date: format specified by the DATEFOrmat attribute of the DEPT above the current element. It controls the format of the values of DATE (of DRWGs) and RVDT (of REVIs) attributes which are automatically generated.DRAFT User Guide Intelligent Text #:uda_name For example: #:UDA1 All relevant qualifiers (see Substrings .0 .7 Accessing Administrative Data Codewords relating to administrative data are: #ADATE #BDATE #CDATE #ADATEX #BDATEX #CDATEX DFDATE #TIME #SYSUSE #PROJECT^NUMBER #PROJECT^NAME #PROJECT^DESCRIPTION #PROJECT^MESSAGE #PROJECT^CODE Date: format mm/dd/yyyy. Other uses of UDA reporting are described in Transforming Position/Direction Data. 09/30/1998 Date: format dd/mm/yyyy. 30/09/1998 Date: format dd mon yyyy.g. 30/09/98 Date: format dd mon yy. e. e.g. e.g. Real UDA may have distance or bore units and will be reported as such.g. For example: #T/TEM24 #T may be used in PLTX or DMTX attributes of Dimensions or Dimension Points. For example: ’ABC#10DEF’ would appear on a drawing as ABCvvvvvvDEF (where v is used here to denote a space).8 14. For example: #NAME#24#CATR output NAME. The codeword #T/name must be the only content of the text string. taking the form #n.0 . The tabbing codeword controls tabbing. 14. where n is the number of the column where the next character is to be output. The referenced text string may contain intelligent text codeword strings. For example: ’#NAME#5#CATR#10#CREF’ would expand to /PUMP1/NSv/NFJJv/PIPE1-1 14:8 12.DRAFT User Guide Intelligent Text DDMONYYYY DDMONYY which gives a format equivalent to CDATE which gives a format equivalent to CDATEX 14.1 Codewords with Special Functions Template Codeword #Tname is the Template codeword. name refers to a text template TXTM. where n is the number of the column where the next character is to be output. 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. However the BTEX attribute of a TXTM cannot itself contain a #T codeword since this could lead to recursion. or in the BTEX attribute of Labels (GLAB or SLAB) or text primitives (TEXP).8. which enables complex text strings to be defined once in a Text Template (TXTM element).2 Tab Generator Codeword #n is the tab generator codeword. then output Catalogue Reference starting in column 24 The blanks in the output character string will be padded with spaces.8. This template may then be referenced from other elements. 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. style 6 or 7) allows you to arrange text neatly in a tabular form. 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.DRAFT User Guide Intelligent Text Tabbing will take account of linefeeds within the text string. GBOX should be set to zero in order for the leaderline to meet the underline. 14.g. 14.8.8. If one of the above codes is used. it is not treated as a codeword. it is possible to generate schedules on drawings easily.4 # Character The codeword ##outputs a single # character.8. when selecting a True Type font from the selection form: 14:9 12.0 . See Schedule Generation.5 Underlining #< #> start underline finish underline When a GLAB text string has been underlined. 14. 14. when the corresponding style is already set as requested by the codeword. Used in combination with Autotagging and the PDMS Programmable Macro Language (PML). whether specified explicitly or by the new line generator code ’#/’.3 New Line Generator The codeword #/ generates a new line. They are not treated as codewords when the PDMS font is in use.6 Emboldening and Italicising %B %b %I %i use the Bold style of the current font turn off the Bold style of the current font use the Italic style of the current font turn off the Italic style of the current font The codes above apply only to intelligent text rendered using a TrueType font.8. if n1 is omitted then 1 is assumed by default.2 Substring Definition by Parts You can define a substring by reference to the constituent parts of the original string. A part of a string is defined by delimiters. If you do #PIPE(C2:) expands to ‘ZONE-4/PIPE-6’ 14. which are user-definable. and if n2 is omitted then the last character of the string is assumed.9.DRAFT User Guide Intelligent Text 14. 14.1 String Definition by Characters Substrings can be extracted from text by following the code word with a substring descriptor of the form: (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.9 Substrings There are two methods of specifying that a substring of the data associated with a code word is required for output.0 . For example: If #PIPE expands to ‘/ZONE-4/PIPE-6’ then #PIPE(C2:6) expands to ‘ZONE-’ By default all PDMS names will be output with the initial slash. The substring required is specified by following the code word with a substring descriptor of the form: (P-n1:n2) 14:10 12.9. DRAFT User Guide Intelligent Text Here P indicates that n1 and n2 refer to delimiter numbers and ‘-‘ indicates the character used as the delimiter. for example. when expanded. one of the integers may be omitted. Any number of substring definitions is allowed. () This is shorthand for (C1:) 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: #POS #NAME #POS()#NAME would. ‘/’ is assumed. For example: #CRFA[2] #:ARRAY[4.10 Array Indexing The format used for the array indices is: [n] or [ n. the second generates a range of array elements. the delimiter before n1 is always included in the output substring but the delimiter after n2 is always excluded.m] where n and m are integers and m is greater than n. when a space is not required between codeword data. Components of position attributes (Eastings. In the second format. If omitted. These are processed sequentially. The first format generates a single array element. 14. Array indices may be used (where appropriate) with both basic codewords and UDA names. If n1 is omitted then the substring will start at the beginning of the ‘parent’ string. where K is the significant length of the array. and if n2 is omitted then the substring will end at the end of the ‘parent’ string. The delimiter must not be numeric. Omission of the first integer implies n=1. For example: If #PIPE expands to the parent string ‘/ZONE-4/PIPE-6’ then #PIPE(P/2:) expands to ‘/PIPE-6’ and #PIPE(P-:2) expands to ‘/ZONE-4/PIPE’ EIt is possible to append a number of substring definitions (both character type and part type) to a code word. left to right. have a space between the two data items: would not. and omission of the second implies m=K. position. The length of an array attribute can be extracted and applied to a sheet using: ‘codeword[SIZE]’ 14:11 12. The start and end of the ‘parent’ string are always assumed to be delimiters. Northings and Uppings) should be extracted using the special codewords for that purpose (e. n1 and n2 are integers that indicate respectively the delimiter numbers at which the substring is to start and finish. For example: #PIPE(P2:)(C2:) expands to ‘PIPE-6’ There is a special form of the substring descriptor. #POSU). displacement or direction attributes.g.0 . Array indices cannot be used with text.6] Embedded spaces are allowed within an array index but are not mandatory. it must refer to an owner of the Design element specified in the DDNM attribute. The [SIZE] suffix may be used with any hash code-word for which array indices are valid.e. This parameter may be a word or name that specifies a Design element. to report the position of P3 of a Box with respect to the Box origin: #P3POS<WRT CE> Only position. 14. P-lines and Structural derived attributes. the implied syntax is: <WRT WORL> The qualifier ‘CE’ must be used to refer to the coordinate system of the current element. it should refer to a reference attribute of the DDNM element. This may be the immediate owner or an element in the database hierarchy above the DDNM element. position and direction attributes will be reported in the coordinate system of the specified element. WRT must be followed by a single parameter to define the coordinate system required. minimum abbreviation is W (or w). If a reference attribute is specified. direction. The qualifier may be used with any position or direction codeword. When outputting a qualified position in +/.format. displacement and orientation codewords may have transform qualifiers. for example: #P1POSU+<WRT /DATUM> 14:12 12. The qualifier uses the keyword WRT (‘with respect to’) to denote the coordinate system to be used.0 . If a name is used. For example. the ‘+’ must appear before the qualifier. This includes some P-line and p-point attributes. including those for p-points.11 Transforming Position/Direction Data If qualified by a transform keyword.DRAFT User Guide Intelligent Text SIZE may be abbreviated down to S and may be lower-case.i. For example: #P1POS<WRT /1201A> This will output the position of p-point 1 of the DDNM element with respect to element / 1201A. for example OWNE or CREF. for example: #POS<WRT ZONE> #POSU<WRT OWNE> If an element type is specified. it must not contain the comma (. 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 . Lower case as wrt is also allowed. The word parameter may either define an element type or a reference attribute.) or closed angle-bracket (>) characters. 0 . This element may be specified by name. The last is a reference array attribute and must be followed by an array index. which may be abbreviated to F (or f). the referenced element being accessed. This keyword may be followed by one or more parameters separated by spaces: <FROM parameter> <FROM parameter parameter parameter> The format for each parameter is the same as that for the transform qualifier (WRT). Up to five parameters may be used. element type or reference attribute. #PARA[3]<FROM /VCHJJ> Outputs value of third array element of relevant PARA #DUTY<FROM CRFA[2]> Outputs the DUTY of the Branch referred to by CRFA[2] The first three examples refer explicitly to elements by name or type. #MTXZ<FROM /VALVE1 TUBE> The order of parameters is important: Outputs the ZTEXT relevant to the implied tubing of /VALVE1. A complicated case might be: 14:13 12.12 Extracting Attribute Data from any Specified Element Attribute data may be extracted from any element rather than the element defined by the DDNM attribute. The keyword for this navigation qualifier is FROM (or from). <FROM CREF OWNE> <FROM OWNE CREF> These two FROM keyword formats do not have the same meaning. Outputs the HBOR of the Branch referred to by the CREF of the DDNM element Outputs the SPRE of the element referred to by the :fred attribute of the DDNM Outputs value of third array element of relevant PARA attribute from referenced catalogue Component.e. element type or reference attribute. i. For example: #POS<FROM /VESS1> #POSE<FROM SITE> #DTXR<FROM TUBE> #HBOR<FROM CREF> #SPRE<FROM :fred> #PARA[3]<FROM SPRE CATR> Outputs the position of /VESS1 (in World coordinates) Outputs the Easting of the Site above the DDNMelement Outputs detailing RTEXT for the implied Tube associated with the DDNM element. The first means the owner of the element specified by the CREF attribute and the second means the element specified by the CREF attribute of the owner. The next three contain reference attributes of the current element. attribute from referenced catalogue Component. More than one navigation parameter may be used to enable compound navigation to acces <FROM CRFA[2] OWNE> means data from the owner of the element referred to by CRFA[2].DRAFT User Guide Intelligent Text 14. element name. as referred to by the DDNM attribute of the annotation element. (Note that SPREF is a pseudo-attribute of NOZZ as well as being a standard attribute for all Piping Components. whatever the order of syntax.1 General The format of distance. 5’-5 13/16” set bores in inches set distances in centimetres set bores in centimetres 14:14 12.reference attributes can be used within codeword navigation qualifiers.13/16 set distance units to ‘USA style’ feet and inches. It is possible to apply both navigation and transform qualifiers. 5’5. e. All intelligent text codewords generate the same format for ‘FINCH’ and ‘FINCH US’ units (as set in the UCOD attribute of the Layer): UCOD FINCH DIST UCOD FINCH US DIST UCOD INCH BORE UCOD CM DIST UCOD CM BORE set distance units to ‘PDMS style’ feet and inches. Standard Codewords such as #BRAN and #DRWG are equivalent to #NAME<FROM BRAN> etc. Position and Bore Data Output 14. For example: #POS<FROM OWNE. For example: #POS<FROM /EQUIP.DRAFT User Guide Intelligent Text <FROM OWNE CREF OWNE :UDARR[3]> This means that data is to be extracted from the third element referred to in the UDA reference attribute ‘:UDARR’ of the owner of the CREF element of the owner of the current Design element. This is normally the current Design element.13 Distance. the appropriate current element is usually used for data extraction. WRT /DATUM> Note that the navigation qualifier is always applied before the transform qualifier. e. the position of /EQUIP will be output in the coordinate system of the ZONE which owns /EQUIP. position and bore data generated by codewords is controlled by the UCOD attribute of the Layer element.0 .) 14. navigation is from the annotation element. However where the codeword obviously refers to annotation data (for example #AUTH. An example of this is #PRFL. Pseudo. WRT ZONE> Here. However certain codewords extract data from a specific element type rather than from the current element.g. If the navigation qualifier is omitted. rather than the Zone of the DDNM element. #TITL refer to AUTH and TITL attributes in the DRAFT database).13.g. Data is extracted from the PRFL attribute of the SUBS element which owns the current element. The starting point for navigation is the current element. For example #XXXX<FR SPREF> will extract the data for attribute XXXX of the element referenced by attribute SPREF of the current Design element. DRAFT User Guide Intelligent Text FINCH (PDMS): 25’3. UCOD settings can be queried by using the pseudo-attributes: Q UCODD and Q UCODB 14. The units may be switched back to the standard units by a subsequent use of a %U code.5 or 1. These are: INCH USA INCH PDMS INCH DECIMAL output of the form: 1/2” or 1 1/2” or 24 output of the form: 0.0 If the qualifier is omitted then DECIMAL is assumed.0 .1/2 or 1. as defined below. A nominal/actual qualifier is available for bores.5 or 24.1/2 or 24 output of the form: 0. the intelligent text string: ’#DIM() %U(#DIM())’ should be used. The two qualifiers have exactly the same effect as the general PDMS PRECI BORE NOM (or PRECI BORE ACT) commands. For example UCOD FINCH PDMS BORES ACT UCOD FI US BO NOM The setting is NOMINAL by default. The UCOD setting controls the bore sizes output to a drawing by DRAFT’s intelligent text system. to generate a dimension in both Imperial and metric units.1/2 FINCH US: 25’-3 1/2” The INCH option may be qualified to allow different formats for distance. position. with the second value in brackets.13. 14:15 12. and bore values generated by intelligent text codewords. Layer Units UCOD INCH DECI UCOD INCH PDMS UCOD INCH US UCOD FINCH PDMS UCOD FINCH US UCOD MM UCOD CM UCOD METRE Alternate Units MM MM MM MM MM INCH DECI INCH DECI INCH DECI The ‘switch units’ code is %U so. which will cause all distances and bores which follow to be output in ‘alternate’ units. for example.2 Mixed Units within Intelligent Text Strings The units used in intelligent text strings are determined by the UCOD attribute of the owning LAYE. However. it is possible to insert a ‘switch units’ code in the text string. imperial fractional values. 32nds and 1 (dp) respectively. SHLB. and angles. By default.3 Controlling the Precision of the Generated Output The precision of both linear and angular data is controlled by the Precision Code (PCODE) attribute. 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. Imperial decimal values.0 . To control the output formats of the positional codewords. Angles output in the decimal format will have no symbols.13. Instead they use the ship reference coordinate system or the XYZ format to describe the position of design model objects. Four pseudo-attributes exist to allow the querying of the individual parts of the PCODE attribute: Q PCODMms Q PCODInches Q PCODFractions Q PCODAngles query metric (mm) precision query Imperial (inch) precision query fraction precision query angle precision 14.e. attributes POSFOR (positional code word format) and GRSYS (grid system) are provided for the following PADD data elements: DEPT LIBY REGI SHLB DRWG OVER SHEE DRTMLB VIEW DRTMPL LAYE SHTMPL 14:16 12.) The following are examples of setting PCODE: PCODE LIN MM TO 2 DPLS PCODE LIN IN TO 2 DPLS PCODE LIN FRA TO 32 NDS PCODE ANG DEG PCODE ANG TO 2 DPLS Set linear (metric) precision to two decimal places Set linear (Imperial) precision to two decimal places Set linear (Imperial. LIBY. PCODE is an attribute of the DEPT. these four values are 0 (dp). output will be set to 4 dp for metre output and 2 dp for centimetre output. ’ or ”). with its value being cascaded down the database hierarchy. fractional) precision to 32nds Set angular precision to nearest whole number of degrees Set linear angular precision to two decimal places Angles output in degrees.14 Position Output Formats Marine users do not use the ENU (East North Up) coordinate system. If required a ° symbol can be accessed from DRAFT’s alternative character set by using the code ~0. minutes or seconds will be in the standard format (i. DRWG. OVER and LAYE elements. 1 (dp). PCODE stores four values of precision for metric (decimal) values. The same coordinate system is used through a particular layer. REGI. using °.DRAFT User Guide Intelligent Text 14. (dp = decimal places. g. ‘X=FR20+200’. there is no other way to override the expansion format individually for a given code word. 14:17 12.g. ‘Y=LP-5’. ‘E 1000’.g.DRAFT User Guide Intelligent Text These two attributes control the output format of the positional codewords that request the position of certain elements (e. Other than using the ‘+’ suffix.0 . a separate LAYE with different settings can be created. The following values are defined for the attribute: Value 0 1 2 3 Test equivalent (query system) ENU XYZ SHIP NUM/BERS Description Default ENU output style (e. #POS+). The value of the attribute will cascade down from the DEPT or LIBY element to their child elements when they are created. ‘Y=-2000’) Ship reference coordinate format (e. the XYZ output is generated instead.g. However. #P2POS.g. as if the XYZ expansion had been requested (e. X=FR40. requesting a purely numerical output (NUMBERS format). If the ‘+’ modifier follows the position code word (e.2 GRSYS (Grid System) Attribute This attribute specifies the grid system to use during a search for the ‘nearest’ GRIDLN element. #PKTOP^POSE). 14. the request for a corresponding coordinate expressed in the Ship Reference System will return instead the coordinate expressed as a pure number in millimetres. Y=LP4. ‘S 2000’) The XYZ output style (e. ‘X=1000’.14. #PKNA^POSS. ‘-2000’).g. ‘Z=DECK02+1500’) Numerical output style (e.14. it overrides the expansion format setting defined by the LAYE. and the element using intelligent text placed there.1 POSFOR (Positional Code Word Format) Attribute This attribute specifies the output format for the positional codewords used by elements owned by the layer (LAYE). 14. If the POSFOR attribute has a different value. If the search for the GRIDLN element fails (no suitable grid lines). Example: POSFOR SHIP sets the output format for positional codewords to ship reference coordinate format. when generating the output from positional codewords used by elements whose POSFOR attribute has a value of 2 (Ship Reference System). Z=5000).g. ‘1000’. as if the ‘+’ suffix was present in the code word If the project does not define the FR or LP positions along one or more of the axes. #POS. the GRSYS attribute is ignored. and its setting will be cascaded down the hierarchy.) All components except the first are optional. The NTEXT attribute allows you to substitute your own ‘null text’.0 .Summary The combined format for a codeword string may be summarised as follows: #word + ^word + [n. LIBY. The substring editing qualifiers may appear more than once in any order. It is an attribute of DEPT. 14. Example: GRSYS NULREF tells DRAFT to use all available grid systems with the default orientation (0. REGI and DRWG. The combined format for the data qualifier list is: <FROM parameter [parameter]. OVER and LAYE elements. 14.m] + <qualifiers> + (Cn1:n2) (P/n1:n2) substring editing by parts substring editing by characters data qualifier array index sub-codeword (after #PK only) basic codeword or UDA name (The + signs are not literal.DRAFT User Guide Intelligent Text The value of the attribute will cascade down from the DEPT or LIBY element to their child elements when they are created. WRT parameter> 14:18 12. All qualifiers may contain embedded spaces.16 Intelligent Text Syntax . 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. For example: NTEXT ’No data’ NTEXT may consist of up to 12 characters. 0. therefore the closing delimiters cannot be omitted.15 Customizing Error Text When it is not possible to extract data from an attribute. Some combinations have no meaning. SHLB. the intelligent text system returns an error and (by default) substitutes the text ‘---’ for the missing data. Lower case and upper case (but not mixed case) forms of all codewords are valid. use the value of the BTEX attribute of text template / T24 detailing RTEXT from the implied rod of the current element outputs VIEW scale as a ratio. as specified by the VRATIO attribute. When a piece of text generated from a # code word itself contains a # code (or a ~ code or % code.DRAFT User Guide Intelligent Text Examples of Codeword Strings #POS<FROM OWNE. 180 characters in their expanded form. 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. Where the word owner appears (unenclosed by quotes) then this means the true owner. delimited by '/'. The P-line name has been omitted. 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 . meaning the P-line used to position annotation At a SCTN this means the POSE attribute. #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. General points: • • • All text strings have a maximum length of 120 characters in unexpanded form. of the HREF of the owner end position of P-line NA in framework coordinates Easting of P-line start position in world coordinates.17 Notes In the codeword descriptions given in this section. otherwise it means the Easting of the POS attribute owner of element 2 of CRFA attribute name of element specified in :udarr[2] of element specified in CREF array element 3 of UDA attribute :FRED of the owning Equipment.0 .not necessarily the true owner. WRT SITE> #CRFA[2]<FROM /VFWA1> #HREF<FROM OWNE>(P/2:3) #PKNA^POSE<WRT FRMW> #PK^POSSE position of owner in Site coordinates name of second element of CRFA attribute of /VFWA1 parts 2 and 3. 14:19 12. N or U (for x = POS. TOP or CON u = blank. where n = integer 0-99 or L or A x = POS.g..2 DRAFT Drawing World Hash Codes. BOR. #NAME #EQUI #HPOSa #HREF #DSCO #PRES #TCON #TREF #CATR #TPOSa #HDIR #INSC #LNTP #TDIR #LBOR #BRAN #PRFL #STEX #HBOR #OWNER #PIPE #HPOS #FUNC #LENG #TBOR #SPREF #POS #CREF #PTSP #BORE #FLOW #ABOR #POSa #TPOS #DUTY #TEMP #HCON a = N. BOP. DIR..18.18 Summary of Commands 14.0 .1 Design World Hash Codes (examples). TOP only e.. #DTITL #STITL #VTITL Drawing title Sheet title VIEW title 14:20 12. E..18. BOP.DRAFT User Guide Intelligent Text 14. P3BOR #CRFA #LSRO #GRA #ANTY #NPOS #POSS #POSE #DERCUT #JOIS #STSP #FIRE #DESC #NPOSE #POSSE #POSEE #DERLEN #JOIE #MATR #ZDIS #FIXT #NPOSN #POSSN #POSEN #DRPS #LSTU #ISPE #CUTB #HSTU #INRE #HSRO #NPOSU #POSSU #POSEU #DRPSE #DRPSN #DRPSU 14. E or U Pnxu. SPACE or RETURN) 14. #codeword[n] or #codeword[n... ( . the second generates a range of array elements.18.. #CDATE #APPR #APDT #RVSN #RVDT #RVAU Drawing name 3D Dimension Point position.. 14. (Cn1:n2) (P/n1:n2) () Substring by characters Substring by parts remove gap between subsequent hash codes 14.18.4 Hash Code Delimiters....5 Sub-Strings. Next character to be output in column n.0 .18. 14:21 12. E or U Author (of DRWG or SHEE) date of creation (of DRWG) approver date of approval revision date of revision revision author 14. gives position in ‘+/-’ format instead of ENU.18.6 Array Indexing. where a = N.. when appended to position codeword.m] where n and m are integers and m is greater than n. The first format generates a single array element.DRAFT User Guide Intelligent Text #DRWG #DIMPOSa #AUTH #ADATE. This is only available for position-generating codewords.3 Special Characters. #BDATE. #Tname #/ ## #< #> #n + template codeword new line single # start underline finish underline tabbing codeword. .. the position will be determined with respect to its origin... If the WRT qualifier indicates a particular grid system.18.10 Querying.. <WRT qualifier> where qualifier is a word or a name that specifies a Design element.18. 14.. taking into account also its orientation.e. i. Q EXBTEX Query expanded form of BTEX attribute 14:22 12.0 .DRAFT User Guide Intelligent Text 14.18..7 Transforming Position/Direction Data. the XYZ output format is chosen instead.18.9 Extraction of P-line Data. element type or reference attribute. The ship reference format (POSFOR SHIP) is handled in a special way. element name.8 Attribute Navigation.. #PK[p-line name][p-line sub-codeword] The available sub-codewords are: ^DIR ^POSS ^POSSE ^POSSN ^POSSU ^POSE ^POSEE ^POSEN ^POSEU ^PKDI ^PKDIE ^PKDIN ^PKDIU p-line direction p-line start position Easting of p-line start position Northing of p-line start position Upping of p-line start position p-line end position Easting of p-line end position Northing of p-line end position Upping of p-line end position position of point along p-line defined by PKDI attribute Easting of point along p-line defined by PKDI attribute Northing of point along p-line defined by PKDI attribute Upping of point along p-line defined by PKDI attribute 14. <FROM parameter> <FROM parameter parameter parameter> The format for each parameter is the same as that for the transform qualifier (WRT). If this qualifier is neither a grid system. 14. nor a world. PDMS style set distance units in metres set bores in inches set inch output to appropriate format set bores in mm set bores in metres query distance units query bore units 14.12 Setting Units (at LAYE). USA styl set distance units in feet & inches. query metric (mm) precision query Imperial (inch) precision 14:23 12. UPDATE option ANNO update attributes holding hash codes options: DRAW. VIEW. PCODE LINEAR MM TO integer DPLS PCODE LINEAR NCHES TO integer DPLS PCODE LINEAR FRACTIONS TO integer [THS | NDS] PCODE ANGLES TO integer [DPLS | DEGREES | MINUTES | SECONDS] Q PCODMms Q PCODInches set linear (metric) precision to integer decimal places set linear (Imperial) precision to integer decimal places set linear (fractional.DRAFT User Guide Intelligent Text Q EXPLTX Q EXDMTX Query expanded form of PLTX attribute Query expanded form of DMTX attribute 14.. or seconds). or minutes..11 Updating.18. LAYE 14.18. Imperial) precision to integer 32ths (or 32nds) set angular precision to integer decimal places (or degrees... SHEE.0 . UCODE FINCH US DIST UCODE FINCH DIST UCODE METRE DIST UCODE INCH BORE UCODE INCH USA UCODE INCH PDMS UCODE INCH DECIMAL UCODE MM BORE UCODE METRE BORE Q UCODD Q UCODB set distance units in feet & inches.18...13 Controlling the Precision of the Generated Output. 0 . GRSYS name/reference Note: The GRIDSY attribute is taken into account only if the POSFOR attribute has the value SHIP. consider exclusively the grid system given in the command.14 Setting Position Output Format POSFOR ENU POSFOR XYZ POSFOR SHIP POSFOR NUMbers set output format to ENU (default) set output format to XYZ set output format to ship reference coordinates set output format to numeric output style 14.18. 0. 0) and purpose SHIP when searching for the nearest GRIDLN.18. consider all available grid systems with the default orientation (0. It is an error to pass a name or reference to something other than a GRIDSY element.15 Specifying the Grid System (for GRIDLIN search) GRSYS NULREF when searching for the nearest GRIDLN.DRAFT User Guide Intelligent Text Q PCODFractions Q PCODAngles query fraction precision query angle precision 14. 14:24 12. FONT. and as part of the 2D-drafting facilities (TEXP elements). text is used by Dimensions (dimension line and projection line text). also the ATEX. which can be set up in ADMIN. (For completeness the font attributes can also be set to 10. These can include user-defined fonts. 2. The installation and configuration of True Type fonts is a system administration function. (See the ADMIN Command Reference Manual for details.) The AVEVA system now supports both PDMS (native) fonts.2 PDMS Fonts DRAFT makes use of the four PDMS font families. There are three text font attributes . and standard Windows True Type fonts. and PFON. PLTX and ETEX text attributes. or 4 in which case the normal version of the relevant font family will be obtained. Labels. and 4). and 40 which are also equivalent to 1. 31. and 41 are equivalent to 1. Variation 5 is always bold and forwardsloping. These font attributes can be set to 1.1 True Type Fonts True Type fonts are only available if they are present on each workstation running AVEVA Plant and are registered in the project’s SYSTEM database. 21. 15:1 12. In such cases the selection of a bold option will result in the use of the appropriate normal font.). 3. font 35 is variation 5 of font family 3. 15. These are used to define the appearance of the various text strings that can appear on Drawings. Variations on these normal versions can be obtained by setting the font attributes to a value obtained from the table below. The text is set using the BTEX. 2. Normal Upward 1 2 3 4 11 21 31 41 Forward 12 22 32 42 Reverse 13 23 33 43 Bold Upward 14 24 34 44 Forward 15 25 35 45 Reverse 16 26 36 46 For example. DFON. 15. DMTX or PLTX attribute of those elements. (See Special Labels and Text Label Templates for other uses of BTEX. 30. Bold fonts are not provided for all font families. 2. as appropriate. and 4.0 . 3. 3. which are supplied with the AVEVA product. From the table it will be seen that fonts 11. DMTX.DRAFT User Guide Miscellaneous Text Facilities 15 Miscellaneous Text Facilities Within DRAFT. 20. %p. %08.switch back to previous font (i. or PFON attribute. as the font switch to a TrueType font specified after the '%' character.1 Alternative Character Set DRAFT incorporates an alternative character set that provides useful symbols. The string will start to be output using the principal font.invalid. Note that the extension character set.e.g. and %t are currently allowed Font switching can be prevented and the escape character output by doubling it (i. subject to a maximum of four fonts per string. toggle) .switch to font 46 . that defined by the font attribute . upright bold) of the principal font. 15. Since the font numbers 05. the steelwork I-beam symbol could be defined as a TEXP by setting the BTEX attribute as: BTEX ’~I’ The tilde may be input as normal text by doubling it (i. Invalid codes (e. which provides the special symbols. These sets are best demonstrated by examples: %24 %46 %02 %30 %37 %51 %2 %P %T %C . ’~~’ produces a single tilde). The special handling of the '0' digit (preserving the current font family or variation) applies to PDMS fonts only.3. %T. 08. %06.3 Multiple Fonts within Text Strings It is possible to switch from one font to another within a single text string. %51) will be output literally.switch to variation 2 of the current font family . Normal text. %07. 07. ‘DEF’) in variation 4 (i. or even parts of words to be emphasised. and 09 are reserved for TrueType fonts. the font switching sequences %05. font family 5 is not defined (only families 1 . This set will be composed of an escape character (%) followed by either two numeric digits or one alpha character.e.e.0 . individual words. 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.e.invalid.4) . See Figure 15:1. only %P. 06.e. and %09 are interpreted literally. this is the one specified by the relevant FONT. DFON. intelligent text and ‘alternative’ characters may be input in any combination. Font switching is controlled by a set of special characters embedded in the string.switch to font 24 (i. This will allow sub-strings. variation 7 is not defined (only variations 1 .switch to font family 3 maintaining the current variation .6) . %%). An ‘alternative’ character is specified by preceding one of a set of normal alphanumeric characters by the tilde (~) sign. The font switching character sequence does not have to be preceded or followed by blank characters.DRAFT User Guide Miscellaneous Text Facilities 15. 15:2 12.switch to principal font (i.e. counts as a font.e.: Alternative Character Set for the full list of available symbols. For example.invalid.invalid. two numeric digits are required . variation 4 of font family 2 . and the middle three characters (i. string exchange facility operating on the attribute in question (see below). Alternative Character Set 15.0 .DRAFT User Guide Miscellaneous Text Facilities Symbol Code B C D E F G H I J K L M N O P Q R S T U V Meaning Footnote symbol Centreline symbol Diameter symbol Symbol Code W X Y Z Meaning Omega Superscript `1' Superscript `2' Superscript `3' Degrees symbol or superscript 0 Steelwork Channel Steelwork Angle Steelwork H-Section Steelwork I-Section Steelwork T-Section Steelwork Double Angle Steelwork L-Section Mu Yen sign Steelwork hollow circular Section Plate symbol Copyright symbol Registered trademark symbol Steelwork hollow rectangular Section Trademark symbol 0 1 2 3 4 5 6 7 * + / < = > [ Line Left arrow Hash Right arrow Much less than Much greater than Up arrow Down arrow ] ^ Figure 15:1. which gives a simple case-sensitive. 15:3 12.4 Editing Text Editing a text attribute is achieved through use of the EDTEXT command. If text_type is not specified. if found) EDT ’fox’ ’fish’ EDT PLTX 3 ’we’ ’a’ EDT OSFN ’A3’ ’A4’ EDT DATE ’1990’ ’1991’ Note: When editing intelligent text the intelligent text code itself must be specified. If this is omitted then the first occurrence.e. not the ‘resultant’ text. The different syntax options of the EDTEXT command are illustrated by the examples given below. ‘fox’ is not found) (attribute PLTX would be altered. replaced by string_2). the cow and the rabbit were in my garden’ (no change. BTEX is assumed.0 . if a value of 0 is specified then all occurrences of string_1 are processed (i.DRAFT User Guide Miscellaneous Text Facilities The EDTEXT command takes the general forms: EDT text_type numberstring_1 string_2 text_type is the text attribute in question. that cat and the rabbit were in the garden’ EDT ’the rabbit’ ’Dolores’ gives: ’The dog. The command EDT text_type APP string will append the given string to the specified text attribute. is assumed. Target string: ‘The dog. which can be any DRAFT text attribute. the cat and Dolores were in the garden’ (change second occurrence of ‘the’ to ‘that’) EDT 2 ’the’ ’that’ gives: ’The dog. the cat and the rabbit were in the garden’ EDT ’the’ ’that’ gives: (change first occurrence of ‘the’ to ‘that’) ’The dog. 15:4 12. including the name attributes OSFN and BSFN. number Several editing instructions may be given in the same command line. if found) (DATE would be altered. if found) (OSFN would be altered. the cat and that rabbit were in the garden’ (change all occurrences of ‘the’ to ‘that’) EDT 0 ’the’ ’that’ gives: ’The dog. is the order of occurrence of string_1 within the target string. that cat and that rabbit were in that garden’ EDT ’dog’ ’horse’ ’at’ ’ow’ 3 ’the’ my’ gives: ’The horse. 15:5 12. 6 face Font no. whereas PFON and DFON identify TrueType fonts (see the ADMIN User Guide). DFON. 1 IR 2 IR 3 IR 4 IR 6 Style 6 Style 4 Style 6 Style 1 Angle 2 Angle 3 Angle 6 Angle 17 17 17 17 ‘Times New Roman’ ‘Arial’ (Arial) (Times) 15. 5 Italic version of the TrueType font no. 5 Bold and Italic version of the TrueType font no. and PFON identify the font to be used for displaying textual information in a drawing. as in the following examples: FONT 1 or PFON 5 DFON 19 In the above example. They can be assigned the font number directly. etc. for example the following information: Fontdirectory /%PDMSEXE% Fontfamily Fontfamily Fontfamily Fontfamily TrueType fonts: Font no. 5 Note that for PDMS fonts the font itself determines its style (Bold. 5 face The commands Q FONTS PDMS Q FONTS TRUETYPE will show either PDMS or TrueType fonts only. the FONT attribute is assigned a PDMS font no.5 Querying Fonts You can display information about all the fonts configured on the system using the command: Q FONTS This may provide.0 .). For TrueType fonts it is possible to preset the fonts as Bold and/or Italic.DRAFT User Guide Miscellaneous Text Facilities 15. Therefore: PFON 1005 PFON 2005 PFON 3005 Bold version of the TrueType font no.6 Assigning Fonts The attributes FONT. Italic. 1. its face name is used instead. The gap for descenders between the base line and the bottom of body is one third of the character height.: Character Height. 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. either in its basic style.0 .7 Character Height DRAFT measures character height from the character base line to the top of the character body. or with the Bold or Italic attributes correspondingly. Character Height The gap between the capitals line and the top of the character body is 20% of the character height. whose description is 'BOM font'. Top of body Capitals line Base line Bottom of body ÁËôý = LHEI (Label Text) DTLH (Dimension Line Text) PTLH (Projection Line Text) CHEI (Label Text) DTCH (Dim Line Text) PTCH (Proj Line Text Letter Height Character Height Figure 15:2. so the letter height = 0. See Figure 15:2. (These proportions do not apply to the SCRIPT font. 15. 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.) Letter Height Character Height = 15:6 12. Note that if the font description is empty.8* character height. Note that the words 'Bold' and 'Italic' must be spelled as shown above to be recognised.DRAFT User Guide Miscellaneous Text Facilities For TrueType fonts it is also possible to specify the font by name: FONT FONT FONT FONT 'BOM 'BOM 'BOM 'BOM font' font Bold' font Italic' font Bold Italic' The above commands select the TrueType font. DRAFT User Guide Miscellaneous Text Facilities 15:7 12.0 . 0 .DRAFT User Guide Miscellaneous Text Facilities 15:8 12. as follows: PPLINe word OF element_identifier STart PPLINe word OF element_identifier ENd The start and end of a p-line are the points at which the p-line crosses the two end-cutting planes of a Section. PPLINe word OF element_identifier units_value This syntax defines an absolute distance from the start of the p-line. it is necessary to specify a distance along that p-line. it may also be used to define the angle of the Label or View Note to the horizontal in the view region. PPLINe word OF element_identifier 16:1 12.0 and 1. In addition. dimensioned and used in 2D drafting. This means that positions and directions in the Design World must be obtained for these elements. There is no change in the functionality for annotating these. where the direction of a p-line is used for position on a Label or View Note.DRAFT User Guide Annotating Structural Elements in DRAFT 16 16. Dimension points of type DPBA do not require p-line data since they are concerned with the limits of a Design element. Annotation elements which (may) require a 3D position include labels (GLAB. SLAB). 16. These are proportional distances 0. Angular Dimension elements (ADIM) and two types of dimension points: DPPT and DPBA. Fittings. In order to use p-line for position.2 3D Position from a P-line Wherever a Design element or p-point may be used for position. This may be done using syntax based on that in DESIGN. The start and end of the neutral axis are coincident with the points defined by the POSS and POSE attributes of the Section. a p-line is a line in a given direction between two points.0 . PPLINe word OF element_identifier PROPortion value This syntax defines a proportional distance along the p-line from its start. Annotation elements that require a 3D direction include Linear dimension elements (LDIM) and Dimension Points of type APPT. may be labelled.0 respectively. a p-line may also be used. However. drafting primitives whose drafting point references (PTRF or PTFA) use a PPPT (drafting point with design data). Nodes and Joints with p-points are treated in the same way as other elements.1 Annotating Structural Elements in DRAFT Basic Annotation Structural elements. View Notes (VNOT). like other Design elements. and does not define a single position. FROM DIRection PPLINe word OF element_identifier -Z [DIRection] TO DIRection PPLINe word OF element_identifier NEGative However. as follows: PPLINe word OF element_identifier This defines the direction along the p-line in the Design. The syntax for p-line direction is based on that in DESIGN. The p-line itself may be used for direction.4 Angle from a P-line The p-line direction as defined above may be used to set an angle.plxyz where plxyz is any one of: X [DIRection] Y [DIRection] Z [DIRection] LEAve [DIRection] The axis of the p-line along the length of the Section is its Y direction. A direction parallel to an axis of the p-line itself may also be selected: PPLINe word [OF element_identifier] [+] plxyz PPLINe word [OF element_identifier] . Syntax for p-line direction qualified by <plxyz> cannot be used to set p-line attributes in the annotation. 16.3 3D Direction from a P-line Wherever a Design element or p-point is used for a direction. meaning the mid-point of the p-line. This default may be altered by using the PKDI SETD command (see P-line Distance). This is true of any element with an ADEG attribute. such as a drafting primitive. or an axis of the p-line may be used. the following command would actually store p-line data in the annotation element: TO DIRection PPLINe word OF element_identifier In this case the p-line direction has not been qualified by specifying an axis.DRAFT User Guide Annotating Structural Elements in DRAFT When no p-line position is stated explicitly the default value for proportional distance is used. The reverse of these directions may be obtained by the use of the minus sign. a p-line may also be used. The Z or Leave direction and the X direction both lie in the plane of the perpendicular cross-section of the Section.0 . DIRECTION syntax of this form will be used to set the DIR attribute rather than p-line attributes. 16:2 12.5. This is equivalent to specifying the p-line -Y direction. The initial value is 0. The following commands are examples of this: NEW LDIM DIRection PPLINe word OF element_identifier LEAVE [DIRection] NEW ADIM ON . This syntax must be used if you wish to store the p-line in the annotation element. Therefore the axis along the length of the Section is what is required and will be stored directly in the database as such. 16... PPLINe word OF element_identifier NEGative This syntax specifies the negative or reverse direction along the p-line in the Design. 5 P-line Attributes The syntax for position. When a p-line is in use. If the p-line is used for position. there is an additional possibility.plxyz ADEGrees PPLINe word OF element_identifier [+] plxyz If p-line is required for angle on a Label or View Note. SLAB) and View Notes (VNOT). the value 0 is taken to mean the neutral axis of the specified Design element. 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. 16. The exception to this is where p-line is used for angle. if that is set. This case is described further in the section on p-line angle (see below). This may be NA. 16:3 12. The ANGle PPLINe syntax may also be used to store p-line for angle in the database. This is normally used to set the ADEG attribute: ANGle PPLINe word OF element_identifier [+] plxyz ANGle PPLINe word OF element_identifier . Where no pline name is specified.DRAFT User Guide Annotating Structural Elements in DRAFT However. The value 0 is the default value for the PKEY attribute.5. 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. 16. the p-point attributes (NPPT or PPDI) are normally unset (value -1). then the p-line attributes (PKEY and PKDI) are set back to the default values.2 P-line Name The p-line name is identified by the PKEY attribute of the annotation element. The syntax for p-line angle is as follows. and uses it to define the angle of the Label or View Note. then the same p-line may also be used instead of the ADEG attribute to store angle.1 P-line Design Element The name of the Design element to which the p-line applies is stored in the DDNM attribute of the annotation element. These attributes and associated syntax are described further below. direction and angle described above is stored in the database using the following attributes: • • • • DDNM for the Design element name PKEY for p-line name PKDI for proportional distance along a p-line under special circumstances. However this will only be done if both of the following criteria are satisfied: • • The p-line identified must be that used for p-line position The p-line direction syntax must not be qualified by a p-line axis 16. If p-line data for an annotation element is replaced by a direct reference to a Design element or p-point.0 . there is a simple way of setting it.5. NAXI or ZAXI as set up in the Catalogue data. PPDI will be used to specify p-line for angle. for Labels (GLAB. 0 respectively. SLAB.6 P-line Angle A p-line may be used for angle on the following elements: GLAB.5. meaning the midpoint of the p-line. SLAB. if set.5. SLAB and VNOT. The default value for this attribute may be altered by the user.5. This stores the proportional distance along the pline from its start. P-line direction is used on LDIM and APPT elements. The p-line is defined by the PKEY and DDNM attributes. Its initial value is 0. 16. The specified element should be that given in the DDNM. The value PPDI -2 16:4 12. VNOT. DPPT and PPPT). 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.DRAFT User Guide Annotating Structural Elements in DRAFT PKEY PPLINe word OF element_identifier The specified p-line must exist. P-line position is used on the following elements: GLAB. with the addition of the distance attribute PKDI to define a position on that p-line. The p-line direction is along the length of the p-line. The PKDI attribute may be set directly using the syntax: PKDIstance STart PKDIstance ENd These commands set the values 0. 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. PKDIstance DEFault This command resets the PKDI attribute to the default value.5.5. 16. 16. It is defined by the p-line attributes (PKEY and DDNM) together with a special value of the PPDI attribute.0 and 1. VNOT.5 P-line Position P-line position is defined by the p-line attributes PKEY and DDNM. DPPT and PPPT.3 P-line Distance P-line distance is stored in the PKDI attribute of the appropriate annotation elements (GLAB.0 . ADIM. ADIM.4 P-line Direction No additional attributes are required to define this. which show plan views of four SCTNs meeting at a node point.: Effect of SCTN DRGP Attribute (a) the DRGP attributes of all four SCTNs have been left at 0.DRAFT User Guide Annotating Structural Elements in DRAFT means that the p-line used to position the annotation is also used for angle. As a result. which confers a priority order on them. DRGP=2 DRGP=0 DRGP=1 DRGP=0 (a) Figure 16:1. DRGP may be set (in the Design Database) to any integer value between 0 (highest priority) and 50. Effect of SCTN DRGP Attribute (b) 16:5 12. The effect is demonstrated in the diagrams below. as a result DRAFT is unable to determine how to draw the intersection lines between the SCTNs and so draws the full outlines of all SCTNs.6 Representation of SCTN Ends Note: The functionality described in this section will be removed at a future release of DRAFT. 16. DRAFT is able to determine the representation that is intended. The DRGP (Drawing Priority) SCTN attribute is used by DRAFT to determine how to draw SCTN ends in hidden-lines-removed views.0 . The top flanges of the SCTNs are coplanar and none of the SCTN ends have been cut back.: Effect of SCTN DRGP Attribute (b) the DRGP attributes of the four SCTNs have been set as indicated. In Figure 16:1. In Figure 16:1. DRAFT User Guide Annotating Structural Elements in DRAFT 16:6 12.0 . 2 Using Plotfiles The command syntax for underlaying and overlaying a plotfile is as follows: BSHEE FILE /plotfile name OSHEE FILE /plotfile name Sets Sheet’s BSFN attribute Sets Overlay’s OSFN attribute. and can be of any size.1 Underlays and Overlays Introduction DRAFT gives you the ability to use underlays and overlays on a Sheet. whereas OSHEE is only valid at OLAYs. see next section To remove an underlay or overlay from a Sheet.DRAFT User Guide Underlays and Overlays 17 17. and must be the same size as.0 . the following commands can be used: BSHEE UNSET OSHEE UNSET Note that BSHEE is valid at LAYE or below. the Sheet being underlayed. An overlay sheet can be placed anywhere on the Sheet. These may take the form of plotfiles held in the system database. An overlay is positioned on the current Sheet by changing the OPOS and OANG attributes of the Overlay element (see next section). but it is only possible to have one backing sheet on a SHEE. They can be used as backing sheets for a title block and border. which determine the position and angle respectively. 17. For example: OPOS @ OPOS X250 Y300 Set overlay origin using cursor Set overlay origin explicitly (relative to the Sheet origin OPOS ENDP OF /LINE1 Set overlay origin to a constructed position OANG 30 Rotate the overlay 30 degrees anticlockwise about its origin 17:1 12. or as overlay sheets for placing such items as keyplans or standard notation. A backing sheet has its origin coincident with. Any number of Overlay Sheets may be used on the one SHEE. or may be DRAFT database elements. file specification and positioning may be combined into a single OSHEE command.0 .3 Database Elements for Underlays and Overlays LIBY DRWG BSRF SHLB SHEE BSRF OLAY BACK OVER OSRF NOTE VIEW NOTE Figure 17:1.DRAFT User Guide Underlays and Overlays Alternatively. DRAFT Database Hierarchy . Note that you can query the size of a plotfile using the command: Query PLOTFile name SIZE The response will be the size rectangle of the plot. 17.Overlay/Underlay Elements 17:2 12. position and orientate overlay sheet Reposition and reorientate currently defined overlay sheet Position Overlay absolutely Position relative to old position These commands may also be used to position Overlay Sheet templates. for example: OSHEE FILE /OS1 ANGLE 90 @ OSHEE ANGLE 60 @ OSHEE @ OSHEE BY @ Define. Any hash codewords defined by TEXP elements will be expanded when the BACK is referenced. Note that when an Overlay Sheet is instanced (i. attribute OSFN is set). See Accessing Data from the DRAFT Database.0 . 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.e. (BSRF may also be set at Drawing level. These would exist as (member) NOTE elements created via DRAFT’s geometric 2D drafting facilities. the LAYE element(s) owned by the VIEW(s) owned by the OVER referenced by the drawing Sheet) that are to be visible. A BACK would probably be used as a frame sheet and would contain frame lines. when a plotfile is used (i.) The BACK/OVER to be used may be specified by using commands such as: BSHEE /BS1 OSHEE /OS1 Underlay specified backing sheet element Overlay specified overlay sheet element The Overlay’s OSLV (‘overlay sheet view layers visible’) attribute defines those Layers of the overlay sheet (i.DRAFT User Guide Underlays and Overlays Elements for use as backing and overlay sheets may be created in DRAFT and stored in the DRAFT database. Note that Point Construction (see Section 11) can be used to create BACK and SHEE elements. authorisation boxes etc. The Layers that are to be visible are specified by a further option of the OSHEET command. but zero is not allowed.Overlay/Underlay Elements.e. The Overlay’s XYSCALE attribute allows independent scaling in the X and Y directions of the instanced overlay sheet or plotfile. An OVER shares many of the attributes of a SHEE. The relevant part of the database hierarchy is shown DRAFT Database Hierarchy . BACKs and OVERs are referred to by the relevant drawing Sheet’s BSRF and the relevant Overlay’s OSRF attributes (respectively). For example: XYSCALE 2 1 Either or both values may be negative. Up to 12 Layers may be made visible at once.e. See also Scaling and Mirroring Special Labels. the PURP attribute) or by their member list position under the VIEW(s) owned by the OVER. OVER elements may also own NOTEs as well as VIEW elements. text is only affected by the scale in the Y direction. However. Control of complex overlays may be achieved by using multiple OLAY elements.e. Most Overlay Sheet attributes are held by the Overlay (OLAY) element. attribute OSRF is set). and would probably be used to overlay graphic details such as keyplans on drawing sheets. The Layers which are to be visible may be referred to either by Layer purpose (i. It is not possible to generate backwards or distorted text. then there is no such safeguard and text could be distorted if differing X and Y scales are specified. For example: OSHEE LAYERS 1 LABS OSHEE ALL OSHEE ALL OFF Make all Layers at list position 1 and all Layers with PURP ‘LABS’ visible Make all Layers visible (default) Make all Layers invisible 17:3 12. These codewords will typically extract data from the DRAFT database. assuming both VIEWs own such Layers. delete OLAY overlay 17. (It is not possible to specify.4.1 Summary of Commands Underlays. 17.4 17.. Must be at OLAY level..2 Overlays. Sets OLAY’s OSFN attribute. a Layer with PURP DIMS to be visible for /VIEW1 but not for /VIEW2. Will ensure that the latest version of the referenced BACK is used and will re-evaluate hash codewords. OPOS xpos ypos OPOS @ OANG value XYSCALE value value OSHEE FILE name ANGLE value @ OSHEE ANGLE value @ OSHEE @ OSHEE BY @ set overlay origin explicitly (relative to the Sheet origin) set overlay origin using cursor rotate the overlay anticlockwise about its origin rescale overlay sheet define.4.DRAFT User Guide Underlays and Overlays The Design graphics may be made visible by including Layer DESI.0 .. OSHEE FILE /plotfile name OSHEE UNSET overlay a specified plotfile on the current SHEE. The above functionality is only available when an overlay sheet template reference is used. for example.) The setting of a Layer’s LVIS attribute has no bearing on the visibility questions discussed in this section. position and orient overlay sheet reposition and reorient currently defined overlay sheet position Overlay absolutely position relative to old position 17:4 12. 17. Must be at SHEE level or below.. BSHEE FILE /plotfile name BSHEE UNSET UPDATE BSHEETS underlay a specified plotfile on the current SHEE. No distinction between Layers can be made when using overlay sheet graphics from a file.. If the overlay sheet has more than one VIEW then the Layer visibility statement will apply across all VIEWs.. Sets SHEE BSFN attribute delete SHEE underlay (valid at SHEET and above) Updates Backing Sheets.3 Manipulating Overlays.4. DRAFT User Guide 2D Drafting 18 18.1 2D Drafting Introduction DRAFT’s 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.2 Where 2D Drafting is Used The 2D drafting application can be used for creating: • • • Backing and overlay Sheets. See Backing and Overlay Sheets. Symbol templates. See Symbol Templates. ISODRAFT symbol templates. See ISODRAFT Symbols. 18.2.1 Backing and Overlay Sheets 2D drafting may be used to create backing and overlay sheets, or may be used to annotate overlay sheets that exist as VIEW elements. The relevant part of the DRAFT database hierarchy is shown in Figure 18:1.: DRAFT Database Hierarchy - Sheet Library/2D Drafting Elements. 18:1 12.0 DRAFT User Guide 2D Drafting SHLB SHEE NOTE VIEW BACK OVER LAYE VNOT VIEW LAYE NOTE NOTE VNOT CIRC ELLI RECT TABL ETRI DMND HEXA MRKP STRA ARC OUTL TEXP SYMB Figure 18:1. DRAFT Database Hierarchy - Sheet Library/2D Drafting Elements 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 NOTE’s 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.0 DRAFT User Guide 2D Drafting (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 JUST ALIG FONT CHEI CSPA/LSPA Note line style and colour Fill style and colour Marker style and colour Text colour Horizontal justification Vertical alignment Text font Character height 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.2.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.0 DRAFT User Guide 2D Drafting 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.3 The Drafting Elements The 2D drafting elements are primitives, Text Strings (TEXP) and Symbol Instances (SYMB). Primitives are basic geometric shapes (rectangle, circle, straight, arc etc). Text Strings may be up to 120 characters in length, may be multi-line and may incorporate intelligent text codes. Four fonts are available, and character height, spacing and alignment may be varied in the same way as for Label text. Symbol Instances (SYMB) are particular instances of Symbol Templates (SYTM). The SYTM defines the composition of the symbol; the SYMB defines its size, position, and orientation. 18:4 12.0 DRAFT User Guide 2D Drafting 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.4 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. Figure 18:3. Drafting Primitives Note: The ‘°’denotes the shape’s (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.0 DRAFT User Guide 2D Drafting As a primitive element is created, its position is stored separately, with a reference to the position being stored as the primitive’s PTRF (or PTFA) attribute. An important feature of this system is that if a series of primitives is created, each primitive’s 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 NEW CIRCLE DIAM 100 AT @ NEW CIRCLE DIAM 150 NEW CIRCLE DIAM 200 would create a series of concentric circles. In a similar way, a series of connected straight lines could be created. (A line may have two position references, one at either end; the start position reference of one line would be set equal to the end position reference of the previous line - see description of STRA primitive below.) A set of primitives connected in this way may be moved as a ‘group’ by using the DRAG command - see below. DRAFT offers you a variety of methods of defining, identifying, sizing, positioning, orienting, moving and querying drafting primitives. Many methods of carrying out these operations are common to all (or most) of the drafting primitives. These methods are described in the next section; methods that apply to particular primitives (and to Symbols) are described in Creating and Manipulating Drafting Primitives - Common Operations. 18.4.1 Creating and Manipulating Drafting Primitives - Common Operations Note: See the Graphical Feedback later in this Section for details of the easiest way of creating drafting primitives. • Creating Primitives and Varying Basic Attributes At NOTE (or VNOT) level, and with a Sheet (or VIEW Layer) in a SHOWn form, the simplest way of creating a circle (for example) would be by giving the commands: NEW CIRCLE DEF @ The cursor would then be used to mark the centre and a circumference point of the circle, which would then be drawn. Hitting a key produces a command line giving the (Sheet) coordinates of the cursor position; such a command line could, of course, be typed in directly.) All the different shapes can be created in a similar way, with a self-explanatory prompt being output in each case. Note that macros driven from forms and menus are particularly useful for 2D drafting. Attributes common to all primitives (except Markers, Lines, Arcs and Outlines) are orientation (ADEG, relative to a line drawn through the shape’s origin parallel to the x-axis) and origin code (OCOD). The origin code determines the position of a primitive’s origin relative to the primitive itself - for example, a circle’s origin may be placed at its centre or on its circumference. Arcs and Straight Lines have a TCOD (Type Code) attribute instead of OCOD. TCOD can be set to the endpoint or midpoint of a line, and to the endpoint or centre of an arc. The TCOD setting defines how to interpret the other attributes of the primitive. Straight lines also have an ADEG attribute. See below (STRA and ARC elements). Clearly, attributes such as orientation cannot be set using the cursor, so if these require settings other than their defaults they must be set afterwards. (Default orientation is 0 and default origin code is CENTRE. For straights and arcs the default TCODE is ENDPOINT.) Alternatively, primitives may be created using one-line commands such as: 18:6 12.0 DRAFT User Guide 2D Drafting NEW CIRC RAD 50 ORIG CIRCUM ADEG 45 AT X900 Y750 NEW RECT XLEN 40 YLEN 20 ANG 45 ORIG CORNER AT @ NEW TABL XLEN 60 YLEN 60 NROW 10 NCOL 5 RPEN 2 CPEN 3 ORIG TS ADEG 45 AT @ The effects of varying the attributes of the different primitives are illustrated in Figure 18:4.: Drafting Primitives - Varying Attributes and Figure 18:5.: Drafting Primitives - Varying Attributes (continued). Figure 18:4. Drafting Primitives - Varying Attributes 18:7 12.0 0 . If the ORIG keyword is used (for example. the Sheet coordinates of the origin change such that the origin moves to the specified part of the primitive . The origin code may also be changed by the OCOD keyword.Varying Attributes (continued) • Shifting the Origin The origin code may be set in two ways. for example 18:8 12.the primitive itself does not move. ORIG @ to set by cursor). Drafting Primitives .DRAFT User Guide 2D Drafting Figure 18:5. The concentric circles described in the introduction to 2D Drafting Primitives are an example of a group of primitives that use the default drafting point .5 BY N500 W1200 Move relative to current 2D position Move relative to current 3D position (VNOT members only) • Moving Groups of Primitives The DRAG command is used to move a group of primitives that share a common drafting point. In either case the origin position may be changed at the same time by using commands such as ORIG X300 Y250 OCOD TRIGHT @ OCOD BLEFT @ The origin is normally invisible.0 . but may be made visible by the SKETCH command: SKETCH ORIGIN SKETCH ORIGIN ALL The command At primitive level. so it is taken as at that of the last-created primitive. ORIGIN node_identifier or FPT node_identifier Examples of the DRAG command (showing examples of node_identifier) are: 18:9 12.the drafting point’s position is not specified explicitly. displays origins of all member primitives 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 Move to new 2D position Move to new 3D position (VNOT members only) Move to specified element origin or p-point (VNOT members only) BY @ BY X10.DRAFT User Guide 2D Drafting OCOD CEN OCOD @ 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. displays primitive origin At NOTE level. (See list of DRAG commands above for examples of node_id. 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. For example: 18:10 12. the identity of the primitive picked and the position of the picked point. FPT.e. THPT or CPT. 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 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. MPT. A drafting point on a STRAIGHT.0 .) 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)).DRAFT User Guide 2D Drafting DRAG BY @ DRAG BY X120 Y-45 DRAG BY S3500 D500 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. TPT.) • 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 query reports the appropriate point. i. the following could be returned: DRA =151/4636 LINE X 100mm Y 100mm X 200mm Y 200mm QUAL X 167mm Y 166mm If the query were applied to a part of a Design element. The database reference ID and the cursor-hit position of any linear element on the Sheet (for example a STRA. this causes its drafting points to move. 18:11 12. Other primitives that use the same drafting points will also change position. The two Vertex identifiers may be the same. The basic syntax is as follows: HIGhlight [prim_id] COMmon Query COMmon. If prim_id is omitted.1/32 Y 7. and the 2D position of the cursor hit. For example. the first vertex identified is the endpoint of the span. and for an Arc these are FPT. The common primitives of a node may be highlighted or queried.at a primitive where prim_id identifies a drafting primitive.0 . In order to help predict the effect that a DRAG command will have. the identity of the element. Q IDNN @ allows both the point and the primitive to be picked by one cursor hit. TPT. (Straights and Arcs may also change in shape.3/32 Y 7. For STRAIGHTS and ARCS.19/32 QUAL X 6.DRAFT User Guide 2D Drafting FPT OF /STRAIGHT3 X 123 Y 456 TPT OF /ARC1 E 3000 N 4000 U 0 VPT /VERT1 NEAR /VERT2 X 495 Y200 In the last case where a span of an OUTLINE was picked. the common drafting primitives may be highlighted or queried. TPT (‘to’ point) or MPT (midpoint).19/32 • Handling Common Drafting Primitives When the DRAG command is used on a specified drafting primitive. The DRAG command may also be used on an individual node of a Straight or Arc. if the query were applied to a STRA element with FPT X100 Y100 and TPT X200 Y200. the following could be returned: DES =35/222 LINE X 6. the common primitives for the current element are highlighted/queried.) These primitives are the common drafting primitives for specified primitive. etc) may be queried using: Q IDLINE @ The query returns the database of the picked element (DRAFT or DESIGN). CPT (centre point) or THPT (‘through’ point). part of Design item. side of a RECT.19/32 X 5. the point identified will be the same as that returned by the Q IDN @ command where the current element is a STRA or ARC.5/16 Y 7. and the second is the Vertex (VRTX element) that owns the span. the pair of 2D coordinates that define the linear element. using the following syntax: HIGhlight prim_id COMmon prim_id Query node_id COMmon Query COMmon node_id At a primitive At a primitive For a Straight these are FPT (‘from’ point). MPT or two nodes.DRAFT User Guide 2D Drafting The node must be currently used by the Straight or Arc. CIRC. TABL. OUTL or MRKP can be mirrored using the MIRROR command to specify a mirror axis. XYPO may be changed directly or by the OFFSET command. In the latter case. RECT. any position reference may be used to specify the axis points. FPT and TPT. ELLI. 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. for example OFFSET X50 Y50 position NOTE VNOT’s origin at given offset owner’s origin AT @ AT X400 Y400 position NOTE/VNOT’s origin at given position on SHEE BY @ BY X60 Y-20 shift NOTE/VNOT’s origin by given amount ADEG 30 rotate NOTE to 30° from horizontal Note: If a VNOT is moved or rotated. This is the offset of the origin from the origin of the NOTE/VNOT’s owner (i. HEXA. DMND. TPT and either a CPT or a THPT. ELLI. For example: MIRROR IN @ Use cursor to specify existing linear element to mirror in 18:12 12. If an unset node or an illegal node is specified. STRA. CIRC. • 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/VNOT’s origin position (XYPO attribute).e. HEXA. A Straight has a single node. DMND. The current element may be mirrored in an existing linear element or two independent points may be specified to define the mirror axis. An Arc has an FPT. ETRI.0 . then an error is output. RECT. The origin of a SHEE is at its bottom left-hand corner and that of a VIEW at the centre of the VIEW rectangle. ETRI. • Rotating a Primitive A primitive of type ARC. TABL. only primitives positioned in 2D will move with it. SHEE/VIEW respectively). OUTL or MRKP can be rotated using the ROTATE command to specify an angle of rotation and a point to rotate about. The positions of primitives positioned in 3D or on Design elements will remain unchanged. STRA. Use of the REPEAT Command illustrates the use of the REPEAT command. illustrated by the following examples: REPEAT 5 BY X20 Y20 Produce five copies of the current primitive. displacement of second and subsequent copies equal to that of first copy from original REPEAT @ Produce five copies of the current primitive. Use of the commands listed below gives the Point Construction Option form. intersection points etc.0 . from which you can choose to define point(s) not only as simple 2D cursor hits but also as line end-points. Y20) from the last REPEAT 5 BY @ Produce five copies of the current primitive. 25 REPE 10 BY Y -25 Figure 18:6. but just one repetition Figure 18:6.: Drafting Primitives . The relevant commands are: 18:13 12. each displaced (X20. using the cursor to define displacement REPEAT 5 @ Produce five copies of the current primitive.DRAFT User Guide 2D Drafting 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. circle centre-points. but with first copy at cursor position.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. Drafting Primitives .Use of the REPEAT Command • Graphical Feedback Many cursor commands generate graphical feedback (rubber banding) which makes the interaction process easy . for example: • • • TOLERANCE 0. ARC STRA ARC ARC 18. If the arc were moved using the DRAG command then the two circles would also move. The primitives that do so may be listed using the Q COMMON command or flashed by the HIGHLIGHT COMMON command.5 mm TOLERANCE may be reset to its default value by the command TOL DEF Control over the TOLERANCE setting is particularly important for the re-input of DATAL macros. This is normally the last point used. HEXA. The use of a shared drafting point may be achieved in one of the following ways: • When a drafting point is created without specifying its position it will be positioned using the default drafting point. BY) work to a tolerance of 0.DRAFT User Guide 2D Drafting Command REGN @ DEF @ ADEF @ DIAMETER @ SPAN @ RADIUS @ ASUB @ TPT @ FPT @ MPT @ CPT @ THPT @ Valid Elements VIEW All 2D drafting primitives ARC CIRC. The default tolerance for re-use of points is 1 mm on the Sheet.0 . ARC ARC STRA. for example. This may happen.g. when Symbol definitions or Backing Sheets are input from macros. ARC STRA. • When a primitive is positioned very close to an existing drafting point in the same NOTE. The re-use of drafting points within the TOLERANCE limit can lead to unsatisfactory performance when a NOTE contains a large number of points. The tolerance used may be controlled by the TOLERANCE command.4.5 Set tolerance to .) For example the series of commands: NEW CIRC RAD 50 AT @ NEW CIRC RAD 25 NEW ARC TCODE CENTRE RAD 75 ASUB 90 would create two concentric circles and a concentric arc. (This applies to the initial node for a Straight or an Arc.2 Re-use of Drafting Points In order for a DRAG command to drag a group of primitives that have the same initial position they must share a drafting point. HEXA VRTX CIRC. although some commands (e. VNOT or SYTM then the point will be re-used to position the new primitive. 18:14 12.001 mm. This is controlled by the ENHANCE command. 18:15 12. The attribute name is PRMVISIBILITY..4. For a primitive or Vertex below a VNOT. PRMVIS is true below a NOTE if the NOTE is visible. the current primitive must be explicitly positioned on the required drafting point.g.g. this means that PRMVIS is TRUE if the VNOT. Basic Drawing Creation & Output. otherwise existing enhanced elements will be unaffected by this command. LAYER and VIEW are all visible (i. which has the general form: ENHANce [SOLEly] selection_criterion selection_criterion .e.6. FPT IDP@ DRAG TO IDDP @ (The Q IDN @ command may be used to identify the FPT or TPT of a STRAIGHT. This is TRUE if all owners of a primitive are visible.4 Enhancing Drafting Primitives Drafting primitives may be emphasised in a more permanent fashion than the flashing provided by the HIGHLIGHT command. if their LVIS attributes are all TRUE).0 .. 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. For example (ALL NOTE MEMBERS WITH PRMVIS TRUE) 18. The brief command UNENHANCE removes all enhancing and should always be used for that purpose. and PRMVIS is always true below SYTMs. without it the selection system will scan around the entire MDB. For example: 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. Enhancing may be removed by the UNENHance command. which may optionally specify a selection criterion. see Section 6. e.3 Visibility of Drafting Primitives The derived visibility of a drafting primitive may be extracted into expressions. The FOR element_identifier command option is important.) 18. The current primitive may then be positioned on the required drafting point by commands such as: ORIGIN point_identifier. Part 1. If neither of these methods is appropriate. ORIG IDDP@ ORIGIN IDDP @ FPT point_identifier e.4.DRAFT User Guide 2D Drafting • • The current TOLERANCE status and value may be queried by Q TOL The current tolerance will also be output to file by the RECREATE DISPLAY macro. When doing a SAVEWORK or a module change the enhancing will not be permanently written to the picture file.4. ‘from’ point and Angle Subtended (from which the position of the ‘to’ points and the value of RADI can be derived if required). applies to all primitives and as such is described in the previous section) or it is similar to the same operation as described for the CIRCLE primitive see CIRCLE (CIRC).e. Basic Creation Method An ARC can be defined in three ways: • • • 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).0 . 18:16 12. 18.DRAFT User Guide 2D Drafting The command UNENHANCE ALL should NOT be used as it causes the entire MDB to be scanned. Enhanced elements may also be HIGHLIGHTed. 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: SETENHAnce COLour integer SETENHA COL BRIGHTORANGE SETENHA COL DEFAULT (sets enhance colour back to default of aquamarine) Overlay (OLAY) elements can also be enhanced.Specific Operations This section describes primitive-specific operations. by defining the position of the centre point. Entering MDB mode causes all chosen elements to be unenhanced and the enhanced element list cleared out. However after a SAVEWORK command the enhanced element list will still exist and the elements will remain enhanced on the screen. • ARC (ARC) Attributes PTFA NLSTYLE NLCOLOUR RADI ASUB TCOD Point references (3) Note line style Note line colour Radius Angle subtended Type code (defines how to interpret attributes). by defining the position of the centre point and two end points. Either set to ENDPOINT or CENTRE. If an operation is not specified then it is ‘universal’ (i.5 Creating and Manipulating Drafting Primitives . When creating plotfiles. enhancing will be ignored. ASUBTENDED value [ANTICLOCKWISE] ASUBTENDED value CLOCKWISE Sets ASUB. respectively. p-point etc). For TCOD CENT this moves the ‘from’ and ‘to’ points radially (by the change in the value of the radius). 3D.DRAFT User Guide 2D Drafting The method: NEW ARC DEF @ results in three points being prompted for (the ‘start’.) For TCOD ENDP this repositions the ‘through’ point (mid-way along the Arc) and changes RADI. ASUBTENDED @ 18:17 12.(CPT) and ‘from’ point (FPT) of the Arc. Defining or redefining an Arc with a centre. 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. Centre point position and ASUB are not altered. A line is drawn through the points and TCOD is set to ENDPOINT. The TCOD attribute is set to CENTRE. ‘end’ and ‘through’ points). ASUBTENDED CLOCKWISE ASUBTENDED ANTICLOCKWISE Sets the value of ASUB to be negative or positive. the positions of ‘from’ and ‘to’ points are unchanged.0 . The first two points are the centre . Centre and ‘from’ points and radius are unchanged. (A positive angle is anticlockwise. ‘from’ and ‘to’ point positions are unaltered.and two endpoints is achieved using the command: ADEFine <dfnpt> <dfnpt> <dfnpt> where <dfnpt> defines a position (2D. This command may also be used with the cursor: ADEFine @ A prompt requests three 2D points to be input for CPT. See Positioning (absolute) overleaf for the second method. FPT and angle subtended. The third point defines the angle subtended by the arc. These two points define the radius. a negative one clockwise. For TCOD CENT this moves the ‘to’ point of the arc. RADIUS X value Y value RADIUS E value N value U value RADIUS IDP @ etc. The TOpoint (TPT) lies in this direction from the Centre (CPT) at the same distance as the FPT from the CPT. For TCOD ENDP this is like THPT @. If used with an existing ARC any existing values of RADI and ASUB are altered accordingly. For TCOD ENDP this moves the ‘through’ point and changes ASUB. 0 . but referring to RADIUS. FPT (‘from’ point). The ‘to’-point and radius are recalculated. then a rotation about the other endpoint takes place. CPT @ etc.e. if the centre point is dragged. Positioning (absolute) (of an arc point) The syntax is similar to that for FPTs of STRAs.e. then the positions of the ‘from’ and ‘to’ points are also moved to preserve the Arc’s appearance. Possible points are CPT (centre point). 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. This changes the Arc to be one with TCOD ENDP (if not already so). ASUBTENDED.DRAFT User Guide 2D Drafting For TCOD ENDP this is like THPT @. Radius and Angle subtended are changed. THPT @ etc. TPT and THPT as appropriate. The new position of the ‘to’ point lies on the line joining the centre-point and the cursor position. For Arcs with TCOD CENTRE. the centre point is moved and the radius changed.i. For TCOD CENT this alters the angle subtended and hence moves the ‘to’ point of the Arc. Querying Similar to Straights. FPT. The effect on the Arc is as follows. CPT. i. For arcs with TCOD ENDP. both radius and angle subtended are altered. the ‘from’ or ‘to’ point of the Arc (as appropriate) is moved whilst maintaining the position of the centre and the angle subtended. This changes the arc to be one with TCOD CENT (if not already so). 18:18 12. For Arcs with TCOD CENT. centre and ‘from’ points and radius are unaltered. • • • for arcs with TCOD ENDP. TPT (‘to’ point) and THPT (‘through’ point). FPT @ TPT @ etc. for Arcs with TCOD CENT. 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. The Centre is moved whilst keeping the ‘from’ point and ASUB unaltered. Thus the radius may change and the position of the other end point will be moved to preserve the angle subtended. The position of the ‘through’ point is moved whilst keeping the ‘from’ and ‘to’ points fixed . Repeated Copying See Circles. if an end point is dragged. the points of the Arc may move. Resizing DIAMETER value [DESIGN] RADIUS value [DESIGN] If DESIGN specified and if underneath a VIEW from which a scale can be obtained. ADEG equal to the angle to this line from X axis. DIAM @ Sets DIAM equal to the distance between the two points. ID RECT @ (rectangle) etc. a scaled circle will be drawn and the diameter stored in the database as a Design value. except where otherwise specified. for example ID ELLI @ (ellipse).1.DRAFT User Guide 2D Drafting • CIRCLE (CIRC) Attributes PTRF NLSTYLE NLCOLOUR FSTYLE FCOLOUR OCOD ADEG DIAM Point Reference for origin Note Line style Note Line colour Fill style Fill colour Origin Code (CENTRE. origin is positioned at the first hit. CIRCUMFERENCE) Angle in owner (useful for OCOD = CIRCU) Circle diameter Basic Creation Method NEW CIRCLE DEF X value Y value X value Y value (‘manual’ method of NEW CIRCLE DEF @ command described in section 14. This method applies to all primitives described below.4.0 . DIAM X value Y value X value Y value Manual method Redefining the Origin ORIGIN @ Prompts: Select a possible origin of the CIRC 18:19 12.) Note: If used with an existing Circle the DEF command always sets ADEG=0 and ORIG=CENTRE Identification ID CIRC @ This method applies to all primitives described below. if ORIG is CIRCUMFERENCE. The Circle itself does not move. 18:20 12.: Moving about the Origin Use of the ORIG Command.0 . See Figure 18:7. Moving about the origin OCOD CIRCUMFERENCE Moves origin to circumference of Circle. 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.DRAFT User Guide 2D Drafting ORIG CENTRE Sets ORIG as required and changes position of origin to point specified. DRAFT User Guide 2D Drafting Figure 18:7. Moving about the Origin - Use of the ORIG Command Rotating about the origin ADEGREE value Sets ADEG as specified, causing the circle to rotate about its origin. (If this is at the centre then no visible change is seen.) Querying In addition to the standard attribute queries the following are provided: Q DESC Queries the origin, position and diameter Q DIAM Queries the diameter in Annotation or Design coordinates as appropriate Q ORIG Queries the origin and its position 18:21 12.0 DRAFT User Guide 2D Drafting Q OFFS Queries the position relative to the NOTE origin • DIAMOND (DMND) Attributes PTRF NLSTYLE NLCOLOUR FSTYLE FCOLOUR OCOD ADEG XLEN YLEN Resizing As for Ellipses. All other operations are as for Circles. Point reference for origin Note line style Note line colour Fill style Fill colour Origin code (CENTRE, TSIDE, BSIDE, LSIDE, RSIDE) Angle in owner X axis length Y axis length • ELLIPSE (ELLI) Attributes PTRF NLSTYLE NLCOLOUR FSTYLE FCOLOUR OCOD ADEG XLEN YLEN Point reference for origin Note line style Note line colour Fill style Fill colour Origin code (CENTRE, FOCUS TSIDE, BSIDE, LSIDE, RSIDE) Angle in owner X axis length Y axis length 18:22 12.0 DRAFT User Guide 2D Drafting Resizing XLEN value [DESIGN] YLEN value [DESIGN] DESIGN option applies to VNOT members only XLEN @ XLEN IDDP @ XLEN IDG @ XLEN IDP @ XLEN ID @ YLEN @ YLEN IDDP @ YLEN IDG @ YLEN IDP @ YLEN ID @ Redefining the Origin ORIGIN @ Changes the XLEN by distance along the X axis of the primitive from the origin. Note that this is not necessarily the Sheet or Note axis. If the origin is at the midpoint of the X axis (i.e.ORIG CENTRE) then XLEN will be twice this distance. If appropriate a Design distance will be used Changes the YLEN by distance along the Y axis of the primitive from the origin. Note that this is not necessarily the Sheet or Note axis. If the origin is at the midpoint of the Y axis (i.e.ORIG CENTRE) then YLEN will be twice this distance. If appropriate a Design distance will be used Sets ORIG as required and changes position of origin to point specified. The ellipse itself does not move ORIG CENTRE ORIG RSIDE ORIG LSIDE ORIG TSIDE ORIG BSIDE All other operations are as for Circles. • EQUILATERAL TRIANGLE (ETRI) Attributes PTRF NLSTYLE NLCOLOUR FSTYLE FCOLOUR OCOD ADEG FRAD LENG Point reference for origin Note line style Note line colour Fill style Fill colour Origin code (CENTRE, LSID, APEX, BRIGHT, BLEFT, RSIDE, BASE) Angle in owner Fillet radius Side length 18:23 12.0 DRAFT User Guide 2D Drafting 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 FCOLOUR OCOD ADEG DIAM Point reference for origin Note line style Note line colour Fill style Fill colour Origin code (CENTRE, CIRCUMFERENCE) Angle in owner Diameter of the enclosing circle 18:24 12.0 DRAFT User Guide 2D Drafting Redefining the Origin As for Circles. ORIG CIRCUM refers to a vertex of the Hexagon All other operations are as for Circles. • MARKER PRIMITIVE (MRKP) Attributes PTRF MSTYLE MCOLOUR Point reference for origin Marker style 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 MSTYLE MCOLOUR CURFIT Note line style Note line colour Fill style (used to hatch the area enclosed by the OUTL) Fill colour Marker style Marker colour Curve fitting control 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.0 DRAFT User Guide 2D Drafting (VRTX) PTRF BULG NLSTYLE NLCOLOUR MSTYLE MCOLOUR CHAM FRAD 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 Point reference Bulge factor Note line style Not in colour Marker style Marker colour Chamfer distances Fillet radius (Can override settings at OUTL) 18:26 12.0 DRAFT User Guide 2D Drafting 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 Above two commands combined. Also SPAN @ 18:27 12.0 SKEtch POInts. Querying Q DESCription is valid at OUTLs and VRTXs.only the origins of the owning OUTLs .0 . the first VRTX below each OUTL. 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. BLEFT. TLEFT. Note that SKETCH ORIG ALL does not sketch all VRTX origins . TSIDE. Q SPAN RADius and Q SPAN ASUBtended are valid at VRTXs only (but not at the first VRTX in an OUTL). See the on-line help for details. • RECTANGLE (RECT) Attributes PTRF NLSTYLE NLCOLOUR FSTYLE FCOLOUR OCOD ADEG XLEN YLEN FRAD Resizing XLEN value [DESIGN] YLEN value [DESIGN] SQUARE value [DESIGN] XLEN @ YLEN @ DESIGN option applies to VNOT members only Sets XLEN and YLEN to value specified. HIGhlight. you must define the TO position by a cursor hit. Uses relevant offset from origin of primitive to define XLEN or YLEN as required. Miscellaneous Commands The Q COMmon. giving you various span definition options. BSIDE. a straight-line span being assumed. RSIDE.i.DRAFT User Guide 2D Drafting a warning message output.e. SKEtch ORIgins and ID @ commands are all valid at OUTLs and/or VRTXs. By default. The Outline Span Construction form will appear. By default the command gives the minor arc. giving the minimum possible radius. TRIGHT. Point reference for origin Note line style Note line colour Fill style Fill colour Origin code (CENTRE. LSID. giving details of origin coordinates and span radius and angle subtended (if appropriate). BRIGHT) Angle in owner X axis length Y axis length Fillet radius 18:28 12. but also: ORIG TLEFT ORIG TRIGHT ORIG BLEFT ORIG BRIGHT Creating Rectangles and Squares Rectangles can be created using the commands: ADEFine dfnpt1 dfnpt2 Defines a rectangle where dfnpt1 defines a position (2D. and dfnpt2 defines the position of a corner. 3D. 18:29 12. and dfnpt2 defines the position of a corner. X400 Y400 and a corner at X500 Y500. for example: ADEFine @ A prompt requests two 2D points to be input. Redefining the Origin As for ELLIPSE. Manual method Sets FRAD to value specified. If this is too big for the existing XLEN or YLEN values then a warning is output and the rectangle is drawn square-cornered. p-point etc) which is the centre of the rectangle. All other operations are as for Circles. Defines a square where dfnpt1 and dfnpt2 define the positions of the corners ASDEFine dfnpt1 dfnpt2 SDEFine dfnpt1 dfnpt2 For example: ADEF X400 Y400 X500 Y450 SDEF X400 Y400 X500 Y450 Defines a RECT 200 by 100 with its centre at X400 Y400 and a corner at X500 Y450. ASDEF X400 Y400 X500 Y450 Defines a RECT 200 square with its centre at These commands may also be used with the cursor.DRAFT User Guide 2D Drafting XLEN X value Y value YLEN X value Y value THROUGH @ THRU @ THR X value Y value FRADIUS value [DESIGN] Manual method Prompts: Input a point on the current Sheet Sets XLEN and YLEN so that a corner of the rectangle is positioned at the point specified. FRAD will be set as specified and will be used when XLEN and YLEN are made large enough. Defines a square where dfnpt1 defines the centre of the rectangle. Defines a RECT 100 square with one corner at X400 Y400 and the other at X500 Y500.0 . DRAFT User Guide 2D Drafting • STRAIGHT (STRA) Attributes PTFA NLSTYLE NLCOLOUR LENG ADEG TCOD Point references (2) Note line style Note line colour Length Angle in owner Type code (defines how to interpret attributes). Set either to ENDPOINT or MIDPOINT.. Basic Creation Methods A STRA can be defined in two ways: • • 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. Changing Length or Slope LENGTH value [DESIGN] ADEG value LENGTH @ ALENGTH @ Moves the From point of the STRA, changing its LENG and ADEG attributes. Moves the To point of the STRA, changing its LENG and ADEG attributes. Changing LENG or ADEG for a two-point STRA will move the ‘to’ point. 18:30 12.0 DRAFT User Guide 2D Drafting 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 prompts: Enter a 2-d position To position at a 3D (i.e. ENU position): FPT POS @ FPT E12500 S5000 U0 To position on a p-point: prompts: Input a point in a View FPT FPT FPT FPT ID @ IDP @ /PUMP2/N1 P1 OF /PUMP2/N1 prompts: Identify element prompts: Identify design p-point 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 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: Input two points on a sheet Input two points in the same View depending upon whether the STRA is currently positioned on a 2D point or a 3D/p-point. BY X55 Y-678 BY N500 W1200 DRAG BY @ DRAG BY X120 Y-45 DRAG BY S3500 D500 FPT BY @ prompts: or: STR As positioned at a 3D point cannot be shifted by an X,Y amount, and vice versa. see comments for BY command Input two points on a sheet Input two points in the same View 18:31 12.0 DRAFT User Guide 2D Drafting depending upon whether the point is currently positioned on a 2D point or 3D/p-point. FPT BY X55 Y-678 FPT BY N500 W1200 FPT DRAG [BY] @ Points positioned at a 3d point cannot be shifted by an XY amount, and vice versa. These commands change the position of drafting point FPT DRAG TO @ to which FPT is attached and hence will change position of other primitives attached to same point. 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 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 18:32 12.0 DRAFT User Guide 2D Drafting • SYMBOL INSTANCE (SYMB) Attributes PTRF TMRF XYSCALE ADEG Point reference for origin Template reference Scale in X, Y directions 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 @ Changes the length of a straight by moving its From Point Changes the length of a straight by moving the end nearest to the cursor Negative values give a ‘mirroring’ effect Sets X and Y scales equally 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 @ @ as above, but alters ADEG as well as the symbol size. All other operations are as for Circles. Updating Symbol Instances The command UPDATE INSTANCES valid at SHEE, BACK, OVER, SYLB, LALB or above, scans the database hierarchy and updates all those parts of picture files that use the graphics instancing mechanism. For example, a SYMB is an ‘instance’ of a SYTM. OLAY and BACK elements are in the same category. 18:33 12.0 DRAFT User Guide 2D Drafting • TABLE (TABL) Attributes PTRF NLSTYLE NLCOLOUR OCOD ADEG XLEN YLEN NROW NCOL ROWSTYLE ROWCOLOUR COLSTYLE COLCOLOUR Point reference for origin Note line style Note line colour Origin code (CENTRE, LSID, TLEFT, RSIDE, TSIDE, BSIDE, TRIGHT, BLEFT, BRIGHT) Angle in owner axis length Y axis length No.of rows No.of columns Style for Internal Rows (if set) Colour for Internal Rows (if set) Style for Internal Columns (if set) Colour for Internal Columns (if set) 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 FONT TXCOLOUR CHEI LHEI CSPA LSPA Point reference for origin Text string (may include # codes) Angle in owner Text font Text colour Character height Letter height Character spacing factor Text line spacing factor 18:34 12.0 DRAFT User Guide 2D Drafting JUST ALIG Resizing - Justification Vertical alignment 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.5 18.5.1 Text Strings Entering Text from DRAFT Text for use with the DRAFT 2D drafting facilities takes the form of TEXP elements that must be created (as NOTE, VNOT or SYTM members) before the text itself can be input. The text itself is input as the BTEX attribute of the TEXP, being positioned (by default) at the default drafting point. The text can be repositioned by an AT @ command. The text size will probably need to be increased, which is done by setting the CHEI (character height) or LHEI (letter height) attribute to a suitable value. A TEXP has attributes governing its orientation (ADEG), text colour (TXCOLOUR), font (FONT), horizontal justification (JUST), character/letter height and spacing (CHEI/LHEI, CSPA) and line spacing and alignment (LSPA, ALIG). All these attributes are the same as those for Label Text - see Labelling for details. In addition to the facilities outlined above, TEXP elements which are NOTE/VNOT members may incorporate intelligent text codes - see Intelligent Text. TEXP elements that are SYTM members may also incorporate intelligent text codes, but these will only be expanded when the SYTM is referenced by a SLAB. The command Q EXTENT BTEX may be used to give the extent of the BTEX text string. Four pairs of coordinates are output, giving the coordinates of the corners of the rectangular area occupied by the text in Top-left, Top-right, Bottom-right, Bottom left order with respect to the direction of the drawn text string. These coordinate pairs may be used to align another string of text with the queried text string. The pair of coordinates to be used depends on the Justification and Alignment attributes of the text to be aligned. Thus if JUSTIFICATION LEFT, ALIGNMENT TBODY is being used, then the position of the next line of text is given by the fourth pair of coordinates. This is true whatever the text orientation. 18:35 12.0 DRAFT User Guide 2D Drafting 18.5.2 Displaying Text from a File on the Drawing The contents of a text file may be read in and placed on a drawing using Programmable Macro Language (PML) file handling facilities. For example (when at a NOTE): 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.6 18.6.1 Summary of Commands Creating Primitives . . . NEW CIRCLE DEF @ NEW CIRC RAD 50 ORIG CIRCUM ADEG 45 AT X900 Y750 use cursor to mark (in this case) circle centre and point on circumference define circle size and position explicitly 18.6.2 Shifting the Origin . . . ORIG @ OCOD @ OCOD CEN ORIG X300 Y250 OCOD TRIGHT @ SKETCH ORIG origin Sheet coordinates change; primitive does not move origin Sheet coordinates remain unchanged; primitive moves to place itself according to new origin code origin Sheet coordinates and origin code change; primitive moves display primitive origin 18:36 12.0 3 Moving Individual Primitives . .6.4 Rotating Individual Primitives . .6.5 BY N500 W1200 move to new 2D position move to new 3D position (VNOT members only) move to specified element origin or p-point (VNOT members only) move relative to current 2D position move relative to current 3D position (VNOT members only) 18. .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.0 . ROTATE 45 @ ROTATE 45 IDP@ use cursor to specify 2D point to rotate about use cursor to specify Design p-point to rotate about 18. 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 DRAG BY S3500 D500 move to new 2D position move to new 3D position (VNOT members only) move relative to current 2D position move relative to current 3D position (VNOT members only) 18:37 12.5 Mirroring Individual Primitives . . .DRAFT User Guide 2D Drafting 18. MIRROR IN @ MIRROR ABOUT @ @ use cursor to specify existing linear element to mirror in use cursor to specify two points to define mirror axis 18. .6.6 Moving Groups of Primitives . moves the two VRTXs of the current span by the given displacements. THROUGH) vertex point coincident with starting vertex. REPEAT 5 BY X20 Y20 REPEAT 5 BY @ REPEAT 5 @ produce five copies of the current primitive. TO. . Y20) from the last as above.9 Outlines . .7 Querying Primitives . . SPAN TO . displacement of second and subsequent copies equal to that of first copy from original as above. SPAN TO CLOSE SPAN STRAIGHT TO X value Y value SPAN RADIUS value SPAN ASUB value SPAN BY X value Y value 18:38 12. .6.8 Copying Primitives . straight line span with vertex at given Sheet coordinates. sets radius of circle of which (arc) span forms a part to given value. vertex point defined by 2D cursor hit vertex point defined by 3D Design p-point cursor hit (similarly SPAN TO. . closes Outline. but use cursor to define displacement s above.6. . . sets angle subtended by (arc) span to given value. SPAN THROUGH. . but with first copy at cursor position.0 .DRAFT User Guide 2D Drafting 18.6. . . NEW OUTL NEW VRTX AT @ SPAN TO @ SPAN TO IDP @ creates a new Outline element creates a new Vertex. each displaced (X20. use the cursor to define its position. Q ORIG Q COMMON Q OFFSET Q DESC Q IDN @ Q IDNN @ queries origin and position of a primitive queries primitives with drafting points in common with the current element queries offset of a primitive origin from the Note origin queries principal dimensional and positional attributes of a primitive queries point on the current STRA or ARC queries point on hit primitive 18. SPAN THROUGH . but just one repetition REPEAT @ 18. sketches all points currently in use 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) .DRAFT User Guide 2D Drafting SPAN DRAG BY Y value CURFIT CUBICFIT CURFIT DEFAULT CHAMFER value [value] FRAD value moves the two VRTXs and all connected drafting primitives of the current span by the given displacement. . displays origins of all member primitives displays origins of all drafting primitives at/below the specified element sketches all points in use for the current primitive at NOTE level. (at OUTL) draws quadratic curve through vertex points turns off curve fit function applies chamfer between two VRTXs applies fillet to current VRTX 18. .similarly for the TPT and MPT 18.6. .6.11 Enhancing Display of Primitives . .10 Sketching Drafting Points . . UNENHANce Q ENHAnce [LIst] SETENHAnce COLour integer SETENHAnce COLour col-name enhances display of specified primitives removes all enhancing lists enhanced elements sets enhancement colour 18:39 12.0 . SKETCH ORIGIN SKETCH ORIGIN ALL SKETCH ORIGIN ALL IN identifier SKETCH POINTS SKETCH POINTS ALL at primitive level. displays primitive origin at NOTE level. ENHANce [SOLEly] selection_criterion . DRAFT User Guide 2D Drafting 18:40 12.0 . spindle and tee points on the symbol. which define the start. They have additional attributes.: ISODRAFT Symbol Libraries and Related Elements.DRAFT User Guide ISODRAFT Symbols 19 ISODRAFT Symbols You can create symbols in DRAFT to be used on the isometrics produced by ISODRAFT. which define the geometry of the symbol. INSU or TRAC (to describe whether the straight represents the pipeline. its insulation or its tracing). ISOLB ISOTM MRKP STRA Figure 19:1. The relevant part of the DRAFT database is shown in Figure 19:1. MRKPs owned by ISOTMs should have their PURP attributes set to one of ARRI. which are identical to SYLBs except that they can only own ISOTMs. except that they can only own STRAs and MRKPs. end. These elements should have their PURP attributes set as follows: • STRAs owned by ISOTMs should have their PURP attributes set to LINE. ISOTMs are stored in ISODRAFT Symbol Libraries (ISOLBs). ISODRAFT Symbol Libraries and Related Elements 19. and MRKP elements. LEAV.1 Creating ISODRAFT Symbol Templates ISODRAFT Symbol templates can only own STRAs. described in Creating ISODRAFT Symbol Templates. • The Arrive and Leave points of the symbol will be used as the reference points for dimensioning. TEE or SPIN. The symbols are created as ISODRAFT Symbol Templates (ISOTMs). 19:1 12.0 . which are similar to normal symbol templates. 0 . For more information. that is.1. Specifies a symmetrical fitting which the flow direction is not relevant Specifies a fitting for which the flow direction is important. If this attribute is set. the existing symbol will be redefined. Default Tracing representation suppressed Symbol to be filled Symbol not filled. see the ISODRAFT Reference Manual. the Symbol Template will include a spindle symbol. Default NONE. the BKEY must be set to a standard SKEY. If this attribute is set to the SKEY of an existing symbol. Default Suppresses the plotting of dimensions Insulation shown on symbol if specified.1 Attributes of ISODRAFT Symbol Templates The attributes of ISODRAFT Symbol Templates that are additional to the attributes of normal symbol templates are as follows: SKEY Symbol key: the SKEY of the new Symbol. Spindle symbol key. such as check valves Specifies a reducing fitting Specifies a fitting which begins with a flange. Default Insulation representation suppressed Tracing shown on symbol if specified. You can use wildcards to define a symbol for several similar SKEYs.DRAFT User Guide ISODRAFT Symbols 19. see Wildcards in SKEYs. Default Marker style (see Colours and Styles) Marker colour (see Colours and Styles) 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 FILL FALSE MSTYLE MCOLOUR 19:2 12. see Wildcards in SKEYs Changes the size of the symbol without redefining the coordinates of the plotted shape (100 = full size). Wildcards can be used. one which is preceded by a gasket Plots flow arrows on the symbol Suppresses flow arrows Plots dimensions alongside the symbol. If a new SKEY is being defined. Base symbol key. when defining a new range of SKEYs.2 Wildcards in SKEYs You can use the * character as a wildcard to define a symbol for several similar SKEYs. This sequence therefore defines the SKEYs VBBW. For example: SKEY ’VB**’ This illustrates the use of the ** characters to cover all end conditions. by setting it to VBBW or VBCP but not to VB**.1. VBFL.0 .1. VBSC and VBPL in a single operation. VBSW.e. i. SC (screwed) and PL (plain).0 NEW STRA PURP LINE TPT OFFS X8. Note: The wildcard option applies only to the definition of SKEYs. CP (compression).0 Y1. You must specify a particular end condition when you set the SKEY attribute of a DTEX element in the Catalogue DB.0 NEW STRA PURP LINE 19:3 12.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. 19.0 NEW STRA PURP LINE TPT OFFS X8. FL (flanged).0 Y1. for example. SW (socket weld).DRAFT User Guide ISODRAFT Symbols 19. BW (butt weld). VBCP.0 Y-1. 0 Y0 19. the file is closed by giving the command: ISOSYMBOL CLOSE This will overwrite an existing file. You can open a new (or existing) file by giving the command: ISOSYMBOL filename The current symbol (i. Note: PDMS Release 12 now user double precision floating point representation for numbers. you must output the Symbols to an ISODRAFT Symbol File using the ISOSYMBOL command. Such files must be regenerated from the symbol elements using the ISOSYMBOL command to create a new file in a double precision release of DRAFT.0 NEW STRA PURP LINE TPT OFFS X0 Y0 NEW MRKP PURP LEAVE ORIG OFFS X8. 19:4 12. ISOTM) can be added to the file by: ISOSYMBOL ADD A symbol that has been added but is not required can be removed from the file by giving the command: ISOSYMBOL DELETE skey When all the symbols have been added.0 .0 Y-1.3 Querying ISODRAFT Symbol Templates The following querying commands are available: Q ALL ISOTM Q ALL ISOLB Q ISOSYM Q ISOSYM NUMBER Q ISOSYM n lists all ISODRAFT Symbol Templates lists all ISODRAFT Symbol Libraries list symbol keys and base symbol keys in the library file gives the number of symbols in the library file gives the symbol key and base key for entry number n. Double precision provides increased accuracy in floating point numbers from six significant digits to 8.DRAFT User Guide ISODRAFT Symbols TPT OFFS X4. Symbol files written by single precision (pre 12.2 Outputting ISODRAFT Symbols When you have defined the symbols you require in the Symbol Library. previously single precision was used.e.0) releases of DRAFT cannot be reopened for modification in double precision releases. 19. g. for example ORIG X300 Y250 It is also possible to construct a drafting point position.1 Introduction A drafting point position may be specified explicitly. e. ONPO. where a 2D position is required. positioning of gaps Dimensioning. it is also possible to construct lines and arcs. FRPO. THPO. positioning of a point through which a dimension line should pass Positioning of Overlay Sheets VIEW position attributes. for example ORIG OFFS X50 Y50 20:1 12.0 .g. using commands such as: ORIG MIDP position position ORIG OFFSET 2D_vector ORIG position DIST distance Here. a 3D) position is required. Point construction is available for • • • • • • Positioning of 2D drafting primitives Labelling.DRAFT User Guide Point and Line Construction 20 Point and Line Construction You can define a position in terms of other positions rather than defining it explicitly using the point construction facilities in DRAFT. position may be any of: • • • • • • • A 2D position: An existing drafting point: A 3D position: A Design Item: A p-point: A position on a p-line: ORIG MIDP X100 Y100 X800 Y800 ORIG MIDP ID@ ID@ ORIG MIDP E150 N7400 U1200 E2150 N4400 U3550 ORIG MIDP /PUMP1/IN /PUMP1/ON ORIG MIDP P0 OF /PUMP1/IN P0 OF /PUMP1/ON ORIG PLIN TOS OF /SECT1 START DIST 150 The 3D position of a Design item. p-point or p-line position 2D_vector specifies an offset position from the owner origin of the primitive concerned. 20. where a 2D (or. if appropriate. e. As well as points.g. e. VREG command SYTM and TXTM positioning. 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 For a VNOT.2 X. DEFINE.DRAFT User Guide Point and Line Construction distance gives a distance and a direction from a point. FPT. TPT. positioning the centre of a circle on a Design element position) are only allowed for drafting below VNOT elements. distance may be expressed as units_value DESIGN direction where direction is a 3D. The distance specified is a Design distance in the current View. 3D point constructions (for example. for example if the point were defined using a tangent to a circle. For example. CPT. All point constructions are carried out in the context of the current database position. LENGTH. For example: 20:2 12. RADIUS etc.0 . e.g. with examples. 20. a point construction will give a 2D point. The following sections describe the various types of point construction. The above syntax may also be used in most drafting commands. In some cases there could be ambiguity about the point to be constructed. 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. DRAG TO. p-point or p-line direction. where point could include: • • • • • • The endpoint of a line or an arc The centre of a circle or an arc A tangency point An intersection points The point on a line or an arc nearest to a given point The point defined by the perpendicular from a given point The constructed point could also be defined explicitly or by a cursor hit. In cases such as this the point to be used can be qualified with a cursor hit. Y Filtering A 2D position may be defined in terms of the X or Y coordinates of other points. If the current element is owned by a NOTE or SYTM. The symbol @ denotes a cursor hit. or the intersection of two circles. 3D positions may also be constructed. 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.General 2D Position. Y coordinate from second cursor hit The process of deriving a coordinate from a coordinate of another point is known as X. Dimension Points etc. e. Y Filtering . X.g. Y filtering can be used with any 2D element which has a position attribute. X. Y 500 2 1 100 100 500 X Figure 20:1. including edits on various Dimension attributes. X and Y filters may be used in any command that requires a 2D position on a Sheet.: X. Y Filtering .DRAFT User Guide Point and Line Construction 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. but this only applies to 2D drafting primitives that are members of VNOT elements. 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. Labels. Examples 1.General 2D Position 20:3 12. Y filtering. See Figure 20:1. VIEWs.0 . 20:4 12.: Use of the MIDPOINT Construction. which may be defined explicitly or by cursor hits. a projection line clearance X coordinate would be set to the X coordinate of the cursor hit.2 Midpoint of an Existing Straight Line or Arc Example 1.1 Midpoint of Two Defined Points A drafting point position may be constructed as the midpoint of two other points using the following command syntax: MIDPOINT position position where position is as described in Introduction. 20. 400).4. DTOF X @ Y250 With a cursor hit at (400.4. enabling 3D positions to be constructed by picks on any line in the Design graphics. 3. 20. This facility is only valid in Plan or Elevation VIEWs. For example: NEW STRA DEF @ TPT POS OF ENDP OF @ Position TO point at end of 3D line. the Y coordinate being set to the Y coordinate of the 2D projection of the given 3D position.3 Construction of 3D Positions A specified 2D point may be projected into 3D. The ‘to’ point is therefore (200. 20. 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.DRAFT User Guide Point and Line Construction Here. A Q DESC command would return a 3D coordinate for the TPT of the line. 20. the above command would move a Dimension text origin to (400.4 Midpoint Position This form of construction derives a position as the midpoint of two other positions. Note that the Q ENUPOS and Q SHPOS commands (see Querying Position Data) also calculate conversions between 2D and 3D positions.0 . 900). NEW STRA FPT MIDPOINT OF @ TPT MIDPOINT OF @ (or NEW STRA DEF MIDPOINT OF @ MIDPOINT OF @) Here. 400). 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. This is done using the POSition OF <point> syntax. 250). 2. PLCL X @ Y OF POS E3000 S2000 U0 Here. 0 . Use of the Quadrant Construction (i) Quadrant points of an arc or ellipse may also be identified. This will be the extreme TOP. If an ellipse is rotated. BOTTOM. For example NEW STRA FPT @ TPT TOP ELLI /ELLI1 constructed point 2 1 Figure 20:4. the nearest extreme of the ellipse will be selected. a rectangle.5 Quadrant Point Position A quadrant point of an existing circle can be used for point construction. As well as using a cursor hit. 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.DRAFT User Guide Point and Line Construction newly defined STRA Figure 20:2. 20. For example NEW STRA FPT @ TPT TOP OF ID @ constructed point 2 1 Figure 20:3. Note: Note that with this variation of the MIDPOINT syntax. Use of the MIDPOINT Construction The required midpoint could also be that of one side of a closed polyline primitive. the STRA or ARC may be identified explicitly.g. 20:5 12. LEFT or RIGHT of the circle. e. Use of the Quadrant Construction (ii) The syntax will always construct a 2D position. the presence of the OF keyword is mandatory. Y 500 (150.6 Endpoint Position This form of construction derives a position as the endpoint of an identified element (typically a line or an arc).DRAFT User Guide Point and Line Construction 20. If there is any ambiguity. or a line that comprises a piece of a design item shown in a VIEW) may be extracted by cursor. 20:6 12.0 . 2.g. NEW STRA FPT X150 Y250 TPT ENDPOINT OF @ (or NEW STRA DEF X150 Y250 ENDPOINT @) Here. 3. NEW STRA FPT X150 Y150 TPT ENDPOINT OF PREV ARC QUAL X400 Y400 Here. the line has one of its endpoints defined explicitly. Line definitions of other elements (such as one side of an EQUI. then a solution will be chosen and returned arbitrarily. The required endpoint could also be that of one side of a closed polyline primitive. NEW MRKP DEF ENDPOINT @ Here. 250) 100 100 newly defined STRA X 500 Figure 20:5. Examples 1. Note that the cursor hit acts as the qualifier. Use of the ENDPOINT Construction Here. Y400). 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. e. the other as the endpoint of the hit arc. a rectangle. a MRKP is positioned on the end of the STRA closest to the cursor hit. Note that endpoints of lines and arcs can also be picked directly using the IDPT @ command. the cursor hit also acts as the qualifier. A qualifier may be added if there is any ambiguity about which endpoint is to be used. and if the qualifier is omitted. Use of the ENDPOINT Construction.DRAFT User Guide Point and Line Construction Y previous ARC in list order 500 (400. NEW STRA FPT X150 Y250 TPT CEN OF @ (or NEW STRA DEF X150 Y250 CEN OF @) Here. 250) 100 100 newly defined STRA X 500 Figure 20:7. the line has one of its endpoints defined explicitly. table. 250) 100 100 newly defined STRA X 500 Figure 20:6. ellipse. rectangle. arc. hexagon.0 . 20:7 12. A point may also be constructed using the focus of an ellipse. Use of the CENTRE Construction 2. with Qualifier 20. the text origin is placed at the centre of the previous circle element in list order. 400) (150. the other as the centre of the element (in this case a circle) hit by the cursor. diamond or equilateral triangle. Example 1.7 Centre or Focus Position This form of construction derives a position as the centre of a specified circle. NEW TEXP text DEF CENTRE PREV CIRCLE Here. Y 500 (150. Use of the FOCUS Construction 20. the MRKP lies at the endpoint of the STRA. the ‘to’ point of the line is placed at the focus of ellipse /ELLI1 qualified by a cursor hit. its ‘to’ point being defined as the nearest point which lies on the previous ARC in list order to the given qualifying point. the MRKP element and the position (X150. 20:8 12. the MRKP element is the nearest point that lies on the previous STRA in the list order to the given qualifying point.8 ‘Nearest To’ Position This form of construction derives the point on a primitive that is nearest to a specified qualifying point. Y newly defined MRKP Y newly defined MRKP (150. NEW MRKP DEF NEAREST PREV STRA QUAL X150 Y250 In the left-hand case shown below. In the right-hand case. NEW STRA FPT X150 Y250 TPT NEAREST PREV ARC QUAL @ Here. 250) X 100 500 X Figure 20:9. constructed point 2 1 Figure 20:8. Y250) lie on the perpendicular to the STRA.DRAFT User Guide Point and Line Construction 3. In both cases. NEW STRA FPT @ TPT FOC OF /ELLI1 QUAL @ Here.0 . Use of the NEAREST Construction (1) 2. Example 1. 250) 100 100 500 100 (150. the STRA has its ‘from’ point defined explicitly. 9 Intersection Here. or CIRC. although line-parts of more complex primitives may be identified by cursor. constructed point 2. but it is only possible to calculate the intersection point between an ellipse and a straight line. The primitives should be chosen from STRA. 250) 100 100 500 X Figure 20:10. INT @ This variation uses a single cursor hit to pick the intersection point explicitly.0 . use of qualifier in Endpoint Position) Examples 1. 20.DRAFT User Guide Point and Line Construction Y newly defined STRA (150. Note that in this case a qualifying point is not needed. INT BETW @ @ This constructs a point at the intersection of two hit primitives: 20:9 12. An ellipse (ELLI) is also an allowable primitive. ARC. a point is constructed which is at the intersection of two primitives. the MRKP element would be snapped to the primitive nearest the cursor hit. NEW MRKP DEF NEAR @ Here. Use of the NEAREST Construction (2) 3. A qualifying point may also be specified when there is more than one point of intersection (cf. DRAFT User Guide Point and Line Construction constructed point 3. Use of the INTERSECTION BETWEEN Construction 20:10 12. INT BETW @ @ In this case the second cursor hit acts as a qualifier: constructed point 1 2 4. 300) 100 100 500 X Figure 20:11. the intersection point is the one closest to (X100. the other endpoint being the midpoint of a specified line. 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.0 . INT /CIRC1 AND /STRA1 QUAL X100 Y100 Here. Y newly defined STRA 500 (200. Y100) constructed point (100. 100) 5. NEW STRA FPT INT BETW PREV ARC AND PREV CIRC QUAL X200 Y300 TPT MIDP OF PREV STRA Here. Y200). 2. Here the cursor hit acts as a qualifying point. NEW STRA FPT X200 Y100 TPT X200 Y100 TAN PREV CIRC QUAL @ Here. Use of the TANGENT Construction to give a Tangential Line 20:11 12. Notice that the STRA produced here is not a tangent line. Examples 1. Use of the TANGENCY Point Construction This STRA element has an explicit FPT. circle or ellipse.DRAFT User Guide Point and Line Construction 20. Y 500 100 (200. NEW STRA FPT X100 Y100 TPT X300 Y200 TAN @ Y 500 (300. 200) (reference point) 100 (100. the STRA has one endpoint defined explicitly and the other defined as the point where the tangent line through (X200. 100) 100 500 newly defined STRA X Figure 20:13.10 Tangency Point This construction generates a point at which a tangent line from a specified reference point meets a specified arc.0 . forms a tangent to the ARC. together with (X300. Y100) intersects the previous CIRC in list order which is closest to the cursor-specified qualifying point. its TPT is the point on the ARC that. 100) 100 newly defined STRA X 500 Figure 20:12. 11 Tangent Lines The TANLINE command can be used to draw a tangent line between any two ARC or CIRC elements. and the third picks the circle and also acts as a qualifier. (Other tangent shown dashed.: Use of the TANLINE command to give a Tangent Line shows various examples of the use of the tangent line facility. the syntax to create a tangent line would be. NEW STRA DEF @ @ TAN @ In this case. generated point (200. 100) 3. the second defines one end of a tangent. Notice how (right-most illustration) the tangent line may lie on the complement of an ARC. See below. The resulting STRA intersects the tangent.0 . for example: TANLINE @ @ Figure 20:15.) Other cases would not need a qualifier since only one tangent would be possible (see below). Provided that the current element is a STRA. 20:12 12. Use of the TANGENT Construction to give a Line perpendicular to a Tangent 20. 1 2 newly defined STRA 3 Figure 20:14. the first cursor hit defines one endpoint of the STRA.DRAFT User Guide Point and Line Construction The qualifier is necessary since in this case there are two possible tangents. 20:13 12. NEW STRA FPT X300 Y100 TPT X300 Y100 PERP PREV STRA Here. NEW STRA FPT X0 Y0 TPT X0 Y0 PERP PREV CIRC QUAL @ Here (see opposite). Use of the TANLINE command to give a Tangent Line 20. 2.0 . arc.) Examples 1.: Use of the PERPENDICULAR Construction. two constructed points are possible and so a qualifying cursor hit is used. or circle) and the perpendicular from a specified point to the primitive. Use of the PERPENDICULAR Construction 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. The perpendicular will always lie in the plane of the paper. Y 500 100 (300. that nearest the specified point is generated (unless this is overruled by the presence of a qualifier.DRAFT User Guide Point and Line Construction Figure 20:15. See Figure 20:16. 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.12 Perpendicular Intersection Point This construction generates a point that is the intersection point between a selected primitive (a line. 100) 100 500 newly defined STRA X Figure 20:16. If there is more than one possible constructed point. 0 . the cursor hit selects the primitive and acts as a qualifier. See below. NEW STRA DEF X0 Y0 PERP @ X0 Y0 Here (see below).DRAFT User Guide Point and Line Construction Y 500 100 100 newly defined STRA 500 X 3. the second defines one end of the line that intersects the circle. NEW STRA DEF @ @ PERP @ In this case. Y 500 100 100 newly defined STRA 500 X 4. newly defined STRA 1 3 2 20:14 12. the first cursor hit defines one endpoint of the STRA. and the third picks the circle (and also acts as a qualifier). 1) and an angle.15 Constructed Lines. For example: NEW CIRC DIAM 10 AT @ REFL @ 1 2 newly defined CIRC The first point to be specified must be explicit. (A linear element includes a STRA element.15. a constructed line is created using the CONLINE command to define a Through point (which may be any of the position options.DRAFT User Guide Point and Line Construction 20. Creation of fillet arcs FILLETRAD -10 @ @ FILLETRAD -5 @ @ 20. The position of the reflected point is along the axis of the two specified points.e. Ray Lines and Bisector Lines 20. see Section 11. the syntax to create a fillet arc would be.0 .g. or any other element on the drawing that is composed of straight lines (e. 3D design elements.14 Fillet Arcs The FILLETRADIUS command can be used to draw a fillet arc between any two linear elements.13 Reflected Points A point may be reflected in another point using the REFLECT syntax. For example: CONLINE @ 30 This would give: 20:15 12. it cannot itself be a constructed point. 20. etc). A 3D position may be constructed if appropriate. the side of a RECT.1 Constructed Lines A constructed line in this context is a STRA element whose endpoints lie on the SHEE boundary. Provided that the current element is an ARC. i. Starting with a STRA as the current element. for example: FILLETRAD 10 @ @ Figure 20:17. A Constructed Line Note: that if the current SHEE size is changed. Ray Lines RAYLINE @ 210 Note: that if the current SHEE size is changed. Starting with a STRA as the current element.) Starting with a STRA as the current element. (The two elements need not actually intersect.2 Ray Lines A ray line in this context is a STRA element whose FPT is user defined. Bisector Lines BISECT @ @ BISECT @ @ LEN 100 Note: that if the current SHEE size is changed.15. a ray line is created using the RAYLINE command to define a From point (which may be any of the position options. the intersection point is derived by projecting the elements if necessary. 20. the TPT of the STRA will not be updated. 20.3 Bisector Lines A bisector line in this context is a STRA element that bisects the angle included between two existing linear elements. a bisector line is created using the BISECT command to define the two lines to be intersected. Its FPT is the intersection point of the two existing linear elements and its TPT lies on a line joining the FPT to the SHEE boundary.15. 20:16 12. For example: RAYLINE @ 30 Figure 20:19.DRAFT User Guide Point and Line Construction Sheet boundary Figure 20:18. the TPT of the STRA will not be updated. and whose TPT lies on the SHEE boundary. the FPT (From point) and TPT (To point) of the STRA will not be updated. For example: BISECT @ @ Figure 20:20.0 . see Introduction) and an angle. For example. For example: 2 1 1 2 CHAMFERD 20 @ @ Figure 20:21. for use with point construction.17. For example.17. (The same effect could be achieved by leaving the order of identification unchanged but switching the chamfer distances values in the command. 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). using the CHAMFERDIST command to specify the two lines to be chamfered and the chamfer distances. with the cursor.17 Non-Drafting Applications of Point Construction The point construction facilities can be used not only with 2D drafting but also with other functional areas of DRAFT such as dimensioning and labelling. directly with the cursor. (Similarly FROM POS OF @. 20. When creating linear and angular Dimensions.16 Chamfer Lines A chamfer line can be drawn between any two linear elements. Chamfer Lines 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. 20. 20. the syntax FROM POS OF INT @ 20:17 12. For example. a dimension line.1 Labelling Point construction is available in all syntax that requires the input of a single 2D position. a label line. and the 2D position lies in the current VIEW. and in some cases can only be used.) If a single value is specified. DIM CENTRE OF @ could be used to position a Dimension line to run through the centre of an existing CIRC element. if appropriate. This procedure is possible provided the current VIEW is orthogonal.0 . a linear piece of the design. can only be picked. for example.2 Dimensioning Point construction is available in all syntax that requires the input of a single 2D (or. this is used for both chamfer distances. These uses of point construction are most useful. it is possible to dimension to a constructed 2D point using the TO POS OF @ syntax.DRAFT User Guide Point and Line Construction 20. a 3D position). 20.5 Other Non-Drafting uses of Point Construction The XYPOS attribute of SYTMs and TXTMs under Label Libraries (LALBs) and Symbol Libraries (SYLBs) can be set to a constructed point position (using the XYPS. REPEAT causes the last picked option to be presented.3 Overlay Sheets An Overlay Sheet can be positioned at a constructed point using the OPOS and OSHEE commands. XYPO or AT commands).17. 20.17. provided the current VIEW is orthogonal. The default can be changed using the PCOPTION command: PCOPTION TWODhit PCOPTION ENDOF PCOPTION CENTReof PCOPTION MIDOF PCOPTION MIDBEtween PCOPTION INTAT PCOPTION INTBEtween PCOPTION NEAREST PCOPTION REPEAT The first eight commands cause the specified option to be presented as the default. 20. The THPO OF @ syntax (similarly FRPO OF @ allows input of a 2D constructed point.17. 20:18 12.17.4 Drawing the Design At VIEW level point construction methods can be used to: • • • position the VIEW using the AT command set the VIEW size and position using the VREGION command set the THPO.6 Point Construction Option Form When the Point Construction Option form is displayed the default option is the 2D Cursor Hit option. and the 2D position lies in the current VIEW.DRAFT User Guide Point and Line Construction will create a Dimension point at the intersection of two (valid) elements. FRPO and ONPO positions of the VIEW.0 . 20. DRAFT User Guide DRAFT Database Hierarchy A A.0 .1 DRAFT Database Hierarchy Basic Hierarchy WORLD STYLWL LIBY DEPT GLYTB GLYPH LSTYTB LINEST OLINES FSTYTB FILLST HPATTE (see overleaf) REGI REPO TEXT DRWG LIBY (see overleaf) SHEE REVI TEXT OLAY NOTE REVI VIEW (see overleaf) LAYE RRUL HRUL VSEC ADIM LDIM PDIM RDIM VNOT GLAB SLAB TAGR (see overleaf) A:1 12. 0 . Note: Automatically created system elements are not shown.DRAFT User Guide DRAFT Database Hierarchy Note: Automatically created ‘system' elements are not shown. A:2 12. The algorithm is designed to distribute picture files homogenously among the subfolders. B:1 12. BACKs etc. The final number is the picture version number (PVNO attribute). Folder Structure The picture file folder %<project>PIC% is split to improve the file system performance on large projects. AVEVA might adjust it in future versions so user applications should rely on the PICFilename pseudo-attribute. there is no user-configurable option. 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). Only those picture elements that may include design graphics (that is SHEEs and OVERs) have picture files. OVER) using the command: Q PICFilename This returns the picture directory and file name. This is incremented every time the picture is modified.DRAFT User Guide Picture File Naming Conventions B Picture File Naming Conventions Filenames Picture filenames incorporate the database reference and version number (PVNO attribute) of the picture element. as it is guaranteed always to return a valid picture file path. with increasing numbers of picture files. The graphics for other picture elements (LALBs. for example: %ABCPIC%/27/M46-2107-20-13 Note: The details of the distribution algorithm are an internal feature of DRAFT. 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. Picture file names have the form: M46-2107-20-13 where the first two numbers are the database reference of the picture element.) are created when required. The picture filename may be queried at the picture element (SHEE.0 . 0 .DRAFT User Guide Picture File Naming Conventions B:2 12. . . . . . 13:21 B BACK (Backing Sheet Template) element 17:3. 18:6. . . . . . . . . . . . . . . 18:12 Angle Subtended (ASUB) attribute 12:31. . . . . . 13:2 Attachment point offset . . . 18:29 ADEG attribute . . . . . 3:5. . . . . . . . . . . . 11:3 BPOF (Bend Point Offset) attribute 13:12. . 18:17. 12:23. . . . . . 13:27. . . . . . . . . . . 12:2. . . . . . . 18:30 ALIG (text alignment) attribute . 5:9. 13:3. . . . . . . . . . . . . . . . . 20:7 Chained dimensions . . . . . 11:3 3D view direction . . . . . . . . 12:35 ADIR angular dimension direction element . . . . . . . . . . . . . 18:10 C CENTRE keyword . . 20:17 CHANGE ACTION command . 12:36 AKEY attribute . . . . . . . . . . . . . . . . . . . 3:10. 3:12 Arc tolerance (ATOL) attribute . . . . . . . . . . . . . . . . . . . 12:3 Bent leader lines . . . 11:3 AUTOSCALE command 3:3. . . . . . . . . . . . . 14:1. . . . . . . . 12:36 CHAMFERDIST command . . . . . . . . . . 18:2. . . 17:4 BSRF (Backing Sheet Reference) attribute 17:3 BTEX (Body Text) attribute 13:4. 3:21 Before/After linear dimension . 18:9. 17:3. . . . 20:2 Attachment point of Labels . . . 12:26. . 2:3. 20:16 Blank areas . 13:8. . . . . 12:23 ALARM command . . 12:34. . . . . 13:14 Attribute Key (AKEY) attribute . . 3:24 ADEFINE command . 3:12 A ABSOLUTE command . . . . . . . . . . . . 13:6 Angle of turn (ADEG) attribute . . . . . 18:2 Background Process . 3:10 ADIM (Angular Dimension) element . . . . 13:23. . . . . . . . 2:6 ALENGTH command . . . . . . . . . . 5:3 Index page i 12. . 13:7. . . . . . . .0 . . 13:28 ADD command . . .5:10. . . 12:5 CIRC (Circle) element . . . . . . . . . 18:26 BY command . . . . . 12:43 APPT angular dimension direction element . . . . . . . 13:6. . . . . . . . . . . . . . 12:36 ARC element . . . . . . . . 3:13. 2:4 ANGLE command . . . 13:28 CHECK REFERENCES command . . . . . . . . . . . . . . . . . . . . . . . . 13:14 BSHEE command . . 18:6. . . . . 13:14. . 18:35 Bulge factor (BULG) attribute . . . . . . . . 5:12. . . 12:6. . . . . . . . 18:19 CLMO (Centreline Mode) attribute . . . . 5:11 Character Height (CHEI) attribute 12:19. . . . . . . . 13:27. 13:27 ALPHA command . . . . 4:6. . . . 18:16 Arc tolerance . . . . . . . . .13:5. . 18:10. . . . . . 12:47 Angular Dimension (ADIM) Elements . 12:46 Autoblanking .DRAFT User Guide Index Numerics 2D Symbolic Representation 3:17. 3:4. 13:28. . 13:5. . . . . . . . . . . . . . . . 3:12 AT command . . 13:10 BISECT command . . . . . . . 18:9. . . . . . 3:26 Autotagging exclusions from . . . . 20:2 CRIT command . 12:48 DRAFT entering . . . . . . Height (DTCH) attribute . . . . 12:23 Dimension Line Angle (DDEG) Attribute 12:25. 18:18. . . . . . . . . . . . . . . . . 12:41. . . . 12:29 Dimension text . . . . . . . 12:46 DLLB (Id List Library) element . . . . . . . . . . . . . . . . . . . . . 12:9 Double Precision . . . . . . . . . . . . . . 12:5 DDNX system attribute . . . . 12:9 Dimension Line Position (DPOS) attribute 12:9. . . . . . . . . . . 3:28 DELETE STEP command . . . . . . . 18:9. . . . . . . . . . . 12:9 Dimension. . . 12:26. . . 13:31 Design elements hatching . . 12:26 Dimension Text Character Height (DTCH) attribute . . . . . . . . . . 12:23. . 3:24 Design Data Name (DDNM) attribute . 4:12. . . . . 12:13. . . . . . 12:48 DPOI (Dimension Point) element 12:3. . . . 20:2 DELETE command . . . . 12:13 Dimension Text Font (DFONT) attribute 12:31 Dimension Text Letter Height (DTLH) attribute 12:19. . . . . . . . . . . 12:19 DIR attribute . 12:45 Dimension lines . . . 18:6. 12:12. . . . 12:2. . . 3:18 Design Symbol Layer (DSLAYE) element 3:18 Design Symbol Link (DRSYLK) . 12:31 Crosshairs Overshoot (CHOSHT) attribute . 3:5. . . 12:31 CSPA (Character Spacing) attribute 13:7. . . . . . . . 12:48 DIMENSION RADIUS command 12:38. . . . . . . . . . . . . . . . 12:14. . 12:35. . . . . 2:2. . 19:4 DPBA (Dimension Point Before/After) element 12:3. . 12:43. . . . 3:7 DELETE NULL ANNO command . . . . . . 13:20. . . . . . . . . . . . . . . . . . . . . 12:39. . . . . . . . 18:15 Index page ii 12. 3:5. . . . . . 12:24. . 12:43. . . . . . . 12:19. . . 12:45 Dimension Offset (DOFF) attribute 12:4. Text. . . . . . . 12:43 Dimension Text Offset (DTOF) attribute 12:14. . . . . . . . . . 12:41 Dimension Line Spacing (DMSP) attribute . . 3:11 Display preserving. 12:32. . . 12:47. . . . . . . . . . . . . . 12:3 deleting unwanted . . 3:18 DESREMOVE command . . . . 8:3 COLSTYLE. 18:8 Draughting points . 12:46 Dimension Line Direction (DIR) . . . . . 12:45 Dimension line terminators . . 18:18. . Character. . 12:5. . 12:20. . . . . . . . . . . . . . 12:35 Dimension attribute key (AKEY) . . . . . . . . . . . . 5:10. . . . . . . 12:9. . . . 12:43 DIMENSION SEPARATION command 12:12 Dimension Style of radial dimensions . . 2:5 DLFG attribute . . 2:4 DRAG command 18:6. . . . . . 13:13. . . . . . . . 12:38. . . . . . . . . . . . . 5:12 DESADD command . . 4:13. . . . . . . . . . . 18:34 Common draughting primitives handling . . . . 18:25 D Databases switching between . . . . . . . . 3:7. 2:1. . . . . . . 12:32. . . . . 3:24 DESSYM (Design Symbol) element . . . . . 12:2. . . . . . . . . . 20:15 Connection Point Offset (CPOF) attribute . . . . . . . . . . . . COLCOLOUR attribute . . . . . . . 13:17 CPT (centre point) command . . 12:9 Direction of View . . . . . . . . . . . . . . . . . . . . 12:38. . . . . 12:21 Dimension points . . . . 12:46 Crosshairs Line style (CHSTYLE) attribute . . 12:39. . . . . 12:43 Dimension origin (of angular dimension) 12:34 DIMENSION PEN command . . . . . 12:24. 12:43 Dimension text underlining in radial dimensions . . . . . . 13:14. . 12:48 DELETE NULL IDLI command . 20:2 Draughting origin shifting . . . . . . . . 12:9 DPPT (Dimension Point/P-Point) element 12:3. . . . . . . 18:19. . 12:43 DIMENSION TEXT command . . . . . . . . . 12:42. . 12:42 Dimension arc . . . . 13:27. . . . . . . 7:14 DIM @ command . . . . . . . . . . . . . . . . . . . . . 2:4 DRAFT command . . . . . . 13:28 Curve fitting . . . 18:14. . . 14:6 DOFF attribute . . . . . . . . . . . . . . . 12:12. . . . . . . . 18:22 DMTX (Dimension Line Text) attribute 12:13. . . 18:31. . . . . . . 12:29 DIMENSION OFFSET command . . 13:3. . . . . . . . 12:8. . . 20:1 identifying . 12:46 DGN Output . . . . . . . . . . recovering . . . 18:11 CONLINE command . . . . 12:42. . 12:43 Dimension text angle . . . 14:1. . . . . . 3:4 DMND (Diamond) element . . .DRAFT User Guide Colours. . . . . . . . . . . . . . 12:35. . 12:32. . . . 3:18 DFLAG attribute . . . . . . . . . . 2:3 DDNM attribute . . . . . 10:8 Crosshairs Colour (CHCOLOUR) attribute . . . 13:23. . . 18:30. . 3:11. . . . . . . . . . . . . . . 12:36 DPOS attribute . 12:41 truncating . . . . . . . . . .0 . . 12:48. . default . . . . . . 2:2 DEFINE command 18:17. . . . . . . . 4:8 Design Symbol (DESSYM) . 12:39. . . . 12:46 Crosshairs Line Style/Colour (CHSTYLE/CHCOLOUR) . . . 6:4 GRSYS attribute . . . . . 2:2 IDLX system attribute . . . . . . . . 4:11 Hatching automatic . . . 12:37. . . . . . 4:9 Hatching Ruleset Reference (HRSF) attribute 3:12 HEXA (Hexagon) element . . . . . . . . 3:4 IDLN attribute . . 5:5 FONT attribute . . . . . 12:13. . . . . . . 18:14 I ID ADIM. . . . . . . . . . . . 13:1 GETWORK command . .DRAFT User Guide positioning . 18:12 moving . . 12:35. . . . . . . . . . . . . . . . . . . . . . . . . . 12:29 DXF output scaling . . . . . 18:23 F Fill Style . . . . . . . . . . 18:15 ERASE command . . . . . . . . . . . . . 3:7 querying . . . . . . . . 18:9. . . . . . . . . . . . 18:6 mirroring . . . . . 5:1. . . 12:6. . . 12:21 GBOX (frame clearance) attribute . . . 12:41. . . . . . 12:39. . . . . . . 18:28 Frame clearance (GBOX) attribute . . . 5:11. . . . . . 20:6 ENHANCE command . . . . . . . 12:43 FRPO (From Point) VIEW attribute . . . . . 2:2 IDNM attribute . . . 5:11 H Hatch pattern in automatic hatching . . . . . . . . . . 2:2 INSERT command . . 12:39 Id List cleaning up . . . . 13:27 FROM command . . . . . . . . . 5:1 ENDPOINT keyword . . . . . . . . . . . . . . . .0 . . 20:15 Filtering X. . . . . . . . 3:16 Hidden lines . . . . . 13:14. . 12:46 DTANGLE attribute 12:14. . . . . . . . . . . . . . . . . . . . 12:32. . . . . . . . . . . . 14:10 INTERSECTION keyword . . . 2:5 Grid snapping to . . . . . . . . 19:1 E EDTEXT command . . . . . . . . . . . . 13:27 General Label (GLAB) element . . . . . . . . . . . 14:17 GTYP attribute . . . 13:30 Gaps. . . . . . . . 13:27 Index page iii 12. . . 15:3. . . . 20:3 Flat Plane (FPLA) element . . . . . . . 5:13. . . . . 2:2. . . . . . . . . . 5:7. . 12:44 DTER (Dimension Line Terminator) attribute 12:20. 18:9 querying . . . 18:15 IDLI (Id List) elements . . .Y . . . . . . . . . . . 2:2 IDNX system attribute . . . . . . . . . . . . 20:1 Draughting primitives copying . . . . . . 15:1 FPLA element . . . . . . . . 18:12 Drawing (DRWG) element . . . . . . . . . . . 14:1 Intelligent text sub-strings . . . . . . . . . . . . . . . . . 18:18. . . . . . . . . . 18:10 rotating . . . 3:11 J JUST (text justification) attribute 13:8. 3:1 DRSYLK (Design Symbol Link) element 3:18 DSLAYE (Design Symbol Layer) element 3:18 DSTYE (Dimension Line Style) attribute 12:46 DSTYLE (Dimension Line Style) attribute 12:29 DTANG attribute . . . . . 12:41 INSTALL SETUP command . . . . . . . . . . . . . . . . . . . . 6:6. . . . . . . 18:11. . . . . . . . . . . . . . 12:24. . 19:4 ISOLB element . . . . . . . . . . . . . . . . . . . . . . 3:7 Id List Library (DLLB) element . . . . . . . . . . . sketching and erasing . . . . . . . . . . . . . 13:4. . . . . 13:9. . . . . . . . 12:43 DTRA (Text Radius) attribute . . . 3:3. . . . . . . . . . . . 12:46 DTUL (Dimension Text Underline) attribute . . . . . . . . . . 13:4. . . . 19:1 querying . . . . 12:26. . . . . . . . . . . . 12:20. . 12:5. . 12:45. . . . . . . . . . . . . . . . 12:3. . . . . 2:5 Intelligent text 11:2. . . . . 8:15 FILLETRADIUS command . . . . . . . . . . . . . . . 3:4 Id List Name (IDLN) attribute . . . . 5:3 IDDP command . . . 18:9 ETRI (Equilateral Triangle) element . . 12:32. 5:5 FPT (From Point) command 18:9. . . . . 12:45 DTFL (Text Radius Flag) attribute 12:25. . . . . . . . . . . . . . . . 18:24 Hidden line views . . . 20:10 ISODRAFT symbols . . . . . . . . . . 2:1. . . . . . . . . . . . . . . . . . . .12:21. . . . . . . . . . . 12:42. . . . . . . . . 4:8 Hatching Rules . . . . . . . . . . . . 19:1 ISOTM element . 7:6 G GAP command . . . . . . . . . . . . . . . . 18:31. . . 18:13 creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15:4 ELLI (ellipse) element . 3:13 HIGHLIGHT command . . . . . 18:19. . . . . . . . . . . . . . 18:23. . . . . . 20:2 FRAD (fillet radius) attribute . . . . 12:25. . . . . . . . . . . . . . . . . . . . . . . . . . ID LDIM commands . . . . 12:46 DTOF (Dimension Text Offset) attribute 12:14. . . . . . . . . . . . . . . . 18:12 moving groups of . . . . . . . . . 18:22 Enclosed planes . 13:9 Labels deleting unwanted . . . . 12:8. . . . . . . . . . . . . . . . . . . . . . 13:16. . . . . . . . . . . . . 18:8. . . 13:10 with Radial Dimensions . . 13:28 LFRA attribute . . . . . . . . . . . . . . . . . . . 11:3 LENG (length) attribute . . 13:27 LFSTYLE (Label Frame style) attribute 13:27 Limits of view . . . . . 12:32. . . 17:3. . . . . . . . . . . . . . . 18:10 Orientation view contents . . . . . . . . . . . . . . . . . . . . . . . 12:45 PCENTRE command . 13:14 orienting . . . . . . . . . . 17:3 OSRF (Overlay Sheet Reference) attribute 17:3 OTPT command . . . . . . . . . 3:18 O OANG (Overlay Sheet Angle) attribute 17:1. . . . . . . . 13:7. . . . 12:33 PCIRCUMFERENCE command . . . . 12:42. . 12:8. 12:45 Leader Line Clearance (LLCL) attribute 13:10 Leader Line connection point . . . . . . . . . . 18:30 Letter height (LHEI) attribute . . . 13:12 LVIS (Layer Visibility) attribute 3:28. . . . . . . 3:14 MODIFY @ command . . . . . 18:25 N NCOL. . . . . . . . . . . . . 18:31 Outline (OUTL) element . . 20:8 NORM attribute . 18:12. . 13:2 Label attributes querying . . . . 3:11 LSHA (Leader Line Shape) attribute . . . . . . . . . . . . . . . . . . . . . . . . 18:25 OVER (Overlay Sheet Template) element 17:3 Overlay (OLAY) element . . . . . . . . . . . . 12:38. . . . . . . . . . . . . . . . . 13:5. . . . . . . . . . . . 12:29 Legibility improving . . . . . . . 18:35 NPPT attribute . . . 12:45 P Parallel dimensions 12:6. 18:12 Omitting from RRULEs . . . 18:3 12:31 MIDPOINT keyword . . . 12:24. . . . . . . . . . . . . . .0 . . . . . . . . . . 13:6 LAYE (Layer) element . . . . . . . . . 11:2. . . . . . . . . . . 3:18 Layer (LAYE) element . . 18:5. . . . . . . . . . . . . . . . 8:19 Marker Style/Colour (MSTYLE/MCOLOUR) Index page iv 12. . . . . . . . . . . 12:38. . . . . 18:37 MLNP (Member line style/colour) attribute 4:4 Modelled wireline view . . . 13:3 NSIZE attribute . . . . . . . 18:30. . . 12:21 LLSTYLE (Leader line style) attribute . . . 18:5. . 12:34 PCOPTION command . . . . .DRAFT User Guide L Label attachment point . 13:29. 13:28 OSHEE command . . . . . . . . . . . . . . . . . . . . . . . NROWS attributes (of Table) . 8:6 Linear Dimension (LDIM) elements 12:1. . . . . . . . . 12:9. 20:13 M Marker Style . . . . . . . . . 13:27 Local hidden lines . . . . 17:4. 5:9. 18:9. . . . . 17:3 Overlay Sheet Position (OPOS) attribute 17:1 Overshoot (OSHT) attribute 12:4. . . . . . 12:35. . 12:12. . . . . 13:10 Leader lines bent . . 13:5. . 12:43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:38. . . 17:4 Obstruction (OBST) level control . 13:29 Leader Line Visibility (LLEA) attribute . . . . . . . . . . . . . . . . . 13:31 for Views . . 5:4 PERPENDICULAR keyword . . . . . . . 18:34 NEAREST keyword . 12:3 OCOD (origin code) attribute 18:6. . 5:11 NOTE (Sheet Note) element 18:2. . 18:30 OFFSET command . . 18:3 Label text font . . 13:30 Label frame attributes setting . . . . . 18:19 ODEF command . . . 18:23. . . . . . . . . 13:3. . . . . . . . 13:28 Leader Line Terminator (LTER) attribute 13:10. . . . . . . . . . . . . . . . . . . 18:31 MRKP (marker) element . . . . 5:5. . . . 13:14 MPT (midpoint) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:36. . . . . . . . . . . . 13:12 Leader Line Spacing (LSPA) attribute 13:7. . . . . 17:4 OSLV attribute . . . . . 12:35. . . . . . . . . . . . 13:30 Label Library (LALB) element 13:1. 4:8 Looking direction . . 4:6 ON command 6:3. . 20:4 MIRROR command . . . . . . . . . . 3:8 LFRA keyword . . . . . . . . . . . . 20:2 LENGTH command . . . . . . . . . . . 3:11 controlling . . . 13:27 Label leader lines . . . . 13:27. . 3:15 Local Rules . . . . . . . . . . . . . 12:32 Perpendicular Flat Plane (PPLA) element 5:1. . . . . . 18:6. . . 13:10. 13:6 Lframe (LFRA) attribute . . . . . . . . 18:12. . . . . . . . . . . 18:5 LCHA attribute . . . . . . . . . . . . . . . . . . . . . 3:10 OSET (offset) attribute . . . . . . . . . 20:18 PDIM element . . . . . . . . . . 3:6 Line Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:41 Linestyles . 13:5 modifying . . . . . . . . . . . 12:42 modifying . . . . . . 3:19 P-point Number (%NUM) attribute . . . . . . 18:10 POSFOR attribute . . . . . . . . . . . . . . . . . 12:45 PLDI (projection line direction) attribute 12:9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19 PPOINTS command . . . 12:31 Projection line text . . 12:44 PTANGLE attribute . 12:42 PJUS (projection line text justification) command 12:17. . 9:2 Recipient name (RNAM) attribute . . . . . . . . . 12:41 P-lines . . . . . . . . . . . . . . . . 13:3. 12:10. . . . 3:11. . . . . . . . . . . . 11:2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:38. 12:17 Projection line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:1 P-point Direction (PPDI) attribute . . . . . . . . . . . . . . 5:11. . . . . . . . . . . . 7:1 PLRF (Plane Reference) attribute . . . . . . . . . . . . . . . . . . . 18:28 Reflected points . . . . . . 12:42 creating . . 9:4 RECREATE command . . . . . . . 12:32. . . . . . 2:1. . . . . . . . . . . . . . . . . . 3:11 Picture files . . . . . . . . . . . . . . 5:11. . . . . . . . . . . . . . 13:20 AKEYS . 5:7. . . . . . 12:9 Projection Line Style/Colour (PLSTYLE/PLCOLOUR) . . . . . 5:13 PLCL (projection line clearance) attribute 12:8. 12:44 Projection Text Letter Height (PTLH) attribute 12:19. 20:15 Registry (REGI) element . . . . . . 5:10. . . . . . 9:2. . 12:32 Radial Dimensions including projection arcs with . . . . . . . . 20:16 RCOD (rotation code) attribute . . . . . . . . . 12:32. . . . 18:16. . . . . . . . . . 12:24 RAYLINE command . . . . . . . . . . . . . . 12:44 Projection text angle . . . 14:6 PMOD (Plane Mode) attribute . . . . . . . . . . . 16:4 PKEY (p-line name) attribute . 3:19 view direction . . . . . . . . 12:36. 17:3 Q Qualifiers:in point construction . . . 12:21 PTANG attribute . . . . . 12:23 Id Lists . . . . . . . 18:15. . 5:12 switching . . . . . . . . . . . . 18:19. . 3:24 Remove Entry (REME) element . . . . . . 20:6 Querying . . . 14:12 PLLB element .0 . . . 2:4 R Radial Dimension (RDIM) elements 12:2. . . . . . . . . . . . 12:19. . . . . . . . . . . . . . . . . . . 12:31 Radius Dimension obtaining from Diameter . . 3:11 controlling . . . . 3:2 REMOVE command . . . . . . erasing . . . . . . . . . . . . . 3:4. . . . . . . . . . . . . . . . . . 5:12 Point construction defaults . 5:12 Plane retained/discarded side determining . . 5:3. . . . . . . . . . . 3:12 QUIT command . . 19:4 view contents . . . . . . . 5:12 Plane querying . . 18:15. . . . . . 12:42 Radial Dimension Position Point (RPOI) element 12:32 Radial Dimension P-Point (RPPT) element . . . . . . . . 14:17 Position converting 2D/3D . 5:10. . . . . . . . . . . . . . . . 12:8 PROJLINE OVERSHOOT command . . . . . . . . . . . 13:6 PPLINE command . . . . . . . . . . B:1 Pitch Circle Dimension (PDIM) elements 12:2. 12:18 Projection Text Character Height (PTCH) attribute . . . . 5:13 Planes Library (PLLB) element . 5:3 Planes. . . . . . 18:19 PURP (Purpose) attribute . . . . . . . . . . 5:5. . . 5:10. . . . . . . . . . . . . . . . . 12:32. . . 12:42 creating . . . . . . . . . . . . . . . . . . 12:18 PTFA (point reference) attribute 18:6. . . . . . . . . . . . . . . 5:3. . . . . . . 18:30 PTRF (point reference) attribute 18:6. . . . . . . . . . . . 12:41 PROJECTION JUSTIFICATION command . . . 5:11 Plane sketching . . . . . . . . . . . . . . . . . 6:4 PPDI (p-point direction) attribute 3:19. . . . . . . . . . . . 14:4. . . 12:25 Recipient (RECI) element . . . . . . . 6:3. 5:12 PLTX (Projection Line Text) attribute 14:1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:42 modifying . . . . . 12:43. . 3:7 symbols . . 4:4 PLOT command . . . . . . . . . . . . . . . . . . . . 7:1 Plotfiles size . . . . 12:44 PKDI (p-line distance) attribute 13:3. . . . . . 3:4 REPEAT command . .DRAFT User Guide PERS attribute . . . . . 12:2 Projection line direction (PLDI) . . 5:10. . . . 3:7 spatial map . . 18:13 Report (REPO) element . . . . . . . . . . . . . . 6:2 PROJECTION DIRECTION command 12:10. . . . 12:9 PROJLINE PEN command . . . . . . . . . . . . 20:18 POS attribute 5:4. 3:11 Perspective . . . 16:3 Plane editing . . . . . . . . . . . . . . . . . . . . 2:5 RECT (rectangle) element . . . . . . . . . . . . . . . . 12:44 PROJLINE CLEARANCE command . . . 9:1 Index page v 12. . . . . 16:3. . 12:32. . 12:12. . 5:3 PLMP (P-line style/colour) attribute . 12:32. . . . . . . . . . . . . . . . . . . . 5:3 SNAP command . . . . . 12:10. . 5:7 STEP command . . . . . . 13:23. 10:2 Revision element . . 13:8. . 3:18 Text Radius (DTRA) attribute . . . . . 18:30 Straight leader lines . . . . 13:27 Text Label Templates (TXTM) . 18:3. 2:2. . . . . . . . . . . . . . . . . 18:35 SPLA element . 9:3 ROTATE command . . . .0 . 12:41 Truncated dimension 12:12. . . . . . . . . 3:6 Special Label (SLAB) element 3:18. . . 20:11 TANLINE command . 18:32. . . . 15:2 Text Alignment (ALIG) attribute 12:26. . 5:7 STRA (straight line) element . . . . . . . . . . . . . . . . . . . . . . . 14:8 TABL (Table) element . . . 13:27 Text extent querying . . . . . . . . . . . . . . 5:11 Stepped Plane (SPLA) element . 2:5 Scale. 12:6. . . . . . . 13:31 Tag Rule (TAGR) element . . . . . . . . . 3:6 Sub-strings of intelligent text . . 12:25 Text Radius Flag (DTFL) attribute . . . . 12:32. 19:1 Symbol Templates (SYTM) . . . . . . . . . 18:33 Symbol templates ISODRAFT . . 18:31. . . . . . . . . . . . . . . 12:35. . 18:13 Rubber banding colour . 20:2 TRACE command . . . . . . . 3:11 THPT (Through Point) command 18:17. . 18:35 S SAVEWORK command . . . 3:28. . . . . . . . . 4:7 Index page vi 12. . . . 5:13. . . . . . . . . . . . . . . . . 4:7 SENSE attribute . . . . . . . . . . 18:33 Symbol libraries: . 3:17 SYTM (Symbolic Label Template) elements 13:1. . . selective allocation . . . . . . . . . . . . . . . . . . . . . . . . . 18:34 Text. . . . . . . . . . . . 10:3. . . 16:5 Selective styles . . . . . . 13:16. . . . . . . . . 18:34. 18:6. . . . . . . . . . . . . . . . . . . 12:43 TOLERANCE setting . 5:7. . . . 18:12. . . 18:35 T Tabbing within intelligent text . . . . 12:38. . . . . . . . . . . 18:18 TLIN (true length) attribute . . . . . . 13:10. . . . 3:18 Symbolic representation . . . . . . . 3:8 SKETCH command . 2:3 SYMB (Symbol Instance) element 18:3. . . . . . . . . . . . . .DRAFT User Guide Representation Rules Querying . . . . . . 10:4 Styles. . . . . . . . 3:10 SCALFG (Scaling Flag) element . . . . . . . . . . 12:37. . . 18:33. . . . . . . 18:3. . . . . 12:38. . . . . . . . . . . . . . 18:3. . . . . . 3:18 SMOD (Section Mode) attribute . . . . 12:12 TMRF (Template Reference) attribute 13:19. . . . . 4:11 Setting up . . 13:31 TANGENCY keyword . . 5:10. . 5:1. . . . . . 12:38 ROWSTYLE. . . . . . . . . . . . . . 18:39 SLAB (Special Label) element . . .12:3. 12:41. . . . . . 4:5. . . . . . 6:4 SORT DIMENSIONPOINTS command 12:7. 14:10 SWITCH command . . . . . 13:10 Style attributes use of to define representation style 4:2. . . . . . . 2:3 True length (TLIN) attribute 12:10. . . . 13:1. . . . 12:38. 18:30 Terminator size controlling . . . . . . . . . . . . 3:18 Scaling Flag (SCALFG) element . . . 3:1 Sheet Library (SHLB) element . . . 10:3 Representation Ruleset Reference (RRSF) attribute . . . . . 12:48 RPPT element . . . . 18:35 Text justification (JUST) attribute 13:8. . . . 20:12 TCOD (Type Code) attribute . . . . . . . . . . . . . . . . . . . . . 18:34 TAG command . . . . . . . 18:3. . . . 4:5. . . . . . 12:45 TXCOLOUR (Text Colour) attribute 13:9. . 12:45. . . . 12:32. 13:20. of view . . . . . 12:48 Rubber banding . . . . 17:3 SIZE attribute . . . ROWCOLOUR attribute 18:34 RPOI element . . . . . . . . . . . . . . . 4:8. . . . . . . . . . . . . . . . . . . . . . 12:25 Text colour:defining . . . . . 15:3 THPO (Through Point) VIEW attribute . . . . . . . 13:29 TEXP (Text Primitive) element . . 8:20. . . 8:20 Sheet (SHEE) element . 18:37 Rotation sense (SENSE) attribute . . . . . . . . 10:3 Representation Style (STYL) element 4:2. . . . . . . . . . . 3:12. . 19:1 Symbol Library (SYLB) element . editing . . . . . . 13:18 Tag Rule Library (TRLB) element . . . . . . . . . . . . . 18:35 Text alternative character set . . . 13:18 TAGGING MESSAGES command 13:22. . . . . . . . . . . . . . . . 8:20 Rules in defining ID Lists . . . . . . . . . . . . . . . . . . . 18:33 TO command . . . . . . . . . . . 18:34. . . . . 18:9. . 10:2 Representation Style assigning . . 13:18 Tag Ruleset (TRST) element . . . . . . . . . . . . 10:2. . . 18:3. . . . . . 12:43 SETFEEDBACK command . . . . . . . 18:14 TPT (To Point) command 18:18. . 18:27 Spatial map use of by ADD WITHIN command .12:21. . . . . . 5:8. . . . 12:41 SPAN command . 3:18 SCTN ends representation of . . . 4:7 VRAT attribute . . . . . . 18:5. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4 WigwamtoAutoCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12 limits . . . . . . . . . . . . . . . . . . . . . 3:25 UPDATE ANNO command . . . . . . . . . . . . . . . . . . . VSCA (View Scale) attribute . . . . . . 5:7. . . . . . . . . . . . . . . . . . . . . . . . . . . 14:14 UDA (User-defined attribute) codewords 14:19 Units Code (UCOD) attribute . . . . . . . . . . . . . 3:25. . . 3:10 querying . . . . 3:10 3:26 3:18 3:10 3:13 W Warning Messages . . . . . . . . . 5:9. . . . . . . . . . . . . . . . . 3:25 UPDATE INSTANCES command 2:3. . . Y filtering . . . . 3:8 gap length . . 3:12 View Scale (VSCA) attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:2 View Gap (VGAP) attribute . 13:14. . . . . . . . 3:19 Visibility of primitives . . . . . . . . . . . . . . . . . . . . . . . . 13:27 XYPS attribute . . . . . 3:6 orientation of on Sheet . . . . . . . . . . VTYP (View type) attribute . . . . 2:2 UPDATE NOWAIT command . . . . . 3:18 XYSCALE attribute . . . . . . . . . . . . . . . . . . . . . . . . . 18:6. . . . . . 3:9 XYSC (XY scaling) attribute . . . . . . . 3:12 UPDATE IGNORE command . 3:10 scale . . . . . . . 5:11 X X. . . . . . . . . . . . . . . . . . . . . 18:15 VNOT (View Note) element 18:3. . 3:19 VIEW element . . . . . . . . . 3:18 View Section (VSEC) element . . . 3:13 WPOS element .DRAFT User Guide TXTM (Text Label Template) element 13:1. . . 3:12 frame . . . . . . . . 2:2 UPDATE TAGGING command 13:19. . . . . . . . . 18:25 VGRID command . . 3:26 UPDATE REFRESH command . . . . . . . . . . . . . 18:33 Z Z-coordinates in DXF files . . . . 5:9 Views labelling . . . . . . . . 3:3. . . . . . . . . . . . . . . . . . 6:5 View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2. . 14:14 Universal representation . . . . . . . . 18:35 Index page vii 12. . . . . 3:16 UPDATE ALL command . . . . 13:23 U UCOD attribute . 3:25 UPDATE DESIGN command . . . . . . . . . 13:5 querying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VREGION command . 17:3. . . . . . . . 13:31 USE command . 18:12. . . . . . 7:5 V Vertex (VERT) element . . . . . . . . . . . 20:3 XY position (XYPS) attribute 13:5. . . . . . . . . . . . . . . . . . . . . . . . 3:25 UPDATE REFS command . . . . . . 7:5 Wireline views . . . . . . . . . . 3:8 type . . . . . . . . . . . . . . . . . 3:10 size . . . . . . . . . . . 5:3. . . . . . . . . . . . 3:25 UPDATE command . . . . . 13:21. . . . . . . . . . . . . . . . 3:25 UPDATE PICTURE command . 13:16. . . . . . . . . . . . . . . . . . . 3:17 centre . . . 3:9 direction . .0 . . . . . . . . . . . . . . . . . . . . . . . . 3:11 ratio . . . . . . . VSCALE attribute . 12:40 UPDATE BSHEETS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8. . . . . 3:13 View contents orientation . 18:33 UPDATE NAMES command . . . .