CadDraft - AER - Block Definition
CadDraft - AER - Block Definition
Manual
1. INTRODUCTION
This Document is all about block definition. Based on the CadDraft standard. Since Autocad is a
Handy Drawing toolbox which provided functionality to create drawings. However AutoCAD also
provide functionality which is difficult in use (not known to every draftsman) and a attack on a
proper maintenance off drawing standards (if now-a-days any known to draftsman).
CadDraft is using a very strict set-up of (own) standard to ensure / guarantee the standar and
easy detection of disruption by others.
A correct definition guarantees the proper use of VCM and the option to Automate specific func-
tionality, such as export of drawing included information as base for further use and/or quality
control purposes.
The definition of block can work much into our benefit and the overall quality of the end product,
the drawing.
A uniform setup of these Symbols provide also opportunities to convert these into other definitions
, purpose or client required .
Blocks can also be used in assemblies, where a combination of symbols and other drawing enti-
ties can be defined as a block, by exploding this block (VCM) during insert, the original blocks
Explanation of Notes
If you don’t want to put your life at risk:
NEVER EVER
do what is indicated here.
2. GENERAL
Blocks can be defined in multiple way’s. As were in real life many definition are less than perfect.
The way we use to define Blocks is maybe also not perfect, but it’s standardized, to be as flexible
as possible and allow other use of the blocks.
AutoCAD specific:
A. Assign each entity to it dedicated layer
When an entity is placed in a specific layer (which entity becomes part of a block) the en-
tity will stay related to this layer once this entity becomes part of block.
However a block conform the first definition (each entity in their own dedicated layer) can be con-
verted into a block as defined as all entities into layer 0, while attributes (editable text) can remain
into their own specific layer or are also converted to be part of layer 0. This is possible when de-
fined separate, once ALL entities become part of layer 0 (or is defined as such) there is no way to
separate the entities into their dedicated layer.
Should however, the conversion be non-required, then a reload of the external blocks enable the
option to roll-back the conversion either complete or partial, pending on possibilities..
This definition also enables a (LISP based) quality check routine, where the entity colours are
temporary altered to check for exploded blocks, which are NOT allowed.
While drawing internal line colours are mainly used to define / present the linewidth of the final
result on paper.
Exception Example(s)
Construction:
When a drawing contains pipes which represent a different function, such as a supply line and a
return line Where supply line often is red (hot) and the return line is blue (cold or lees hot )
Schematical:
When a drawing, such as an cable layout (cables not on actual size) contains cables carrying a
different voltage (Such as High - & low voltage).
NOTE Both types of drawings need to include a legend, explaining the use of the colours.
4. TYPE OF ENTITIES
Roughly there are 4 types of entities. All these entities are compiled into an drawing. As where
each entity type has his unique character. The use of the correct entity type might improve not
only the quality of the drawing, but also the creation speed.
4.2 Text
A specific type of entity to produce text in the drawing. Case CadDraft restricted to the ISO font.
These font is used in standard predefined letter heights. Both as Standard and Annotative , where
the annotative font definition is mainly used for construction drawings, where scale is part of a
correct presentation of the drawing.
The ISO font is used since this is standard and ensures a cleary different presentation for each
character, while other fonts might present different character almost equal and NO other font is
needed to produce a correct drawing.
The use of Mtext is very restricted, only as addition to the drawing outline to include extra func-
tionality such plot date & time and the filename.
The reason for this restriction is the option to include text formatting in the text, which is unwanted
and might result is difficulties both in use and results on a later date.
The only other use of Mtext is to produce a large amount of text as part of the drawing, based on
the ISO font definitions and without the use of text formatting.
Attributes:
Still a specific type of text, special available to be part of a predefined block, while the text remain
editable, WHILE THE BLOCK ISN’T exploded.
Never use an Exotic font other than the predefined ISO font whit corresponding letter
heights.
The use of exotic fonts often comes with additional problems, such as readability
and/or the difficulty to maintain the font (if the Fontfile is non-standard Autocad Font-
file).
4.3 Dimensions
Adaptive Dimensions are mostly used as part of construction drawings will be based on an Anno-
tative text style definition, since this allows the correct presentation in multiple viewports (different
scale) without the adaption within the drawing model space.
The Dimension scale is predefined based on a ISO font-type with a letter height of 2,5mm. A dif-
ferent fontsize is a rare exception and therefore not defined.
The use of non-adaptive Dimensions can be considered as being part of non-constructional draw-
ing, such as schematics (such as Isometric drawings), were the dimension itself is not defined by
picking the distance but is a manual input. This type of drawing is also not related to scale and a
standard (non Annotative) font definition is used.
4.4 Blocks
Autocad allows the definition of two block types:
A normal block, which can be part of the drawing and also maintain outside of the drawing. This
type is and stays the way it is defined.
Dynamic blocks, however fancy, this of block shouldn’t be used to maintain a high rate of inter-
changeability (modification by other AutoCAD look-a-like CAD programs).
Since the use of block – attributes is unknown to many (based on the time blocks are
still exploded to modify the text) the use of dynamic block is strictly prohibited.
In very many cases this type of block doesn’t add any value to the drawing only diffi-
culties, maintaining a correct standard.
Units
Not and entity, but a variable which defines how entities act, special during insertion (of blocks).
The best units are used related to the final content of the drawing, where millimetres are the most
frequently used units scale (by far the most of construction drawings).
For schematical drawings also the units millimetres can be used (or no units definition). Working
always in these unit type may avoid funny acting during insertion since some Autocad variables
has impact on the way a block is inserted.
6. LAYERS
ALL entities drawn COLOR BY LAYER
7. BLOCK DEFINITION
Blocks are defined on a grid with an interval of 5mm. This way, during the creation of the actual
drawing a grid of 5mm also can be used. This will result in a clear drawing where lines are drawn
on a regular interval (of 5mm minimal).
Symbols are often placed on top of a line, a simple wipeout beneath the symbol content
(draworder) can avoid a lot of work, breaking lines or other content. This wipeout will follow the
outline of the symbol, s is often drawn at last, while moved to its correct position using
“draworder”. Wipeouts will be drawn on the layer “WIPEOUTS” this enables the option to disable
the use of wipeouts (freeze laer “WIPEOUTS”, Note however that than needs to be adjusted to
incorporate symbols (blocks).
A bug in Autocad, sometimes reorder wipeouts and then wipeouts are re-positioned
on top, so hiding the block/symbols. A LISP routine (VCM) solves this Autocad Bug.
VCM LDOrderV1-2.lsp part of VCM will solve this Autocad Bug. Blocks can be moved to
top.
Likewise DrawOrderOnTopPerLayer.lsp
Normal entities like lines and so on, will be drawn on a layer “ENTxxx” where xxx is correspond-
ing with the penwidth.
7.1 Entities
(see 4.1 Lines, circles and other components)
While ALL entities are defined “COLOR BY LAYER”, entities part of a block need to be defined in
different layers than all other entities
To create the upmost flexibility of the use of blocks, three layers are used to define entities in a
multipurpose blocks.
BLKTHICK The outline of a block (used as symbol). When a clear outline is existing.
BLKNORM Normal content of the block (inside the symbol)
BLKTHIN Entities such as divider lines
All type of text are defined in a layer TXTxxx where xxx is pen width / font height related, either for
normal or annotative type of text. While the only Font type used is based on the ISOCPEUR font.
Attributes (variable text inside a block) and fix text are defined on their corresponding layer, main-
ly layer TXT025 and TXT018, where TXT025 is the preferred layer and textsize. The fontstyle
ISO025 (defined based on ISOCPEUR with a text height of 2,5mm) to be used for Attributes and
text definitions. Likewise TXT018.
7.2.1 ATTRIBUTES
Defining an Attribute comes with at least two
issues You need to take care for:
Uncheck the Lock_Position, rarely the posi-
tion of an attributes remain unchanged.
When the lok_position is checked you are not
able to move the attribute (text) of an already
inserted block. Better avoid this issue.
TAG General prefix, followed by an underscore and an ID to define the correct use.
TAG_EQUIP
TAG_LINE
TAG_INST
TAG_ELEC
The prefix TAG_, makes an overall selection (TAG_*) possible.
Tag Devided over two rows e.g.
TAG_LETT
TAG_NUMB
An Invisible TAG (Constant) can help to solve this issue. Once the information of the Attributes is
extracted, the value included in the invisible TAG can provide clarity. This way a drawing related
Equipment list and Line list can be presented e.g. used for checking.
7.2.2 TEXT
Text is rarely used inside blocks, since a change is not possible. Much better is the use of a AT-
TRIBUTE with a default value. A change of the text is then possible, should this occur.
While blocks defined for a specific purpose use the entity related layers (such as ENTxxx and
TXTxxx, where xxx is penwidth related).
Attributes
VCM ChangeLayerNameInBlock.lsp will allow the change of layer names inside blocks en-
abling the option to use the blocks multi-purpose, both as defined as will related to a
specific use (color by layer)
Next command
Wipeout Polyline previous created polyline <pick> Yes
The last ‘Yes’ to erase the polyline used for creation of the wipeou, so only the wipe-
out remains.
Note: this wipeout is best created in the layer ‘Wipeout’
Autocad bug:
The way a wipeout is handled in Autocad isn’t always perfect. Sometimes the wipeout
is moved to the background (not on top) however this can be solved with a lisp routine
which moves all the symbols to the end of the database, so they will be drawn on top
of all other entities.
Work around (worst case)
Case all wipeouts are defined in layer ‘WipeOut” they can be excluded from use
(freeze layer). This case reordening of the symbols don’t provide the suitable solution.
Where:
The actual core symbol contains the Attributes (easy for extrac-
tion purposes)
Insertion also hide entities in the background, so lines don’t
need to be interrupted and moving the symbol will automatically
correct the ‘line-break’
If for instance the symbols need to be layer color depended this
can be solved easily with a lisp routine. But is mainly installation
based.
More easy to maintain the symbol library
In above example the core block is used together with maximum 2 additional blocks.
The lisp routine provide the option to use 4 additional blocks, think about the combinations possi-
ble
8. ATTRIBUTE DEFINITION
EACH and EVERY BLOCK DEFINED will at least contain 1 Attribute starting with the prefix
‘TAG’, as where a suffix will define the Discipline to which the TAG is related to.
Exception of this rule are block which are no physical part of the drawing content, such as the
Drawing tile block and Drawing Revision Block.
ALL ATTRIBUTES ARE DEFINED IN UPPER CASE TEXT (prompt might contain a different Text
Case).
Process. While mainly the owner of the TAG, this suffix is rarely use, since all TAGs are related
to other disciplines. Already TAGs are defined in the P&ID (Process & Instrumentation Diagram)
but NON of these equipment’s are MAINTAINED by the Process department / discipline. TAG
however are assigned to the discipline which will define and Maintain this piece of equipment.
Suffix Description
_PROC Process. mainly the owner of the TAGS, but not the discipline which maintains
this Equipment.
_CIVIL Civil
_MECH Mechanical
_CNTR Control (E&I) Electrical & Instrumentation, but instrumentation isn’t always
Electrical (Pneumatic and/or hydraulic), Control is therefore more suitable.
8.1.1 Specials
Special TAG definitions are defined to include the purpose and to make a more detailed extrac-
tion possible or in other cases to Extract values related to entities which are not based on blocks.
In many cases these TAGs are assigned to a Block which defines a row in a list or is assigned to
an Entity, such as a line (CABLE, PIPE, TANK) or a number of blocks defining the final drawing
component such as a Distillation Column.
While initial these TAGs belongs to a Discipline, a more detailed extraction requires a more de-
tailed Attribute name. The Attribute Name than is defined:
TAG_’Discipline’_’Catagory’(_’SubDiscipline’) (_’SubCatagory’),, where:
TAG Is the fixed prefix for a TAG
TAG_LETT Case the TAG is based on 2 attributes (Letter part)
TAG_NUMB Case the TAG is based on 2 attributes (Number part)
‘Discipline’ Is the ‘Standard’ discipline abbreviation
‘Catagory’ Is the Name to define a specific Category of TAGs
_’SubDiscipline’ When the specific Owner is a Sub discipline (often the case)
_’SubCatagory’ When the specific Category has a Sub Category / Task
During attribute extraction so called wildcards (such as ‘*’) can be used to extract TAG related to
as Specific Category which might spam multiple disciplines (Like E&I CABLES).
Case CABLEs, often maintained by E&I (Electrical & Instrumentation) which is already a combi-
nation between disciplines)
To extract Attributes ONLY related
Suffix Description
Process. While mainly the owner of the TAG, this suffix is rarely use, since
all TAGs are related to other disciplines. Already TAGs are defined in the
P&ID (Process & Instrumentation Diagram) but NON of these equipment’s
are MAINTAINED by the Process department / discipline.
CadDraft - AER - Block Definition.docx Page 14 of 19 2020-10-19 | 4:33 PM
TECHNICAL DRAWINGS
CadDraft - AER - Block Definition
_CNTR_CABLE_x
Which can be part of the Attribute Extraction and later to Group Specific TAGs.
Based on this information the Manufacturer & Manufacturer Modelpart can be selected.
This Attribute isn’t displayed (invisible – Constant) since the final selected component is used in
the part-list.
Examples:
INSTRUMENTATION
Type = ‘Coupler”
MECHANICAL
Type = Tank
Type = Centrifugal Pomp
The attribute ‘HANDLE’ is available on those blocks which are entity related, such Lines (pipe)
and Cables. Or other entities which are an assembly of multiple blocks to define the final symbol
such as ‘Distillation Columns’.
This Attribute will be handled by VCM and is filled with the related entity identifier.
When the original related entity is removed, and the relation with this entity (included in the relat-
ed block) is lost
VCM include functionality to check this relations and correct / re-assign related block to the cor-
rect HANDLE.
Prefered therefor is to draw a line (pipe or cable as a Pline entity. Which has the following bene-
fits.
9. BLOCK USE
Blocks are inserted in the drawing, using VCM.
Blocks are inserted in the drawing in the layer “Blocks” or for a printable colour a special as-
signed layer. Conversion (block internal to layer 0 (zero)) of the block inserted to the special as-
signed layer will adapt the block colour to the colour used for this layer.
VCM VCM will make the insertion on the correct Layer easy. However Standard AutoCAD
functionality will be helpful also (e.g. correcting mistakes.
VCM
NOTE
In principe