Electrical Engineering

Rights and license
Electrical Engineering ___________________

management 1
Devices (Base objects) for
___________________
EE 2
___________________
Standard tables for EE 3
Comos
___________________
Interactive report templates 4
Comos
Electrical Engineering ___________________
Evaluating report templates 5
___________________
Connections 6
Operating Manual
___________________
Working with reports 7
Object connections
___________________
(connectors) 8
Evaluation (order lists /
___________________
materials lists / parts lists) 9
___________________
Miscellaneous 10
___________________
Tools for E&IC (EMR) 11
___________________
Request and Implementation 12
Product data and
___________________
manufacturer devices 13
___________________
EPLAN (Import/Export EXF) 14
04/2009
HB120_90E05
Legal information
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the corresponding information is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation for the specific task, in particular its warning notices and
safety instructions. Qualified personnel are those who, based on their training and experience, are capable of
identifying risks and avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be adhered to. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this
publication may be trademarks whose use by third parties for their own purposes could violate the rights of the
owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Siemens AG order number: HB120_90E05 Copyright © Siemens AG 2009.

Industry Sector Ⓟ 09/2010 Technical data subject to change
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 Rights and license management................................................................................................................ 9

2 Devices (Base objects) for EE ................................................................................................................. 11
2.1 Script ............................................................................................................................................11
2.2 EE| D Device view (DIN 40719)...................................................................................................12
2.2.1 DIN labels.....................................................................................................................................12
2.2.2 Symbols .......................................................................................................................................13
2.2.3 Connectors and auxiliary connectors...........................................................................................15
2.2.4 Attributes and calculated attributes..............................................................................................15
2.2.5 Request properties.......................................................................................................................15
2.2.6 Product data.................................................................................................................................16
2.2.7 Device labelling ............................................................................................................................16
2.2.8 EE| D| I Potential..........................................................................................................................16
2.2.8.1 EE| D| I| A Potential .....................................................................................................................16
2.2.8.2 Predetermining potentials in the base data .................................................................................18
2.2.8.3 Potential chains / Master-Slave potentials / Potential references................................................19
2.2.8.4 Potentials with report object.........................................................................................................20
2.2.8.5 EE |D |I |B Potential rails..............................................................................................................20
2.2.8.6 EE |D |I |C Potential bundles........................................................................................................21
2.2.9 EE| D| K K Relays, coils...............................................................................................................22
2.2.10 EE |D |O O Other base objects....................................................................................................23
2.2.10.1 A O Blackboxes, segments..........................................................................................................23
2.2.10.2 A O |01 O Blackbox, automatic contact points ............................................................................23
2.2.10.3 A O |02 O Blackbox, Comos device.............................................................................................25
2.2.10.4 A O | 11 segment .........................................................................................................................25
2.2.10.5 A O |12 O Sheet areas I&C..........................................................................................................28
2.2.11 EE| D| W Cables ..........................................................................................................................28
2.2.11.1 Aim ...............................................................................................................................................28
2.2.11.2 Control of the extended capabilities.............................................................................................28
2.2.11.3 Attributes ......................................................................................................................................29
2.2.11.4 Symbols for cables.......................................................................................................................31
2.2.11.5 Complete cable ............................................................................................................................32
2.2.11.6 Placing the cable on the report ....................................................................................................32
2.2.11.7 Shield ...........................................................................................................................................33
2.2.11.8 Other objects (wire, shield, stranding) .........................................................................................34
2.2.11.9 Supporting documents .................................................................................................................34
2.2.11.10 Pre-allocating wires to connectors..........................................................................................35
2.2.12 EE| D| X X Terminal - / plug strips ...............................................................................................35
2.2.12.1 Aim ...............................................................................................................................................35
2.2.12.2 Control of the extended capabilities.............................................................................................35
2.2.12.3 Terminal strips..............................................................................................................................36
2.2.12.4 Terminals .....................................................................................................................................36
2.2.12.5 Bridges .........................................................................................................................................37
2.2.12.6 Supporting reports .......................................................................................................................37
2.2.12.7 Plug strips ....................................................................................................................................38
2.3 EE| E Elements ............................................................................................................................39
2.3.1 J auxiliary contacts.......................................................................................................................39
2.3.2 W Wires, color codes ...................................................................................................................39
Electrical Engineering
Operating Manual, 04/2009, HB120_90E05 3
Table of contents
2.3.3 X Terminals, plugs ...................................................................................................................... 39

2.4 F Component view (IEC 61346).................................................................................................. 39
2.5 G Document groups |@NameSystem Structure ......................................................................... 39
2.6 J Project |@E Project defaults EE .............................................................................................. 40
2.7 L Locations |E Location structure EE.......................................................................................... 40
2.8 O Documents | EE Electrical engineering................................................................................... 40
2.9 U Units......................................................................................................................................... 41
2.10 Z Symbol structure ...................................................................................................................... 41
2.11 eClass 4.0 ................................................................................................................................... 41
3 Standard tables for EE............................................................................................................................. 43
3.1 Systemology................................................................................................................................ 43
3.2 0 System tables........................................................................................................................... 44
3.2.1 Import assignment of attributes................................................................................................... 44
3.2.2 1 Modules.................................................................................................................................... 44
3.2.2.1 Luetze Manufacturer node .......................................................................................................... 44
3.2.3 G Document groups .................................................................................................................... 45
3.2.3.1 DynNum Dynamic numbering ..................................................................................................... 45
3.2.3.2 RefDocSortMode Reference name............................................................................................. 45
3.2.4 O Documents .............................................................................................................................. 45
3.2.4.1 PMA Connector-, Connection list................................................................................................ 46
3.2.4.2 PPB Parts, label list..................................................................................................................... 46
3.2.4.3 PPC Parts list .............................................................................................................................. 46
3.2.5 Y Attribute catalog....................................................................................................................... 46
3.2.5.1 02 Construction ........................................................................................................................... 46
3.2.5.2 2 Tab collection ........................................................................................................................... 47
3.2.5.3 3 3D section ................................................................................................................................ 47
3.2.5.4 D Devices .................................................................................................................................... 47
3.2.6 Base project: @IRF_xxx.............................................................................................................. 48
3.2.7 Base project @System................................................................................................................ 48
3.2.7.1 Base project: @System |@Bridge symbols ................................................................................ 48
3.2.7.2 Base project: @System |@Class | Detail.................................................................................... 49
3.2.7.3 Base project @System |@Connection........................................................................................ 49
3.2.8 System project @ConnectionType E .......................................................................................... 50
3.2.9 System project @System............................................................................................................ 50
3.2.9.1 System project @System |@BridgeType.................................................................................... 50
3.2.9.2 System project @System |@ELO_KSP...................................................................................... 50
3.2.9.3 System project @System |@WireColor ...................................................................................... 50
3.2.9.4 System project @System |@WireCrossSection ......................................................................... 50
3.2.9.5 System project @System |@WireTypeInfo................................................................................. 50
4 Interactive report templates ..................................................................................................................... 51
4.1 Circuit diagrams .......................................................................................................................... 51
4.1.1 Attributes ..................................................................................................................................... 51
4.1.2 Options for EE reports................................................................................................................. 51
4.2 Layout diagrams.......................................................................................................................... 53
5 Evaluating report templates ..................................................................................................................... 55
5.1 PMA Connection schematics ...................................................................................................... 55
4 Operating Manual, 04/2009, HB120_90E05
Table of contents
5.2 PPB part -, label lists....................................................................................................................55

5.3 PQA Check -, test reports ............................................................................................................55
5.4 PPC Parts list ...............................................................................................................................56
6 Connections............................................................................................................................................. 57
6.1 Graphical connections .................................................................................................................57
6.2 Preparing connections .................................................................................................................57
6.3 Creating connections ...................................................................................................................57
6.4 Defining graphical properties .......................................................................................................58
6.5 Parallel connections.....................................................................................................................59
6.6 Open connections ........................................................................................................................60
6.7 Wiring direction ............................................................................................................................61
6.8 Displaying the connection direction .............................................................................................64
6.9 Connection / wiring for terminal bridges ......................................................................................65
6.10 Document cross-references.........................................................................................................66
6.11 Reconciliation of database and report connections .....................................................................69
6.12 Connection dependent objects ....................................................................................................71
6.13 Borders of the "connection dependent objects" technique ..........................................................72
6.14 Connection information ................................................................................................................75
6.14.1 Bridges .........................................................................................................................................75
6.14.2 Potentials .....................................................................................................................................75
6.15 Cables and wires / wire information without wires .......................................................................75
6.15.1 Cables and wires / wire information without wires .......................................................................75
6.15.2 Shielded cables............................................................................................................................76
6.15.3 Combining cables in cable channels / routes ..............................................................................78
6.16 Direct connecting .........................................................................................................................79
7 Working with reports ................................................................................................................................ 81
7.1 Special points concerning circuit diagrams..................................................................................81
7.1.1 Superimposing and hiding information ........................................................................................81
7.1.2 Placing devices ............................................................................................................................82
7.1.3 Revising and controlling devices..................................................................................................83
7.1.4 Setting pointers in the report / allocating information...................................................................84
7.2 Special points regarding layout diagrams....................................................................................84
7.3 Special points regarding single line diagrams .............................................................................84
7.3.1 Report template ...........................................................................................................................84
7.3.2 Allocating ELO connectors and single line connectors................................................................84
8 Object connections (connectors) ............................................................................................................. 85
8.1 Definition of connection................................................................................................................85
8.2 Setting connections in the Navigator ...........................................................................................85
8.3 Working with the Connectors tab and the Navigator ...................................................................86
8.4 Working with two properties windows..........................................................................................87
Table of contents
8.5 Working with the "Connect device" dialog window ..................................................................... 87

8.6 Connection information for connectors: Dialog window "Characteristics for connections"......... 88
8.7 Preallocating connectors with logical potentials ......................................................................... 89
8.8 The Strip tab................................................................................................................................ 89
8.9 Terminals and terminal strips ...................................................................................................... 90
8.10 Bridges ........................................................................................................................................ 90
8.11 Product data and manufacturer devices ..................................................................................... 91
8.12 Other auxiliary tools .................................................................................................................... 92
8.12.1 Change per rule:name, label....................................................................................................... 92
9 Evaluation (order lists / materials lists / parts lists)................................................................................... 93
9.1 General........................................................................................................................................ 93
9.2 The Settings tab .......................................................................................................................... 93
9.3 Materials lists .............................................................................................................................. 94
9.4 Order lists .................................................................................................................................... 94
9.5 Parts lists..................................................................................................................................... 94
10 Miscellaneous .......................................................................................................................................... 95
10.1 Translation / language management .......................................................................................... 95
10.2 Rights and license management................................................................................................. 95
11 Tools for E&IC (EMR) .............................................................................................................................. 97
11.1 Ruplan ......................................................................................................................................... 97
11.1.1 Base objects and configuration................................................................................................... 97
11.1.2 Options and interface .................................................................................................................. 97
11.1.2.1 Open the Ruplan import .............................................................................................................. 97
11.1.2.2 Structure of the Ruplan import window ....................................................................................... 97
11.1.2.3 The "Ruplan data" area............................................................................................................... 98
11.1.2.4 The "Comos data" area............................................................................................................. 100
11.1.2.5 Import ........................................................................................................................................ 100
11.1.2.6 Conversions .............................................................................................................................. 101
11.1.2.7 Ruplan configurator................................................................................................................... 101
11.2 ECAD components import......................................................................................................... 103
11.3 Conversion IEC to JIC............................................................................................................... 105
11.4 Modification of Name / Label..................................................................................................... 107
11.5 Change per rule: Name / Label................................................................................................. 107
12 Request and Implementation ................................................................................................................. 109
12.1 Request ..................................................................................................................................... 109
12.2 Implementation.......................................................................................................................... 110
12.2.1 Implementation phase (order preparation)................................................................................ 110
12.2.2 The Implement request dialog window ..................................................................................... 111
12.2.2.1 Icon bar (Window control) ......................................................................................................... 111
12.2.3 List area..................................................................................................................................... 112
12.2.3.1 Superimposing additional columns ........................................................................................... 112
12.2.3.2 New column (programming the special column)....................................................................... 113
Table of contents
12.2.3.3 Sorting the list area ....................................................................................................................114

12.2.3.4 Filtering list area.........................................................................................................................115
12.2.3.5 Schemes for the list window (ScanDevices)..............................................................................116
12.2.3.6 Attributes in dependency of a line reference object...................................................................118
12.2.3.7 Attributes in dependency of the line and column object ............................................................119
12.2.3.8 Other icons and fields ................................................................................................................120
12.2.4 Replacing or retaining a request ................................................................................................121
12.2.4.1 Project option "Implement request replaces objects" ................................................................121
12.2.4.2 Setting the implementation pointer ............................................................................................122
12.2.4.3 Base object change ...................................................................................................................123
12.2.5 Releasing device requests.........................................................................................................123
12.3 Report PQA................................................................................................................................123
13 Product data and manufacturer devices ................................................................................................ 125
13.1 Definition and area of application ..............................................................................................125
13.2 Function right product data ........................................................................................................126
13.3 Preparing requests.....................................................................................................................127
13.3.1 Preparing request base objects .................................................................................................127
13.3.2 Preparing attributes....................................................................................................................127
13.3.3 Controlling the display of product relevant attributes.................................................................128
13.4 Importing manufacturer devices.................................................................................................129
13.5 Planning work (input product data) ............................................................................................130
13.6 Selecting a manufacturer device................................................................................................131
13.6.1 Creating manufacturer devices by feedback .............................................................................131
13.6.1.1 Feedback for an individual engineering object ..........................................................................131
13.6.1.2 Feedback for a engineering branch ...........................................................................................132
13.6.1.3 Automatically creating structure branches for manufacturer details..........................................132
13.7 Manufacturer device selection ...................................................................................................133
13.7.1 Configuring the manufacturer device selection..........................................................................134
13.7.1.1 Configuration options for the manufacturer device selection.....................................................134
13.7.1.2 Defining a local path for the manufacturer device selection ......................................................134
13.7.2 Allocating device requests to manufacturer devices..................................................................136
13.7.2.1 Allocating a single device request to a manufacturer device.....................................................136
13.7.2.2 Design of the manufacturer device selection.............................................................................137
13.7.2.3 Column and control elements of the manufacturer device selection. ........................................137
13.7.2.4 Allocating multiple device requests to manufacturer devices ....................................................138
13.7.2.5 Columns and control elements of the device selection (product data) window.........................140
13.7.2.6 Deviations from the manufacturer device templates (orange background)...............................141
13.8 Output product data ...................................................................................................................141
14 EPLAN (Import/Export EXF) .................................................................................................................. 143
14.1 Background information .............................................................................................................143
14.1.1 EPLAN structures in comparison with Comos structures ..........................................................143
14.1.2 EPLAN pages compared to Comos reports...............................................................................145
14.1.3 Overview of an export of Comos data to EPLAN.......................................................................148
14.2 Preparing a Comos engineering project ....................................................................................149
14.3 Importing EPLAN data (EPLAN -> Comos) ...............................................................................152
14.3.1 Importing EPLAN article base data to Comos ...........................................................................152
14.3.2 Importing EPLAN symbols to Comos ........................................................................................153
14.3.3 Importing plot frames .................................................................................................................158
Table of contents
14.3.4 Importing forms ......................................................................................................................... 159

14.3.5 Importing project data ............................................................................................................... 160
14.3.5.1 Exporting projects from EPLAN ................................................................................................ 160
14.3.5.2 General import details ............................................................................................................... 161
14.3.5.3 The EXF import tab ................................................................................................................... 161
14.3.5.4 The import process ................................................................................................................... 162
14.3.5.5 Converting individual objects .................................................................................................... 163
14.4 Working in Comos with (imported) EXF data............................................................................ 165
14.4.1 Prepared labelling systems and objects ................................................................................... 165
14.4.2 Prepared objects in the categories ........................................................................................... 166
14.4.2.1 Documents category ................................................................................................................. 166
14.4.2.2 Terminal strips category............................................................................................................ 166
14.4.2.3 Control category........................................................................................................................ 167
14.4.2.4 Cables category ........................................................................................................................ 167
14.4.2.5 Devices category....................................................................................................................... 168
14.4.3 Cross-references....................................................................................................................... 168
14.5 Exporting from Comos (Comos -> ExF).................................................................................... 168
14.5.1 Exporting from Comos (Comos -> ExF).................................................................................... 168
14.5.2 The EXF export tab ................................................................................................................... 169
14.5.3 The Export symbols tab ............................................................................................................ 169
Rights and license management 1
The EE module requires an EE/I&C license. The EE/I&C license is used when:
1. Basic operations are carried out with ELO connectors (connect, disconnect, edit wires or
potentials)
2. connectors get signals or process the signals of the connectors
3. one of the actions 1. or 2. is carried out in the properties window of engineering objects
(device)
4. an interactive report is opened with write access (as before)
5. the "Marshaling Manager" or "Implement requirements" are opened
Note
"Signal tracking" is a read-only method and does not require an EE/I&C license.
For completeness, we want to remind you of the method concerning the license query:
licenses are drawn from the floating license for each work session. If Comos is opened
several times on a workstation, then several licenses will also be drawn, depending on the
involved action.
For reports there is the | Open Read Only command to prevent a license from being drawn.
Rights and license management
Devices (Base objects) for EE 2
All devices related to electrical engineering are grouped together in branch ET I&C, Electrical
engineering
All devices grouped in this branch have certain basic properties and are structured according
to the standards DIN 40719 and IEC 61346 as described in Volume 120, section EE| D
Device view (DIN 40719) (Page 12) and in Volume 120, section F Component view (IEC
61346) (Page 39).
In addition, there are objects that offer additional properties and capabilities. These special
devices are explained in detail individually in the following sections.
2.1 Script
Automatic implementation
A function for automatic implementation is available in the script:
Workset.Lib.Elo.AutoImplementation Node, Device
Example:
EE | 3 Structures I&C | 02 Signal | 01 Channels | 01 Measurement recording
channel| E1 Sensor (Element)
"Script" tab, script block OnReferencedByDevice.
The automatic implementation sets a flag at the element of the device. If the preconditions
for "Automatic implementation" are again given, it is nonetheless not executed due to the
marking.
Background: the function, Volume 30, section 14.1.43: RestoreRequest (Request) otherwise
led to all restored requests being implemented at once again.
Devices (Base objects) for EE
2.2 EE| D Device view (DIN 40719)
2.2.1 DIN labels

The devices are sorted in accordance with standard DIN 40719 and given the corresponding
letters at the first position:
EE I&C, Electrical engineering
--| D Devices
-| A Assemblies
-| B Transmitters, sensors
-| C Capacitors
-| D Logical elements
-| E Various
-| F Safety devices
-| G Generators, powers, supplies
-| H Indicator modules
-| A H Optical indicators
-| 01 H Indicating lamp
and so on.
These DIN letters are also created at the engineering objects. There is a text mask on the
"System" tab of the base object for this purpose. Here is an example of a drive:
The DIN conform letter "A" is also generated combined with a counter in the engineering
object as a name.
2.2.2 Symbols
Basic symbol (graphical symbol)

All simple devices have one or more symbols on the "Symbols" tab. Drawing types
"DETAIL", "DESIGN" and "SLINE" are provided with symbols as a rule:
As long as drawn symbols are involved, they can be adjusted. Please note: The symbols
inherit themselves downwards hierarchically.
Scripts for the drawing types "DESIGN" should not be modified. These are no fixed symbols,
but instead an automatic display calculation for the 2D design diagrams.
The plan mode symbols initially own a fixed size and are optimized for a particular grid and
scale. However, various options can be used so that the symbols can also be used on
reports with a different grid and a different scale.
Each symbol has a placing point which is used for the positioning on the grid. The placing
point is only seldom at the top left-hand corner, but is created in such a way that the
connectors lie on the grid.
Text symbol
A text symbol is created on the topmost node at EE| D Devices for some of the drawing
types:
This text symbol is inherited to all base objects underneath it, but it is not evaluated in all
base objects. It is only evaluated at the base objects that call the text symbol by means of
*V* P Textpoint*. See Volume 60, section 10.6.1: Text symbol for more information
concerning text symbols.
The EE text symbol puts out following information:
● BMK
● Own description
● The first attribute of the "Technical data" tab that has a unit
● Attribute "HSD.001". Whereas "HSD" is the "Manufacturer data" tab and "001" is the "Part
number" attribute.
Additional symbol / placeholder texts

*V*P CD: <Stammobjekt>*
This function allows additional graphics to be incorporated via the base object structure. The
SystemFullName of the base object is used as the parameter, whereby the individual
hierarchy levels are separated by periods (full stops). Example: @1EA.A001.
Placeholders can be rotated just like any other type of text so that they are easier to read.
Normally a rotation of the text in this way has no effect on the to be placed object, and hence
the object always appears in the default direction.
If the rotation of the text is to affect the rotation of the to be placed object, the following
option must be activated in the project properties:
Tab "Module options" subtab |" Detail":
Option "Consider rotation of *V* variables".
2.2.3 Connectors and auxiliary connectors

According to DIN, connectors may only carry one connection. In Comos each connector can
only have one counterpart connector.
In practice, it may occur that multiple connections are made to a terminal, for example. In
order to display engineering data in such a case, you can create auxiliary connectors.
Auxiliary connectors always relate to an existing connector. Auxiliary connectors get the
name of the already existing connection plus a counter, e.g. [1] in the "ConnectorName"
field.
2.2.4 Attributes and calculated attributes

Each device is provided with its own special attributes on the "Attributes" tab. The attributes
are inherited hierarchically and are supplemented or modified by additional ones at each
level, if required.
Attributes that can be used centrally are also managed centrally. For this purpose there is
the "catalog": EE| Y Attributes catalog. The catalog attributes are only have to be called for
EE devices:
2.2.5 Request properties

The base data is prepared to the extent that the "Request and implementation" technology
can be used.
The "Request" property is activated at the "higher levels" for this purpose:
The manufacturer devices are incorporated at the "lower levels" and the "Request" property
is deactivated there.
See also Volume 120, section Request and Implementation (Page 109).
Use the | Administrator | Base data | ECAD components import command to import
manufacturer devices. See Volume 120, section ECAD components import (Page 103).
2.2.6 Product data

The base data is prepared to the extent that the "Product data and manufacturer device"
technology can be used.
For this, the attributes on the "Technical data" and "Manufacturer data" tabs are declared as
product data relevant:
See also Volume 120, section Product data and manufacturer devices (Page 125).
2.2.7 Device labelling

For each project you can - via the project properties - define which device labelling is
supposed to be used. More information on this in Volume 20, section 7.5.1.1: Group:
Prefixes and delimiters and Volume 20, section 7.5.4.4: Device labelling group.
2.2.8 EE| D| I Potential

EE I&C, Electrical Engineering|D Devices|
I Potentials
Class "Device", subclass: "Potential"
Central node for various potential objects. Output: Potentials are normally not displayed in
part lists. You can assign user-defined line types to the potentials. (Regarding user-defined
line types see Volume 60, section 16.1: User-defined line types (USERLNTYPE).)
In practice, the objects "A Potential" and "B Potential rail" are often used together. The
potential rails represent the current input, and outputs of the rail are then get a potential
(which is then passed via the connectors of the engineering objects.) In such a case you
would, for example, label the potential rail with L1 and and the outputs (electrical
connections on a report) would get the logical potential L1.1.
2.2.8.1 EE| D| I| A Potential

EE| D Device view (DIN 40719)| I Potentials| A Potential
Aim
A potential is - similar to the wire information - an additional piece of information on an
electrical connection.
As opposed to potential rails, potentials do not own any connectors of their own. The
information has its origin on a connector (as a rule, on a protective device). It is passed on
by means of links and terminals to the relevant connections. (The passing of the information
can be deactivated through a parameter in the project options.) If you take the current supply
input as given, you can then only work with potentials, otherwise you would have to plan
both a potential and a potential rail.
Control of the extended capabilities

No extended capabilities.
Application
● Create the logical potential as an engineering object.
● Open the device in the Navigator or the properties window of the device.
● Drag the potential onto the connector or
● drag the connector onto the potential.
Effect:
● The logical potential is displayed at the connector in the Navigator. The | Columns | Log.
Potential mouse command on the "Connectors" tab in the properties window of the device
must be used first of all. The logical potential is displayed in the new column.
● In the diagrams the label of the logical potential appears at the potential object (Read
mode) and at open connections.
Placing potentials on connections

There is also the alternative that you first have potentials in the Navigator and then allocate
these to a connection. For example, fuses are always automatically equipped with potentials.
Thus you also have potentials available when you create a protective switch within the
Navigator.
Click on the Allocation tool and drag the potential onto the connection:
You then get all connectors that are located at this potential. Only one connector is available
in the example, this being connector "A1T1". This connector is offered in the box.
You will of course get nothing if there are no connectors at the potential yet. Precisely one
connector is available in the above example. You can simply mouse-click on one of the
connectors to create the connection.
Please ensure that you use the Allocation tool for this.
Disconnecting potentials on the report

After having dragged a potential on a connection of the report, the following mouse menu is
available: |Potential| disconnect. If you execute this menu the connection is deleted and the
potential is deleted from the connection in the database.
Name syntax
The name of the logical potential that has been set is input on the "Connectors" tab in the
"Log. potential" column. Another character can be input before the name, often a minus sign.
This involves a prefix, thus the separator that was input in the project options.
An asterisk can appear at the end of the name. The asterisk only appears for exactly one
object: the "start object", namely, the object from which the logical potential has its origin.
Thus you can tell at once whether the information concerning the logical potential was only
taken over ("inherited" via the connector) or had been defined here.
Disconnecting a potential
The | Columns | Log. Potential mouse command on the "Connectors" tab in the properties
window of the device must be used first of all. The logical potential is displayed in the new
column.
Only here in the "Log. Potentials" column the potential can be deleted again. Therefore you
use the mouse context command | Disconnect.
Connectors / display
If a potential is placed on a report, then the on the reference end output information is taken
from the @System |@Connection table. If you want to see a different text or want to edit or
format an additional graphic or text, then you have to change the according entry in this edit
table. See also Volume 120, section Base project @System |@Connection (Page 49).
2.2.8.2 Predetermining potentials in the base data

Connectors can be prepared in such a way that the allocation of a potential already exists
when the engineering object is created.
See Volume 120, section Preallocating connectors with logical potentials (Page 89).
2.2.8.3 Potential chains / Master-Slave potentials / Potential references

There are two ways to organize potentials across reports:
● Chain
Potentials are initially created as a chain. Thus all potentials are treated equally. The
order of the chain is defined in the project parameters.
● Master / slave
Alternatively, potentials can have a "Master-Slave" relation. In this case all potentials
relate to a master potential.
You can switch between these two options:
| Options...
Chain -> Master / Converts a chain into a master-slave relationship

Master->Chain or back again as applicable. This option is only
available for the master potential.
Start of chain This potential is set as the start of the chain, the
additional members of the chain are calculated
automatically.
Slave->Master Specifies this slave as the new master potential.
The two options determine where the "label" is initially output.
● Master: Label right
● Slave: Label left
● Chain: on both sides.
Differing from the standards, the label can be switched on or off at either side by means of
the mouse menu:
| Options...
Label right Turns on the label at the right-hand end. The

name is displayed if there is no label.
Label left Turns on the label at the left-hand end. The name
is displayed if there is no label.
Arrow direction to the left inside Is the option active, the label on the left of the
potential points to the inside. This way it is
displayed in which work directions the
components are supposed to be connected.
Arrow direction to the right inside Is the option active, the label on the right of the
potential points to the inside. This way it is
displayed in which work directions the
components are supposed to be connected.
For potential references the functions PotName, PotDescription, PotUnit and PotLocation
are available. The functions work analog to the known functions DevUnit and DevName
functions.
Note
For potentials there is the | Options| connect in document order command for logical chains.
Therewith you create the state that potentials solely reference to each other according to the
sheet order.
2.2.8.4 Potentials with report object

If you place a potential on a report, then a RoPotential object is generated on the report. This
has the following effects:
● Own change marks in the revision management.
● No cascading of the electrical connections anymore. Instead all electrical components are
connected to the potential by means of an electrical connection.
● The potential on this report can be copied as consistent.
● The document analysis (Mouse menu |Check | Document) counts the potentials.
● The potentials can be grouped on the report.
2.2.8.5 EE |D |I |B Potential rails

EE| D Device view (DIN 40719)| I Potentials| B Potential rails
Aim
Potential rails are set on the report or in the databasein order to be used like a busbar: as
many outlets as required can be made available at any desired point, which all have the
same current potential. Among others, potential rails are also needed for the construction of
control cabinets.
The potential is often created underneath a location, since the potential has to supply the
location with electricity. However, in principle a potential can be created anywhere.
Controling extended capabilities

Control through Comos as soon as a base object has the "Potential" subclass. The name is
optional. A symbol is not created, instead it is included by the subclass.
Connections
Typical for potentials is that they do not have a fixed number of connection points but instead
can be connected to as many devices as desired. That is why the potential objects are only
set up with one connection, and to this connection there are as many auxiliary connections
created as devices that are to be connected to the potential.
Therefore the help connectors are usually created automatically:
Alternative 1: Create a new output of the potential rail on the report by connecting a new
connection.
Alternative 2: Drag a free device connection on the "Connection" tab of the potential.
Of course you can also manually create help connectors via the mouse context menu.
Overlap
Potentials can own an overlap which reaches beyond the grab points. This overlap is
controlled through the PotentialProlongation variable in the options script of the template
file. Default of the variable is Null [0]. The overlap is only visible if the description is turned off
on the according line ends. Therefore you mark the potential and from the mouse context
menu select the | Label right command (the check is turned off) or | Label left.
Display and use on the report

The potential rail can have one or more outputs on a desired position, whereby the outputs,
as all other object, are aligned to the grid. Each output generates an additional connection.
Alternative display type:

Display of the potential as point from which an output starts. Therefore one of the two grabs
is dragged onto the other. In this case the display of the left label is turned off automatically
because both texts would otherwise lie on top of each other.
Adjusting reference symbols or reference texts
The on the reference end put out information is taken from the @System |@Connection edit
table. If you want to see a different text or want to edit or format an additional graphic or text,
then you have to change the according entry in this edit table. See also Volume 120, section
2.2.7.3: Base project @System |@Connection.
2.2.8.6 EE |D |I |C Potential bundles

EE |D Devices |I Potentials |C Potential bundles
Aim
Potential bundles and also the potential rails belong to the group of physical potentials, and
are part of the power supply. Potential bundles are used in connection with single line
diagrams (SingleLine reports). A potential bundle always has the following structure:
● The potential bundle itself that is used on the single line diagrams. The potential bundle
only has one SL connector.
● Underneath the potential bundle there are potential rails as elements that are used on
"normal" EE reports.
The single SL connector and the EE connectors recognize each other.
The potential bundles have been prepared for three-phase devices, hence there are three
rails underneath the bundle. Example: On the single line diagram you can connect a motor
with the potential bundle and see only one line. However, in the background Comos also
automatically connects the three EE connectors of the motor with the three potential rails
that have been created as elements of the potential bundle.
See also Volume 120, section Special points regarding layout diagrams (Page 84) regarding
single line diagrams.
2.2.9 EE| D| K K Relays, coils

EE |D Devices |K K Relays, coils
Class "Device", Subclass: "Coils/Relays"
Aim
Use on the report as a relay or contactor, including a tabular listing of the connector points
(contact mirror).

Control by Comos:
The base object must have the subclass "Contactor/Relay".
The name of the base object must be included standard table System project: @System |
@ELO_KSP. If an object has the "Contactor / Relay" subclass, Comos then compares the
name of the object against this list. The object on the report only gets a contact mirror if the
name is also found in this description.
The symbol contains no specialties: it draws the display of the contactor/relay and defines
the connector points.
Initialization
The contactor/relay object has various auxiliary contacts on the "Elements" tab, which are
created as "virtual elements". The contact mirror only becomes visible on the diagram once
at least one of the virtual elements has been created. Do this from the mouse menu with the
| Create or | Create N command.
Determining the position

Typically the contact mirror is not displayed directly next to the contactor but at the lower
edge of the sheet, for example. Thus CONTACTMIRROR_X and CONTACTMIRROR_Y
determine where the contact mirror is to be inserted. See Volume 60, section 12.33:
ContactMirror_X (Double), Volume 60, section 12.34: ContactMirror_Y (Double).
The contact mirror can also be repositioned manually. Mouse-click once on the object or the
contact mirror. Mouse-click a second time on the contact mirror (two single-clicks, no double-
click!). The contact mirror gets "grab points", which can also include a rectangular point at
the top end of the contact mirror. Drag this grab point to the new position.
Determining the position

Typically the contact mirror is not displayed directly next to the contactor but at the lower
edge of the sheet, for example. Thus CONTACTMIRROR_X and CONTACTMIRROR_Y
determine where the contact mirror is to be inserted. See Volume 60, section 12.33:
ContactMirror_X (Double), Volume 60, section 12.34: ContactMirror_Y (Double).
The contact mirror can also be repositioned manually. Mouse-click once on the object or the
contact mirror. Mouse-click twice on the contact mirror (two single-clicks, not a double-click!).
The contact mirror gets "grab points", which can also include a rectangular point at the top
end of the contact mirror. Drag this grab point to the new position.
Display
The numbers and letters have the following meaning:
(6.3) Describes the sheet name and the path number, and relates to the object that is
joined at this connector. The zone number is not specified, so this form of notation
states the column in which the object is to be found.
In the example on the left, the object is thus on sheet 6, path 3.
13 The symbolized connector. The number is derived from the designation of the
connector.
Blank cross- A blank (unset) cross-reference. The text that is displayed for a blank cross-
reference reference is stipulated under Additional options in the project properties.
2.2.10 EE |D |O O Other base objects
2.2.10.1 A O Blackboxes, segments

EE| D| O O Other base objects| A O Blackboxes, segments
2.2.10.2 A O |01 O Blackbox, automatic contact points
Aim
This object serves as a blackbox with automatic contact points. Blackboxes are used on
reports to allow connection planning to be made before a concrete device is known.

This object uses the method that automatically places an object as a blackbox in the EE
module if the following applies:
● Class "Device", tab "Symbols": No symbol exists for this drawing type.
A number of scripts have been prepared in this object, but these are not capable to function
as automatic blackboxes. The principle of the automatic blackbox even applies if these
scripts have been deleted. The scripts ensure that the object can be processed without any
errors in the further course of planning.
If symbols exists for some drawing types and not for others, then this object behaves like a
blackbox in the case of drawing types without symbols and as prepared beforehand within
the symbol for other drawing types.
Application
Please note: No preview of the objects is displayed during the drag&drop operation, since
blackboxes with automatic contacts do not have any symbols. Only a cross-hair is visible
while the blackbox is being moved by drag&drop.
If the base object is dragged onto the diagram, then an engineering object that initially has
no connectors is generated. The connectors are generated by Comos on the bounding line,
one per grid point. If additional connectors are required, you can drag out the blackbox to
make it bigger until it covers more grid points.
No Comos connector is generated if a connection terminates as open. A connector is
generated automatically if a connection terminates at a RODevice.
● Name of the Comos connectors:
Comos connectors that were generated automatically get the following names:
Connector located on the left-hand side:
– IX< No.>
Connector located on the right-hand side:
– OX< No.>
Connector located above:
– IY< No.>
Connector located underneath:
– OY< No.>
Whereby <No.> is not a sequential counter but is derived from the grid point. Example:
OX10 is a connector on the right-hand side of the blackbox that is located on the tenth
grid point (without the grid points of the edge).
A connector that had been generated automatically can be opened in the Navigator by
right-clicking on the properties window. If a label is input there (as long as no
implementation has been made yet), the label is also displayed at the blackbox.
Blackbox across sheets:

Blackboxes should not to be used across sheets.
In principle, these blackboxes (as almost all EE objects) can also be placed multiple times
across multiple sheets. A corresponding cross-reference is displayed if a connection is made
on one of the reports to a grid point connector that has already been used on another report.
However, this mode of working does not tolerate a lot of mistakes and should not be used by
beginners.
2.2.10.3 A O |02 O Blackbox, Comos device
Aim
Blackbox with predefined contacts. This blackbox is primarily intended to be used to connect
plug-in cards. In this case there are only connectors going in one direction based on the
plug-in card.

By means of a symbol script.
Application
This blackbox owns a symbol with four prepared connectors. Additional connectors are
generated on the report if the blackbox is placed and drawn out to make it bigger.
All connectors initially lie on the upper edge of the symbol, however, the symbol can be
rotated and thus the outgoing direction of the connectors can be stipulated retrospectively.
No Comos connector is generated if a connection terminates as open. A connector is
generated automatically if a connection terminates at a RODevice.
Multiple placing
The blackbox with predefined contacts can be continued across multiple reports. A
corresponding cross-reference is displayed if a connection is made on one of the reports to a
grid point connector that has already been used on another report.
2.2.10.4 A O | 11 segment
03 Structures |EIC Electrical, Measuring and Control engineering |310 Product view acc. to
DIN 40719 |O O Other base objects |A O Blackboxes, segments |11 Segment
Class "Element", subclass "Segment"
Aim
ID segments (label segments) are rectangular areas on circuit diagrams that group objects
belonging to one location for the purpose of a more simple and clearer labeling. This
abbreviation of texts at the devices also covers cables (class: "Device", subclass: "Cable").
These segments are stipulated in addition as the target for the automatic placing function
("AutoLoop").

Control by Comos as soon as a base object has the class "Element", subclass "Segment".
The name is optional. The symbol does not contain specialties: it draws the display of the
segment and outputs a text.
Application
1. Drag a base object of type "ID segment" onto the diagram by means of drag&drop.
2. Single-click twice on the ID segment until the grab points become visible.
3. Drag out the ID segment until it is large enough to accommodate all desired devices (but
only those devices) within the rectangle:
If the labelling of the segment matches the labelling of the objects within it, the labelling of
the objects is displayed in abbreviated form:
Without labelling segment With labelling segment
If a selection frame is dragged out with the mouse (multiple selection), then the ID segments
are not selected.
Single-click to select an ID segment. When pressing [Ctrl]+ left mouse button, the sequence
decides whether an ID segment can be selected.
Note
Via the mouse menu | Settings| Continuation left respectively | Settings| Continuation right
you can change the appearance of the label segment.
Configuration
Right-click to open the properties window of the ID segment:
Label is valid for

This options group is required in connection with abbreviated labels and has not significant
for automatic placing.
The option controls which label texts are displayed at the segment and therefore should be
hidden at the devices.
For label segments the %N DevDescription% option is evaluated (OwnDescription from the
base object).
Sheet zone
This options group is required in connection with automatic placing and is not significant for
abbreviated labels.
The name of the sheet area is used as a target during automatic placing. In other words:
Comos detects on the basis of this detail withins which segment the devices are to be placed
in. For that reason a sheet area name also should not be available twice on a report. In the
dropdown field there are a number of prepared names that are typically used in the I&C field.
Multiline output
It may occur that the description text which is displayed within the label segment will get very
long. In such a case it is recommended to activate the "Multiline output" checkbox. Is the
checkbox activated the label text is distributed on multiple lines.
The default settings of the checkbox is taken from the SYS.SegmentDefaultMultiLine
attribute.
2.2.10.5 A O |12 O Sheet areas I&C

EE Electrical, Instrumentation and Control| D Device (DIN 40719)| O O Other base objects|
12 O Sheet areas I&C
Class "Element", subclass "Segment"
Aim
This object has the same aim as the 11 O ID segment object, but is optimized for I&C
(different attributes and symbols).
2.2.11 EE| D| W Cables

EE| D Device view (DIN 40719) W Cables
Class "Device", subclass "Cable"
2.2.11.1 Aim
Usually EE connections do not have any objects. This means that the connectors of two
devices are connected directly with each other. A connection is drawn on the report, but this
connection itself has no counterpart in the database. Only the end points of the connection
have counterparts in the database.
In some cases it is necessary to define the connections more precisely. Therefore the
objects have prepared. Cable systems that can be specified down to the level of the wires
are provided.
2.2.11.2 Control of the extended capabilities

Cable systems are two-level.
● 1st level: Base objects with the class "Device", subclass "Cable"
● 2nd level: Base objects with class "Element", subclass "Wire
"(wire elements and shield elements)
The subclasses "Cable" and "Wire" have the effect that additional tabs are displayed and
that RO_Cable.dll is evaluated.
Wires and shields have the same "Wire" subclass. In principle, shields can thus be described
as wires. In other words: "indirect shields" are used in the default libraries that are taken
along to shield the cable.
It is necessary to additionally activate the "Object settings: shielding" option on the "System"
tab so as to distinguish shields from normal wires.
In addition, cables, wires and shields have special attributes and symbol scripts, especially a
description. See also Identification key in EE reports in section Superimposing and hiding
information (Page 81).
2.2.11.3 Attributes
A cable can only be placed correctly on a report once the wires have been created. There
are two ways to get cables with wires:
Select one of the basic cables and create the necessary wires yourself, see this section.
Basic cable
EE| D Devices| W W Cables|A W Cable acc. to VDE | 0000 W Base cable
Select one of the fully configured cable objects in which the wires have already been
created. See Volume 120, section Complete cable (Page 32).
Basic cable, attribute tab "Technical data" tab (creating cable)

The basic cable initially does not have any wires. Open the properties window and switch to
the "Technical data" tab to create wires.
The following procedure is independent of whether you are working with a base object or an
engineering object. However, a copy of the basic cable should first be made in the base data
before any new wires are created. In this way the original basic cable thus remains
unchanged.
Wire number
The total number of wires, including a potential conductor if applicable.
Number of shields
Number of shields.
Separator
This separator is used when the "Number of wires" and the "Cross section" are added to the
"Cable cross-section" details.
With protective grounding conductor

Turns one of the created wires into a grounding conductor. The label is also changed when
doing so.
Cross section
Is taken into the "Cable cross-secton" field along with the "Number of wires" on the "System"
tab.
Wire label
A number of color libraries have been prepared in branch ZZZ Other objects. Here these are
offered in the dropdown menu. The wires are created according to the library, depending on
the "Number of wires". If the number of wires is greater than that of the predefined wires in
the library, the remaining wires are created numerically.
[CREATE CABLE]
Creates the wire elements on the basis of the relevant details. The details can still be
modified or supplemented later. If you again click on [Create Cable], the wires are modified
or supplemented correspondingly. See also Attribute tab System, Wire node.
Basis cable, Attribute tab "Cable calculation"

After having completely filled out the "Data" options group, you can then click on the
"Calculation" options group button with the exclamation mark. The loss values are then
automatically calculated.
Attribute tab "System data"

● Group "System settings"
– Sheet zone
Is used for the automatic placing and in I&C for the automatic placing.
– Data display of
Switches the display of the attributes in the properties windows.
– Standard system
Is used in I&C and switches the edit tables.
– Allowed multiple placing
● Group "Object settings"
– Cable type
Self-explanatory.
– Cable cross-section
Is set by the system if the VDE cable uses the [Create cable] option.
– Wire node
Is evaluated by the system if the VDE cable uses the [Create cable] option.
– Number of parallel cables
Group "Graphic settings"
– Description left/top
Self-explanatory.
– Shielded display
The cable gets a graphical shield symbol on the report. This option has nothing to do
with the shield object, see Volume 120, section Shield (Page 33).
– Wire description vertical
Self-explanatory.
– DESINA conform
Controls the color of the cables on the report according to the DESINA code.
2.2.11.4 Symbols for cables

The behavior of cables is primarily controlled by the symbol script. This is done, for example,
by marking the DETAIL drawing type and then clicking on the [S] button in the "Symbol"
group.
Please note: the grabs must be called "RU" and "LU", otherwise the cable objects on the
report do not function correctly.
2.2.11.5 Complete cable

Two cable systems have been prepared in the base data:
● VDE-compatible
Cables with stranding have also been prepared beforehand under the 0815 Telephone
cables category.
● Oilflex cables from "U.I. Lapp GmbH".
Please note: If you use objects from these cable systems, you can subsequently create or
modify other cables or wires with the help of the [Create Cable] button.
| W | VI Connection information
This object is also offered in the circuit diagram. Place the object next to one or multiple
connections and activate the grabs. Afterwards you extend the object until the desired
number of connection is exceeded.
In the mouse menu of the connection information object you then have the following
command: |Settings | connection information.
All descriptions you enter in the dialog are assigned to all overlapped connections.
2.2.11.6 Placing the cable on the report

The cable objects (not the wire objects!) are placed on the report:
The cable is displayed on the diagram in the form of a dotted line.

The grab points can be activated by two single-clicks. The grab points can be used to drag
out the cable symbol to be wide enough to include all connections that are to belong to the
cable:
The texts mean:
-W2 Name of the cable object

NYM-J Label of the cable object
5x1.5 Cable cross-section (number of wires x wire cross-section)
The wires are numbered sequentially. This number is also entered on the diagram at the
intersection of the cable and the connection:
If wires have already been set in the database, this information is retained as far as possible,
but the remaining wires are set during positioning on the diagram if only part of the
information has been set. Thus the free wires are allocated in the due order, and more
precisely, in the order in which they are displayed in the unsorted list window.
Settings for the cable symbol

The | Settings mouse menu is not offered as long as the cable symbol is grouped together
with the shields. If you want to use this mouse menu, then you must
● single-click several times on the cable symbol. The single-clicks "run through" the group
until only the cable symbol is marked.
● Remove the grouping and only mark the cable symbol.
The settings in the engineering object are transferred to the "System" tab in the "Graphic
settings" options group.
2.2.11.7 Shield
Class "Element", subclass "Wire"
The knowledge of Volume 120, section Control of the extended capabilities (Page 28) is
required.
Display and use on the report

See Volume 120, section Shielded cables (Page 76).
One or more shields are available, depending on whether a basic cable or a preconfigured
cable object was used. Drag the shield onto the connections in the report.
You can activate the grab points with two single-clicks. Use the grab points to drag out the
shield until it is wide enough to include all connections on the report.
Connect PE grounding conductor

Shields have a connector to the left and right respectively to which a grounding conductor
can be joined. The grounding conductor may not remain open but must always be
connected, for example, with a terminal.
No connector is displayed in the engineering object of the shield within the Navigator.
Instead, the relevant information on the grounding conductor is given on the "Wire" tab.
Additional shields
There are the following methods to create additional shields:
● Mark the cable (not the connection!) on the report and select the | New | SH Shield
command from the mouse menu. The new shield now "glues" to the mouse pointer.
● Open the properties window of the cable on the "Technical data" tab to make new inputs
and mouse-click on [Create cable]. The new shield still has to be placed on the report.
● Select the | New | SH Shield mouse menu within the Navigator. The new shield still needs
to be placed on the report.
Moving or editing shields

If additional shields were placed on the report, these are first grouped with the cable. A
group of this kind can be moved or deleted, etc., as desired.
If you want to move or delete a shield individually, then
● single-click several times on the shield. The single-clicks "run through" the group until
only the shield is marked.
● Select the relevant shield on the report and then select the | Grouping | Remove
command from the mouse menu. Now all shields can be moved freely.
If you select the | Grouping | Restore mouse command, all shields are again linked with the
cable symbol.
2.2.11.8 Other objects (wire, shield, stranding)

This branch has preconfigured elements that are used in the cable systems: wires, shield,
stranding.
Stranding
The stranding is used in the branch | Cables acc. to VDE | 0815 Telecommunication cable.
The stranding object is used instead of a normal cable object.
2.2.11.9 Supporting documents

PDF file "Shortcut explanations for VDE type abbreviations"
This document comes from the Faber Kabel company and contains the type abbreviations of
cables and wires in according to VDE.
Cable list
Outputs the cables, including the wires.
Cable types list

Outputs the cables. The "Cable length", for example, is evaluated as well.
2.2.11.10 Pre-allocating wires to connectors

Properties window of a connector, "Wire" field. From Comos 7.1 onwards.
2.2.12 EE| D| X X Terminal - / plug strips

Class "Device", subclass "Terminal strip"
2.2.12.1 Aim
Aim
Providing terminal strips and plug strips.
Terminals and terminal strips can only be regarded as a unit in Comos. It is meaningless to
use a terminal strip without terminals, since only the terminals can have connections. But it is
also meaningless to think in terms of a terminal without a terminal strip, since the terminal
must be placed somewhere.
See also Volume 120, section The Strip tab (Page 89).
2.2.12.2 Control of the extended capabilities
Two-level structure
1. level: Base objects with class "Device", subclass "Terminal strip"
2. level: Base objects with class "Element", subclass "Terminal"
The subclasses "Terminal strip" and "Terminal" have the effect that TerminalStrip.dll is
evaluated. This dll superimposes, for example, the additional tabs.
Terminal strips and terminals can be named as desired.
Terminal strips do not have symbols, since they are not placed on reports. The terminals
symbol has no special features: it draws the terminal and provides the connectors.
Three-level structure
Terminal strips can be organized over three levels: terminal strip - deck - terminal. This
structure is similar to that in multi-deck terminals. The "decks" in the case of terminals are
also often called "positions". They are intended to display the installation position of the
relevant terminal in the cabinet. A sample terminal strip with installation positions is given in:
| EE| D| X| 02.
These objects can control any desired number of terminals per deck.
The deck elements of the terminal strip are controlled via the "Equipment" subclass. This
subclass has the following effects, among others:
● The connectors of the terminals are displayed on the "Connectors" tab of the terminal
strip.
● If you drag the terminal strip onto the report, then one terminal is placed, this being the
first free terminal of the first free deck. If there are no more decks with free terminals, then
a deck and a terminal are created automatically. This also applies in the event that a
terminal strip from the base data is dragged onto the report: the terminal strip, the deck
and the terminal are created automatically in the Navigator.
The label of the terminal strip and the label of the deck appear separately on the report at the
terminal.
Example:
EE |D Devices |X Terminal / plug strips |99 X Plug strip, new objects
These objects currently control only one terminal per deck.
2.2.12.3 Terminal strips
Technical data tab
"Number of same terminals per block"

This attribute is not used by Comos itself but is provided for an ECAD import.
"Configuration"
This attribute is not used by Comos itself but is provided for an ECAD import.
2.2.12.4 Terminals
Terminals typically have two connectors. In Comos the two terminal connectors are
distinguished by the "internal" (%N I %) and "external" (%N O %) sides.
The external connector is marked by a point in the diagram:
This marking point is not defined in the symbol of the terminal, but is inserted from the
RO_Device.dll. If you want to turn off a marking point, you can set options parameter
DrawTerminalSideMark = 0.
By default, the internal connector is above and the external one is underneath. This
arrangement is reversed by means of the | Options | Direction Rotated mouse command.
If a terminal strip is dragged onto an interactive report with an electrical engineering template
by means of drag&drop, then it is not the object of the terminal strip that is placed but instead
the next unused terminal. The procedure creates a new terminal if a free terminal cannot be
found but there are virtual terminals available.
System information tab

"There is a separator after this element"
The terminal is underlined in the terminal diagram. This underlining indicates that a separator
has been inserted in the actual terminal strip after this terminal.
"There is a sheets break after this element"

The report starts on a new sheet after this terminal.
"Grid gap..."
The default gap between the terminals is one grid point. The placing gap can be changed
here.
2.2.12.5 Bridges
Bridges connect terminals. This means that bridges can only be set within a terminal strip.
Thus there can only be connections between the various terminal strips, but not bridges.
Bridges can be created in the report:
● Volume 120, section Connection / wiring for terminal bridges (Page 65)
Bridges can be created in the properties window of the terminal strip:
● Volume 120, section Bridges (Page 90)
2.2.12.6 Supporting reports
Terminal diagram (default)

Outputs the pin-outs of a terminal strip in tabular form. The pin-outs are grouped by inside
and outside.
Document properties of the terminal diagram, attributes, "Settings" tab:
"Suppress unit / location:"

There is a "Label" column in the terminal diagram. The unit and location of the connected
device are also output in this column. When the option is activated, the unit is not stipulated
for the devices if it is identical to the unit of the terminal strip. The same applies to the
location.
"Output with bridge symbols:"

On: Instead of icons, the graphic symbols that are defined in @Bridgesymbols are output for
the terminals. The output of bridge symbols is especially suitable for a DXF export, since
AutoCAD has problems in working with icons.
Terminal diagram (matrix)

An alternative form of a tabular display, in which primarily the columns for "Cable" and
"Device" are swapped. Cables are handled separately and connections are only handled by
numbers.
Terminal diagram (graphically)

Document properties of the terminal diagram, attributes, "Settings" tab:
"Sorting"
Self-explanatory.
"Output all terminals

"Off: Unused terminals are filtered.
"Suppress unit / location (component)"

There is a "Label" column in the terminal diagram. The unit and location of the connected
device are also output in this column. When the option is activated, the unit is not stipulated
for the devices if it is identical to the unit of the terminal strip. The same applies to the
location.
"Symbolic display"
This option only functions if graphic terminal diagram is used in the GRPLAN drawing type.
On: The symbols defined on the "Symbols" tab are displayed on the graphical terminal
diagram.
Off: The objects are displayed in the form of simple rectangles that are provided by Comos in
this drawing type.
"Output terminal strips recursively"

Normally a terminal diagram is located underneath a terminal strip and outputs precisely
that. If this option is activated, you can then create the terminal diagram under a unit or
under a location and the terminal diagram outputs all terminal strips located there one after
another.
2.2.12.7 Plug strips

Plug strips behave in principle in the same way as terminal strips, but cannot be used as
bridges.
2.3 EE| E Elements
2.3 EE| E Elements
2.3.1 J auxiliary contacts

Auxiliary contacts are used in all kinds of places within the EE branch, among others in:
● K Relays, coils
● Q Main power switchgear
● S Switch, push button, selector switch
● and at other places.
2.3.2 W Wires, color codes

Here, wires have been prepared that are used in cables, see Volume 120, section EE| D| W
Cables (Page 28).
2.3.3 X Terminals, plugs

Terminals and plugs that are used in the terminal strips and plug strips are provided
prepared here, see Volume 120, section EE| D| X X Terminal - / plug strips (Page 35).
2.4 F Component view (IEC 61346)

The devices that are located in this node are structured according to the IEC 61346 norm,
and are labeled with the according descriptions. Almost all devices in this node inherit from
the device that is located in the D device (DIN 40719) node (see Volume 120, section EE| D
Device view (DIN 40719) (Page 12)), and have the same properties as they do.
See also
EE| D| X X Terminal - / plug strips (Page 35)
2.5 G Document groups |@NameSystem Structure

A sample structure for document groups. Is used in base object @J Project | @E Project
templates EE. The EE documents and these document groups are prepared in such a way
that automatic referencing can be done.
2.6 J Project |@E Project defaults EE
2.6 J Project |@E Project defaults EE

If this base object has been set for a project, then a unit, location and document structure is
made available.
2.7 L Locations |E Location structure EE

A sample structure for locations. Is used in base object @J Project | @E Project templates
EE.
2.8 O Documents | EE Electrical engineering

Contains the document base objects for electrical engineering.
BSL Order list

Outdated. Predecessor for STL Parts list / order list.
DES layout plan

Outdated. Predecessor for DVW layout plan with views.
DVW layout plan with views

See Volume 130, section 1.2.5.2: Interface: Metzner Triathlon.
GAP Device connector plan

See Volume 120, section Supporting reports (Page 37).
IMP Circuit diagram

Was required to import Logocad Triga 1.04.
KLP Terminal plan

See Volume 120, section Supporting reports (Page 37).
LTV Cable routing

"Output": Controls the sorting by which the list of the evaluation report is created. Example:
"PMB List of cables, PMB.5 cable routing".
2.9 U Units
MTL Materials list

Outdated. Predecessor for STL Parts list / order list.
SLP Circuit diagram

See Volume 120, section 5.2: Preparing connections.
SPS PLC overview

Is used in the report PMA.1 PLC overview. This concerns an overview that outputs the
addresses and connections of a PLC station.
STL Parts list / order list

See Volume 120, section Evaluation (order lists / materials lists / parts lists) (Page 93).
2.9 U Units
A sample structure for units.
2.10 Z Symbol structure
Class "Element", subclass: "Graphic"

Objects of this subclass are used solely to hold a graphic. Symbols can be defined in the
usual way for the base object and placed on an interactive report. However, no engineering
object is created. Thus the symbol can never be inconsistent and hence also will not be
displayed in red.
2.11 eClass 4.0

As a service in the SO1_Ext base project the eClass catalog is prepared in the 4.0 norm.
eClass is not used is not used in the EE branch.
2.11 eClass 4.0
Standard tables for EE 3
The relevant standard tables of the base project are introduced in the following.
3.1 Systemology
The EE standard tables are set up structurally in the same way as the EE base data:
For the "1 Modules" base data branch there is also a "1 Modules" branch in the standard
tables and so on. The entries in the standard tables use as far as possible the name of the
associated attribute as their name.
Standard tables for EE
3.2 0 System tables
3.2 0 System tables
3.2.1 Import assignment of attributes

This list is used to compare data imported into Comos against existing attributes.
Name Unique string

For reasons of clarity, in the ComosDB this name is the same as "Value 1",
but this is not essential. However, since the string must be unique, a counter
must be appended if a name is used twice, for example M001 and M001a. (In
this case two different external attributes are mapped to a common Comos
attribute).
Description Any.
Value 1 Any desired value.
Contains the FullName of the attribute, hence the name of the tab plus the
name of the attribute.
Value 2 - Value 4 ECAD attribute, TRIGA attribute, EPLAN attribute
Value 5 - Value 10 Unused.
See Volume 120, section .

See Volume 120, section EPLAN (Import/Export EXF) (Page 143).
3.2.2 1 Modules
3.2.2.1 Luetze Manufacturer node

Belongs to the base data branch
EE |1 Modules |A Cabinet engineering |B Manufacturer |LUETZE.
The standard tables in the LUETZE branch serve solely as support for input and have no
other meaning.
● 11 Carrier rails
In the LUETZE branch belongs to
B Style B | B Mounting parts| 01 Carrier rails.
● 21 Mounting rails
In the LUETZE branch belongs to
B Style B | B Mounting parts|11 Mounting rails
3.2 0 System tables
3.2.3 G Document groups

The two following standard tables are not binding for all document groups. Instead, each
document group can have its own base object. In the Comos EE module, EE-specific base
objects have been predefined for document groups and only these EE-specific base objects
access the following standard tables.
This means that the EE base data can be copied in isolation together with the EE standard
tables.
But vice versa, this also means that the other modules could save their own settings for
document groups. The standard tables DynNum and RefDocSortMode can also exist in
other places as well.
3.2.3.1 DynNum Dynamic numbering

Application: Properties of a document group, tab "System data", dropdown list "Numbering
mode".
Name Unique string

For reasons of clarity, in the ComosDB this name is the same as
"Value 1", but this is not essential.
Description Any.
Value 1 Unique value. Comos identifies the setting on the basis of this value.
See Volume 60, section 4.5.4: Generating a virtual page number.
3.2.3.2 RefDocSortMode Reference name

Application: Properties of a document group, tab "System data", dropdown list "Reference
name".
Name Unique string

For reasons of clarity, in the ComosDB this name is the same as
"Value 1", but this is not essential.
Description Any.
Value 1 Unique value. Comos identifies the setting on the basis of this
value.
See Volume 60, section 4.5.3: Generating names of reference documents
3.2.4 O Documents
Belongs to the base data branch EE |O Documents.
3.2 0 System tables
3.2.4.1 PMA Connector-, Connection list
SYS01 Sorting for GA

Belongs to "04 Terminal plan, graphical layout", tab "SYS", attribute SYS01.
SYS06 cable output
3.2.4.2 PPB Parts, label list

SYS01 Sorting for GA
Belongs to "04 Terminal plan, graphical layout", tab "SYS", attribute SYS01.
SYS06 cable output
3.2.4.3 PPC Parts list

SYS01 list type
, SYS02 output
Belongs to "01 Parts, order list", tab "SYS".
3.2.5 Y Attribute catalog

Belongs to base data branch EE |Y Attributes catalog.
Only special points are covered in the following.
3.2.5.1 02 Construction
ETK025 Cabinet type

The table is used for mounting control in control cabinets.
Name Unique string

Description Any. This is the visible text in the "Cabinet type" dropdown list.
Value 1 Relative installation height.
Value 2 Contains data for the export to Triathlon. MP = mounting plate;
MS = mounting rail; BT = component; KK = cable channel.
Value = 1:Cabinet frame, is excluded from all controls and checks. Value = 1 must be set for
the cabinet frame.
Value > 20 and not placed on the plate/rail, etc.: Message: Floats freely in space.
Call of the list: Tab "EBD Installation data", attribute "M029A Cabinet type".
Example:
3.2 0 System tables
EE |1 Modules |A Library objects |A Cabinet parts
Comparison with the Mounting key tab

Tab "MKY Mounting key": The entries from the above standard table are listed once again
on this tab. In this case the "Name" of the checkboxes must be spelled the same way as the
"Description" in the standard table.
When mounting is conducted, a check is made as to whether the cabinet type that had been
set in the "EBD Installation data": "M029A Cabinet type" attribute belongs to the types of
cabinets that have been permitted on the "MKY Mounting key" tab.
● Tab "MKY Mounting key" does not exist:
All cabinet types are allowed.
● Tab "MKY Mounting key" exists, but no entry was clicked (the collective string of the
permitted cabinet types is blank):
All cabinet types are allowed.
● Tab "MKY Mounting key" exists and at least one entry has been activated:
Only those cabinet types that have been input here and activated are permitted.
The user receives a message if an attempt is made to install a prohibited cabinet type.
3.2.5.2 2 Tab collection

Self-explanatory.
3.2.5.3 3 3D section
Self-explanatory.
3.2.5.4 D Devices
The standard tables under category are predomantly created with the help of a naming
syntax that is oriented towards the systemology of the DIN (ECAD) catalog: A - Z = DIN
section. Example: A = Assembly groups; B = Transducers, etc.
Upper limit value, Lower limit value

|B Transmitters, sensors|B Measuring transmitter |ZB02 / Upper limit
|B Transmitters, sensors |B Measuring transmitter |ZB03 / Lower limit
These two lists contain a script for Value 1 equals "1". The script draws a triangle and reads
the MB03 min.-max. range attribute. In doing so, ZB02 reads the XValue (0) (= left-hand or
lower limit value) and ZB03 reads the XValue (1) (= right-hand or upper limit value).
Action lines for auxiliary contacts

@1EA|SJ_01 / Action lines for auxiliary contacts
This has been renamed and moved to:
3.2 0 System tables
EE |Y |0 |05 |ETS066 Action lines
Cables in accordance with VDE

EE |Y |D Devices |W Transmission devices|VDE
Belongs to the base data branch

EE |D Devices |W Cables |A W cable acc. to VDE
The name of the base object is identical to the name of the corresponding branch in the
standard tables. The name of the attribute in the base object is identical to the name of the
standard table itself.
Example:
Base object "0250 W Power / Control cable", tab TD, attribute LT01. This attribute uses
standard table LT01 Base type.
|VDE |WIREMODE Wire label
WIREMOD enables the assignment of wires by means of color coding.
3.2.6 Base project: @IRF_xxx

@IRF_Detail, @IRF_Detail_PNEU, @IRF_SLINE.
The text functions input here are made available in the Symbol Designer when you create a
text and fold out the "Text functions" branch within the text properties.
The relevant description is offered according to which drawing type the symbol was created
for.
3.2.7 Base project @System
3.2.7.1 Base project: @System |@Bridge symbols

Contains the graphical symbols that belong to the "Symbolic display" option of graphical
terminal diagrams. This option only functions if the graphical terminal diagram is used in the
GRPLAN drawing type.
On: The symbols defined on the "Symbols" tab are displayed on the graphical terminal
diagram.
Off: The objects are displayed in the form of simple rectangles that are provided by Comos in
this drawing type.
3.2 0 System tables
3.2.7.2 Base project: @System |@Class | Detail

Contains the header classes that can be used in EE to set up symbols. A header class
identifies a text. Thus this text can be shown or hidden in a targeted way. Ultimately the
same can be done with the header class as with a layer. Layers and header classes can be
mixed.
Example: Header.Class = "eBT"

eBT = electrical engineering components. If class eBT is hidden, then all marked texts of this
type are hidden, regardless of which layer they are located in.
3.2.7.3 Base project @System |@Connection

Contains the symbols for EE connections. In other words: if a connection is shown in EE that
has a cross-reference at the end, then this description controls what information appears
there and how this information is formatted.
The mode of working thus corresponds exactly to the procedure by which you draw a symbol
for a device. Switch in the third column to the required drawing type. Do this by right-clicking
on the column header and selecting the | Symbols menu from the right bottom:
Then double-click on the symbol. You can now make the desired changes.
The "Symbols" created in @System | @Connection are displayed at the connection break.
The individual entries have the following meaning:
LOGPOTREFERENCE: If a logical potential is allocated to a connector, then REFERENCE
is no longer output at the relevant connection, but instead LOGPOTREFERENCE. See
Volume 120, section EE| D| I| A Potential (Page 16), Volume 120, section Open connections
(Page 60).
PHYSPOTREFERENCE: See Volume 120, section EE |D |I |B Potential rails (Page 20).
REFERENCE: See Volume 120, section Open connections (Page 60).
REFERENCEBRACKET: See Volume 120, section Open connections (Page 60).
3.2 0 System tables
3.2.8 System project @ConnectionType E
Application
Properties window of a connector, field "Subtype".
Connectors with different subtypes are not allowed to be connected anymore. A connection
is prevented in the Navigator. In the report the according connections are marked as
inconsistent.
3.2.9 System project @System
3.2.9.1 System project @System |@BridgeType
Application
Properties window of a terminal strip, "Strip" tab, | Bridge/Connection mouse menu
Report, mouse menu of a connection when the connection points to a bridge.
3.2.9.2 System project @System |@ELO_KSP

If an object has the Contactor/Relay subclass, Comos then checks the name of the object
against this list. The object on the report only gets a contact mirror if the name is also found
in this standard table.
3.2.9.3 System project @System |@WireColor
Application
Anywhere where the mouse menu | Color for connectors or connections is offered.
Examples:
Properties window of the engineering objects, "Connectors" tab, | Color mouse menu.
Report, mouse menu of a connection: | Settings | Color.
3.2.9.4 System project @System |@WireCrossSection

Similar to WireColor, but here for the cross-section.
3.2.9.5 System project @System |@WireTypeInfo

Similar to WireColor, but here for the type info.
Interactive report templates 4
4.1 Circuit diagrams
4.1.1 Attributes
See Volume 120, section Preparing connections (Page 57).
4.1.2 Options for EE reports

Important script options for EE reports:
Single commands
Application = "ELO"
In this case Xdoc_Elo.dll is used.
ContactMirror_X, ContactMirror_Y
Volume 60, section 12.33: ContactMirror_X (Double), Volume 60, section 12.34:
ContactMirror_Y (Double).
RestoreReferencesAfterCopy
Volume 60, section 12.105: RestoreReferencesAfterCopy (Boolean)
Controlling connections
ConnectionHook
Controls the display of the connection hook. If a connection is also a bridge, dynamic
connectors are always displayed in the form of a hook, regardless of the script entry. See
Volume 60, section 12.30: ConnectionHook (Double).
ConnectionLineMode
Volume 60, section 12.32: ConnectionLineMode (String)
ConnectionReference
The previous option via the script method ConnectionReference in the template document has
been dispensed and only exists due to compatibility reasons in Comos.
You can now depart from the default standard for references across sheets by defining
symbols with scripted texts (Edit table: @SYSTEM | @CONNECTION).
ShowConnectionInfo
Volume 60, section 12.114: ShowConnectionInfo (Boolean)
SetWireNumberByCoord
SetWireNumbersByCoord(ByVal ReportDocument As REPORTLib.Document)
All connection end points are provided with a unique number per quadrant ("ladder"). This
information is input instead of the quadrant label if the connection owns a logical potential.
Interactive report templates
4.1 Circuit diagrams
DisplayConnectedWith
Enables the automatic execution of a script at closed connections. The prerequisite for this is
an entry in the @connection table with the StandardValue ConnectedWith. If a script has
been stored for this StandardValue, it is then then executed.
EnableButtonSpline
Volume 60, section 12.61: EnableButtonSpline (Boolean)
EnableButtonANSICable
Volume 60, section 12.59: EnableButtonANSICable (Boolean)
PreferredConnectionDirection
Controls the preferred output direction when a connector is joined to a connection on the
report.
ShowLineModeControl
Volume 60, section 12.118: ShowLineModeControl (Boolean)
Paths and zones

Interactive reports of the EE/I&C module are often split up into an invisible checkerboard
pattern for a better orientation. The columns are called "paths" and the rows are called
"zones". Thus a text can be created that is displayed in the description of the report objects
of a path.
● A text is created in a path on the interactive report (for example, at the top edge of the
report).
● Input the text.
● Activate the "Path text" checkbox.
● Confirm with OK, and a text frame appears.
● This frame must be dragged out to be as big as desired but should not be wider than the
path itself. All objects that are located completely within the width of the frame (if you
mentally extend the edges of the text frame downwards) are given the path text.
Do not create two path texts within a path.
The path text is only displayed for those objects that do not have a description already. In
other words: an already existing description is not overwritten.
4.2 Layout diagrams
● Path / zones variables

QuadrantOffsetTop = 0
QuadrantOffsetLeft = 0
QuadrantSizeX = 60
QuadrantSizeY = 60
QuadrantStartChrX = "0"
QuadrantStartChrY = "A"
QuadrantStepX = 1
QuadrantStepY = 1
● Path and zone calculation, variable
Dim Pfad(7)
Dim Zone(5)
Sub OnCreate
For i = 1 to 7
Pfad(i) = CStr(i - 1)
Next
For i = 1 to 5
Zone(i) = CHR(i + 64)
Next
End Sub
Variable for the output of potential rails

RightBorder
Stipulates the initial width of a potential rail when it is placed on a report.
SignByEmptyReference
Volume 60, section 12.129: SignByEmptyReference (Boolean)
4.2 Layout diagrams

See Volume 130, section 1: Cabinet engineering.
4.2 Layout diagrams
Evaluating report templates 5
The following report templates for evaluation reports are used in EE.
5.1 PMA Connection schematics

● Terminal diagram (default, matrix)
● Connection list, general
● List of potentials (Unit/Location)
● PLC overview
● Marshalling diagram
5.2 PPB part -, label lists
Electrical consumers
Electrical consumers are determined on the basis of attributes. The report does this by
accessing an object query. In this object query there is the "Power" column, which evaluates
a whole series of attributes in the column properties. Objects that do not have at least one of
the attributes listed here are not listed as consumers either.
The class "Devices", subclass "Consumer" is not evaluated.
The script can be modified to suit your own needs.
Others
● Engraving list
5.3 PQA Check -, test reports

● Wires that have no connections
● Change after a revision
● Checking the required device against the manufacturer device.
See Volume 120, section Request and Implementation (Page 109).
● Connector with too many connections
Evaluating report templates
5.4 PPC Parts list
5.4 PPC Parts list

● Parts list
Connections 6
6.1 Graphical connections
These section covers the Comos method on how to draw and control connections on
reports. This initially involves a form of graphical work that is largely independent from the
electrical engineering connection information such as cross-sections, colors, bridges, etc.
6.2 Preparing connections

The following attributes are available if you have worked with the SLP Circuit diagram
document template:
Document properties, attributes, "Settings" tab: "Wire color", "Cross-section", "Cable type".
These three fields use the standard tables WireColor, WireCrossSection and WireTypeInfo.
If these fields have been set and no cable object has been allocated to connection on the
report, the corresponding details are written to the relevant connectors of the connected
objects.
6.3 Creating connections

The "Connection" tool is located on the menu bar of the report. This tool is used to create
connections to objects (components).
Please note: In addition there is also the "Line" tool on the menu bar of the report. While you
can use it to draw a line in purely graphic terms between two components, this does not
generate an actual connection.
You can find an illustrated introduction concerning the use of the Connection tool in
Quickstart EE, section "Construction (Design)".
The Connection tool has the following basic abilities:
● "Magnetic" connection points: the Connection tool automatically snaps to the connector
point within a certain radius around the connection point of symbols. This automatic
snapping of a cable to a connector point can be deactivated by holding down the <Ctrl>
key while holding down the mouse button and moving the mouse.
● "Magnetic" grid points: the Connector tool automatically snaps to a grid point. This
automatic snapping of a cable to a grid point can be deactivated by holding down the
<Shift> key while holding down the mouse button and moving the mouse.
● Connections can also be dragged across components, the connections are dissolved and
the object incorporated into the connections.
Connections
6.4 Defining graphical properties
● The connections are closed when an object in the document is deleted.

● If an object is set to connections, the connections are separated, meaning that the object
is incorporated into the connections.
● The connections are changed correspondingly when components are moved.
● Connection crossings on connection cables
● Two other connections can also end at the same point when joining connectors. A
connection crossing is displayed to distinguish such a case from a situation where a
connection runs over another connection but in a purely visual form.
Automatic connections
If two connectors exactly overlay each other on a report, a database connection is generated
automatically.
6.4 Defining graphical properties
Defining graphical properties of connections

When necessary, you can change the graphical properties of connections you have dragged
to the report.
1. Right-click on a connection which is located on the report and select Options| Graphical
properties.
2. In the window that opens you can edit the width, line type, level and further parameters
that consider the design of the connection:
Connections
6.5 Parallel connections
Defining graphical properties of potentials

You can also edit the graphical properties of potentials you have placed on the report.
1. To do so right click on a potential which is placed on the report and select Options|
Graphical properties.
2. In the window that opens you can e.g. edit the width, line type and the color of the
potential:
6.5 Parallel connections

When clicking the Connector tool, a dropdown menu appears in the menu bar with the
numbers from one to five. In the menu you select the desired number of parallel connections.
This involves the selection of the maximum number of connections to be made. The
Connection tool checks the actual situation and also reduces the number of parallel
connections, if necessary.
Example: If the Connection tool is set to "3" and the user starts to make a connection to a
motor that only has two connectors, then only two connections are drawn.
The parallel connections have a preset gap of one grid point. If the grid is increased, the gap
of the parallel connections is correspondingly increased as well.
The Connection tool changes this gap if required. Example: If the Connection tool is set to
"2" and the user starts to make a connection to a motor that has two connectors, the two
connections are set precisely to the connectors of the motor, regardless of how far apart they
are.
Connections
6.6 Open connections
6.6 Open connections

Open connections are usually not allowed as a rule and are marked as "inconsistent"
(marked in red).
But there is an exception:

1. Single sided open component connections with a reference.
Reference brackets / Collected references

If multiple open connections point to the same target, you can set a reference bracket:
Collected references can also be connected with the help of the mouse menu in the same
way as for other connections. First from the mouse menu select the | Connection | Mark...
command and then the | Connection | Set... command.
Note
If a connection has a reference bracket, then the edit table
BRACKET(LOGPOT)REFERENCE is evaluated for the texts of the connection arrow
symbol. Is the edit table not existent an empty string will be put out.
Textfunction RefHierarchical
New: %N RefHierarchical(x)
Connections
6.7 Wiring direction
This controls the reference brackets in the ELO drawing type. X = Number of levels which is
searched to the top, if the referenced object is not placed. Example application: a component
is already placed, the connector derives from a not placed element.
Open connections with logical potential

The cross-reference symbol is swapped if an open connection owns a logical potential.
Without potential:
With potential:
Potentials without connected devices

If a connection still does not have any connected devices, a logical potential can still be
specified nonetheless. Do this by marking another potential, select | Connection | Mark and
then allocating the connection with | Connection | Connect with....the connection to.
Half-open connections to the same device

Via the mouse menu Connection| connect with you can also connect different connectors of
the same device with each other. This e.g. makes sense if you are working with a complex
component whose symbol takes up a lot of space on the report. In this case it is
recommended to work with a lot of tear-offs. The references between the tear-offs are then
set with the |Memorize and |connect with functions in the graphic.
Adjusting reference symbols, respectively reference texts

In the already describe cases, the on the reference end output information is taken from the
standard table @System| @Connection. If you want to see a different text or want to edit or
format an additional graphic or text, then you have to change the according entry in this edit
table. See also Volume 120, section Base project @System |@Connection (Page 49).
Aim
If connections are dragged onto a report, then it actually only matters that all physically
connected components are somehow also conected on the report.
In order to achieve to it is also permitted to make connections at any desired point on the
diagram to another connection.
Connections
In reality, it is not permissible to make connections only to connectors / terminals in plant

design and construction. It is illegal to simply make connections anywhere on a cable.
The planning on the report can be conducted far more quickly if you can simply make
connections "anywhere", but there is a gap in the information for the actual cabling in plant
design.
This information can be closed by means of the "wiring information". For that it is also
grahically displayed on the report on which component a connection really ends in reality.
Example
A simple form of motor switching with safety switches has been set up in the following
illustration. If you look at the connections of the separate safety switch at the bottom in the
illustration from a purely graphical point of view, it is not possible to tell with which
components it has been wired:
It is of course quite simple in this case, but it is a matter of the principle involved.
A "connection hook" is attached to the contact points of the connections to display the
missing information:
Now you can see at once that the safety switch is wired on the left to the motor (or the
terminal strip before it) and on the right to the drive:
Effect of the wiring direction in the engineering data

You can only tell on the report to which component a connection has been wired. However,
Comos goes beyond drawing management, and also manages the connectors by means of
the engineering data. The reports and the engineering data are reconciled automatically.
Connections
Thus if an object has been wired to a specific component, then this means that actual
concrete connectors have been connected to it in the report. The wiring is not restricted to
the report but also effects the engineering data.
See Volume 120, section Reconciliation of database and report connections (Page 69).
If you want the wiring to function, free connectors must thus be available at the components
involved. (In Comos an actual concrete connector can only be joined to just one counterpart
connector.) Nonetheless, with certain components auxiliary connectors are generated
automatically as required so that a connection can be closed.
Initial wiring direction

Wiring hooks initially run against the direction of the characters. As an example, a terminal
X1 is connected with horn H1:
If a cross-connection is now started to this connection, the wiring then points to X1:
Manually determining the wiring direction

You find an illustrated introduction to the connection hook / direction of wiring in Quickstart
EE, section "Construction (Design)". However, the principle is very simple:
● Start the connection on the other connection,
● does not set the second click in a right angle, but offset (here: offset to the right):
● and sets the next clicks in the usual way so as to continue and terminate the connection.
If the second mouse-click is offset to the left, the wiring correspondingly points in the other
direction.
Potential outputs usually do not have a wiring direction.
Connections
6.8 Displaying the connection direction
Retrospectively changing the wiring

Single-click twice on the connection until the grab points become visible. Enlarge the image
until you can clearly see the wiring hook. The wiring hook has its own round grab point,
which you can simply push onto the other side of the connection point:
Note
This action also changes the connector pin-outs in the engineering data!
6.8 Displaying the connection direction

If you have created a connection between two different devices, you can make the
connection direction of connection visible if necessary.
● To do so right-click on the sheet area and select | Options | Direction arrows visible.
Direction arrows appear along the connection:
In addition Comos offers the option to change the connection direction of an already created
connection:
● Do this by selecting the connection for which you want to change the direction. Open the
mouse menu and select | Options | Change direction.
Connections
6.9 Connection / wiring for terminal bridges
6.9 Connection / wiring for terminal bridges

See also Volume 120, section Bridges (Page 37).
Default case: Connecting terminals directly

If terminals of a terminal strip are connected, then an "internal connection" is created initially.
You can switch to various brdige types with the help of the mouse menu.
The introduced mechanisms function both when the terminals are joined by an internal
connection and also when the terminals are joined by a bridge.
Example: A connection runs from terminal 1 to terminal 2
A new connection is dragged from terminal 4 to the corner:
Terminal 4 is automatically connected to terminal 2:
Finally, terminal 4 is connected to the connection line:
Comos automatically corrects the wiring direction. Terminal 3 is now connected to terminal 2
and to terminal 4:
In other words: The wiring of terminal 2 and terminal 4 was removed automatically.
Please note: The wiring of the terminals is conducted on the basis of the position on the
report. It is of no importance that the terminals in the above example have sequential
numbers. If the terminals on the report had the names 3-17-6-1 in relation to the order, the
terminals would be wired in this order.
Connections
6.10 Document cross-references
Special case: Creating bridges indirectly

Devices and terminals can also be formed by auxiliary connectors, so it seldom comes to the
state that a "connector is missing".
You can make use of this capability to generate bridges indirectly and not, as in the above
example, by directly connecting and bridging the terminals.
We already stated above that you can input a wiring direction by means of the "connection
hook". Thus cross-connections have a preset direction for the connection hook.
If you always connect all devices going outwards from the terminal strip and then create
cross-connections, the wiring then points to the terminals:
You only need to mark the connection and to switch it over to a bridge by means of the
mouse menu.
Alternatives
It is simpler to set bridges in the database. Predefined columns for bridges are already
provided there, see Volume 120, section Bridges (Page 90).
Aim
Document cross-references indicate on which report a connection is continued. Logically

enough, document cross-references are only of interest if the diagrams are so large that they
cannot be drawn on a single report. Fundamentally there are two types of cross-references:
Connections
● Cross-references from connections

● Cross-references from potentials
"Cross-references" should not be understood literally in the case of potentials, since in a
sense they "refer" to themselves and thus make it possible for a potential to reach across
multiple sheets. See Volume 120, section EE |D |I |B Potential rails (Page 20).
"Direction" of document cross-references

Directions are of no importance for the functional wiring of components. A correct diagram is
also correct if it is inverted.
It makes no difference regarding the consistency of the data as to which document cross-
reference is drawn on the "left" or the "right". The only thing that matters is that the document
cross-references on the report in their totality are consistent with the links in the database.
That is why both of the following drawings are valid:
Definition of the Comos standard: The order of the cross-references on the report results
from the device labeling. To the left is the predecessor, to the right the successor. In the
example you find the specification "(2.1) -M3". In this example 2 stands for the sheet, and 1
for the path (hence the column). M3 is the owner.
Creating references for reports with multiple sheets

For the reference creation Comos considers that a report may have multiple sheets.
Herefore you have to have selected the "EE/I&C References" tab from the Document order
tab, and there the sheet number setting:
Connections
Example:
You have four reports. Of these four reports the first three are single sheets and the fourth
one has two sheets. You now set a reference from the first report to the second sheet of the
fourth report. The result in the reference is: "5.1". There 5 stands for sheet and 1 for the path
that is referenced:
Bridge references: DocumentOrderBridgeReference

References to half/open bridges are as a default labeled in a way that the reference is built
according to the placing information.
If you do not want to have the bridge references calculated via the placing you can turn off
the option via the options script of the report.
DocumentOrderBridgeReference = False (Default):
The bridge references are only calculated via the placing.
DocumentOrderBridgeReference = True
The bridge references are first calculated via the placing. If this does not work, then the
reference construction is conducted via the Comos connectors.
Display or calculation of the cross references

The display or the calculation of the references can be influenced, see Volume 20, section
7.5.6:. EE/I&C References. Therewith the order can also change.
Display or calculation of the BMK

The display of the manufacturer device labeling can be influenced by the user. For more on
this see Volume 20, section 7.5.4.4: Device labelling group.
Display or calculation of the cross references

The display or the calculation of the references can be influenced, see Volume 20, section
7.5.6:. EE/I&C References. Therewith the order can also change.
Display or calculation of the BMK

The display of the manufacturer device labeling can be influenced by the user. For more on
this see Volume 20, section 7.5.4.4: Device labelling group.
Subset of document references

When working with references, then not all connections in the database have to be drawn on
the report. References in Comos have multiple lines.
Connections
6.11 Reconciliation of database and report connections
Example:
The following horn has a connected auxiliary connector on connection 2:
If a connection for a reference is drawn on the report on connector 2, then both counter
connectors are automatically displayed:

The connections that were dragged onto the report reflect the connection of the connectors
in the database but are not identical with them from a technical point of view. It is thus
possible to have report connections without their corresponding counterparts in the
engineering data and vice versa.
Read/Write mode controls the extent to which the report connections and the joining of the
connectors in the engineering data are reconciled.
Read/Write mode
A drodown menu also appears when the Connection tool is called:
Connections
● "Read"
The connections must have been set in the database. The connection line on the report
searches for the corresponding connection in the database. The connection line is
consistent if the connection is found. With this option the connection lines in the report
have no effect on the database.
Consistent connection: blue
Inconsistent connection or
no connection in the database: red
● "Read / Write
"As described above, if no connection is found, the connecting line generates the
connection between the objects in the database. With this option the connection lines
write into the database if no connections had been set in the database before.
Consistent connection or
no connection in the database: black
Inconsistent connection (the connection in the database is connected with another
object): red
● "Write"
A connection between the engineering objects is generated if no connection is found in
the database. If a connection is already entered at the object connectors, this connection
is deleted and overwritten. With this option the database information is always overwritten
by the diagram connection lines.
Color: green
Subsequently resetting the Read/Write mode

This connection option can normally be switched for an existing connection via the mouse
menu:
You can use ShowLineModeControl in the options script of the Master Report to prevent the
mouse menus to switch the connection mode from being visible in interactive reports .
Note: When you delete a write or read-write connection, the OwnPotential pointer on the
Comos connector is deleted. This produces the following desired effect: Place fuse, draw
connection => potential is displayed, delete line and redraw => this turns red because the
potential pointer on the Comos connector was deleted.
Connections
6.12 Connection dependent objects
Intended and unintended differences

As explained above, the technical differences between report connections and connections
involving connectors can lead to differences.
● Connectors are joined in the engineering data, but there are no associated report
connections
This is usually no problem. However, this can be an inconsistent if only a part of the
connections involving connectors exist as connections on the report.
● Report connections without associated connected connectors
In this case the report connections are marked in red (inconsistent).
6.12 Connection dependent objects
Aim
To create a template that you can copy into the engineering data and in which you can
reconcile the objects on the report with the objects in the engineering data with just a few
mouse-clicks.
Implementation
The objects are marked as "Connection dependent" on the report by means of the mouse
menu:
Marked objects of this type are displayed in blue (synonymous with the display of read-type
connections in blue).
Example
The following example is easy to set up as a model and demonstrates the technique.
A horn is to be connected to a terminal.
The terminal is marked and labelled as "Connection dependent" in the mouse menu.
Connections
6.13 Borders of the "connection dependent objects" technique
Effect: the terminal turns blue:

Next, the horn is joined to any desired terminal via the connectors in the engineering data.
Now the horn is connected in the engineering data, but not on the report, and the final step is
to draw a connection in the report between the horn and the terminal. The connection must
have the "read" option:
Effect
Effect
the connection dependent terminal on the report is joined with the terminal from the
engineering data. The terminal information is now output on the report. The connection on
the report is consistent, since it matches the corresponding information on the connection
and the connectors in the engineering data.

There are a number of different cases in which it is not possible to work on the report with
connection dependent objects.
Please note: The following cases are based on connections with the "Read" option. As a
rule, there will be no inconsistency in the case of write-type connections, since the details
from the report simply overwrite the engineering data until it matches.
Auxiliary connectors
Example: A device owns a connector and an auxiliary connector. For example, there is a
connector CP1 and CP1(1) at the device; from a technical point of view, CP1 and CP1(1)
have been short-circuited.
Connections
In the default case a connector "2" now appears twice in the properties window of the
"Connectors" tab, since the connector and the auxiliary connector own the same label. This
display is consequently meaningful since it involves short-circuited connectors from a
electronical point of view, and these are treated as connectors.
Both are connected to a terminal respectively.
Two connection dependent terminal exist on the report and these are connected with the
device. Effect: Both of the connections are marked as inconsistent on the report:
Reason:
A piece of information is missing if two connection dependent objects run together at a short-
circuited connector: Comos cannot determine which of the connection dependent terminals
on the report is to be allocated to which terminal in the engineering data. The engineering
data is correct, but Comos cannot transfer the engineering data onto the report. For that
reason the connection dependent terminals are not allocated on the report and the
connections are displayed in red.
Assessment in practice:
The case described above will not occur often, since in practice the terminals are usually
connected on both sides. If the second connector supplies useful information, Comos can
allocate the terminals and the data thus becomes consistent:
Connections
Differing number of connections

If two connectors have been joined in the database but only one connection has been drawn
on the report, then there are in fact two errors:
1. Too few connections have been drawn on the report, and
2. the connection drawn on the report cannot be allocated unambiguously to one of the two
connectors that were joined.
Thus the following case is inconsistent:
You can create a similar case if you draw more connections on the report than actually exist
in the engineering data.
Bridges
Bridges are not evaluated in order to produce a consistent connection logic.
Example:
A light and a fluorescent lamp are connected via terminals to the same terminal strip:
If an engineering object is assigned to one of the two components (for example, the light),
then in theory a consistent logic could be set up. Starting from the specific component, first
the terminal is found, then the other terminal is found via the bridge, and from there also the
fluorescent lamp in the engineering data.
But if you try this, you will get the following result:
Connections
6.14 Connection information
Reason:
Bridges very often include more than two terminals and thus are not unique. For that reason
bridges are not evaluated in the connection logic.
6.14 Connection information
6.14.1 Bridges
See Volume 120, section Connection / wiring for terminal bridges (Page 65).
6.14.2 Potentials
See Volume 120, section EE| D| I Potential (Page 16).
6.15 Cables and wires / wire information without wires
6.15.1 Cables and wires / wire information without wires

EE connections on the report are not objects in themselves but only the graphical display of
two connectors that have been joined together. If you want to allocate additional information
to an EE connection (such as color, cross-section, type info), then there are two options
available for this
● Creating a cable object
The cable is managed separately by means of a cross-reference. See Volume 120,
section EE| D| W Cables (Page 28).
● Allocating the corresponding information to the connectors. The connectors pass this
information to the connection.
● Do this by marking the connection and select |Settings | Connection information... from
the mouse menu.
● In the window which opens you can select the information you need by using the edit
tables.
Connections
"Typinfo" is thus the information on the material structure and properties of the cable; this
information is managed in the form of a key.
See also Volume 120, section Connection information for connectors: Dialog window
"Characteristics for connections" (Page 88).
Technical background: The function is only offered if the selected connection (at least one
connection in the case of multiple selection)
● is no logical potential,
● is also consistent in the database (i.e., not displayed in red on the report),
● and the connection has not been allocated to a cable.
The cable object takes priority. If wire information already exists at the connectors and a
cable object has also been assigned to the connections, the information of the cable object is
then evaluated and displayed.
Disconnecting wires
Wires can be disconnected in the open properties window of the device:
● Mouse-click on the entry in the "Over" column and select the "Wire" mouse menu.
● Select the "Disconnect" submenu.
If a counterpart connection was set, there is the option of disconnecting the counterpart
connection, including the wire information, or of only disconnecting the counterpart
connection while retaining the wire information.
Alternatively, the wires can be disconnected in the opened properties window of the cable:
● Mouse-click on an entry and select the "Disconnect" mouse menu.
Changing the cable type

From a database point of view, the information on the cable is not part of the logical chain
between the devices. The information on the cable is managed by means of a reference. For
that reason the cable type can be changed at any time without needing to adapt the devices
or connectors.
If you wish to substantially retain the wires, then drag within the engineering project in the
properties window of the cable that had been created a new base object onto the "Base
data" tab. The wires are reallocated from top to bottom and the information is retained if at all
possible. If the new cable type has fewer wires than allocated before, then information will of
course be lost.
6.15.2 Shielded cables

See also Volume 120, section Shield (Page 33).
Connections
Display and labeling

A shielded cable is displayed as an flat oval in the diagram. The wires are automatically
assigned to the connections when the shielded cable is dragged over a connection. Thereby
the label for the wires (here: "2" next to the left-hand connection and "1" next to the right-
hand connection) is written next to the connection:
The labels have following meaning:
-W7 Designation of the cable, whereas the minus sign is the separator taken from the
project options. This designation can be generated automatically.
(N)YM-J Subtype of the cable. This information is taken from the "parent object".
10x1,5 Number of wires and cross-section. This information is taken from the "Name" field
of the object.
The wires are displayed in the database together with the allocated connections:
Changing the shielded cable

Grab points appear when you single-click twice (no double-click!) on the shielded cable:
The shield can be made broader with the help of these grab points. Do this by left-clicking on
the dot, holding down the button and dragging the grab point to the new position.
In addition to these three designations ("-W7", "(N)YM-J" and "10x1,5") a rectangular point
appears for each of them so that the designation texts can be moved.
In addition, a round dot can be seen at the far left. The shielded cable can be rotated
vertically with the help of this dot.
Allocating screening / shields

Drag the shielded cable on the diagram across one or more connections.
The connection is automatically allocated to a free wire. If you wish to allocate another
connection that is spatially nearby on the diagram, you can simply change the width of the
shielded cable.
Connections
If you wish to allocate a connection that is somewhat further away spatially on the diagram,
drag the same engineering object (not an additional shielded cable from the base objects!) a
second time onto the diagram.
You can "open" the shield if the connections on the diagram are so far apart that they cannot
all be comprised by the shield or if the connections are on different reports, then:
● Select the shields individually (not the group)
● | Settings | Start of the Shielding.
(The hook should disappear.)
The result is that the left rounding is removed from the diagram:
If you were to deactivate the | End of the Shielding command in addition, the shielded cable
would also be displayed as open to the right. Thus you can always tell from the diagram
where the shielded cable is complete or whether it has additional connections at another
point in the diagram.
6.15.3 Combining cables in cable channels / routes

A "route" is an additional piece of information for a cable. A "route" engineering object is
created in the usual way in the engineering project.
Base object: EE |K Route

The next step is to open the properties window of the cable that is to be allocated to the
route:
Connections
6.16 Direct connecting
The route is dragged from the Navigator into the properties window of the cable, onto the
"Implementation" field. Confirm the action with [OK] and close the properties window.
Alternative allocation of routes

Using drag&drop in the Navigator, simply drag the route onto the cable and release the
mouse button there.
Result in the engineering project

All cables that are within it are shown in the Navigator under the route.
A "processing object" is displayed in the Navigator under the cable and under this is the list
of the routes via which the cable is led.

Does this still need to be described?
Connections
Working with reports 7
7.1 Special points concerning circuit diagrams
7.1.1 Superimposing and hiding information
BMK visible / invisible

Mouse menu on a selected object (or for a selected amount) | Settings| BMK visible
Turns the device labels on or off. Usually the device name plus the name of the owner is
used as BMK.
The device label is calculated in ROUtilities. If you turn off the "|BMK visible" option, then
ROUtilities does not return a text for this symbol, but an empty string..
Exceptions
following %N texts are always returned:
● %N Device.Name, see Volume 60, section 10.5.17: Device
(In contrast to e.g. DevName, which is covered by the "|BMK visible" option.)
● %N DevSpec, see Volume 60, section 10.5.6: ComosDevSpec
● %N ElmSpec, see Volume 60, section 10.5.7: ComosElmSpec
● %N ComosSpec, see Volume 60, section 10.5.9: ComosSpec.
Layers in EE reports
Reports can have layers, see Volume 60, section 8.15.1: Setting up layers for reports. In the
symbol construction the symbol text is then allocated to a layer (thus in each text, each line,
etc.). See Advantage of layers and labels, p. 10-185. In the report itself you can hide/unhide
the layer and control what is supposed to be visible, see Volume 60, section 8.15.2: Using
layers.
Identification keys in EE reports

Graphical objects in EE reports can be identified by means of identification keys. Therefore
in the symbol script you enter one or more Header.Class: Advantage of layers and labels, p.
10-185, dropdown menu Label:, p. 10-188. Identification keys are a relative old technique in
the EE environment and therefore often have pretty awkward names.
Regard from the Comos side used name (see Header.Class, p. 10-224). Important
identification keys are:
Working with reports
● Shieldings
Start of the shielding: "eSB" (electronical Shield Begin),
End of the shielding: "eSE" (electronical Shield End).
The shielding is located in the base data in: EE| E Elements| W Wires| SH Shield. When
you open the symbol script you find the following code:
– Header.Class = "eSB"
– DrawArc p5, p3, p1
– ...
– Header.Class = "eSE"
– DrawArc p6, p2, p4

Therewith a semi circle is drawn in the right of the symbol and labeled with the "eSB"
key. Afterwards a semi circle is drawn on the left and labeled with the "eSE" key.
If you select the select the mouse menu of the shielding on the symbol of the report
and turn "|Settings |Begin shielding" off, then the eSB key is hidden: the right semi
circle is missing.
If you select the mouse menu of the shielding on the symbol of the report and turn
"|Settings |End shielding" off, then the eSE key is hidden: the left semi circle is
missing.
● Device label
– "eBC" (electrical component Cable),
– "eBT" (electrical component)
● General labelling of graphics:
– "eGR" (electrical graphic)
Different Header.Class can be used within a script. While working off the script the
corresponding class is switched. In doing so different components of a symbol can haven
different identifiers.
Editing fixed texts in reports

Fixed texts can be edited in reports via a command in the mouse menu |Options| Edit
symboltexts. A requirement is that the fixed text has some sort of Header.class. Is a fixed
text placed in the symbol and as usual the the default "New Text" is replaced by another text,
then the text gets a random Header.class from Comos. This is sufficient.
7.1.2 Placing devices
Modifying the display of the devices

Devices can be edited as usual in the EE area: The grab points appear once you single-click
twice on the object. In this way you can rotate the object and move the texts.
Mouse menu | Settings
| Search text
See Volume 60, section 18.2: Settings.
| Connection dependent
If this option is assigned to engineering objects, the objects then only function as
placeholders. They are shown in red in the interactive report.
The objects change each other according to the dependency, for example, via the
connectors. A chain of dependencies of this type is usually triggerd when an object in the
chain is redefined.
See Volume 120, section 5.12: Connection dependent objects.
Mouse menu | Graphical settings

This mouse menu only appears for objects that have predefined "additional symbols". A call
is included in the symbol script of the base object:
DrawText p6, "*V*P S:SYS.ADDITSYMBOL*", 0, 2
The commands change the display of the device; typically the symbol is supplemented by
additional graphic components (hence "additional symbol").
Examples: |EE |S Switches..
7.1.3 Revising and controlling devices
Modifying the display of the devices

Devices can be edited as usual in the EE area: Grab points appear when you single-click
twice on the object. In this way you can rotate the object and move the texts.
Mouse menu | Settings | Search text
See Volume 60, section 18.2: Settings.
| Connection dependent
If this option is assigned to engineering objects, the objects then only function as
placeholders. They are shown in red in the interactive report.
The objects change each other according to the dependency, for example, via the
connectors. A chain of dependencies of this type is usually triggered when an object in the
chain is redefined.
See Volume 120, section Connection dependent objects (Page 71).
Mouse menu | Graphical settings
This mouse menu only appears for objects that have predefined "additional symbols". A call
is added to the symbol script of the base object:
DrawText p6, "*V*P S:SYS.ADDITSYMBOL*", 0, 2
The commands change the display of the device; typically the symbol is supplemented by
additional graphic components (hence "additional symbol").
Examples: |EE |S Switches..
7.2 Special points regarding layout diagrams
7.1.4 Setting pointers in the report / allocating information

This tool is used to retrospectively modify objects in the interactive report.
This tool offers the following options, for example:
● Allocating a unit / location to an object or changing the allocation,
● allocating a potential to a connection
see Volume 120, section EE| D| I| A Potential (Page 16).
● Changing the base object.
● Changing the engineering object.
Simply drag the desired new object with the Object tool onto an object on the drawing area.
The addressed object in the interactive report changes its color.
If another base object or engineering object was assigned, then the display of the symbol in
the diagram also changes accordingly. Connections are retained as far as possible.
7.2 Special points regarding layout diagrams

See Volume 130, section 1: Cabinet engineering.
7.3 Special points regarding single line diagrams
7.3.1 Report template

Application = "ELO.SLINE"
7.3.2 Allocating ELO connectors and single line connectors

In the properties window of connectors of types "EE/I&C" and "Single line" there is an edit
field if both EE/I&C connectors and single-line connectors are available in a base object. At
EE/I&C connectors the field is called "Single line connector"; and with single-line connectors
the field is called "EE/I&C connectors".
You can allocate precisely one single-line connector to an EE/I&C connector, while each
single-line connector can have multiple EE/I&C connectors allocated to it.
All connectors must belong to the same base object.
Object connections (connectors) 8
8.1 Definition of connection
Connections are the logical cross-references of objects that have been set in the database.
Existing connections can be checked at the "Connectors" tab, which are always displayed
when working with base objects but is only displayed when required with engineering
objects.
Connecting lines in the diagram are to be distinguished from connections: connecting lines
represent (database) connections, but are not identical to them. Thus it is possible for the
diagram to have (database) connections without connecting lines and also connecting lines
without (database) connections. The function logic only works if the (database) connections
have also been set.
Connectors always have one of the following states: "Input", "Output" or "Neutral". A
connection without one of these states cannot exist.
8.2 Setting connections in the Navigator
Joining connectors
The idea concerning this procedure is to make the connectors of both devices visible in the
Navigator and then to edit them by using drag&drop.
Use drag&drop to drag a connector onto another connector.

This procedure can only be used to select items individually.
Disconnecting a connection in the Navigator

Mouse-click in the Navigator on one of the linked connectors and select the | Disconnect
Connection mouse command.
Condition: The connector was not set via an interactive report but via the Navigator or the
"Connectors" tab.
Allocating connection information in the Navigator

In the Navigator a connector can be dragged onto a signal or a logical potential by using
drag&drop. The pointer is set automatically. This also functions vice versa.
Object connections (connectors)
8.3 Working with the Connectors tab and the Navigator
Display in the Navigator

If the connectors in the Navigator are not displayed directly underneath the owner, the full
label ("FullLabel") is then displayed instead of the label ("Label"). Example: Signal; Potential.
It is not necessary to input the details of the signal after the connector if the connector is
located directly under the signal.
8.3 Working with the Connectors tab and the Navigator

It is more convenient to open the properties window of one of the two objects that are to be
connected.
Connecting by means of drag&drop

First open the properties window of one of the two objects by using the mouse menu (or by
double-clicking). Switch to the "Connectors" tab.
Then select the second object in the Navigator and open the tree structure in the Navigator
until the connectors are visible.
Now one or more connectors can be dragged by means of drag&drop:
There are two options when making a multiple selection:

1. A multiple selection is only made in the tree structure. In the properties window the free
connectors are allocated in the due order, this being the order in which they had been
sorted on the "Connectors" tab.
2. A multiple selection was made both in the tree structure and also in the properties
window. In such a case the database tries to allocate the selected connectors in the due
order.
3. A corresponding warning message is put out if the number of the relevant selected
connectors does not match. If you decide to carry out the action regardless, the
connectors are processed in due order until the smaller of the two groups has no
connectors left.
The method of using a properties window in connection with the Navigator also allows
convenient sorting functions. You can control via the symbols which connectors are to be
displayed in the properties window and sort the list in addition.
8.4 Working with two properties windows
Disconnecting connector cross-references

Connections can be disconnected in the open properties window:
● Mouse-click on an entry in the "Connected with" column and select the "Connection"
mouse menu.
● Select the | Disconnect submenu.
Condition: The connector was not set via an interactive report but via the Navigator or the
"Connectors" tab.
● If you have already set the wires, you can keep the cable information with "|" Disconnect
(Retain Wires).
8.4 Working with two properties windows

There is the option to set connectors completely without the help of the tree structure by
using two properties windows.
Normally only one properties window is opened, meaning that double-clicking on a second
object displaces the information on the first object in the opened properties window.
The "Keep visible" switch on the top right-hand corner allows you to open multiple properties
windows simultaneously.
Activate the relevant "Connectors" tab once you have opened both properties windows. Now
you can use drag&drop to drag one or more connectors from one window into another.
Fundamentally speaking, two properties windows behave in the same way as just using one
properties window in connection with the Navigator. However, you now have two options
available to filter and sort information. For example, you can only display inputs in the first
properties window and only outputs in the second one.
This method is especially useful for two-shield solutions, since one of the relevant properties
windows can be positioned on one of the two shields.
Disconnecting connector cross-references

Connections can be disconnected in either of the two open properties windows.
8.5 Working with the "Connect device" dialog window

The last option is a method that is very similar to one using two properties windows. Select
the | Extra | Detail | Connect device menu. Use drag&drop in the dialog window to drag an
object into the left-hand window half and the other object into the right-hand window half.
The order and the choice of right or left is entirely up to you. The result is that the dialog
window looks very much like two opened properties windows.
The procedure now is exactly like the previously described case.
8.6 Connection information for connectors: Dialog window "Characteristics for connections"
The advantage of the Connect device dialog window is that chain connections can be set
more quickly or that large numbers of connections can be handled: The contents of the
window are change very quickly when a new object is dragged into the dialog window.
However, it takes a comparatively long time to exchange information in properties windows.
The "Connect device" dialog window saves working time if the object to be edited is
frequently changed.
8.6 Connection information for connectors: Dialog window

"Characteristics for connections"
This dialog window is used if you are not working with cable objects but instead when the
connection information is to be written to the connectors. See also Volume 120, section
Cables and wires / wire information without wires (Page 75).
Procedure
● Set a start object by means of drag&drop.
● Write the desired texts into the edit fields "Cable type, Cross-section" and "Color".
● Select the desired option for "Overwrite".
The dialog window writes the details into the system-internal attributes of the connectors.
(These attributes are thus not visible on an Attribute tab of the base object.)
The "Wire cross-section" and "Wire color" columns on the "Connectors" tab can be made
visible by means of the mouse menu. The information that had been set in the dialog window
or which had been set in the report via the | Settings mouse menu for the connections is
displayed in these columns.
Connector with a wire but without a counterpart connection
The wire Information is managed independently of the connection information. Thus there
can be a connector in which the wire information has been set but which nonetheless has no
connection. Such a case is indicated by a red cross with a question mark on the
"Connectors" tab.
Subsequent changes
"Overwrite"
The "Determine information for connection" dialog window can be used multiple times on
engineering objects. If the option has been deactivated, the information for all objects that
had already been processed is retained. If the option has been deactivated, the information
on the cross section and color is overwritten with the new inputs.
8.7 Preallocating connectors with logical potentials
Retrospective setting of a cable

If a cable object (and thus wire information) is retrospectively allocated to the connector, the
information of the cable is taken over. In other words: the information of the cable object
overwrites the information that had been written to the connector attributes.
8.7 Preallocating connectors with logical potentials

Connectors can be prepared in such a way that the allocation of a potential already exists
when the engineering object is created.
● Open the properties window of the base object. (if necessary switch to the base project).
● Switch to the "Elements" tab. The logical potential must exist as an object, a cross-
reference is not sufficient. For that reason you select the | New command from the mouse
menu.
● Input the following details:
Class Device
Name Name of the connector, e.g. CP1
Label Any
Subclass Potential
virtual Off
Note
The connector and the logical potential created on the "Elements" tab must have exactly the
same names!
Result in the engineering project

When the engineering object is created, the connector gets the logical potential with the
exact same name, unless a logical potential had been set already.
The "Log. potentials" column must be made visible by means of the mouse menu so that you
can see the result on the "Connectors" tab.
Potentials support the "NestedLabel" function.
Effect:
For example, if there is a signal under a fuse, the label of the fuse is prefixed to the potential
label.
8.8 The Strip tab

See Volume 120, section EE| D| X X Terminal - / plug strips (Page 35).
8.9 Terminals and terminal strips
8.9 Terminals and terminal strips

The "Strip" tab groups the connectors of all terminals located underneath.
Schemes
Schemes can be saved for terminal and terminal strips, see Volume 120, section Schemes
for the list window (ScanDevices) (Page 116).
Use terminals for AutoLoop / AutoConnect

The "Marshalling number" attribute was formerly used when marshalling connections. Thus
terminals that belong to the same item, for example, were connected automatically. This
functionality is to be implemented in future via the AREA name.
8.10 Bridges
See also Volume 120, section Bridges (Page 37).
The "Connectors" tab of the terminal strip is opened first to set a bridge. The terminals that
are to be connected by a bridge are selected on the tab:
Two bridge categories are managed for each terminal, an internal (on the left) and an
external bridge (on the right). The internal bridge should thus symbolize the internal
connectors, namely, the connections running from the terminal into the interior of the cabinet.
Select the mouse menu in the left-hand area of the list window to get the | Bridge (internal)
menu:
According to the use of the mouse menu in the right area.

The same types of the relevant bridge are offered in both menus. Each brdige type is
symbolized by its own color:
Blue Wire bridge or also ridged bridge

Red Switching bridge, open
Green Switching bridge, closed
These predefined colors can be changed, see Global settings for bridges below.
8.11 Product data and manufacturer devices
If bridges are set and deleted repeatedly, this may lead to display problems. Select the
| Update (Bridges) mouse menu if bridges can no longer be displayed for any obvious
reason.
Mouse menus on the Strip tab
| Change bridge type This option is only available if you right-click precisely on a bridge that
had been created.
You can switch between the single bridges, and the symbol color also
changes when a switch is made.
| Insert into the bridge A bridge connector point is inserted into the marked bridge. Exactly one
bridge must be marked so that the menu item becomes available.
| Disconnect bridge The bridge is removed completely.
| Disconnect from the A bridge connector point is removed from the marked bridge. Exactly
bridge one bridge must be marked so that the menu item becomes available.
| (Un)mark bridge Marks or unmarks the selected bridge. The bridge does not need to be
selected completely.
The cursor must be positioned exactly on a bridge, and then the
functions in the mouse menu can be called by right-clicking. A marked
bridge is displayed in violet.
Calling the function again unmarks the bridge.
| Group bridges A single bridge that contains all bridge connector points is made up
from several bridges of the same type. All bridges that are to be
grouped together must be marked.
| Optimize bridges Simplifies the bridges. A bridge is deleted if there is another bridge of
the same type that the first bridge is a subset of. The bridge information
is thus not lost, since this bridge switching likewise exists at another
bridge.
| Bridge information Shows the switching information for the bridge that had been clicked
on.
Inserting extra columns for bridges

Three columns for internal bridges and three columns for external bridges are provided in the
default settings. You should use the | Columns | Expand Bridge Columns menu if you require
a greater number.
Global settings for bridges

Bridges are controlled via a table in the system project. The details in this table also
determine which colors are used to display the bridges on the "Connectors" tab.
8.11 Product data and manufacturer devices

See Volume 120, section Product data and manufacturer devices (Page 125).
8.12 Other auxiliary tools
8.12 Other auxiliary tools
8.12.1 Change per rule:name, label

See Volume 120, section Ruplan (Page 97).
Evaluation (order lists / materials lists / parts lists) 9
9.1 General
Only objects that meet the following criteria are taken into the above-mentioned lists:
1. The objects are in a direct ownership relationship, i.e., cross-references are not evaluated
2. Only objects that are within the unit structure or location structure respectively on the unit
or location side respectively are evaluated
3. A base object exists for the engineering object
4. The engineering object is not of type "Potential"
5. The engineeing object is not of type "Cable".
6. It has the "Installation data" tab.
7. It has the "Manufacturer data" tab.
8. It has the "Delivery data" tab.
9. The "not order relevant" property is not active.
10.The "Article number" field is not blank.
9.2 The Settings tab

Select the "Report" tab and from there allocate to the "Report template" field the template
CRP | AWR | PPC | PPC.1 Parts list by means of the button on the right.
Sorting by Determines the sorting criteria that are to be used later in the
list. Regard the order!
[Reset] Deletes all previous inputs for this options group.
Evaluation (order lists / materials lists / parts lists)
9.3 Materials lists
Output with Specifies whether the output is to be made with or without strips
 Terminal strips / plug strips and terminals/plugs.
Accessory Specifies whether the output is to be done with or without

accessories.
Page break Specifies whether there is to be a page break if the contents of
the first sort criteria change.
Unit Selection between always, never or matched with the report
object.
Location: Selection between always, never or matched with the report
object.
List type Determines the list type, selection between order list, materials
list or parts list.
9.3 Materials lists
Columns
Position, material number, device description, manufacturer, unit price
All devices that can be ordered are listed, devices with the same part number are grouped
together for output, terminal strips and plug strips as well as accessories are dissovled by
their own allocation and are listed.
9.4 Order lists
Columns:
Position, number, order number, order text, manufacturer, price, total
The order list behaves like the material list, but it only considers the manufacturer devices,
i.e. the ISREQUEST option must be set to FALSE.
9.5 Parts lists
Columns
Position, unit, location, name, description, manufacturer, order number, device description,
price
All items are listed individually, terminals and plugs are sorted by type underneath a strip.
Accessories are sorted underneath the devices, this is made clear through "+" in the Pos
column.
Miscellaneous 10
10.1 Translation / language management
See Volume 20, section 17: Language management (localization).
10.2 Rights and license management

The EE module requires an EE/I&C license. The EE/I&C license is used when:
1. Basic operations are carried out with ELO connectors (connect, disconnect, edit wires or
potentials)
2. connectors get signals or process the signals of the connectors
3. one of the actions 1. or 2. is carried out in the properties window of engineering objects
(device)
4. an interactive report is opened with write access (as before)
5. the "Marshaling Manager" or "Implement requirements" are opened
Note
"Signal tracking" is a read-only method and does not require an EE/I&C license.
For completeness, we want to remind you of the method concerning the license query:
licenses are drawn from the floating license for each work session. If Comos is opened
several times on a workstation, then several licenses will also be drawn, depending on the
involved action.
For reports there is the | Open Read Only command to prevent a license from being drawn.
Miscellaneous
10.2 Rights and license management
Tools for E&IC (EMR) 11
11.1 Ruplan
11.1.1 Base objects and configuration

The base objects of the Ruplan import are located in Import | RUPLAN. The general
configuration of Ruplan imports can be conducted via the Ruplan configurator: Import|
RUPLAN| System| 002 Ruplan Configuration, tab "| Settings of the Ruplan import". (See
Volume 120, section Ruplan configurator (Page 101).)
11.1.2 Options and interface
11.1.2.1 Open the Ruplan import

In order to open the Ruplan import proceed as follows:
● In the Comos menu Plugins point to Mechatronics and then click on Ruplan import.
You can conduct the Ruplan import via the window which opens.
11.1.2.2 Structure of the Ruplan import window

In order to open the Ruplan import proceed as follows:
In the Comos menu Plugins point to Mechatronics and then click on Ruplan import.
You can conduct the Ruplan import via the window which opens.
Figure 11-1 In the lower area the settings for the Comos data is conducted:
Tools for E&IC (EMR)
11.1 Ruplan
11.1.2.3 The "Ruplan data" area

A complete Ruplan import consists of a symbol file, sheets and devices. However, it is not
always necessary to import all three categories. If symbols had already been imported and
have not been changed since, then you only need to import the sheets and the devices.
Selecting the symbol file

Proceed as follows to select the symbol file:
1. In the "Symbol file" column click on the button.

2. In the window that opens search for the folder which contains the symbol file, open it.
3. Click on the file and then on Open.
4. Click on Read .
After having clicked on Read a symbol preview is put out in the Plugin window.
Select the devices file

The device file contains descriptions regarding the engineering objects that are placed on
the sheets.
11.1 Ruplan
Proceed as follows in order to select the device files:
1. In the "Devices file" column click on the button.

2. In the window which opens search for the folder which contains the devices file and open
it.
4. Click on Read .
After having clicked on Read a preview of the device data is displayed in the Plugin window.
Select sheet file

Proceed as follows to select the sheet file:
1. In the "Sheet file" column click on the button.

2. In the window which opens search for the folder which contains the sheet file and open it.
4. Click on Read .
After having clicked on Read you get a preview of the sheets.
Translation file
The translation file serves to replace the placeholders of the type #. See also Placeholders in
section Conversions (Page 101).
Saving the identification key

The identification keys from Ruplan are imported and saved in Comos:
<comos>\ocx\ComosPlugIns\ KennAbbildung _RP .txt. See also Text marks in section
Conversions (Page 101).
11.1 Ruplan
11.1.2.4 The "Comos data" area

The following table gives you an overview of the control elements in the Comos data area.
Control element Explanation

Importing symbols This button starts the import of the selected symbol file. I.e. only after
clicking on this button Comos data is created or changed.
Importing devices This button starts the import of the selected device file. I.e. after clicking
on this button Comos data is created or changed.
Importing sheets This button starts the import of the selected sheet file. I.e. after clicking
on this button Comos data is created or changed.
Base data underneath Is the base data checkbox underneath System is activated, the
System imported base objects for symbol files underneath the Import| RUPLAN|
System are generated. If it is deactivated they are project specifically
stored, i.e. in the Import| RUPLAN| SY_Proj node.
Report template Select a report template from the document group Import| Ruplan. The
template is copied and the Ruplan template of the imported symbol file
is imported into this copy. The via the button selected report template is
displayed in the underneath located text field for control purposes. Prior
to importing the sheets, you can in the Comos data area define if all
sheets or only sheets of a certain area are supposed to be imported
(from: Start sheet, until: End sheet).
Cancel Cancels the import process.
Open log data Opens the automatically generated log file.
Target object Via this field a concrete target object can be selected, underneath
which the import is conducted.
Owner The "Owner" option is only evaluated if no target object is set. In this
case a unit or location is created directly underneath the project, and
the import is conducted underneath. On which base object the unit or
the location is based is defined in the Ruplan configurator.
11.1.2.5 Import
Import the symbols and devices into the base project. Afterwards you can import the sheets
into the engineering project. You have to ensure that the symbols and devices that are used
from the imported sheets are already available as base objects in Comos. If this is not the
case they are not imported correctly.
But you can "reload" base data into the engineering project. If the import data also contains
base data, then these are automatically created in the base project, even if the current
project is an engineering project: The base project is opened in the background and the base
data is entered there.
Currently the data is sorted into folders during the import. This applies to the "Owner" option
as well as for the "Target object" option.
Documents are sorted and arranged based on their sheet designations (AP_numbers). All
associated sheets and objects are created underneath a folder. The sheets and the Comos
objects with the device name are stored together in parallel.
11.1 Ruplan
11.1.2.6 Conversions
Text marks
The in the Ruplan files contained "text marks" are imported and matched with the in the
following file contained conversion table: <comos>\ocx\ComosPlugIns\KennAbbildung_RP.txt.
In this ASCII file you can define what is supposed to happen with the texts in Comos.
If the Ruplan file contains text marks that are not yet part of this table and you click the [Save
text marks] button, then these missing test marks are entered at the end of the file as "UU"
(=unknown). The user has to manually edit the file and has to define how these text marks
are supposed to be processed.
There are different options on how to further process the texts. Most of the time you will have
to assign a text to an attribute. Another option is to detect, by means of the text, if an object
is supposed to be created as a unit or a location.
Placeholders
If the import file contains placeholders for texts, it is checked in the translation file during the
import on how to replace these placeholders.
Background: This is not a translation into a foreign language. This file is used to replace
placeholders of type #. In Ruplan a placeholder is initiated by means of a # (hash or pound
sign). As a rule, placeholders of this type serve as variables, for example to insert a date.
The placeholders are replaced by the texts within the translation files in the course of the
import operation.
Object conversions
● Ruplan wiring symbols are replaced by dynamic connectors. Background: In Ruplan the
intersection and contact points of electrical cables are displayed by symbols of their own.
However, in Comos neither electrical connections nor the intersection and contact points
of electrical connections have symbols of their own.
● Ruplan cross-reference symbols are imported as objects and are created on the report as
text and graphics on layer 101. The usual connections and links are created within
Comos and can likewise be displayed or hidden.
● Polygon lines are imported.
● The attributes from the device file are written to the engineering objects as attribute
values.
● The unit name from Ruplan is stored in Comos as the unit label.
● The document attributes (hence the attribute of the plot frame) are taken over and are
displayed on the document.
11.1.2.7 Ruplan configurator

The general configuration for the Ruplan imports (i.e. the default settings for all Ruplan
imports) is conducted on the base data side via the following base object:
| Import| RUPLAN| System| 002 Ruplan Configuration, tab "| Settings of the Ruplan import".
11.1 Ruplan
"Settings of the Ruplan import" tab

The following is an overview over the attributes of the "Settings of the Ruplan import" tab:
Edit field Explanation

Base parameter
RUPSYS001 Reference object for the unit If no owner was selected for the concrete import:
The base project for the unit which is created
under the project node on the engineering side
and under which it is imported.
If an owner was set for the import: The base
object for the API folder, which is generated
underneath the owner and under which is
imported.
RUPSYS002"| "Reference object for the location Base object for the location or the API folder in
the location world; analog
toRUPSYS001"|"Reference object for the unit
RUPSYS003"| "Reference object for the report During the base data import: an empty report
template: template in which the template (the frame) is
imported, and is used to import the sheets later.
Individual parameters
RUPSYS004"| "Reference object for the dummy The document group in which the templates and
document group. the sheets are imported to.
RUPSYSAK01"|" Standard description for wires: Default description which is taken if an imported
wire has no description.
RUPSYSHK01"| "Identification key for base Identification key which defines that an object is
objects: imported as a base object.
RUPSYSKST01"| "Identification for a separator: Identification key which defines that an object is
imported as a separator.
RUPSYSBR01"| "Bridge type: All imported bridges get this type.
RUPSYSPOTZIEL"| "Identification key for potential Identification key which defines that an object is
counter target: imported as potential counter target.
RUPSYSPOTREF"| "Identification key for potential Identification key which defines that an object is
references: imported as a potential reference.
RUPSYSDokGrp| Identification key for the AP Identification key which defines that an AP
number: number will follow.
RUPSYSBMK| Identification key for BMK: Identification key which defines that a BMK
follows.
RUPSYSANL| Identification key for unit: Identification key which defines that a unit
follows.
RYUPSYSORT| Identification key for location: Identification key which defines that a location
follows.
RUPSYSCLASS"| "Set symbol class: Active:
If base objects are not classified (i.e. were not
imported with the "Device" class): During the
import of the device data you can search for the
entered identification key in RUPSYSHK01"|"
Identification key Base objects. For all devices
that have this identification key: The class of the
base object is set to "Device".
11.2 ECAD components import
Edit field Explanation

RUPSYSLOGPOT"| "Importing logical potentials Self-explanatory.
RUPSYSKNR"| "Identification key for channel Identification key which defines that a channel
number: number follows.
RUPSYSCON"| "Identification key for connection: Identification key which defines that a connection
key follows.
RUPSYSPOTART| Identification key for potential Identification key which defines that a potential
mode: mode follows.
RUPSYSPOTTEIL"| "Identification key for potential Identification key which defines that a potential
part: part follows.
RUPSYSUNITLOCATION"| "Creating units and The units and locations are also imported from
locations: Ruplan.
Thereby the in RUPSYS001| Reference object for
the units, or RUPSYS002| Reference object for the
locations are used.
Parameter for engineering objects
RUPSYSKab01"|" Reference object for cables: Base object for cables.
RUPSYSAder01"|" Reference object for wire: Base object for wires.
RUPSYSBI01"| "Reference object for sheet Base object for a reference to another project.
reference 1 (ext.):
RUPSYSBI02"| "Reference object for sheet Likewise.
reference 2:
RUPSYSBI03"| "Reference object for sheet Likewise.
reference 3:
RUPSYSCONINFO"| "Connection information: Base object for connection information.
RUPSYSANS01"| "Reference object for Base object for a connection reference.
connection reference 1:
RUPSYSANS02"| "Reference object for Likewise.
RUPSYSANS03"| "Reference object for Likewise.

Importing partial stocks from the ECAD catalog into existing or new Comos objects.
Preparing the import

The import operation is based on the control table in the base project "@1EA Catalog EE
| Import" which you can open via | Administrator| Base data| Standard tables.
The attributes from ECAD are allocated to the Comos attributes in this standard table. There
is no technical necessity for a 1-to-1 matching. The standard table is made up as follows:
Column 1: "Name" Each row of the standard table requires a unique name, but it does not
matter what the name is. As a rule, the name of the attribute is used
here.
Column 2: "Description" Here it is stated how the Comos attribute ist described, i.e., which entry
is to be given in the "Description" field. Please note: This column is not
updated automatically. If the descriptions of the attributes are changed,
the new descriptions must be input here manually. In any case the
value in this column is solely used for information purposes, the import
procedure also functions if there are incorrect entries.
Column 3: "Symbol" (Not used for the ECAD import. In general, a symbol that is used for the
Comos object can be created here.)
Column 4: "Value1" Full name of the Comos attribute used in the import (including the
name of the tab). The Comos attributes are located in the Base project
in:
@Y Catalog specifications |EE Electrical engineering |1 General
chapters
Column 5: "Value2" Name of the assigned ECAD attribute.
Column 6 and and the other imports that have no meaning for ECAD.
following:
If necessary, you can adapt the this to fit company internal needs.
Preconfigured import
When text files are created in ECAD format, each line of text has an initial marker ("tag").
The following tags are recognized and imported:
● NO (Main components)
● TD (Technical data)
● ZB (Accessories); can be controlled via options, see below for more details.
● DD (= Attributes under manufacturer on the Product Data tab)
K1 data sets (channels) are also imported. The following channel types are considered:
COIL, MAIN, AUX, PRIM, SEC, UNI and PCL.
Conducting the import

Use the | Administrator | Base Data| ECAD Components Import command to open the
following small dialog window:
11.3 Conversion IEC to JIC
"File"
Select a vrg file.
"Target"
In the "Target" field ypi set underneath which branch the data is to be created by means of
drag&drop. In other words: You must import one block of manufacturer devices at a time
underneath the relevant branch for the request. New objects are created underneath this
target node or else the attributes are updated in the case of existing objects.
The import procedure (adapting the data structure and the attribute values) has been set up
in such a way that the import function can also be used to update data that has already been
imported.
The options
● "Read accessories"
Lines with the ZB tag are imported and created underneath the main components (NO
tag).
Accessories are those devices that are available for a specific other device but are not
managed individually. Accessories are thus used as an "element" on the "Elements" tab
of another device from the catalogs. The main reason for adding accessories to another
device as an "element" is that you can thus automatically create complete order lists.
● "Log all"
A log file is created when an import operation is carried out. This file is located in the
same directory as that of the to be imported file. The file name of the log file is made up
of the name of the file to be imported, a sequential number and the file extension ".pcl".
The log file is always newly created.
– Off: Only errors are logged.
– On: The complete import operation is logged, also the details from which objects were
created, what information was written where, etc.
"ASCII-ANSI character set conversion"

An ASCII character set is converted to ANSI by means of the Windows routine.
The import process is displayed by a progress bar.

The DETAIL_JIC drawing type exists in the ComosDB. This is a US norm for the display of
EE diagrams. In the ComosDB the JIC symbols are part of the regular EE branch.
Example: EE Electrical-, Instrumentation and Control| D Device view(DIN 40719)| K Relay,
Contactor
If you open this base object you find an additional symbol in the DETAIL_JIC line on the
Symbols tab.
Report template
"Documents" tab: EE Electrical Engineering| PFSS Circuit diagrams | PFSS.31 Circuit
diagram, JIC-Conversion.
Preliminary work
The IEC symbols are not automatically converted to JIC, since the JIC norm stipulates other
(ANSI) symbols. This is why it is definitely necessary to prepare base objects with JIC
symbols. This applies in particular to recurring symbols such as terminals. If according
symbols are missing Comos creates blackboxes.
Please note: Up to including Comos 8.2 no vertical physical potentials are supported. For a
conversion to JIC such potentials are not processed correctly. From Comos 9.0 on vertical
potentials are possible.
The JIC symbols have to prepared as follows:
● The names of the contact points have to be retained.
● The position of the contact points in regards of the point of origin of the symbol has to hit
exactly the new connection lines after the conversion.
The connection lines are mirrored through the conversion (see below) and are not
recalculated. The symbols are not mirrored but repositioned according to the point of origin.
If the new JIC symbols were not exactly prepared, then the mirrored connection and the new
contact points do not meet graphically and the connection on the report is torn. In this case a
reference would be set to the graphically torn connection. The connection in the database, of
course remains existent as long as the name and contact points were preserved.
That is why following approach is recommended:
Take a IEC symbol and mirror it 45 degrees via the symbol axis. Through this you get exact
positions of the new contact points. Afterwards you delete the mirrored IEC symbol and only
keep the mirrored contact points. Now you draw the IEC symbol around these mirrored
contact points.
PlugIn "Converts IEC to JIC"

Based on a start object all documents are searched with a previously defined report
template.
The reports are copied and then converted as follows:
● The reports get the previously defined JIC report template.
● The existing connections are mirrored around the 45° of the axis of the report. The mirror
axis runs from the left top to the bottom right. Everything that previously was vertical is
horizontal after the conversion.
● The placed devices are moved in a fitting manner and the device symbol is exchnaged
according to the setting in the new report template. Since the JIC symbols are already
designed for horizontal connections, the placed devices do not have to be rotated
anymore in the JIC conversion procedure.
Contact mirror
For the DETAIL_JIC plan mode the contact mirrors are written from left to right.
11.4 Modification of Name / Label
Exceptions
Local changes are lost. So if a symbol was changed on the report by using |Edit symbols,
then this edited symbol is still replaced in the course of the conversion with the by the base
object provided JIC symbol.
11.4 Modification of Name / Label

You open the dialog window via | Extra | Detail | Modification of Name/ label.
11.5 Change per rule: Name / Label

You can open the dialog window via | Extra | Detail | Change per Rule.
The dialog window is used to automatically edit the regularities of "Label" and to process
them in a numeric order.
You determine in the two top edit fields which objects are to be investigated (initial quantity).
An entry must be made in both fields to do so:
11.5 Change per rule: Name / Label
● "Owner": This field determines in which branch a search is to be made for the objects.
● "Prototype": The lower field is an example and determines what kind of fields are to be
searched.
In the mot simple case you drag an object into the lower "Prototype" field; this automatically
sets the current owner of the prototype in the upper "Owner" field.
However, in principle the two fields are independent. You can select a start object in the
"Owner" field and then the prototype that is entered in the lower field can be taken from a
completely different branch.
At the very bottom you can see which text mask the system has determined. These details
are only serve as information and cannot be changed. The details of whether a text mask
has already been defined in the base object, and if so, which one, are given in the "Base
object" column.
Details of which mask is used as the basis for the renumbering of the text masks are given in
the "Edit mask" column. In other words: even if no details have been given in the "Base
object" column, there will be an entry in the "Edit mask" column. In this case the system
attempted to determine an "Edit mask" by itself.
Request and Implementation 12
12.1 Request
Definition of request
● Each base object can be defined as a request if the "Request" option in the properties
window on the "System" tab has been activated.
● The "Device request" class is also available.
Base data branch @1EA Electrical Engineering

The "Request" option is activated in the "higher levels".
The manufacturer devices are divided into "lower levels" (or in other words, with objects that
have been specified more precisely) and the "Request" property is disabled there. Thus the
requests and the manufacturer devices can be organized in one branch and you can
distinguish these two groups from one another. An example:
@1EA Catalog EE
-| H Indicator modules
-| L Optical indicators
-| A Indicating lamp
-| EAO LUMITAS Manufacturer’s catalog
-| 10-1319.1199 Incandescent lamp
-| (other devices from the manufacturer)
-| (other manufacturer’s catalogs)
Request are created down to level A Indicating lamp. Under that level are the manufacturer
catalogs, here, for example, that of EAO LUMITAS. You can find the manufacturer devices in
the EAO LUMITAS catalog, here, for example, a light bulb.
Request and Implementation
12.2 Implementation
Display of device requests

Requests get a small blue triangle in the bottom right-hand corner. On the left there is an
example for a request of class "Device".
Additionally, the "Implementation" edit field appears in the properties window of the
engineering object:
Manufacturer devices (real devices)

Import: The details on the manufacturer devices change very quickly, so there it makes little
sense providing entries in the ComosDB. Manufacturer devices must be imported or else
created manually in the base data.
Use the | Administrator | Base data | ECAD components import command to import
manufacturer devices. See Volume 120, section .
"Mixed" objects
It is not vital to first create objects with the "Request" option and then objects under them
without this option. Vice versa is also possible.
A number of objects to handle measuring problems have been created under the @F
Functions | A General functions heading. The objects were created without the "Request"
option. However, the objects contain elements that were created with the "Request" option.
12.2 Implementation
12.2.1 Implementation phase (order preparation)

The following can be implemented:
● All objects whose base objects has the "Request" (IsRequest) setting.
● All objects of class "Device request" (Device ClassDeviceSpecification).
Types of implementation
● Request on request
● Manufacturer devices on request
12.2 Implementation
The ECAD manufacturer catalog (plus a number of Siemens devices)

See Volume 120, section .
Manufacturer devices must have been prepared as a counterpart to the device request. The
details on the manufacturer devices change very quickly, so there is little point providing
entries in the ComosDB. Manufacturer devices must be imported or else created manually in
the base data.
Examples
● ECAD catalog underneath the device requests:
– @1EA Catalog EE | ... (approximately from the fourth level).
– Phoenix Contact
– @1EA Catalog EE | A Assemblies, subassemblies | Phoenix Contact
● Siemens AG:
– @1EA Catalog EE | A Assemblies, subassemblies | Siemens AG
12.2.2 The Implement request dialog window

The "Implement request" dialog window should be used in order to implement manufacturer
devices for device requests. Select | Implement requests from the | Extra | Detail menu.
The "Implement request" dialog window uses a dialog area that can be described as a "list
window".
12.2.2.1 Icon bar (Window control)

The symbol bar contains buttons for the navigation in the Navigator and to granulate the
search and display.
Table 12- 1 Base data side: Consideration of the "collection"
On the engineering side all objects underneath an object are

automatically part of the "Elements" collection of the object. This is
different on the base data side. Here it is explicitly defined which
"CDevices / Elements" objects are contained in the "Elements" collection.
"CDevices
"Based on the initial node "under Object" all objects are searched
that are contained in the "CDevice" collection. In other words: all
objects that are not contained on the "Elements" tab of the object.
and so on: of all found object the objects are searched again that are
not contained on the "Elements" tab of the objects.
"Elements
"Based on the initial node "under Object" all objects are searched
that are contained in the "Elements" collection. In other words: all
objects that are contained on the "Elements" tab of the object. and so
on: Of all found object the objects are searched again that are
contained on the "Elements" tab of the objects.
12.2 Implementation
Enters the owner of the currently entered object into the "under
object" field.
"to owner..."
12.2.3 List area
12.2.3.1 Superimposing additional columns

Call: right mouse click in the window of the list objects, |Column|...
| delete An additionally inserted and marked column is deleted from the window again.
| Reset for all The default settings for all columns is arranged again: Sortings and filters are
deleted.
| Definition Opens the "Special column" dialog window. See Volume 120, section .
The following four commands | Unit, | Location, | Implementation and | Request read out the
"Pointers" of the respective object. If no "pointer" is set – e.g. if no "Unit" field can be found in the
properties window – it is searched in the owner structure as an alternative.
The four commands are not identical to the commands for a column reference object of an attribute
(see Volume 120, section ).
| Project Superimposes a column in which the "Project" of the respective object is
displayed.
Makes sense for base data, since these can derive from different projects: e.g.
the local base data (from the engineering project) and the global base data (from
the base project!) is displayed.
| Document A column with all in the fixed structure found documents is inserted.
| Stelle A column "Positions" is added. In this column the position is entered which
belongs to the marked object.
| TimeStamp Two columns are added to the right of the marked column: one for the creator
name ("...by") and one for the creation date ("...on"). The timestamps can be
created for each column (except for the timestamp column itself).
| Status Superimposes one or more columns with status information. This is especially
interesting for the project check, since only a status view can be displayed in the
Navigator.
| Object name A column for the object name is inserted.
12.2 Implementation
12.2.3.2 New column (programming the special column)

First variant: Special column of type "general"
"Column number" The column number displays from which column the dialog window was called.
Especially if a number of new columns was already defined, you can with this
information always quickly check if you "caught" the line you wanted to edit.
"Reference The reference column defines where the reference object is searched. Different
column" objects can be available within a line, e.g. the line reference object, the unit, the
location, etc...
"Column title" The title of the newly defined column can be entered here.
"Column type" "General" or "Attribute".
"Display symbol" Superimposes the symbol for the object.
"Function" There are two functions:
 one with which the object is defined: Function ColumnObject
 and one which defines the to be displayed text: Function ColumnText
At least the text function Function ColumnText has to be filled, both would be
better.
These two functions mean:
The Function ColumnObject function passes an object to the list. All functions
that depend on an object can only be executed if Function ColumnObject was
programmed correctly. Part of this can be:
 the mouse context menu |Properties or
 the ability to deviate a new column from this newly defined column.
The Function ColumnText function can on the one side use the line reference
objectRefColObject , on the other side the object which was calculated in
Function ColumnObject can be used.
With the OutputDebugString you can send outputs to DBMon.
[Example] Here a window with a functionable example is unfolded. You can copy the text
into the "special.Column".
[Script Test] Only calculates the script for the marked line. Usually the result of a line is
sufficient for a test, and it will take considerably less time as calculating the
results with [OK] for all lines.
Second variant: Special column of type "Attribute"
12.2 Implementation
This technique generates an algorithm which was described in Volume 120, section .
"Column number" The column number displays from which column the dialog window was
called. Especially if a number of new columns was already defined, you
can with this information always quickly check if you "caught" the line you
wanted to edit.
"Reference column" The reference column defines where the reference object is searched.
Different objects can be available in a line, e.g. the line reference object,
the unit, the location, etc.
"Column title" The title of the newly defined column can be entered here.
"Column type" "General" or "Attribute".
Drag&Drop edit fields The three fields "Class", "NestedName" and "Description" are filled by
means of drag&drop.
● Attributes via drag&drop into the list window
The attribute always refers to the line reference object.
● Defining attributes with the help of the dialog window:
The reference object can be freely defined. Especially a newly programmed column can
be used as reference column.
12.2.3.3 Sorting the list area

List windows can be sorted. Click in the title line of the column description to do so. You can
switch between an ascending and descending sorting. The sorting is removed again upon a
third click.
It is possible to set a multiple sorting. There it is first sorted for one column, and if there was
no analogousness for a second column.
Click on <ctrl> and click on the next column for which it is supposed to be sorted.
The first column which is sorted gets a sorting mark with two double arrows, all following
columns only a single double arrow. There >> stands for ascending, and << for descending
markings.
12.2 Implementation
12.2.3.4 Filtering list area

List windows can be filtered. Right-click into the title line. The clicked title line is the default
for the filter:
| Page Setup Defines the display for printing the list window.
| Print Prints the content of the list window (with the "PageSetup" settings) on the default
printer.
| Excel Hands over the content of the list window to Excel. A reimport is not possible. Do not
mistake this with the Excel export function from the bulk processing tool.
[Off] With [off] the filter can be deleted again.
[Extended] Switches into the dialog window "Extended filter".
An active filter is symbolized by the ¥ symbol in the column description. You can also set a
multiple filter. The filter consists of an "Operator" and a "Filtertext". The filter only displays
objects that have a text in the marked column which corresponds to the filter text and the
selected operator:
"Operator" In the "Operator" field you set the condition for the matching of the filter text with the
value of the line. As a default the operator " = " is set for all values. Especially for
numeric attributes (e. g. temperature, pressure, voltage), other operators are also
possible.
Like, i.e.: the letter is allowed in the text. Like a would have the same effect as *a*.
Not Like means: the letter is not allowed in the text.
= equal
> greater than
>= greater or equal
< smaller than
<= smaller or equal
<> smaller or greater
Mask: The use of jokers is possible here. Therewith an "?" stands for exactly
one desired character and an "*" for a number of optional characters.
Between: Two dropdown menus are available for this option, with which you can
set the lower and upper value.
"Filtertext" Here the column text from the currently marked line is initially input. It can be taken
over as filter text or be overwritten with an optional search text.
Turning off the filter

Again right-click on the column on which you set the filter. You then click on the [Off] button
in the filter dialog.
12.2 Implementation
The extended filter

Whereas the simple filter and the simple sorting for each column has to be set individually,
the extended filter offers the possibility to define a multiple filter and a multiple sorting in one
work step.
In the left window area you define the sorting of the visible list entries.
[Add] Adds a sorting. The dialog window "Dialog" opens, in which you can select a column
and define the sort mode:
 -> ascending
 <- descending
[Change] Changes the sorting for the marked line.
[Delete] Deletes the marked line.
The filter can be defined in the right window area:
and The defined filter is added.

or The defined filter may occur as an alternative.
() The brackets form logical terms. Therewith the brackets have to be used if the "and"
and "or" terms are mixed.
[Add] Adds a filter. The following dialog window "Filter" functions the same way as the above
described simple filter.
[Edit] Changes the conditions for the marked filter.
[Delete] Deletes the marked filter.
12.2.3.5 Schemes for the list window (ScanDevices)

A scheme is a special way on how to search a subset from a number of given objects.
In the previous sections it was explained that the list window can be filtered and sorted in
different ways. Hence you influence which objects are displayed and how they are displayed.
The desired action will then only have an effect on the visible objects, not on the larger initial
object quantity.
"Scheme Save/ Load" The way you have set the list window is also
described as "Scheme" and can be saved.
The icon is not visible immediately in all list windows. By means of the
<Ctrl> S
12.2 Implementation
command the icon can be turned on or off. Please regard that the list window is also marked
and not an element in the main Navigator (The keyboard command has a differing meaning
there). Clicking on the icon opens the "Save / Load" dialog window:
Note
Please regard that saving via the <Ctrl> S only saves the content of the list window! Most
dialog windows contain other dialog areas that are not covered. In such a case there is
usually another option to save a scheme which covers the entire dialog window. These
additional schemes are described in the corresponding sections.
Default storing (cba files)

The created scheme can be saved via the [Save as...] button.
The entry in the "Save Bulk processing scheme under" scheme defines under which name
the scheme is displayed in Comos.
The file name of the scheme is "Scan1.cba", whereas the last character of the file name is
incremented for each new stored scheme. (Additionally another file "Ctrl1.cba" is internally
created automatically in which the title is also saved, with which the scheme is displayed in
the dialog window.)
"Private" active Is the "Private" checkbox marked, the scheme in the NT directory
\Profiles\USERNAME\Comos \ScanDevicesSeparate is saved in the
"Scan1.cba" file, respectively incremented. In this case the scheme is only
available for the user who belongs to the profile.
"Private" inactive When the "Private" field not marked, then the "Scan1.cba" file in the program
directory...\Comos \Bulk processing is put in the database directory. In this
case the scheme is available for each user who logs onto the database. In
order to emphasize this the scheme is marked with ** at the end of the name
in Comos.
Manually creating the scheme file (sos files)

When the "File" option was selected the display of the dialog window changes, and only the
[save as] and [open] buttons are available.
When you select the [Save as] button you can state the name and storage location. The file
ending is as follows: sos (search object scheme).
12.2 Implementation
This sos file contains the same information which can also be stored in the dialog scheme
(cba-file): all filters and sortings as well as the settings of the icon buttons.
There is one principal difference:
● The cba-files mainly serve as basis of the dialog window. As a consequence the cba-files
are always saved in the same location and are loaded from there (subdirectories in the
"Profile" directory).
● The sos files primarily serve as an information source in reports. That is why sos files can
be deposited at any desired location. In use the sos files are deposited in subdirectories
of the report directories and are loaded from the report relatively from the subdirectories.
The advantage is obvious: is the report directory copied or moved, the sos-files are still
found by the reports.
12.2.3.6 Attributes in dependency of a line reference object

For the object search additional attributes can be added to the list field. You have two
alternatives in this case: You can firstly drag&drop the attribute from a tab or secondly drag
the attribute from the detail window.
1. First alternative: Drag&Drop from the tab
Call: Mark the object, right mouse click | Properties
Open the properties window of an object in the Navigator or in the list field of the object
search. Superimpose the "Attributes" tab.
Drag an attribute text per drag&drop from the attributes tab into the list field of the object
search:
2. Second alternative: Drag&Drop from the detail window:

Mark an object, open the tree structure
(Depending on the setting the attributes in the Navigator are not visible in the Navigator
or visible in the detail window, see Quickstart Basic.) Drag an attribute per drag&drop
from the Navigator into the object search list field:
12.2 Implementation
Result
After having dragged an attribute into the list window, there is not always an attribute value in
the new <Spec-Name> column. The explanation is really easy: an attribute was found - e.g.
dimensioning - but there is no value. (Please note: the number 0 is also a value! No value
means: nothing has actually been input.)
Sometimes three question marks can be seen, and this case is a bit more complicated. The
question marks mean:
The match algorithm did not find a fitting attribute in this line.
The match algorithm is as follows:
Attribute <Class, NestedName> =?
[Object.Class = <Class>].Spec<NestedName>
To start off, the first part of the equation. The owner of the <Class> as well as the name
<NestedName> is detected from the to the list window dragged object. The object class
could be a "Device", "Accessory", etc. See the administrator manual regarding NestedName.
Now the right part of the equation. Here it is tried to find a match object.
The match object is searched based on the line reference object (which is sometimes also
called "Main object" .
Each line owns a line reference object ("Main object"), or, in other words: each line
represents an object. You can quickly find out which respective object this is by clicking in
the column "Label" or "Description" and calling the | Navigate | Object command.
Based on this object the owner structure is navigated ascending as long as an object with
the class of the attribute owner is found:
Zeilenbezugsobjekt.Class or
Eigentümer.Zeilenbezugsobjekt.Class oder usw.
... =? Spec <Class>
In other words: If no object is found from the line object upwards to the project start node
which does not own the same class as the attribute object, then no value is displayed for the
attribute column. And completely independent from attributes being found with a fitting name
or not.
Is an object with a fitting class is found in the owner structure, this object is evaluated for an
object with an according name. If an attribute with a fitting name is found, then the value is
readout and written into the list window.
12.2.3.7 Attributes in dependency of the line and column object

You can add attributes into list windows in dependency of a column object. A column object
e.g. is an implementation.
There are two available alternatives: You can first drag&drop the attribute from a tab or
secondly drag the attribute from the detail window.
Note
In both cases you have to keep the <Ctrl> key pressed.
As a result of <Ctrl> drag&drop is displayed in the list window of the mouse pointer as a
reference symbol. Upon releasing the clicked mouse, a mouse context menu is offered:
12.2 Implementation
| Object (Standard) has the same effect as the previously described default case
(dragging without <Ctrl>).
The other commands generate a column which is in dependency to the in the
command mentioned column object. The four commands read out the "Pointers"
of the respective object. If no "pointer" is set – e.g. if no "Unit" field can be found
in the properties window – it is searched in the owner structure as an alternative.
Especially for | Implementation and | Request the object classes may vary a lot.
The four commands are not identical to the commands in the submenu | Column... (see
Volume 120, section List area (Page 112)! Instead: These mouse menus are "Special cases"
of a programming technique that is explained in Volume 120, section New column
(programming the special column) (Page 113). Thereby the "Special cases" are rather
standard cases in everyday use. "Special cases" can here only be understood in a way that
the in the section introduced programming techniques can also generate these four options.
Using the mouse menus is faster: a column which can here be selected directly (e.g.
implementation) needs two columns in the individual programming: one column with the
reference object and one attribute column which refers to the reference column.
The reference object is searched for based on the column reference object.
Then the case arises that two objects are listed in a line: the line reference object - lets say
as an example a "Request" for a measuring function – and the "Implementation". Even if two
lines (i.e. two line reference objects) can have the same class, the corresponding
implementations can own different classes! One time a "Device" could be selected as an
implementation, and another time an "Assembly group".
Now, based on the in the line found line reference object - in this case this means: based on
the implementation - it is navigated in the owner structure to the top until an object with the
class of the attribute owner is found.
Afterwards, as on the top, it is checked for matching names of the attributes (see "The match
algorithm").
Result
If a fitting attribute is found, but this owns an empty value, then an empty text field is
displayed. If no fitting attribute is found the following entry is displayed: --???--
12.2.3.8 Other icons and fields

The remaining icons have the following meaning:
Display filter. If pressed, not implemented request

are also displayed.
Display filter. If pressed, implemented requests

are also displayed.
The display filters are additive.
12.2 Implementation
As explained above, each base object can have the "Request" option. However, in most
cases the base objects will have the "Device" class. Select the entry "D Devices" from the
"Class" dropdown list.
The fields "below object" and "below base object" can be set by means of drag&drop: Drag
the desired objects onto the field by using the mouse.
With "below object" you determine which object is used as starting node when searching for
device requests.
The "below base object" field provides an additional filter to narrow down the search.
The found requests are now appear in the list area, according to the set filter. One or more
objects can be marked in the list window, in the usual way.
Marked requests can now be allocated to devices from the base objects or to the
unit/location view. This can happen individually or collectively:
12.2.4 Replacing or retaining a request
12.2.4.1 Project option "Implement request replaces objects"

Project properties, "Module options" tab, "Implement request replaces objects" option:
● Deactivated
– A new engineering object is created; it is based on the selected manufacturer device.
The engineering object which is based on the request receives an implementation
pointer that points to the new engineering object.
● Activated
– The base object pointer of the engineering object based on the request is replaced:
the engineering object is now based on the manufacturer device, not the request, but
it is still the same engineering object (same SystemUID).
12.2 Implementation
12.2.4.2 Setting the implementation pointer

The implementation pointer that has been set is displayed in the "Implement request" dialog
window once you have dragged a manufacturer device onto the marked requests:
If the "Implement request replaces object" option is deactivated, a new engineering object is
created for the manufacturer device. Now both the manufacturer device and the request
object are visible in the Navigator. In addition to that, the edit fields in the properties windows
are adjusted correspondingly:
Correspondingly, the edit field "Request" will be set in the properties window of the newly
created object.
An implementation presupposes that the device request and the manufacturer device are
reasonably similar. In certain cases Comos does not carry out an implementation and
informs the user by means of an infobox.
Continuing the implementation

If an object receives the implementation pointer and has already been joined to another
object by means of a connector, an attempt is made to implement the partner object as well
recursively. A number of different conditions must be evaluated. The same applies if the
implementation is released.
12.3 Report PQA
12.2.4.3 Base object change

If the base object is changed, there are no special features that indicate this. The resulting
object takes over the attributes, elements and so forth of the new base object. The elements
of the object to be implemented are also checked during the implementation. If any elements
with identical names are found, then these elements are likewise implemented, meaning that
they are swapped in the database and on the report. All placed elements for which there are
no elements of the same name in the implementation are lost in the database and are
displayed in red on the report to indicate that there are inconsistencies. If the implementation
was successful, it is not possible to tell from created they were created as the result of an
implementation.
12.2.5 Releasing device requests

This option is only available for Option 1: "Set implementation pointer". In the case of
Option 2 all information on the original request is lost, and hence the original state cannot be
reconstructed either.
In order to release an implementation that has already been set for Option 1, mark the object
in the "Implement request objects" dialog window and select the | Release command from
the context-sensitive mouse menu by right-clicking.
Comos releases the implementation and prompts whether the objects that have been
created are likewise to be deleted.
12.3 Report PQA

Checking the required device against the manufacturer device.
12.3 Report PQA
Product data and manufacturer devices 13
13.1 Definition and area of application
Definition of product data

Product data constitutes the minimum amount of attributes that are required to order a
concrete product. In other words: In the course of the planning a certain partial quantity of all
user inputs is used to select or describe a manufacturer device (or "real device") that can be
ordered.
In detail, the Comos product data function area fulfills the following tasks:
1. A number of the attributes in the base data are labelled as product data-relevant. The
user can immediately see on the engineering side which attributes have to be filled in
order to place an order.
2. In addition, a template can also be input in the base data. As long as the base object is a
request, this template from the base data is only displayed as information. If this involves
a manufacturer device in the base object, then the input fields get an orange background
to make it clear to the user that there was an impermissible deviation from the order
criteria.
3. On the basis of the product data that had been input on the engineering side, a search
can be made within the existing manufacturer devices and the user can select a concrete
device from the results.
4. Alternatively, in the case of special production items (for which there can be no existing
manufacturer devices already for obvious reasons), a manufacturer device can be
created from the product data that had been input on the engineering side.
Technical implementation
The technical basis for the use of product data is a base object change.
1. First of all, a base object that is to serve as the basis of the request ("prepare requests")
is configured.
2. In addition, base objects are created for the manufacturer devices. This is often done by
importing catalogues from manufacturer devices ("importing manufacturer devices").
3. Technical implementation
4. The technical basis for the use of product data is a base object change.
– First of all, a base object that is to serve as the basis of the request ("prepare
requests") is configured.
– In addition, base objects are created for the manufacturer devices. This is often done
by importing catalogues of manufacturer devices ("importing manufacturer devices").
Product data and manufacturer devices
13.2 Function right product data
Limits
Supported base object classes for product data:
● Class Device
● Class Element
● Class Accessory
● Class Position
● Class Location
Exceptions
Device request class is not supported.
13.2 Function right product data

In order for a Comos user to prepare orders he needs the necessary rights. If you are an
administrator you can allocate the necessary rights to the user via the rights management.
Proceed as follows in order to be able to work with the rights management.
1. Mark your project in the Navigator and press the <Ctrl>+<A> keys on the keyboard.
2. Click on the "Rights" tab in the window that opens.
3. Activate the Function rights option.
13.3 Preparing requests
4. Right click on an employee or employee group in the lower area of the window and select
| properties [Name of the employee or Name of the employee group].
5. A window is opened. Activate the product data option and confirm your selection by
clicking on OK.
13.3.1 Preparing request base objects

Activate the "Request" option on the "System" tab in the base object.
When this option is activated, an "Implementation" field appears in the properties window of
the engineering object. However, you should not use this field when you are working with
product data. The Request/Implementation method is the older one in Comos, but is still fully
supported. The product data technique: The Request/Manufacturer device method is the
newer one and has a considerably enhanced functionality.
13.3.2 Preparing attributes

Product data is handled as attributes. In other words: The "Product data" option is used for
all attributes that appear both in the request and also in the details of the manufacturer
device, and in addition the "Product data" option is needed for a basis for or against a
manufacturer device.
Activating product data and setting the operator

Activate the "Combination" option on the "Links" tab in the properties window of the attribute:
A field for the "operator" is displayed after having activated the option.
The "operator" stipulates what relationships between the templates in the base object and
the planning data are supposed to be valid. The "=" character was selected in the above
example. This means that input in the engineering data must be exactly the same as the
template from the base data for the input to be valid.
Exactly which entries in the "Operator" list are available depends on the display type of the
attribute. The operators have the following meaning:
"None" An input must be made on the engineering side, but it the input does not
matter.
"=, >, < etc." Numeric comparison between the input on the engineering side and the
template.
"Within, Outside" Only for range attributes. The input on the engineering side must be
respectively within or outside the values of the template from the base
object.
"Prefix" Alphanumeric comparison. The input on the engineerin side must be the
prefix of the template from the base object. This is very useful for order
numbers. Within the order numbers the first digits often give type details and
the remaining digits merely add additional ordering details.
For example, if the order number for a motor is M4x0815, where the "M"
stands for motor and the "4" for a four-pole connector, it is then sufficient to
input the prefix "M4" on the engineering side to describe the product
adequately.
"Subset" This allows a subset of the elements created for an object can be taken into
account. If one or more of the elements defined here exists in an
engineering object, the entry is valid. The check is based on identical
names.
This is also used with the SYS.ELMSTRING attribute on contactors.
Input the defaults for the request
After you have set the product data and turned on the operator, the display of the attribute
changes. A gray display field is added:
In the gray display field itself you cannot input any own information, instead the input from
the left is taken over and is displayed.
While the Connection field is later overwritten by the user on the engineering side, the input
in the display field remains the same.
13.3.3 Controlling the display of product relevant attributes

Via an attribute you can set how an attribute with the "Combination" (= "product request")
property is to be displayed on the engineering side.
13.4 Importing manufacturer devices
In this case the attribute with the name "ProdReqShow" must exist in the base object on the
"SYS" tab. This attribute must be created as a combobox with three states.
Name Description
0 Data display of request / manufacturer device
1 Data display of request
2 Data display of manufacturer device
The properties window is not automatically updated when switching over the combobox. For
that reason it is a good idea to explicitly initiate an update in the Sub OnChange script function:
Sub OnChange()
'After editing the unit or the value
Set App = Workset.Globals.AppCommand
App.Execute "RefreshDeviceForm", ""
End Sub
See also the script function with which you can control the output of the product data in
reports: Volume 120, section Output product data (Page 141).
13.4 Importing manufacturer devices

The manufacturer devices can be created manually in the base data, but usually the
manufacturer devices are imported.
The base data should appropriately be set up as follows:
1. There is a central branch for each technical area. The topmost levels of the branch are
base objects with the activated "Request".
2. The manufacturer devices are located underneath the request objects (without the
"Request" option, of course).
The administrator imports the manufacturer devices by means of an action object
underneath the request objects (see Volume 50, section 13: Standard import: Blank for
tables)
13.5 Planning work (input product data)
Automatically creating structure branches for manufacturer details

When importing manufacturer devices there is also the option to automatically create a node
for the manufacturer.
Attributes with keynames in which the necessary details for the manufacturer have already
been stored must already exist in such a case. The keynames are:
ECAD Tab: "HSD"

Attribute name: "M003"
(M-zero-zero-three)
eCl@ss Tab: "PA"
Attribute name: AAA001
(Three times A-zero-zero-one)
eCl@ss Tab: "E11"
Note
In the long term there will only be one keyname for eCl@ss.
Effect
When an import operation is started, then first of all a branch with the name of the
manufacturer is created in the base data. The manufacturer devices are stored underneath
this node point.
13.5 Planning work (input product data)

Create the engineering objects in the usual way. The product data-relevant attributes can be
seen at once via the additional display field:
The display field for the product data
If templates had been input at the base object for the request, then these templates are
visible:
Details for the request
Otherwise the attribute can be edited in the normal way in the course of the planning. The
subsequent procedure to be followed depends on which type of implementation you choose.
13.6 Selecting a manufacturer device
13.6.1 Creating manufacturer devices by feedback
13.6.1.1 Feedback for an individual engineering object

In Comos it is not absolutely necessary to first create the manufacturer devices separately in
the form of base objects so that they are already available at the time of implementation. You
can also work in the opposite way: You work with engineering objects and then use these
details to create a suitable base object. Thus there is feedback from the engineering project
to the base project.
Application
Make all preparations as described above.
Once all required inputs have been made, click in the properties window of the
engineering object on the "Create base object "product data"" icon.
Note
The icon can only be used if the user owns the "Product data" function right. In principle, this
icon and the associated functionality can occur in the case of objects of class "Accessory",
class "Element" and class "Device".
Effect
1. A base object is created in the project from which the original base object derives.
2. This new base object becomes the new basis of the engineering object.
3. In this new base object the inputs that had been made for the engineering object are now
taken over as the inputs.
4. The "Request" option is removed. A manufacturer device base object is now allocated to
the engineering object, more specifically, the one which had been created above.
5. Due to the allocation of a manufacturer device, the orange background function now
takes effect, see Volume 120, section Deviations from the manufacturer device templates
(orange background) (Page 141).
Note
Preparing manufacturer devices by means of "Create base object product data"
This method can also be used to create smaller amounts of manufacturer devices. Do this by
inputting the desired product data, click on "Create base object "Product data"", input the
next product data item, and again click on "Create base object "product data"", etc.
13.6.1.2 Feedback for a engineering branch

The "Product data" tool serves the same purpose as the above-mentioned "Create base
object "Product data"" icon in the properties window of an engineering object. This enables a
feedback of the engineering data to the base data and base objects are created if required.
1. In order to use the "Edit product data" tool in the Comos menu select the | Extra | Check |
Edit product data command.
2. In the window which opens drag a branch of an engineering project or of a base object
into the start field.
Effect iin the case of a branch of an engineering project

1. All engineering objects lying underneath are searched to see if product data had been
input.
2. A base object is created for each engineering object in which product data had been
input. This base object is then located in the project from which the original base object
derived.
3. This new base object becomes the new basis of the engineering object.
4. In this new base object the inputs that had been made for the engineering object are now
taken over as the inputs.
Effect on a base object

1. All engineering objects that had been derived from this base object are searched to see if
product data had been input.
2. The subsequent steps are the same.
Due to the allocation of a manufacturer device, the orange background function now takes
effect, see Volume 120, section Deviations from the manufacturer device templates (orange
background) (Page 141).
13.6.1.3 Automatically creating structure branches for manufacturer details

With both methods of feedback there is also the option to automatically create a node for the
manufacturer.
For this, attributes with keynames must exist in which the necessary details regarding the
manufacturer are stored. The keynames are:
13.7 Manufacturer device selection
ECAD Tab: "HSD"

Attribute name: "M003"
(M-zero-zero-three)
eCl@ss Tab: "PA"
eCl@ss Tab: "E11"
Note
In the long term there will only be one keyname for eCl@ss.
Effect:
When the feedback is initiated (with the "Create base object" icon in the properties window
or the [Edit] button dialog window, as applicable), then
● First of all, a branch with the name of the manufacturer is created in the base data.
● The new base objects for the manufacturer devices are created underneath this node
point.

After having conducted the previously described steps you can start to search manufacturer
devices for your device requests. Comos supports two different technologies for searching
manufacturer devices.
● You can search for manufacturer devices in a database based mode.
● You can search for manufacturer devices in an XML based mode.
If you select the database based mode the window for the manufacturer device selection is
offered the same way as on the known user interface.
If you select the XML base mode, all manufacturer devices that fit your request are imported
to a temporary XML string. This enhances the search speed for the search for manufacturer
devices (see also Volume 120, section Deviations from the manufacturer device templates
(orange background) (Page 141)).
Note
When shipped, Comos as a default is configured in a way that the XML base mode for the
manufacturer device selection is active.
13.7.1 Configuring the manufacturer device selection

You can configure the manufacturer device selection as desired.
Proceed as follows to configure the manufacturer device selection:
1. In the Navigator click on your project and select properties.
2. In the window that opens click on the "Options" tab and then on the "EE/I&C-Options 1"
tab:
The "EE/I&C-Options 1" tab is displayed:
3. Select the desired option in the "Manufacturer device selection" working area
4. Confirm your selection by clicking on [OK].
13.7.1.1 Configuration options for the manufacturer device selection

The following table gives you an overview of the configuration options in the "Manufacturer
device selection" working area.
Option Description
XML based mode The "XML based mode" option is active as a default. Deactivate the
option if you want to use the pure database based mode for the
manufacturer device selection.
Only list local manufacturer Activate this option if you only want to have a project based selection
devices of manufacturer devices to be considered.
Note: You can only activate the option if you previously defined a
local path for the project based selection of manufacturer devices
(see Defining a local path for the manufacturer device selection
(Page 134)).
Local manufacturer devices Via the field you can define a path for a project related selection of
manufacturer devices (see Defining a local path for the manufacturer
device selection (Page 134)).
13.7.1.2 Defining a local path for the manufacturer device selection

In Comos you deposit the manufacturer devices for you device request in a local path.
Through this you have the option to define a project based selection of manufacturer
devices. This makes sense if, e.g. you want to only consider devices of a certain producer
for the manufacturer device selection.
Proceed as follows in order to define a local path for the manufacturer device selection:
1. Click on the "Base objects" tab.

2. Create a new base object. To do so right-click on your project and select New| New base
object in engineering project.
3. In the window that opens enter e.g. "@Device" in the "Name" field and confirm your entry
with [OK].
The newly created base object is displayed underneath the project in the Navigator.
4. Create the manufacturer device structure you need underneath the base object.
5. Open the "EE/I&C-Options 1" tab.

6. Drag the "@Device" base object from the Navigator onto the "Local manufacturer
devices" field on the "EE/I&C-Options 1" tab.
7. Confirm you selection by clicking on [OK].

If you now select the "Only list local manufacturer devices" option, only the manufacturer
devices that you created in the manufacturer device structure underneath the @Device base
object are considered.
Note
If you click on the delete reference button " ", the folder which you dragged into the "Local
manufacturer devices" field is deleted from the field.
13.7.2 Allocating device requests to manufacturer devices

There are two possibilities on how to allocate device requests to manufacturer devices:
● You can allocate a single device request to a manufacturer device.
● You can allocate a branch of device requests to multiple manufacturer devices in bulk.
13.7.2.1 Allocating a single device request to a manufacturer device

If you want to allocate a single request object to a manufacturer device, proceed as follows.
1. In the Navigator right-click on the device request to which you want to allocate a
manufacturer device and select properties.
2. In the window that opens click on the set reference button.

The manufacturer device selection is displayed:
3. Mark the manufacturer device which fits to you device request in the lower area of the
manufacturer device selection.
4. Confirm your selection by clicking on [OK].
After having clicked OK, the manufacturer device selection closes and the name of the
selected manufacturer device is displayed in the "Base object" field:
13.7.2.2 Design of the manufacturer device selection

In the upper area of the manufacturer device selection the device request which you
selected is displayed in the accompanying order data. In the lower area of the manufacturer
device selection a list of the manufacturer devices that fit to the device request is displayed.
If you have activated the "Only local manufacturer devices" option (see Volume 120, section
Defining a local path for the manufacturer device selection (Page 134)), only the
manufacturer devices are listed in the lower area of the manufacturer device selection which
you actually placed in the local path.
Provided that you are working in the XML based mode of the manufacturer device selection
(see Volume 120, section Manufacturer device selection (Page 133)), Comos acts in a way
that while opening the manufacturer device selection the available base objects are imported
into an XML string. This XML string is kept as long as the manufacturer device selection is
open. If you search the device data in the lower area while having the manufacturer device
selection open, Comos searches or sorts only those files that were imported into the XML
string, and not the base objects in the database. This significantly enhances the search
speed.
13.7.2.3 Column and control elements of the manufacturer device selection.

The following table gives you an overview of the columns and control elements in the
manufacturer device selection:
Column/Control element Description

Update Via this button you can update the display of the manufacturer
devices in the lower table, if e.g. you selected a new selection
criteria.
Display important attributes If you click on the arrow next to the button, you can select if all
attributes of the currently selected device request or only the most
important attributes of the selected device request should be
displayed in the upper table.
Display all manufacturer If you click on the arrow next to the button you can select if all
devices manufacturer devices or only the manufacturer devices for which you
defined a local path should be displayed in the lower table (see
Volume 120, section Defining a local path for the manufacturer
device selection (Page 134)).
Owner The column displays after which categories that attributes of your
device request are grouped. There are attributes that are taken from
the "Technical data" tab and attributes that are taken from the "Order
data" tab.
Attributes In this column the attributes are displayed which you allocated to the
device request.
Requirement In this column the attribute values are displayed which you allocated
to the device request via the "Technical data" and "Order data" tabs.
Selection If you mouse click on a line in the column you can select a sorting
criteria for the display of the manufacturer devices in the lower table.
Manufacturer device The name of the found manufacturer devices is displayed in the
column.
Description A short description of the manufacturer device is displayed in the
column.
13.7.2.4 Allocating multiple device requests to manufacturer devices

If you want to allocate several device requests to manufacturer devices at once you have to
proceed as follows:
1. In the Extra Comos menu point to Detail and then click on device selection (product
data).
2. In the window that opens specify a class via the "Class(es)" field (e.g. by selecting A
Equipment).
3. In the Navigator click on a device and drag it onto the "Start objects" field.
In the upper area of the window a list of the device requests is displayed which are
located underneath the devices which you dragged into the "Start objects" field.
4. In the upper area of the window mark the device requests which you want to allocate to
the manufacturer devices.
In the lower area of the window the manufacturer devices are selected that fit to the
selected device requests.
5. In the lower area of the window mark the manufacturer device which you want to allocate
to the selected device request.
6. Click on the set base object button.
The base object pointer is newly set for all selected device requests. The device requests
are not labeled as a request anymore.
The base object pointer is newly set for all selected device requests. The device requests
are not labeled as a request anymore.
13.7.2.5 Columns and control elements of the device selection (product data) window
The following table gives you an overview of the control elements that are located in the
upper area of the device selection (product data) window.

Export data When you click on the arrow next to the button another button is
displayed via which different export formats can be selected for
the data that is displayed in the window (e.g. Excel, Access or
XML).
Script block action
Search at once If the button is active the search is started automatically as soon
as the device is dragged into the start object field. If the button is
not active the search is only conducted if you click the
Search button.
Search This button is only active if the search at once button is
deactivated. Via the button you can manually start a search after
having dragged an equipment into the start object field.
Search mode When you click on the arrow next to the button another button is
displayed via which you can select which search mode to use
for the manufacturer device selection (e.g.: Recursive, via
reference - attributes or database based).
Start object(s) In-/Exclude When you click on the arrow next to the button another button is
displayed via which you can select if the objects you have
dragged into the "Start object(s)" field should be included in the
search subset or not.
Folder filter
Placing filter
Options
Create columns with When you click on the arrow next to the button another button is
product data attributes displayed via which you can select for which product data
attributes columns should be displayed in the upper window
area (e.g. Create all, Only create with values, Only create with
own values.
Request When you click on the arrow next to the button another button is
displayed via which you can select if only requests, only
manufacturer devices or requests and manufacturer devices
should be displayed in the upper area of the window.
The following table gives you an overview of the control elements that are located in the
lower area of the device selection (product data) window.

Search at once When the button is active the search for manufacturer devices is
started automatically as soon as you mark one or more device
requests in the upper area of the window. If the button is not
active the search is only conducted if you click the Search
button.
Search This button is only active if the search at once button is
deactivated. You can manually start a search by marking one or
more device requests in the upper area of the window.
13.8 Output product data

Create columns with When you click on the arrow next to the button another button is
product data attributes displayed via which you can select which product data attributes
should be displayed in the lower area of the window.
Columns with product data When you click this button, the column arrangement for the
attributes like engineering objects manufacturer devices is structured exactly the same as the
those for the device requests in the upper area of the window.
Set base object Via this button you can allocate a manufacturer device to a
device request which you selected in the upper area of the
window.
13.7.2.6 Deviations from the manufacturer device templates (orange background)

Once a manufacturer device has been allocated, the inputs in the engineering object and
templates from the manufacturer device base object are compared.
If your inputs do not match the templates that are visible in the additional display field, then
the input fields are displayed in orange.
A note appears in the tooltip if the mouse briefly hovers over one of the orange input fields:

<workset>.Lib.ProductRequestDisplayText<Spec>
This function supplies the output text of a ProductRequest attribute, whereby individual
values such as Min/Max and unit are separated by the "|" character (vertical bar) (e.g.
"100|200|cm")
The manufacturer device data is supplied as a complete string (e.g. "100 - 200 cm") as on
the tabs.
EPLAN (Import/Export EXF) 14
14.1 Background information
14.1.1 EPLAN structures in comparison with Comos structures

EPLAN organizes its data as follows, broadly speaking:
"Normal" base data and article base data

This division broadly corresponds to the Comos scheme. In Comos as well there is base
data in the form of templates for engineering data (EPLAN: "project data"). The article base
data roughly corresponds to the manufacturer catalog in Comos.
However, in EPLAN there is a strict separation of "normal" base data and article base data.
Not so in Comos: here the manufacturer catalog is managed within the normal base data.
For that reason "normal" base data from EPLAN is not imported into Comos either. It is
sufficient to import the article base data to Comos.
Please note; there is only one form of import for article base data. There is no interface to
transport Comos article base data to EPLAN.
Symbol files
A symbol file contains all symbols from one of the relevant seven symbol types within
EPLAN. In other words: a component can appear in a maximum of seven different display
types.
● Variants in EPLAN symbols
Position changes (rotations) are controlled by variants. The rotated symbol is thus not
calculated but the relevant separate symbol is created for up to four different angles of
rotation.
This is no problem when importing, since each of the variant symbols can be used and
processed further.
However, rotated symbols cannot be exported, since there is no corresponding form for
rotated symbols in EPLAN. If a rotated variant is exported to EPLAN, the rotation is
ignored completely and the base symbol is exported. If you intend to export to EPLAN,
then you should only work with unrotated variant symbols.
● Separate management of symbols in EPLAN
In EPLAN the symbol files are kept strictly separated from the base data and the project
data. Within the project data there is only a text reference to a symbol which is then
loaded at runtime.
Not so in Comos: here the symbols are part of the base objects and thus (via inheritance)
also part of the engineering objects.
EPLAN (Import/Export EXF)
Plot frames
A plot frame is used to print ("plot") information. This roughly corresponds to a Master Report
in Comos.
However, document management in EPLAN is relatively limited and there are only one or a
few plot frames. Not so in Comos: here a large number of reports can be used, and from a
technical point of view, as many as you wish. In Comos it is also not strictly necessary to
work with Master Reports, since a report that can be printed can be generated.
Forms
Forms take in information and display it. The forms are used within a plot frame and are then
called plot forms. Forms are not evaluation reeports from the Comos point of view, despite
what one might think from the name.
● The EPLAN default forms are:
– Terminal plan
– Cable plan
– Terminal strips overview
– Cable overview
– Terminals connection plan
– Parts list
– Device list
– Terminals parts list
– Switch cabinet layout
– Table of Contents
– Title page/cover page
– PLC overview
Compared to EPLAN, Comos has more options for handling information. For example,
you can collect data in object queries that is completely seperated from any type of
documentary display. Cosmos only makes a graphic representation of the data in the
reports.
Project data
EPLAN projects (i.e. engineering data) fundamentally only exist in the form of documents
("pages"). These pages contain all engineering details and also anything from one to seven
references (links) to symbol files. There is no separate form of data management such as
there is in Comos in the form of objects.
In Comos there is also a document-oriented view of the engineering data in the form of the
reports, but Comos reports and EPLAN pages do not match functionally one to one. In
Volume 120, section EPLAN pages compared to Comos reports (Page 145) you can find a
comparison of the most important properties from the import point of view.
Binary files
Moreover, binary files can be managed within EPLAN. Comos can of course manage binary
files of all types, but these files cannot be imported from Comos via the EPLAN interface.
They have to be transported "by hand" to Comos if required.
File endings
● *.exf
EPLAN eXchange format. An EPLAN project is saved and managed in a database. This
database consists of multiple single files. The EXF format provides a complete EPLAN
project as a single file.
Operation in Eplan: *drawings "Data exchange" | EPLAN ->EXF-Export | Circuit diagram:
Creates an exf file.
● *.sym
Symbol files, this is approximately like the symbols of the base data in Comos.
Operation in Eplan: *symbols (.SYM) "Data exchange" | EPLAN ->EXF-Export | Plot
frame: Creates an asc file per symbol database.
● *.asc
Article base data, evolves from the converted sym files.
● *.skg
Eplan plot frame, this is approximately like a report template.
Operation in Eplan: *Plot frame (.SKG) "Data exchange" | EPLAN ->EXF export | Plot
frame: Creates an exp file per plot frame.
● *.exp
Eplan plot frame, is created from a converted skg file.
● *.sk* (except *.skg)
Forms (.SK*) depends on the form type. Operation in Eplan: "Data exchange" | EPLAN -
>EXF export| Forms: Creates an nto file for each form.
14.1.2 EPLAN pages compared to Comos reports
Page numbering
("pages"). The identification of the engineering information kept is done primarily through the
designation of documents; thus this property has considerably greater importance within
EPLAN than in Comos.
See also Volume 120, section The EXF tabin section Preparing a Comos engineering project
(Page 149).
Page type
EPLAN pages always have an entry under "Type". A page type is meant with this.
● "Type" (EPLAN):
A = Circuit diagram ("Logical, Interactive")
B = Free graphic "(Graphic, Interactive)
"C = Switch cabinet layout "(Graphic, Interactive)
"D = Plot frame generation "(Graphic, Interactive)
"E = Title page/cover page "(Graphic, Interactive)
"J = Table of contents "(Graphic, Automatic)
"K = Terminal plan" (Graphic, Automatic)
"L = Terminal parts list" (Graphic, Automatic)
"M = Terminal connection plan" (Graphic, Automatic)
"N = Cable plan" (Graphic, Automatic)
"O = Parts list" (Graphic, Automatic)
"U = Ordering list" (Graphic, Automatic)
"P = Device list" (Graphic, Automatic)
"Q = PLC page" (Logical, Automatic)
"R = Terminal strip overview" (Graphic, Automatic)
"S = Cable overview "(Graphic, Automatic)
"T = PLC (SPS) overview" (Graphic, Interactive)"
Meaning:
– "Graphic, Automatic" - Roughly corresponds to evaluation reports.
– "Graphic, Interactive" - Roughly corresponds to interactive reports.
– "Logical (Automatic / Interactive)" - Roughly corresponds to logical diagrams.
The EPLAN "Type" often corresponds to the EPLAN "Form". This "Type" or "Form" generally
has no counterpart in Comos, since a sharper differentiation must be made within in Comos
with its considerably broader functional scope. Instead, a combination of three factors
corresponds to this "Type" or "Form":
● "Drawing type" (or a "Symbol Type" in the report template")
"EPLAN pages are converted into one of the DETAIL drawing types: These drawing types
are created especially for EE. Evaluation reports do not have any drawing type.
● "Report template"
The report templates are made up of a Master Report (created from a plot frame) and a
subreport (created from a form).
● Document base object
Document base objects are created in @O Documents |EXF EXF import. Document base
objects for EXF have the "EXF settings" tab and the following dialog fields there:
"Page type" (Comos field):
● EPLAN page
● Free graphic
● FG switch cabinet layout
● FG table of contents
● Plot frame generation
● RS scheme
● Terminal module holder overview
● SAPIM
● NCRS
● FG terminals plan
● FG terminals parts list
● FG terminals connection plan
● FG cable plan
● FG parts list
● FG device list
● EPLAN page for PLC
● Terminal strip overview
● Cable overview
● Title page/cover page
● PLC overview
"Form":
This field is not filled in manually as a rule, but takes over the text relating to the form used
when importing the EPLAN project data. The text is passed back to EPLAN when exporting,
and then EPLAN attempts to allocate a form on the basis of the text.
Many pages in EPLAN have a form, but by no means all. For example, EPLAN circuit
diagrams have no form, but on the other hand a switch cabinet layout does. Whether or not
an EPLAN page possesses a form therefore does not depend on whether this page is
interactive.
The EPLAN documentation explains the criteria by which EPLAN pages do or do not
possess forms.
Page size
EPLAN pages do not use DIN sizes. The page sizes must be transferred as well when
importing EPLAN pages.
In the ComosDB there are a number of report templates that have already been set up with
valid EPLAN page sizes. As a rule these report templates are marked with the appendage
"EPlangr".
Multi-page documents
As far as we know at the moment, there are no multi-page documents in EPLAN. Each
document thus comprises exactly one page. The affiliation of the pages can be determined
on the basis of the numbering. If pages are generated automatically (via a form), then
multiple separate pages are created as required.
In Comos there are multi-page documents.
Report templates for EXF: EXFConformable

The script option ExfConformable can be set in the options script of a report template.
Effect:
● The texts of the labelling segments can no longer be moved but instead appear at
specific positions. This position of the texts is controlled via: marking a segment, right-
click | Properties options group "Device tag position".
● Texts of components / devices, etc. can no longer be moved but appear at specific
positions.
● The grab points are deactivated.
14.1.3 Overview of an export of Comos data to EPLAN

In principle, "normal" Comos data can also be exported to EPLAN, but this data is then
placed as images or free graphics. Thus this data can no longer be changed or edited within
EPLAN. In practice, it is virtually impossible to organize the original Comos data in such a
way that a functional and consistent EPLAN project can be created with it.
If you nonetheless wish to work further with EPLAN, then proceed as follows:
● Create a special EXF project in Comos.
See also Volume 120, section Preparing a Comos engineering project (Page 149).
● Export all required base data in EPLAN:
Article base data; Symbols; Plot frame; Forms
See the EPLAN documentation, you can find a schematic overview of these procedures
in exporting article base data from EPLAN, p. 13-181, Exporting symbols from EPLAN, p.
13-183, Export plot frames from EPLAN, p. 13-187, Exporting forms from EPLAN, p. 13-
189.
● Export the base data from EPLAN to Comos.
See also Volume 120, section Importing EPLAN data (EPLAN -> Comos) (Page 152).
● Export an engineering project as EXF in EPLAN.
See the EPLAN documentation, there is a schematic overview of this procedure in
Volume 120, section Exporting projects from EPLAN (Page 160).
● Import the EXF data to Comos.
See also Volume 120, section Importing EPLAN data (EPLAN -> Comos) (Page 152).
14.2 Preparing a Comos engineering project
● Continue processing the data in Comos

See also Volume 120, section Working in Comos with (imported) EXF data (Page 165).
● Export the modified engineering data as an EXF file in Comos.
See also Volume 120, section Exporting from Comos (Comos -> ExF) (Page 168).
● Import the EXF data to EPLAN:
See the EPLAN documentation.

The Comos project must be linked with the following template: @J Project |@X Project
suppositions EXF.
This project template has the following specialties:
● An "EXF" attribute tab is created in the project. This "EXF" tab is created in the base data
in @Y Catalog attributes |EXF EXF Import| 04 Project settings EXF.
Purpose: EPLAN projects have project information. When importing to Comos, this
project information is read from the header of the EXF file and written in the "EXF" tab.
This data is evaluated again during an export operation and is also written into the header
of the exported EXF file. See further below regarding the "EXF" tab.
● A unit system is prepared in the mouse menu.
● The default document folder is prepared in the mouse menu
● A location system is prepared in the mouse menu
● The unit system, the default document folder and the location system originate from @J
Project |@X Project suppositions EXF.
● Regarding the prepared mouse menu, see Volume 120, section Working in Comos with
(imported) EXF data (Page 165).
The EXF tab
● Page numbering
("pages"). The identification of engineering information is done primarily through the
designation of the documents; thus this property has considerably greater importance
within EPLAN than in Comos.
Comos documents also have a "page", but this property actually contains only a page
number. The complex page numbering used in EPLAN is expressed in Comos through
the hierarchical structure of the engineering data.
Depending on the EPLAN page numbering, the engineering data created within Comos is
set up differently in an import operation:
– Overall numbering
The documents have a sequential number. This corresponds to the procedure used
within Comos of numbering documents sequentially within a document group. Within
EPLAN "sub-pages" (2a, 3B, 3.1, 3.8, etc.) are also permitted in such a case. The
overall numbering within EPLAN covers from 1 to 99999. The overall numbering
depends on the criteria within a unit.
Import: The newly generated reports are only created on the "Documents" tab.
– DIN: Unit (descr. location)
Apart from the page number, the unit is also used for identification. The location is
added as an additional description but does not play any role at all for identification. In
practical terms the option is thus identical to "DIN: Only unit".
Import: The newly generated reports are only created on the "Units" tab; the unit
structure is created accordingly.
– DIN: Unit and location
Apart from the page number, the unit and location are also used for identification.
EPLAN: Locations of the same name can also occur with different units; in such cases
it does not involve the same locations. The numbering always starts at 1 within the
locations.
Import: The newly generated reports are only created on the Units tab, but locations
are also created underneath the units. This involves a so-called "mixed structure" from
the Comos point of view.
– DIN: Only location
Apart from the page number, the location is also used for identification.
Import: The newly generated reports are only created on the Locations tab; the
location structure is created accordingly.
– DIN: Only unit
Apart from the page number, the unit is also used for identification. In practical terms
the option is thus identical to "DIN: Only unit (descr. location)".
– KKS
EPLAN: The KKS label (German power station labelling system) made up of two
characters is applied as the superordinate sort criteria. The unit comes after that.
● "Type of labelling"
This determines how the devices are labelled on the documents (or reports, as
applicable). EPLAN and Comos work in a sufficiently similar way to each other in this
respect. Example: If label type DIN: Unit and location was selected for the device, then
the following text is output on the report at the device: "=Anl1+Ort1|Kennzeichen". In the
case of "Anl1", etc., this of course involves a placeholder that is filled by the
corresponding text in the report. There are the following labelling types:
– "Device"
Import: The device label is created accordingly during the import operation. A
subsequent change to this entry no longer has any effect on existing Comos data.
Export: Is evaluated correspondingly in EPLAN. Please note: This setting must be
reconciled with "Page numbering" in accordance with the rules in EPLAN! The rules
currently applicable can be found in the EPLAN manual.
Example (valid as of the date of creating this manual):
"Page numbering" "1 overall numbering" allowed:
"1 Overall: Without page prefixes" / "2 Overall: With page prefixes"
– "Terminals"
Import: The EPLAN setting is used on the "EXF" tab, but is not evaluated in Comos.
Export: Is evaluated correspondingly in EPLAN.
– "Potentials"
Export: Is evaluated correspondingly in EPLAN.
– "Project data"
General details.
Export: Effect in EPLAN unknown.
Other specailties at the project level

Comos project options, Options tab:
Do not use any "Spaces" with units of the same type. This setting cannot be read within
EPLAN.
14.3 Importing EPLAN data (EPLAN -> Comos)
14.3.1 Importing EPLAN article base data to Comos
Exporting article base data from EPLAN

You can find details of the applicable procedure in the EPLAN documentation. Roughly
speaking, the procedure is as follows:
In the EPLAN main menu: Article | Management
In the following window, click on Data Transfer | Export.
Only mark the "Individual part" option in the "EPLAN item management - Export" dialog
window. All other options can be left at the defaults. The article base data is exported as an
asc file.
Importing article base data to Comos

Select Administrator | Base data| Import ECAD Components. See also Volume 120,
section ECAD components import (Page 103).
The article base data must be imported before the engineering data in all cases, since
otherwise the article base data cannot be allocated to these objects when importing the
engineering data.
Often the article base data is only imported once, since as a rule the base data remains
constant for a certain period of time.
● "File"
Here the file type must be changed to asc. After that the EPLAN file with the article base
data is selected.
● "Target"
The following object in the ComosDB must be set here by drag&drop: Import |EXF Eplan |
System special symbols |@A Article/Manufacturer catalog.
● "Read accessories"
This option is not evaluated in the case of asc files.
"ASCII-ANSI character set conversion"
This option is not evaluated in the case of asc files.
● "Log all"
If this option is activated, then all steps of the import operation are logged, otherwise only
any errors that occur.
Comos structure of the imported data

The main level of the base data already exists under |@A Article/Manufacturer catalog. Base
objects are created at this first level and get Attribute tabs on the basis of the imported data.
First of all, a level is created for the manufacturer and the articles follow underneath it. The
structure taken from EPLAN as of today is then as follows:
Import
|- EXF EPlan Import/Export
|- System special symbols
|- @A1 Article/manufacturer catalog
| 0 cannot be identified
|-...
|- A Assemblies
|- Bosch
|- 123abc article1
|- ...
|- Siemens
|- 456abc article1
|- ...
|- and so on
14.3.2 Importing EPLAN symbols to Comos
Exporting symbols from EPLAN

You can find details of the applicable procedure in the EPLAN documentation. Roughly
speaking, the procedure is as follows:
● In the EPLAN main menu: Data Transfer | EPLAN-> EXF export.
● In the following window, click on Export | Symbol files.
Symbol files have the extension "sym" and can be written as text files with the extension
"asc".
Import symbols into Comos

The Import/Export dialog is available in the "PlugIns" iconbar.
The symbol files must be imported before the engineering data in all cases, otherwise the
symbols cannot be allocated to these objects when importing the engineering data. Please
note: It may be necessary to call this functionality several times if the desired EPLAN project
addresses several symbol files.
Often the symbols are only imported once, since as a rule the symbol libraries remain
constant for a certain time period.
If the base data structure of a symbol file is to be updated, then you must delete the
corresponding base data branch in Comos and reimport the symbol file.
The "Symbol import" tab
● "File"
Here you can select the asc-file with the symbols.
The EXF tab in the case of symbol objects
● "Component type"
This field offers a standard table of all possible EPLAN components. This list is also gets
the cross-reference of the display. The component type also determines the allocation of
the class, subclass and "Special symbol". See the following.
● "Caption text"
In EPLAN texts that originate from the "Electrical value" and "Additional text" attributes
are output underneath a device.
The attributes "M11 Electrical value" and "M12 add. field" are therefore created for it on
the Comos EXF tab.
These attributes can be joined individually with other attributes by means of links.
Examples:
– In the case of a motor, with the capacity
– In the case of a fuse, with the turn-off capacity.
– In the case of other objects, with the description of the device (OwnDescription)
● "Article data"
In EPLAN up to 10 article numbers can be allocated to the components in the project
data.
Currently the first article number is read in Comos when importing the project data and
written in the device of the allocated symbol object in the first field of the "Article data".
See also Volume 120, section Importing project data (Page 160).
Comos structure of the imported data

The symbol file is transfered to the Comos structure in the course of the conversion:
1. Central import node Import | EXF EPlan
Please note: The import to the base project is made in all cases, even when an
engineering project has been opened! You must therefore have the corresponding
function rights.
2. Importing symbol files
One import per symbol file. The symbol files are created as base data; thus a separate
branch is created for each symbol file. If all seven forms of display of the symbol are used
within EPLAN, then seven symbol files must correspondingly be available and you need
to conduct the import into Comos seven times.
However, in Comos you are not restricted to seven symbol files. Underneath Import | EXF
EPlan you can create not just seven branches (= symbol files), but instead as many as
you wish.
3. One base object per symbol
One base object is created for each symbol. A symbol holds up to 512 symbols. As a
rule, placeholder objects are created for the symbols that have not been used yet. The
"Name" of the symbol base objects runs from 0 to 511.
The following steps are then carried out in the base objects of the symbols:
● Determine class / subclass

The Class / Subclass is set accordingly:
– Contacts (normally open, normally closed, etc.), component type from [0 - 49]: Class
"Element", subclass "None"
– Coils, component type from [50 - 99]: Class "Device", subclass "Contactors/relays"
– Terminals, component type from [100 - 149]: Class "Element", subclass "Terminal"
– All other objects: Class "Device"
● Transferring the tabs:
– "EBD" Mounting data
– "GD" Geometry data
– "HSD" Manufacturer data
– "LFD" Supplier data
– EXF
– SYS system
Note
Nothing is created on the "Symbols" tab at this level of the base data. The symbol
display is only done at the level of "variants".
1. One element object per "variant"

Up to four elements are created underneath the base object. Each of the four elements
thus displays one of the variants, with which symbols can be displayed in rotated form
within EPLAN.
A base data level is created for the variants in all cases, even if there is only one variant.
The base data structure looks like the following if configured correctly (example):
Import
|- DIC_WUPD symbol file
|- ...
|- 259 MMT motor with thermistor
and so on.
The following steps are then carried out in the base objects of the variants:
– Allocation "Special symbols"
Contacts and terminals are identified on the basis of the label abbreviation (S, SV,
etc.). A base object with a matching name is searched for in the Import |EXF Eplan |
System special symbols base data branch. If a suitable base object is found, a base
object link is set on the "System" tab of the variant object.
This allocation to the objects in SYSTEM special symbols is also needed in order to
set up a contact mirror.
The base object link interrupts the hierarchical inheritance. The element object now
inherits from the base object to which the reference (link) points. Exception: Symbol
script, see the following.
If no base object link is set, then the variants inherit from the symbol base object from
3 the attribute tabs taken from @A Article and the class/subclass.
– Transferring the EPLAN symbol to the "Symbols" tab
A symbol script is created from the data of the ExF symbol file and stored in Comos at
the base object of the relevant element on the "Symbols" tab.
This is also done if a base object reference had been set!
– Setting up a naming convention
If there is corresponding data in the symbol file, a corresponding text mask is created
on the "System" tab.
This does not occur in the case of a base object link.
– Creating connectors
In Comos symbols must have connectors so that they can be connected. This is done
by creating the corresponding connectors on the "Connectors" tab.
This does not occur in the case of a base object link.
14.3.3 Importing plot frames
Export plot frames from EPLAN

The applicable procedure is described in the EPLAN documentation. Roughly speaking, the
procedure is as follows:
● In the following window, click on Export | Plot Frame.
● The plot frame is written to an exp file when it is exported.
Importing plot frames to Comos

The Import/Export dialog is located in the "PlugIns" iconbar. Plot frames are created
within Comos in the form of Master Reports.
The plot frames must be imported before the forms in all cases, since otherwise the plot
frames (or in Comos, the Master Report) cannot be allocated to these objects when the
forms are imported.
Plot frames are often only imported once, since as a rule the templates remain constant for a
certain time period.
On importing a plot frame, the date and user are taken over from EPLAN. This means that,
instead of issuing a new timestamp for the master report, the master report takes over the
data of the plot frame.
The Plot frame tab
● "File"
Here you select the exp file that contains the plot frame.
● "Forms to"
Plot frames are converted into report templates within Comos. Here you stipulate where
the corresponding report templates are to be stored. As is usual within Comos, the report
templates can only be created within the base project.
A document group is already provided within the ComosDB. When the "EPLAN data
transfer" dialog window is opened, this document group is entered as the default.
However, another document group can be set instead by using drag&drop.
● "PLC overview"
No special plot frames are used within EPLAN for page type "PLC overview". In Comos
special reports are used for PLC.
The simplest way to synchronize EPLAN and Comos here is to import the same EPLAN
plot frame twice and to import the plot frame with the "PLC overview" option once. Effect:
– PLC overview deactivated: The Master Report that was created is given the "Detail"
drawing type.
– PLC overview activated: The created Master Report is given in the "Detail_2" drawing
type. In addition, the document objects and the crp files get the suffix "SPS" at the end
of the name.
14.3.4 Importing forms
Exporting forms from EPLAN

The applicable procedure is described in the EPLAN documentation. Roughly speaking, the
In the EPLAN main menu: Data Transfer | EPLAN-> EXF export.
In the following window, click on Export | Forms.
Importing forms to Comos

The Import/Export dialog is located in the "PlugIns" iconbar. EPLAN forms are created
within in Comos as subreports and thus require a plot frame to be created as the Master
Report.
Often the forms are only imported once, since as a rule the templates remain constant for a
certain time period.
The "Forms" tab
● "File"
A form is selected here. Each form must be imported individually.
● "Plot frames"
Here you stipulate the Master Report that was created in Volume 120, section Importing
plot frames (Page 158).
A Master Report is already provided within the ComosDB. When the "EPLAN data
However, another interactive report template can be set instead by using drag&drop.
Importing forms with identical names

Two or more EPLAN forms with identical names can be imported if they have different types
(file endings).
Their type is appended to their name with an underline character.
Example:
EPLAN: ABC.NTS, ABC.NTF
->
Comos Name: ANC_NTS, ABC_NTF
14.3.5 Importing project data
14.3.5.1 Exporting projects from EPLAN

The applicable prodcedure is described in the EPLAN documentation. Roughly speaking, the
● In the following window, click on Export | Project.
The EPLAN project is exported as an exf file.
14.3.5.2 General import details

● "Drawing type" (or a "Symbol Type" in the report template)
EPLAN pages are converted into one of the DETAIL drawing types:
– Page types "EPLAN page for PLC" and "PLC overview" (Comos document objects,
"EXF settings" tab, "Page type" field) are given the "DETAIL_2" drawing type when
imported,
– All other EPLAN pages get the "DETAIL" drawing type when imported.
Evaluation reports do not have any drawing type.
● Document base object
All pages receive @O Documents |EXF EXF Import |EXF Standard.
14.3.5.3 The EXF import tab
● "File"
The exf file is specified here.
Options group "Templates"

● "Template"
Here a plot frame that had been converted is stipulated as the Master Report.
A Master Report is already prepared within the ComosDB from Comos. When the
"EPLAN data transfer" dialog window is opened, this document group is entered as the
default. However, another interactive report template can be set instead by using
drag&drop.
● "PLC template"
Here a plot frame that had been converted is stipulated as the Master Report, whereby
the "PLC overview" option had been activated when it was imported to Comos.
A Master Report is already prepared within the ComosDB. When the "EPLAN data
However, another interactive report template can be set instead by using drag&drop.
● "Forms"
Here you stipulate the document group in which the converted EPLAN forms are located.
A document group is already provided within the ComosDB. When the "EPLAN data
However, another document group can be set instead by using drag&drop.
● "Start object"
Optional. Here you stipulate the start object for an article catalog. You should input the
following object here in the ComosDB:
Import | @EXF Eplan | System special symbols | @A Article/Manufacturer catalog.
Options group "Pages"

● "All / From...to"
As described above, EPLAN only recognizes single-page documents. These single-page
documents are also designated as "pages".
"All" activated All pages of the project are imported.
"All" deactivated State in the "From... to" fields which pages are to be imported. In this
case an exf file must already have been stipulated. The page information is taken from
this exf file and offered in a dialog window.
● "Only circuit diagrams"
Activated: Within this page range only those documents that are classified as "circuit
diagrams" are imported. Currently that applies to EPLAN pages with the label "1".
14.3.5.4 The import process
Creating the report

A report with all information on EPLAN page is produced within Comos.
Creating engineering objects

When the EPLAN pages are imported, the devices and any other objects placed on them are
investigated. The device have a text that designates the accompanying symbol. On the basis
of this text, a search is made in the Comos base data for the symbol file and within it, for the
symbol base object.
If the symbol is found, an engineering object is created underneath the report on the basis of
this symbol base object.
Allocating article base data and symbols

The device on the EPLAN page can additionally have up to ten different article numbers. The
first article number is written in the above symbol engineering object that has been created
on the "EXF" tab in the first field of the article data.
This article number is compared with the Comos base data in the @A Article/manufacturer
catalog branch. If a base object with the corresponding article number is found there, this
base object is copied under the symbol base object. The symbol engineering object is then
no longer based on the variant but instead has the article base object as base object:
Import
|- DIC_WUPD symbol file
|- ...
|- Siemens
|- 456abc article1
Connecting the report objects

No connection information is stored within EPLAN, instead only the relative position of the
objects to one another (under one another, next to one another) constitute the links. The
objects are simply connected to one another according to their position.
This function is reproduced in Comos during the import.
14.3.5.5 Converting individual objects
Allocating a device tag to components

Components without a device tag are collected at a node point. A graphic allocation of the
components is done towards the end of the import: A line is drawn whose height is exactly
one grid point is created. Starting from a component without device tag, a search is made to
the left for the next device tag.
Object without device tag is element: If a suitable object with a device tag is found, the
component without device tag is shifted within the engineering data underneath the object
with device tag that had been found. The device tag is taken over.
Object without device tag is device: The device tag is taken over. (In EPLAN it is possible to
have device tags that are not unique.)
It is possible that a component cannot be allocated, in which case it remains within the
collector nodes.
Terminals
1. EPLAN terminals only have one connector, while Comos terminals have two. In addition,
the two Comos terminals are classified as "inside" and "outside".
The second terminal connector is created automatically and connected graphically during
the import operation. This is done by drawing a line through the connector that exists and
identifies the next connector (in graphic terms) on the document.
2. A terminal strip is not input in the exf file for each terminal, but only for specific terminals.
The ExF label is not sufficiently unique to include all subsequent terminals of this terminal
strip (up to the next terminal strip).
For that reason the allocation of the terminals to the terminal strip is done as follows:
This allocation is taken over if there is a unique allocation of the terminal and terminal
strip within the ExF data.
All other terminals are allocated on a purely graphical basis. This is done by positioning
the terminals on the document as stipulated within the ExF data, after which the nearest
terminal with a terminal strip allocation is searched for horizontally to the left. (This is the
same method as in the allocation described above for the device tag.)
Contactors / coils: NClosed contacts, open contacts and changeover contacts

The names of open contacts, closed contacts, etc., are not unique in the ExF data. For that
reason the device tag is also accessed. Normally open contacts are created together with a
device tag. If a coil with the same device tag is found during the import operation, the
normally open contacts are shifted to under the coil (the coil becomes the owner of the
normally open contacts).
Path texts
The path texts are taken over and created as report objects. The path designation is written
in the description for all objects of the path.
Screening / shielding
EPLAN cables can have several forms of shieldings. The location of the shield connection
can be moved.
This functionality is to be implemented in Comos.
Connector points not joined on a connection

In EPLAN connectors can exist on a connection without actually being joined. This is not
possible in Comos, since all connectors are automatically linked to connections. The
conversion still remains open concerning this point.
Connections
In EPLAN connectors are automatically joined when they are uniquely allocated in a
graphical form (for example, vertically under one another without any obstacles in between).
If you do not want an automatic connection of this type in a particular case, then you have to
place an "interrupter" between the connectors in question between the two objects.
14.4 Working in Comos with (imported) EXF data
If a connection has to be "bent", then "diversion points" must be placed, these being objects
that only go to one connection and continue on at a right angle.
All these functionalities are reproduced when importing and exporting.
PE connectors
PE connectors are not uniquely marked as such in the ExF data. The conversion still
remains open concerning this point.
14.4.1 Prepared labelling systems and objects

If you right-click on the globe in the "Units" tab or the "Locations" tab, a number of objects
are offered to you.
A mixed system is available on the Units tab: subunits and also locations can be created
underneath units.
Only locations can be created on the "Locations" tab.
This object structure directly implements the "Page numbering" function from EPLAN and
may not be changed. For information on "page numbering", see Volume 120, section
Preparing a Comos engineering project (Page 149):subsection The EXF tab.
Note
If you export to EPLAN, the existing object structure, in connection with the "Page
numbering" project option has a decisive effect on the page numbering created within
EPLAN.
In other words: If you freely plan within Comos and then transport this data to EPLAN, then
you must pay close attention to ensure that the existing structure of the engineering objects
matches up with the "Page numbering" setting in the project.
The labelling systems are based on the base objects in Import | @EXF EPlan Im-/Export
| @EX objects under mouse menu New.
This catalogue is a copy of the Comos EE catalog but without its links and references. This
means that this catalog always has to be maintained separately.
14.4.2 Prepared objects in the categories

"Categories" are offered underneath the locations. This is a pure Comos technique.
Categories are automatically folders:
● Only specific objects are offered in the mouse menu of a category object. Thus only
specific objects can be created.
● And vice versa: the objects belonging to a category are automatically moved there if they
are created at another point.
14.4.2.1 Documents category
Circuit diagram
The circuit diagram has a document-specific symbol bar with the most important symbols.
PLC cross-references list

That is a PLC overview. PLC report templates also have the scripts required for PLC
terminals. See also the PLC device box in Volume 120, section Control category (Page 167).
14.4.2.2 Terminal strips category

Terminal strips have two stages in Comos: The terminals are elements of the terminal strip.
Before the terminals can be placed, first of all a terminal strip must be created.
Procedure:
● Create a terminal strip (special symbol -91)
● Create one of the offered terminals
● Placing terminals
14.4.2.3 Control category
PLC device box

The PLC device box also belongs to the "special symbols". This is displayed as a "segment"
on the circuit diagram and on the PLC cross-references list report. The PLC device box
object offers the following elements in the mouse menu:
● PLC terminal
PLC terminals can be placed both on circuit diagrams and on PLC cross-reference lists.
The PLC terminal can be regarded as a type of channel. PLC terminals are also called
"end terminals that can have cross-references".
● "Terminal setting" tab:
– The channel address is input in the "PLC address" field.
– The channel type is input in the "Connector type" field.
● Terminal
– "Normal" terminals possess no address, but can be allocated to a type of channel. The
type of channel can be stipulated on the "System" tab.
– "Normal" terminals can only be placed on circuit diagrams, not on a PLC cross-
references list.
● Plugs
As for terminals.
14.4.2.4 Cables category

Cables as per VDE and the special symbol "-93 cable" are offered here.
Special symbol "-93 cable"

Cables have two levels in Comos: The wires and screening are elements of the cables. The
cable is placed on the report, not the wires (differing from a two-stage terminal strip!).
Procedure:
● Create a cable (special symbol -93)
● Create the wires or screening
● Placing the cable on the report
14.5 Exporting from Comos (Comos -> ExF)
Alternative:
If only the screening needs to be displayed graphically or if you only have a screened cable,
then the procedure is as follows:
● Create a cable (special symbol -93)
● Create the shielding
● Place the shielding on the report
14.4.2.5 Devices category

All the electrical devices are offered here.
Contacts (normally closed, normally open) for coils or switches
The object first has to be selected in the case of contacts that only exist as elements under
the object. Example:
● Select a safety coil
● Select a contact for the safety coil
● Place the contact in the report
14.4.3 Cross-references
Objects that have been placed several times in the circuit diagram are displayed with cross-
references. Example: an auxiliary contact of a protective motor switch.
If symbols possess a cross-reference of this type, then the display of the cross-reference can
be controlled within the context-sensitive mouse menu for the symbol:
● Mouse-click on the symbol
● Right mouse button | Settings | Component type
● Select the type of cross-reference
14.5.1 Exporting from Comos (Comos -> ExF)

This section concerning exporting from Comos to EXF can only be understood if you have
already read the section about importing. The following only describes those input fields and
procedures that differ from those for import operations.
The Export dialogue is in the "PlugIns" iconbar.
14.5.2 The EXF export tab
General points regarding export

The Attribute tab "EXF settings" is in the Properties window of the report.
● "Page type":
All pages are exported as "free graphics", with the exception of pages of types "EPLAN
page" and "PLC EPLAN page".
The EXF export tab

● "File"
Input here in which exf file the export is to be made.
● "Start object"
– Start object is a document: only this document is exported.
– "Start object" is a unit, location or document group: all the documents located under it
are exported. This also includes those documents that only exist under the start object
as a reference or link: the document links are traced back to the original and this is
exported as well.
– "Start object" is blank: all the documents of the entire project are exported.
14.5.3 The Export symbols tab
The "Export symbols" tab enables the export to a previously imported symbol library or a
symbol library that had been created within Comos according to the rules for EPLAN.
The EPLAN methodology regarding symbol libraries

See Volume 120, section Importing EPLAN symbols to Comos (Page 153), subsection
Comos structure of the imported data.
It is necessary to pay special attention to the following points when exporting symbol
libraries:
● The "Component type" field must be set in a valid way on the EXF tab.
● This field offers a standard table of all possible EPLAN components.
The "Label" must be filled in. The symbol name is input in the "Label"; this is the description
by which the symbol is identified within the symbol file in terms of the contents.
Label Component type

C Capacitors
D Delay and storage devices
E Various (lighting, heating)
F Protective devices
G Generators
H Indicator modules (optical and acoustic)
K Contactors, relays
L Inductances
M Motors
M6 Motor with 6 connectors
N Amplifier regulators
P Measuring and test devices
Q Main power switchgear (power switches, protective switches)
R Resistances, potentiometers
SL Open power contacts
S Switches
T Transformers
U Modulators, converters
V Semiconductors, pipes
W Changeover contacts
WM Changeover contacts, middle
WR Changeover contacts, right
X Terminals, plugs, sockets
Y Electrically operated mechanical devices (solenoid valves, brakes)
Z Termination, filters, rectifiers
● The "Name" must be unique and should be meaningful

The symbols belonging to the standard as named as follows:
1st character: Device ID character
2nd character: Number of connector points
Example: Fuses
There is a fuse F1 and a fuse F3 in the symbol file from EPLAN. The ID character for
protective devices (fuses) is F. The number of current paths follows: 1 for a single fuse (1
current path) and 3 for the 3x fuse with three current paths
Symbols tab
Note the following regarding the symbol:
● It must be a quad grid.
● The connectors must be located on the grid points
The Export symbols tab

● "Export to file"
File name under which the symbol library is to be exported.
● "Symbol file to be exported"
Root node of the symbol library to be exported. This field is set via drag&drop.

Electrical Engineering

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Electrical Engineering

Uploaded by

Copyright:

Available Formats

Rights and license

Electrical Engineering ___________________

Siemens AG order number: HB120_90E05 Copyright © Siemens AG 2009.

1 Rights and license management................................................................................................................ 9

2.3.3 X Terminals, plugs ...................................................................................................................... 39

5.2 PPB part -, label lists....................................................................................................................55

8.5 Working with the "Connect device" dialog window ..................................................................... 87

12.2.3.3 Sorting the list area ....................................................................................................................114

14.3.4 Importing forms ......................................................................................................................... 159

2.2 EE| D Device view (DIN 40719)

2.2.1 DIN labels

Basic symbol (graphical symbol)

Additional symbol / placeholder texts

Option "Consider rotation of *V* variables".

2.2.3 Connectors and auxiliary connectors

2.2.4 Attributes and calculated attributes

2.2.5 Request properties

2.2.6 Product data

2.2.7 Device labelling

2.2.8 EE| D| I Potential

2.2.8.1 EE| D| I| A Potential

Control of the extended capabilities

Placing potentials on connections

Disconnecting potentials on the report

2.2.8.2 Predetermining potentials in the base data

2.2.8.3 Potential chains / Master-Slave potentials / Potential references

Chain -> Master / Converts a chain into a master-slave relationship

Label right Turns on the label at the right-hand end. The

2.2.8.4 Potentials with report object

2.2.8.5 EE |D |I |B Potential rails

Controling extended capabilities

Display and use on the report

Alternative display type:

2.2.8.6 EE |D |I |C Potential bundles

2.2.9 EE| D| K K Relays, coils

Control of the extended capabilities

Determining the position

Determining the position

2.2.10 EE |D |O O Other base objects

2.2.10.1 A O Blackboxes, segments

2.2.10.2 A O |01 O Blackbox, automatic contact points

Control of the extended capabilities

Blackbox across sheets:

2.2.10.3 A O |02 O Blackbox, Comos device

Control of the extended capabilities

Control of the extended capabilities

Without labelling segment With labelling segment

Label is valid for

2.2.10.5 A O |12 O Sheet areas I&C

2.2.11 EE| D| W Cables

2.2.11.2 Control of the extended capabilities

Basic cable, attribute tab "Technical data" tab (creating cable)

With protective grounding conductor

Basis cable, Attribute tab "Cable calculation"

Attribute tab "System data"

2.2.11.4 Symbols for cables

2.2.11.5 Complete cable

2.2.11.6 Placing the cable on the report

The cable is displayed on the diagram in the form of a dotted line.

The texts mean:

-W2 Name of the cable object

Settings for the cable symbol

Display and use on the report

Connect PE grounding conductor

Option "Consider rotation of V variables".