Electrical Design Software | Elecdes Design Suite by Scada Systems Ltd

Component Naming

Tagnames

Elecdes assumes that any symbols with the same name and location represent the same physical object.

For the purposes of reporting, the name of a device is TAGNAME and the location is PNLNO.

Similarly:

  • WIRENAME is the name of a wire.

  • CABLENAME and CORENAME combined form the name of a cable core (conductor) .

  • TBLOCK and T1 combined form the name of a terminal. The location is PNLNO.

TAGSUFX and TERMPRFX

The TAGSUFX and TERMPRFX attributes enable you to use simpler names for components and their terminals on schematic drawings without losing the ability to uniquely identify those specific components and their terminals in cross references, reports and wiring diagrams.

TAGSUFX

TAGSUFX enables you to specifically label each use of a particular modular component but keep that label separate from the TAGNAME on the schematic.

When using TAGSUFX, the TAGNAME will contain just the main component name on the schematic but in reports and other places the component name will have the TAGNAME with the TAGSUFX added to the end. On the schematic the two parts of the name are in separate attributes so you can choose separately whether you will show or hide each attribute and, if both are shown, you can put each attribute in a different place around the symbol.

Prior to TAGSUFX it was not possible in Elecdes to distinguish between two identical modular components if they were named identically. If each module were given a unique name, the modules would be unrelated to the main component.

Modular components with a TAGSUFX will be treated as entirely separate components for wiring diagrams - i.e. separate entry in the WD device list and placed individually. They are also treated as separate components for cross-reference - i.e. have their own cross-reference list or table header and entries.

The TAGSUFX attribute can be added to schematic device symbols (HI* and VI*), the MTD tag block (HIMTDT* or VIMTDT*) and the MTD terminal symbols (HTTERMP* and VTTERMP*). In an MTD symbol the terminals and the MTD tag block of that symbol should all have the same TAGSUFX value. It is not correct to mix TAGSUFX values in the terminals of one MTD symbol as one MTD symbol can represent only one component.

A TAGSUFX attribute should not be added to cross-reference header blocks (RHEAD*) or the wiring diagram tag block (WDTAG*). In these blocks the TAGNAME and TAGSUFX value are combined in the TAGNAME attribute.

TAGSUFX can contain letters, numbers or both.

Since the TAGSUFX is used to label each use of a modular component, it should be entered when the symbol is inserted. TAGSUFX should not be specified in the catalog or pre-set in the attributes of the symbols.

e.g.  A relay named K13 has two modular contact blocks each containing one normally open contact. The two modular contact blocks will be given the TAGSUFX values C1 and C2. On the schematic drawing of the first modular contact block you can choose to show or hide separately the TAGNAME of K13 and the TAGSUFX of C1.
The cross-reference header and wiring diagram for the first modular contact block must have the combined name, K13C1. The name of the first modular contact block in the reports will show the combined name, K13C1.

TERMPRFX

TERMPRFX is applied to groups of terminals of one component when that component has separate blocks of terminals that repeat the same terminal numbering as each other.

When using TERMPRFX the terminal attributes will contain just the terminal number and the TERMPRFX will contain just the block number on the schematic but in reports and other places the terminals will have the TERMPRFX and the terminal number combined into one value for each terminal.

Prior to TERMPRFX each terminal number attribute would have to be unique throughout the whole device so each terminal would need the block prefix specified in the terminal number attribute.

The TERMPRFX attribute can be added to schematic device symbols (HI* and VI*) and MTD terminal symbols (HTTERMP* and VTTERMP*). One MTD symbol can contain terminals from more than one block of terminals because each terminal can specify its own TERMPRFX value. If an MTD symbol will contain terminals from only one terminal block then the TERMPRFX attribute can also be used in the MTD tag block (HIMTDT* or VIMTDT*) which makes the symbol easier to identify in the Navigate function. One standard device symbol can contain terminals from only one terminal block because each standard device symbol has only one TERMPRFX attribute.

A TERMPRFX attribute should not be added to cross-reference header blocks (RHEAD*) or the wiring diagram tag or terminal blocks (WDTAG*, WDLT* and WDRT*). In these blocks the TERMPRFX value and terminal number are combined in the terminal number attribute.

TERMPRFX can contain letters, numbers or both.

When TERMPRFX is used to differentiate blocks of terminals that are part of the standard manufactured configuration of a device, the TERMPRFX value can and should be specified in the catalog entries for the device, or pre-set in the attributes of the terminals in MTD symbols for the device.

e.g. Consider a device with three blocks (labelled A, B and C) of terminals each containing terminals 1-10. Without TERMPRFX you would need to put A1-A10, B1-B10 and C1-C10 into the terminal attributes of the device symbols. With TERMPRFX you can have the just the terminal numbers (1-10) in the terminal attributes on the schematic and the block letter (A, B or C) shown in a separate TERMPRFX attribute. You can choose the show or hide the TERMPRFX attribute as required.
The terminal numbers are therefore shorter and the schematic drawing is less cluttered.
In the reports and other places the TERMPRFX will be added to the start of the terminal numbers as if they had always been entered as A1-A10, B1-B10 and C1-C10.

See also

Conductor Naming and Continuation