New Features

2018-19.00
Technical Inquiries
Please contact our support department!
E-Mail: [email protected]

Note:
Zuken is not responsible for any errors, which may appear in this documentation. Liability, due
to direct and indirect losses resulting from the delivery or use of this documentation, is
excluded to the extent permitted by law. This
documentation contains copyrighted information.
All rights, especially those pertaining to the duplication and distribution as well as the
translation, are reserved. This documentation, whether wholly or in part, may not be
reproduced in any form (photocopy, microfilm, etc.), or processed, duplicated or distributed
using an electronic system without Zuken’s prior written consent.

Contact
Zuken E3 GmbH
Lämmerweg 55
D-89079 Ulm/Einsingen

Phone: 07305/9309-0
Fax: 07305/9309-99
Web: http://www.zuken.com
E-Mail: [email protected]

© Copyright 2018, Zuken E3 GmbH

E3.series Releasenotes
Date: 6/6/2018

2018 Build 19.00

!! Please Note when Switching to New Version !!

Projects and databases are converted when opening them with this new E3.series Release.
Please consider that these projects cannot be edited with an older version afterwards. That's
why we recommend to backup projects before.

Note:

o The latest version of the license server must be installed when using a Flexnet-license
server. In particular, the provided new ECADLM.EXE must be used.
o Starting with Microsoft Office Version 2016, the TrueType font ‚Arial Unicode MS‘ is no
longer included in the standard delivery of Microsoft Office due to financial reasons.

This font has been and is still in use for E3.series, E3.template projects and E3.example
projects. You have most likely used this font to documents for E3.projects. Presently,
Zuken is not aware of any comparable functionality that is free-of-charge for ‚Arial
Unicode MS‘.

To ensure that your new and older projects and the documents generated from them are
displayed correctly on devices without older MS Office versions, we recommend you
purchase and install the original font ‚Arial Unicode MS Regular‘ on your devices.

o E3.series 2018 supports Windows Server 2016

Flexnet-Licence server does not support Windows Server 2016 Thus, the Flexnet-Licence
server must be installed on another operating system

This manual describes the following functions of version:

 New Features

1
Update Information of Version 2018

o Windows Support
o Installation
o Databases
o Projects
o Multi-User Installation
o ORACLE
o Microsoft SQL Server

Windows Support

The following Windows systems are supported with E3.series 2018:

 Windows 7
 Windows 8
 Windows 10
 Windows Server 2008/2012

For more information please refer to the installation description.

Installation

Before installing, we recommend you make a backup of your current installation (at least the
data and databases).

The installation of E3.series 2018 is started using

SETUP.EXE

which can be found on the DVD's main directory.

The Version can be installed in addition to an existing E3.series Version.

The Default Directory is: \Program Files\Zuken\E3.series_<version>

Therefore, this version can also be used alongside existing versions of E3.series. However,
note that you cannot use your existing database(s), or the existing projects, in both versions,
as they are updated when opened in E3.series 2018, so copies should be used for E3.series
2018.

Databases

With this new version, a new default database is installed. Existing databases are not
overwritten.

The new database contains new components and symbols.

Projects

Existing projects are automatically converted upon opening with the new version. So long as
the file has not been saved in the new version, it can still be opened with an older version.
After saving a project with E3.series Version 2018, a project can no longer be opened with an
earlier version.

2
Multi-User Installation

Existing multi-user projects from Version 2017 can directly be opened with Version 2018. They
are automatically converted upon opening. However, this cannot be undone, and the projects
can no longer be opened with Version 2017.

That’s why we recommend installing Version 2018 multi-user projects in parallel to the existing
version, so that it’s also possible to still access these project with E3.series Version 2017.

To transfer the projects to Version 2018, these projects must be saved in Version 2017 as
Single-User projects. They can then be stored in the multi-user environment of Version 2018.

In order to run the Multi-User databases in parallel

 a new SQL Server process must be installed for Microsoft SQL Server or another server
must be installed
 a new database user account for ORACLE must be used

The E3 Server process must then access the new database or the new database user account.

ORACLE

When setting up the E3-MU-Server, a new name must be specified for the Multi-User
Administrator.

Thus a new database user account is created and both E3.series versions can work
simultaneously in the multi-user environment.

Microsoft SQL Server

First, a new instance of the SQL Server processes must be installed.

Enter a new instance name, which must be used with the set-up installation of the E3-MU-
Server.

The rest of the installation continues as described in the separate MuSetup installation
description.

3
New Features 2018 Build 19.00
The following functionality is new in Version 2018 Build 19.00:

 Attributes

o Specify which Owner Shall Be Used for a Placeholder Assigned an

Attribute with Several Owners

 Cables/Conductors/Wires

o Conductors in Dynamic Cables and Wires Can Now Be Renamed in the Tree
View

 COM

 COM - DBE Interface

o New DbeComponentInterface for Editing Components in DBE

o New DbeAttributeInterface for Editing Attributes in DBE
o New DbeSymbolInterface for Editing Symbols in DBE
o New DbeTextInterface for Editing Symbol Texts in DBE
o New COM Interface DbeGraphInterface for Editing Graphics in DBE

 COM - E3_Starter

o Start E3 with Any Start-Up Parameter using COM

 COM-Interface - Miscellaneous

o Enhancement to Return Values in JobInterface for ExportPDF and

ExportPDFEx
o Enhancement to Return Value in SheetInterface for ImportDxf
o Enhancement to Return value in DeviceInterface for
RemoveFromInstallationSpace
o Enhancement to JobInterface for Loading and Saving Different
Device Table Views
o Change in 'Sheetinterface' for Creating Sheets with Regions (Checks
to make sure scale is not 0!)
o Enhancement to Return Value in 'SheetInterface' for 'AlignObjects'
o Enhancement to Return Value in 'SheetInterface' for 'PlacePart' and
'PlacePartEx'
o Enhancement to 'ApplicationInterface' for Controlling the Visibility of
Components and Symbols using Table Views
o Enhancement to JobInterface for Resetting Access Control on
Structure Nodes
o Enhancement to COM Interface for Querying Locked Objects
o Enhancement to TextInterface for Determining the Height of a Text
Box using an Existing Text and Specified Width

4
 o Enhancement to DeviceInterface for Reading Item Designation
without Suffix
o Flags for Position of Text Box for Get/Set Ballooning Now Evaluated
Correctly in TextInterface
o Enhancements to 'ApplicationInterface' and
'DbeApplicationInterface' for Saving and Restoring the Workspace
Configuration
o Enhancement to JobInterface for Exporting Structure Nodes and
Their Attributes
o Enhancement to DeviceInterface for Recognizing the Connector Type
'Feed-Through Connector'
o Enhancement to Return Values in JobInterface for ImportDrawing
and ImportDrawingEx
o Enhancement to SymbolInterface for Removing Reference Symbols
o Enhancement to 'ApplicationInterface' for Outputs in Output Window
Enabling User to Jump to Variant Tree by Double-Clicking
o Enhancement to 'DeviceInterface' for Determining the Terminal
Position on Mounting
o Enhancement to JobInterface for Checking whether Password Set for
Variant/Option Structure
o Enhancement to Return Value in JobInterface when using 'Save'
Informing User an Open External Document Has Been Closed without
Saving the Data
o Enhancement to DeviceInterface 'GetValidComponentCodes()' for
Returning the Desired List Options
o Enhancement to SymbolInterface for Accessing Database Symbol and
Reading Its Attributes
o Change to SymbolInterface for PlaceTable() so that No Table Can Be
Placed Outside Display Area of Sheet
o Enhancement to Return Value in the GroupInterface for Create() and
SetName() because Length of Name Limited to 256 Characters
o Change in Behavior and Return Value for Settings of
Variants/Options
o New ClipBoardInterface for Modifying Elements Contained therein
before Transferring to Project
o Change to Return Value in PinInterface for pin.HasDevice
o Enhancement to Return Value in JobInterface for SaveAs and in
ExternalDocumentInterface for CheckIn Informing User an Opened
External Document Was Closed without Saving the Data
o Enhancement to Return Value in SignalClassInterface for Delete and
RemoveSignalId if Error Occurs
o Enhancement to ComponentInterface for Determining Subtype of
Component
o Enhancement to SymbolInterface for Determining Subtype of Symbol
o Enhancement to PinInterface for Returning Cavity Part on Wire Ends
of Wire
o Change to Behavior in PinInterface for SetOuterDiameter

 Connections

o Specific Functionality of Inheriting Net Number Can Now Be Deactivated

o Display All Placed Conductors/Wires on Connection Line Ending on
Connection Node with the Property 'Passes wires' using Arrow Symbol
o Control whether the Name Equivalence Shall Also Be Considered in
addition to the Signal Equivalence when Routing Conductors

5
 Display

o Existing Sheet Area Now Adapted to New Sheet Format when Enlarging
Sheet Format of Formboard or Topology Sheets
o Control whether Grid Points Shall Also Be Enlarged when Zooming
o Component Preview Symbol Can Now Be Displayed in Preview Window
when Selecting Symbol in Schematic

 Electrical Checks

o Internal Resistance Can Now Be Defined for Individual Connector Pin

Terminals and Pins

 Export

o Enhancement to DXF/DWG Export

o Structure Node Assignments and their Attributes Can Now Be Exported
and Imported

 Fields / Dynamic Symbols

o Now Possible to Edit Corners of Fields (Add / Delete / Move)

 Graphics

o Possible to Control whether Arrowhead of Ballooning Text Points to

Graphic of Corresponding Symbol
o Arrows Can Now Be Placed on the Line Ends of Arcs
o User-Defined Line Types Can Now Also Be Used for Ovals and Curves (with
FONTS.DAT)
o 'Japanese Industrial Standards' Line Style Can Now Be Selected

 Placement / Purge

o Clipboard Structures/Structure Nodes with Contents Can Now Be Deleted

in the Tree View
o 'Place on Segment' Functionality Now Possible for Curved Connections

 Symbols

6
 o Defining the Symbol Order for the Component Definition Has Been
Simplified
o Table Symbols Now Possible for Normal Devices in Formboard
o Symbol Properties Can Now Be Called Up in Formboard Tables

 Terminals

o Location and Assignment Can Now Be Selected for the Internal and
External Sides in the Terminal Plan and Terminal Table

 Texts

o Text Properties Can Now Be Opened by Double-Clicking on Text

 Topology

 New Shared Sheets in Topology

o Multiple Display of Overlapping Regions on Separate Sheets

o Example: Topology Base Sheet and Its Shared Sheets
o Generate Shared Sheets using Specific Values
o Generate Shared Sheets Graphically
o Display Shared Sheets
o Overview of All Shared Sheet
o Restrictions
o COM Enhancement to SheetInterface for Creating Shared Sheets on
Topology Sheets

 Topology - Miscellaneous

o An Installation Space Can Now Be Placed Automatically for a Device

when Placing a Device on a Topology Sheet
o Harness Name Can Now Be Adopted by the Routed Conductors/Wires
in the Harness
o Now Possible to Place/Move Installation Spaces on Open Line Ends
o Several Devices Can Now Be Placed Simultaneously in an Installation
Space

 Tree Views / Bulk Data Management

o Device Table Configuration Can Now Be Saved (and Reloaded)

o Cable End Attributes Can Now Be Added to Cables in the Device Table
o Jump from Different Objects (Device, Symbol, Sheet) to the Database Tree

 Update in Project / Change Component

7
 o Control whether Signals on Connector Pins of Block Connector Shall Be
Overwritten when Updating Project
o Additional Assignment Now Possible when Changing Component

 Variants

o Procedure for Placing and Deleting Variant Positions Has Been Modified
o Export Translated Texts from Variant Tree in an XML File
o Assign Different Variants/Options to Pins of a Pin Group

 Views

o 'Normal' Device Symbols Can Now Be Defined as Symbol Views on

Connectors in E3
o Views Can Now Be Created even if Devices Placed on Locked Sheets

 Zoom / Pan / Selection

o Specific Object Types Can Now Be Filtered in a Area Selection

8
Attributes

 Specify which Owner Shall Be Used for a Placeholder Assigned an Attribute with
Several Owners

Specify which Owner Shall Be Used for a Placeholder Assigned an Attribute with
Several Owners

Previously, it wasn't possible to specify which owner should be used for a placeholder assigned
an attribute with several owners.

Now it's possible to define the desired owner (source) on the attribute in the database.

To do so, a new attribute must be created in the database editor like before, which is then
assigned to the text type (text placeholder) later. Since this attribute can have different
owners, a preselected owner must be defined. Afterward, the desired owner is selected for
the attribute assigned to the text type from a new selection list, which supplies the
corresponding information later in the project.

Preparations in Database Editor

Step 1: Create the attribute and assign the owner to be used

Create a new attribute (in the example BBB) in the Database Editor and select the owner to be
used for this attribute:

The following owners are available:

1. Cable
2. Cable end - with the connected end on the pin
3. Cable type
4. Cable type end - with the connected end on the pin
5. Cable conductor
6. Cable conductor end - with the connected end on the pin
7. Conductor type
8. Conductor type end- with the connected end on the pin
9. Hose/Tube
10. Hose/Tube end - with the connected end on the pin
11. Hose/Tube type
12. Hose/Tube type end- with the connected end on the pin

9
13. Hose/Tube inside
14. Hose/Tube inside end - with the connected end on the pin
15. Hose/Tube inside type
16. Hose/Tube inside type end - with the connected end on the pin
17. Net
18. Net segment
19. Signal
20. Special type: Connector pin terminal
The information is displayed by an attribute assigned to the pin terminal component for
this special type. The desired attribute must be selected from the column Assigned
Attribute under Database ->Format -> Text types. This attribute must have the
owner 'Component'.
21. Special type: Wire seal
The information is displayed by an attribute assigned to the wire seal for this special
type. The desired attribute must be selected from the column Assigned Attribute under
Database ->Format -> Text types. This attribute must have the owner 'Component'.

Step 2: Create the new text type and assign the attribute to this text type

Create a new text type (in the example AAA) in the database editor and assign the newly
created attribute to this text type:

Step 3: Assign the text type to the symbol

Add the desired text type to the symbol and group the text nodes on the corresponding pin:

10
Note:

11
  The attribute is evaluated only if the text is assigned to a pin.
Exceptions: Formboard symbols and attribute text template symbols

Step 4: Select the desired source for the text type

 right-click on the text type and select the Text Properties... command
 select the desired Owner for the text placeholder from the new drop-down list for the
text type under Source in Text Properties - Text:

12
Note:

Only the following symbol types are permitted:

 Normal symbol
 Connector symbol
 Attribute text template symbol
 Device symbol
 Table symbol
 Node template symbol

Note: The drop-down list is deactivated for all other symbol types that are not permitted.

Usage in Project Mode

The predefined attributes are now displayed on the symbol, provided that an entry exists in
the project:

Reference(s): Designer-15467

13
Cables/Conductors/Wires - Misc

 Conductors in Dynamic Cables and Wires Can Now Be Renamed in the Tree View

Conductors in Dynamic Cables and Wires Can Now Be Renamed in the Tree View

Previously, it wasn't possible to rename several conductors in dynamic cables and wires at the
same time in E3.series. With the new functionality Rename Conductors/Wires several
conductors and wires in dynamic cables can be renamed together in E3.series.

To do so, there is the new context menu command Rename Conductors/Wires in the tree
view.

To rename several conductors in dynamic cables or wires:

 using multi-select (pressing the CTRL or SHIFT key) in the device tree, select the desired
conductors/wires and then right-click
 select the new context menu command Rename Conductors/Wires:

 the Rename Conductors/Wires dialog opens:

Enter the desired new star and end values for the selected conductors/wires in the input
fields Start string: and End string:.

14
15
Rename Conductors/Wires

Start string Define the start value for the first conductor/wire name and then the
last value.

End string Note:

The following...

 maximum of 64 characters permitted

 alphanumeric characters are permitted
 none of the following characters are permitted: : , < > { } ' leading
or subsequent blank spaces

Displays the selected conductors/wires for renaming.

Selected
conductors/wires

New
conductor/wire Displays the new wire names. These are adopted after pressing OK.
names

Reference(s): Designer-05116

16
COM-Interface - Overview
Following functionalities are now available in the COM-Interface and are described in these
chapters:

 COM - DBE-Interface
 COM - E3_Starter
 COM-Interface - Miscellaneous

17
COM - DBE Interface

 New DbeComponentInterface for Editing Components in DBE

 New DbeAttributeInterface for Editing Attributes in DBE
 New DbeSymbolInterface for Editing Symbols in DBE
 New DbeTextInterface for Editing Symbol Texts in DBE
 New COM Interface DbeGraphInterface for Editing Graphics in DBE

New DbeComponentInterface for Editing Components in DBE

Enhancement to the DbeApplicationInterface for creating a new DbeComponentInterface

object:

 ret = e3dbe.CreateDbeComponentObject

o ret The return value is a DbeComponentInterface object.

 ret = e3dbe.GetComponentIds ( ids )

o ids Returns the IDs of all components, which are opened in the DBE.
o ret Number of IDs if successful, otherwise -1.

 ret = e3dbe.GetActiveComponentId

o ret The return value is the ID of the component on the current sheet if successful.
The following values are possible if an error occurs:

 -1 No project or no sheet opened!

 -2 Current sheet is not a component sheet!

The new DbeComponentInterface contains the following COM commands:

 ret = dbecmp.GetId

o ret The return value is the ID of the DbeComponentInterface object if

successful, otherwise 0.

 ret = dbecmp.SetId ( id )

o id ID of DbeComponentInterface object
o ret The return value is the ID of the DbeComponentInterface object if
successful, otherwise 0.

 ret = dbecmp.Remove ( save_changes )

o Removes the component from the DBE.

o save_changes Default value is 0. If the value is set to 1, all changes are saved.
o ret The return value is 1 if successful. The following values are possible if an error
occurs:

 -1 No project opened or no valid ID set!

18
  -2 Database is read-only!
 -3 Component could not be deleted!

 ret = dbecmp.Save

o Saves the current attribute.

o ret The return value is 1 if successful. The following values are possible if an error
occurs:

 -1 No project opened or no valid ID set!

 -2 Database is read-only!
 -3 The value could not be saved!

 ret = dbecmp.GetAttributeIds ( ids[, end, attnam] )

o ids Returns the IDS of the attribute.

o end The following values are possible and only valid for cable types:

 0 Attribute value of body

 1 Attribute value of end 1
 2 Attribute value of end 2

o attnam If set, then only attribute values of this attribute are returned.
o ret Number of IDs if successful, otherwise -1

 ret = dbecmp.AddAttributeValue ( name, value[, end] )

o name Name of the attribute

o value New value of attribute
o end The following values are possible and only valid for cable types:

 0 Attribute value shall be created on the body.

 1 Attribute value shall be created on end 1.
 2 Attribute value shall be created on end 2.

o ret The return value is the Id of the new attribute value if successful. The
following values are possible if an error occurs:

 -1 No project opened or no valid ID set!

 -2 The attribute value could not be added!

 ret = dbecmp.GetName

o ret Name of component

 ret = dbecmp.GetVersion

o ret Version of component

 ret = dbecmp.GetSubType

o ret The following values are possible:

19
  -1 No project opened or no valid ID set!
 0 No subtype assigned!
 1 Accessory component
 2 Fixture component
 3 Protection tube component
 4 Protection tape component
 5 Protector component
 6 Splice component

 ret = dbecmp.SetSubType ( subtype )

o subtype The following values are possible:

 0 No subtype assigned!
 1 Accessory component
 2 Fixture component
 3 Protection tube component
 4 Protection tape component
 5 Protector component
 6 Splice component

o ret The return value is the previous subtype. The following values are possible if
an error occurs:

 -1 No project opened or no valid ID set!

 -2 Subtype invalid!
 -3 Invalid component

Reference(s): Designer-31578

New DbeAttributeInterface for Editing Attributes in DBE

Enhancement to the DbeApplicationInterface for creating a new DbeAttributeInterface

object:

 ret = e3dbe.CreateDbeAttributeObject

o ret The return value is a DbeAttributeInterface object.

The new DbeAttributeInterface contains the following COM commands:

 ret = dbeatt.GetId

o ret The return value is the ID of the DbeAttributeInterface object if successful,

otherwise 0.

 ret = dbeatt.SetId ( id )

o id ID of a DbeAttributeInterface object
o ret The return value is the ID of the DbeAttributeInterface object if successful,
otherwise 0.

20
  ret = dbeatt.SetValue ( value )

o value Sets the value of the current attribute.

o ret The return value is 1 if successful. The following values are possible if an error
occurs:

 -1 No project opened or no valid ID set!

 -2 The value could not be set!

 ret = dbeatt.Delete

o Deletes the current attribute.

o ret The return value is 1 if successful. The following values are possible if an error
occurs:

 -1 No project opened or no valid ID set!

 -3 The value could not be deleted!

Reference(s): Designer-31579

New DbeSymbolInterface for Editing Symbols in DBE

Enhancement to the DbeApplicationInterface for creating a new DbeSymbolInterface

object:

 ret = e3dbe.CreateDbeSymbolObject

o ret The return value is a DbeSymbolInterface object.

 ret = e3dbe.GetSymbolIds ( ids )

o ids Returns the IDs of all symbols, which are opened in the DBE.
o ret Number of IDs if successful, otherwise -1.

 ret = e3dbe.GetActiveSymbolId

o ret The return value is the ID of the symbol on the current sheet if successful. If
an error occurs, the following values are possible:

 -1 No project or no sheet opened!

 -2 Current sheet is not a symbol sheet!

The new DbeSymbolInterface contains the following COM commands:

 ret = dbesym.GetId

o ret The return value is the ID of the DbeSymbolInterface object if successful,

otherwise 0.

 ret = dbesym.SetId ( id )

21
 o id ID of a DbeSymbolInterface object
o ret The return value is the ID of the DbeSymbolInterface object if successful,
otherwise 0.

 ret = dbesym.Remove ( save_changes )

o Removes the symbol from the DBE.

o save_changes Default value is 0. If the value is set to 1, all changes are saved.
o ret The return value is 1 if successful. The following values are possible if an error
occurs:

 -1 NO project opened or no valid ID set!

 -2 Database is read-only!
 -3 The symbol could not be deleted!

 ret = dbesym.Save

o Saves the current symbol.

o ret The return value is 1 if successful. The following values are possible if an error
occurs:

 -1 No project opened or no valid ID set!

 -2 Database is read-only!
 -3 The symbol could not be saved!

 ret = dbesym.GetAttributeIds ( ids[, attnam] )

o ids Returns the IDs of the attribute.

o attnam If set, only the attribute values of this attribute are returned.
o ret Number of IDs if successful, otherwise -1.

 ret = dbesym.AddAttributeValue ( name, value )

o name Name of attribute

o value New value of attribute
o ret The return value is the ID of the new attribute value if successful. The
following values are possible if an error occurs:

 -1 No project opened or no valid ID set!

 -2 The attribute value could not be added!

 ret = dbesym.GetGraphicIds ( ids )

o ids Returns the IDs of the graphics.

o ret Number of IDs if successful, otherwise -1.

 ret = dbesym.GetTextIds ( ids[, texttype] )

o ids Returns the text ID(s)

o texttype If set, only texts of this text type are returned.
o ret Number of IDs if successful, otherwise -1.

 ret = dbesym.GetName

o ret Name of symbol

22
  ret = dbesym.GetVersion

o ret Version of symbol

 ret = dbesym.GetCharacteristic

o ret Characteristic of symbol

 ret = dbesym.GetSubType

o ret The following values are possible:

 -1 No project opened or no valid ID set!

 0 No subtype assigned!
 1 Accessory symbol
 2 Fixture symbol
 3 MultiHolding symbol
 4 Connector symbol
 5 Detail symbol
 6 Figure symbol

 ret = dbesym.SetSubType ( subtype )

o subtype The following values are possible:

 0 No subtype assigned!
 1 Accessory symbol
 2 Fixture symbol
 3 MultiHolding symbol
 4 Connector symbol
 5 Detail symbol
 6 Figure symbol

o ret The return value is the previous subtype. If an error occurs, the following
values are possible:

 -1 No project opened or no valid ID set!

 -2subtype invalid!
 -3 Invalid symbol

Reference(s): Designer-31650

New DbeTextInterface for Editing Symbol Texts in DBE

Enhancement to the DbeApplicationInterface for creating a new DbeTextInterface object:

 ret = e3dbe.CreateDbeTextObject

o ret The return value is a DbeTextInterface object.

The new DbeTextInterface contains the following COM commands:

23
  ret = dbetxt.GetId

o ret The return value is the ID of the DbeTextInterface object if successful,

otherwise 0.

 ret = dbetxt.SetId ( id )

o id ID of a DbeTextInterface object
o ret The return value is the ID of the DbeTextInterface object if successful,
otherwise 0.

 ret = dbetxt.Create ( symbolid, texttype, x, y[, textvalue] )

o symbolid ID of DBE symbol

o texttype Sets the text type.
o x,y Coordinates of DBE symbol on the sheet relative to the 0 point
o textvalue Value of text
o ret The return value is the Id of the new text if successful. The following values
are possible if an error occurs:

 -1 No project opened or no valid symbol!

 -2 No valid text type!

 ret = dbetxt.Delete

o Deletes the current symbol text.

o ret The return value is 1 if successful. The following values are possible if an error
occurs:

 -1 No project opened or no valid ID set!

 -2 The text could not be deleted!

 ret = dbetxt.SetType ( texttype )

o Sets the text type.

o texttype Sets the desired text type.
o ret The return value is the ID of the new text if successful. The following values
are possible if an error occurs:

 -1 No project opened or no valid symbol!

 -2 No valid text type!

All additional new COM commands are identical with the COM commands from the
TextInterface:

 dbetxt.GetAlignment
 dbetxt.GetBallooning
 dbetxt.GetColour
 dbetxt.GetFontName
 dbetxt.GetHeight
 dbetxt.GetLevel
 dbetxt.GetLocking
 dbetxt.GetMode
 dbetxt.GetRotation
 dbetxt.GetSingleLine
 dbetxt.GetStyle

24
  dbetxt.GetText
 dbetxt.GetType
 dbetxt.SetAlignment ( newval )
 dbetxt.SetBallooning (onoff, type )
 dbetxt.SetColour (value )
 dbetxt.SetFontName ( newname )
 dbetxt.SetHeight ( newval )
 dbetxt.SetLevel ( newval )
 dbetxt.SetLocking ( newval )
 dbetxt.SetMode ( newval )
 dbetxt.SetRotation ( rotation )
 dbetxt.SetSingleLine ( newval )
 dbetxt.SetStyle ( newval )
 dbetxt.SetText ( newtext )

Reference(s): Designer-31655

New COM Interface DbeGraphInterface for Editing Graphics in DBE

Enhancement to DbeApplicationInterface for creating a new DbeGraphInterface object:

 ret = e3dbe.CreateDbeGraphObject

o retThe return value is a DbeGraphInterface object.

The new DbeGraphInterface contains the following COM commands:

 ret = dbegra.GetId

o retThe return value is the ID of the DbeGraphInterface object if successful,

otherwise 0.

 ret = dbegra.SetId ( id )

o idID of a DbeGraphInterface object

o retThe return value is the ID of the DbeGraphInterface object if successful,
otherwise 0.

 ret = dbegra.CreateArc ( symbolid, x, y, radius, start, end )

o Creates an arc at the desired position

o symbolid id of the symbol
o x, y center coordinates of the Arc (relative to symbol origin )
o radius radius of the arc
o start, end starting and ending angle of the arc
o ret Id of new graphic item if successful, otherwise -1.

 ret = dbegra.CreateCircle ( symbolid, x, y, radius )

o Creates a circle at the desired position

o symbolid id of the symbol
o x, y center coordinates of the circle (relative to symbol origin )

25
 o radius radius of the circle
o ret Id of new graphic item if successful, otherwise -1.

 ret = dbegra.CreateRectangle ( symbolid, x1, y1, x2, y2 )

o Creates a rectangle at the desired position

o symbolid id of the symbol
o x1, y1 lower left coordinates of the rectangle (relative to symbol origin )
o x2, y2 upper left coordinates of the rectangle (relative to symbol origin )
o ret Id of new graphic item if successful, otherwise -1.

 ret = dbegra.CreateLine ( symbolid, x1, y1, x2, y2 )

o Creates an line on the desired position

o symbolid id of the symbol
o x1, y1 first coordinates of the line (relative to symbol origin )
o x2, y2 second coordinates of the line (relative to symbol origin )
o ret Id of new graphic item if successful, otherwise -1.

 ret = dbegra.CreatePolygon ( symbolid, pnts, x, y )

o Creates a polygon at the desired position

o symbolid id of the symbol
o pnts number of points of the polygon
o x, y arrays from x-coordinates and y-coordinates
o ret Id of new graphic item if successful. The following values are possible if an
error occurs:

 -1 no symbol or no project
 -2 an array was not correct

 ret = dbegra.CreateCurve ( symbolid, pnts, x, y )

o Creates a curved polygon at the desired position

o symbolid id of the symbol
o pnts number of points of the polygon
o x, y arrays from x-coordinates and y-coordinates
o ret Id of new graphic item if successful. The following values are possible if an
error occurs:

 -1 no symbol or no project
 -2 an array was not correct

 ret = dbegra.CreateCloud ( symbolid, pnts, x, y )

o Creates a clouded polygon at the desired position

o symbolid id of the symbol
o pnts number of points of the polygon
o x, y arrays from x-coordinates and y-coordinates
o ret Id of new graphic item if successful. The following values are possible if an
error occurs:

 -1 no symbol or no project
 -2 an array was not correct

26
 ret = dbegra.CreateImage ( symbolid, xpos, ypos, xsize, ysize, filename, embed
)

o Creates an image at the desired position

o symbolid id of the symbol
o xpos, ypos lower left x-coordinate and y-coordinate of graphic item
o xsize, ysize x/y size of the image (if 0: original value)
o filename name of the image
o embed The following values are possible:

 1 (default) Image will be stored internally

 0 Only a reference to image will be stored internally

o ret Id of new graphic item if successful, otherwise -1.

 ret = dbegra.CreateBlob ( symbolid, filename )

o symbolid id of the symbol

o filename name of the file
o ret Id of new graphic item if successful. The following values are possible if an
error occurs:

 -1 no project or id is not valid

 -2 file not found
 -3 file could not be opened
 -4 file is empty

 ret = dbegra.SetBlobInfo ( filename )

o filename name of the file

o ret Id of new graphic item if successful. The following values are possible if an
error occurs:

 -1 no project or id is not valid

 -2 file not found
 -3 file could not be opened
 -4 file is empty

 ret = dbegra.SaveBlob ( filename )

o filename name of the file

o ret Id of new graphic item if successful. The following values are possible if an
error occurs:

 -1 no project or id is not valid

 -2 file exists
 -3 file has no blob or is empty
 -4 file could not be saved

 ret = dbegra.Place ( x, y )

o Places a graphic item on the desired position

o x, y desired x/y coordinates (lower left of graphic item)
o ret Return value is 1 if successful, otherwise 0.

 ret = dbegra.Delete

27
 o Deletes a graphic item
o ret Return value is 1 if successful, otherwise 0.

 ret = dbegra.GetTypeId

o ret The following values are possible:

 0 No valid graphic item

 1 Line
 2 Polygon
 3 Rectangle
 4 Circle
 5 Arc
 12 Image
 15 Curve
 16 Cloud
 17 Blob

 ret = dbegra.GetImageInfo ( xpos, ypos, xsize, ysize, filename, embed )

o Returns image info at the desired position

o xpos, ypos lower left x-coordinate and y-coordinate of the graphic item
o xsize, ysize x/y size of the image (if 0: original value)
o filename name of image
o embed The following values are possible:

 1 (default) Image will be stored internally

 0 Only a reference to image will be stored internally

o ret Return value is 1 if successful, otherwise 0

 ret = dbegra.SetImageInfo ( xpos, ypos, xsize, ysize, filename, embed )

o Sets image info on the desired position

o xpos, ypos lower left x-coordinate and y-coordinate of graphic item
o xsize, ysize x/y size of the image (if 0: original value)
o filename name of image
o embed The following values are possible:

 1 (default) Image will be stored internally

 0 Only a reference to image will be stored internally

o ret Return value is 1 if successful, otherwise 0

 ret = dbegra.GetArc ( xm, ym, rad, startang, endang )

o Gets coordinates of the arc

o xm, ym x,y coordinates of the arc (center position)
o rad Radius
o startang, endang start and end angle of the arc
o ret Return value is 1 if successful, otherwise 0.

 ret = dbegra.GetCircle ( xm, ym, rad )

o Gets the coordinates of the circle

o xm, ym x,y coordinates of the circle (center position)

28
 o rad Radius
o ret Return value is 1 if successful, otherwise 0.

 ret = dbegra.GetLine ( x1, y1, x2, y2 )

o Gets the coordinates of the line

o x1, y1 x,y coordinates of the line first point
o x2, y2 x,y coordinates of the line second point
o ret Return value is 1 if successful, otherwise 0.

 ret = dbegra.GetRectangle ( x1, y1, x2, y2 )

o Gets the coordinates of the rectangle

o x1, y1 x,y coordinates of the rectangle (lower left)
o x2, y2 x,y coordinates of the rectangle (upper right)
o ret Return value is 1 if successful, otherwise 0.

 ret = dbegra.GetPolygon ( npnts, xarr, yarr )

o Gets the coordinates of the polygon

o npnts Number of points
o xarr, yarr x/y array of coordinates
o ret Return value is 1 if successful, otherwise 0.

 ret = dbegra.GetCurve ( npnts, xarr, yarr )

o Gets the coordinates of the curve

o npnts Number of points
o xarr, yarr x/y array of coordinates
o ret Return value is 1 if successful, otherwise 0.

 ret = dbegra.GetCloud ( npnts, xarr, yarr )

o Gets the coordinates of the cloud

o npnts Number of points
o xarr, yarr x/y array of coordinates
o ret Return value is 1 if successful, otherwise 0.

 ret = dbegra.GetColour

o ret Returns colour of graphic. The color ranges from -1 to 255. -1 means 'use an
automatic color'.

 ret = dbegra.SetColour ( newcol )

o newcol new colour

o ret Return value is the previous colour if successful, otherwise 0.

 ret = dbegra.GetLevel

o ret Returns level of graphic

 ret = dbegra.SetLevel ( newlev )

o newlev new level

29
 o ret Return value is 1 if successful, otherwise 0.

 ret = dbegra.GetLineColour

o ret Returns colour of line. The color ranges from -1 to 255. -1 means 'use an
automatic color'.

 ret = dbegra.SetLineColour ( newcol )

o newcol new colour

o ret Return value is the previous colour if successful, otherwise 0.

 ret = dbegra.GetLineStyle

o ret Returns style of line.

 ret = dbegra.SetLineStyle ( newstyle )

o newstyle new style

o ret Return value is the previous style if successful, otherwise -1.

 ret = dbegra.GetLineWidth

o ret Returns width of line.

 ret = dbegra.SetLineWidth ( newwid )

o newwid new width

o ret Return value is the previous width if successful, otherwise -1.

 ret = dbegra.GetHatchColour

o ret Returns the line colour of a graphic hatch. The color ranges from -1 to 255. -1
means 'use an automatic color'.

 ret = dbegra.SetHatchColour ( newcol )

o newcol new colour

o ret Return value is the previous colour if successful, otherwise 0.

 ret = dbegra.GetHatchLineDistance

o ret Returns the line distance of a graphic hatch.

 ret = dbegra.SetHatchLineDistance ( newdist )

o newwid new width

o ret Return value is the previous width if successful, otherwise -1.

 ret = dbegra.GetHatchLineStyle

o ret Returns the line style of a graphic hatch.

 ret = dbegra.SetHatchLineStyle ( newstyle )

30
 o newstyle new style
o ret Return value is the previous style if successful, otherwise -1

 ret = dbegra.GetHatchLineWidth

o ret Returns the line width of a graphic hatch.

 ret = dbegra.SetHatchLineWidth ( newwid )

o newwid new width

o ret Return value is the previous width if successful, otherwise -1.

 ret = dbegra.GetHatchPattern ( angle1, angle2 )

o angle1 Returns angle1 from -90 to 90 degrees

o angle2 Returns angle2 from -90 to 90 degrees
o ret Following values are possible:

 1 solid hatch
 2 lined hatch
 4 crossed hatch

 ret = dbegra.SetHatchPattern ( newpat, angle1, angle2)

o newpat new pattern. The following values are possible:

 1 solid hatch
 2 lined hatch
 4 crossed hatch

o angle1 Valid angles are from -90 to 90 degrees

o angle2 Valid angles are from -90 to 90 degrees
o ret Return value is the previous pattern if successful, otherwise 0.

Reference(s): Designer-31654

31
COM - E3_Starter

 Start E3 with Any Start-Up Parameter using COM

Start E3 with Any Start-Up Parameter using COM

E3 can now be started with any start-up parameter (e.g. /multiuser) using COM.

This takes place using an internal or external script or a plug-in (e.g. in C#).

There are two different functions for starting E3.series with any E3 parameter, which returns
the CT.Application object of the started E3.series. These CODE fragments must be integrated
in the corresponding scripts or plug-ins.

The following function is used for internal scripts and plug-ins:

 object StartSameImage(string arguments, int milliSecondsTimeOut)

starts the same E3 exe, which executes the plug-in or internal script.

The following function is used for external scripts:

 object Start(string fileName, string arguments, int milliSecondsTimeOut)

Both functions block the script or plug-in until E3 signals it is ready or the timeout has expired.
If -1 is specified as the timeout, there is no time limit for the waiting time.

Examples

Example-Script 1 - only suitable for internal scripts and plug-ins

Set oProcessStarter = CreateObject("CT.E3Starter")

Set oE3 = oProcessStarter.StartSameImage( "/multiuser", -1 )

oE3.PutInfo 1, "Hello world"

Example-Script 2 - only suitable for external scripts (with timeout 30s and bug fixes)

Set oProcessStarter = CreateObject("CT.E3Starter")

Set oE3 = oProcessStarter.Start( "\\temp\ ... \Release\E3.series.exe",

"/multiuser", 30000 )

If( Err.Number ) Then

WScript.Echo Err.Description

Err.Clear

Else

oE3.PutInfo 1, "Hello world"

End If

32
Please note when using the COM-command 'StartSameImage':

In this case, the EXE must not be created. Otherwise, the call up will start the EXE. This may
cause an endless recursion, e.g.:

using System; using System.Collections.Generic; using System.Diagnostics; using

System.Linq; using System.Text; using System.Threading.Tasks; namespace
E3_Starter_sample { class Program { static void Main(string[] args) { int
e3ProcessId = 0; var e3Starter = new Zuken.E3Starter(); e3.IApplicationInterface
e3Application = null; Console.ReadLine(); try { // DON'T DO THIS IN A EXE -
BECAUSE THIS LEADS TO A ENDLESS RECURSION e3Application =
e3Starter.StartSameImage("/schema /nosplash /noplugin /multiuser", 30000) as
e3.IApplicationInterface; } finally {
System.Runtime.InteropServices.Marshal.FinalReleaseComObject(e3Application);
Process.GetProcessById(e3ProcessId).Kill(); } } } }

Registration Info

Note: If the registration wasn't successful, it can be implemented later.

 Start the E3_Starter.exe with administrator rights

 the E3_Starter Setup dialog opens:

By selecting the option field Register E3_starter for COM the COM interface can be
registered.

Reference(s): Designer-31155

33
COM-Interface - Miscellaneous

 Enhancement to Return Values in JobInterface for ExportPDF and ExportPDFEx

 Enhancement to Return Value in SheetInterface for ImportDxf
 Enhancement to Return value in DeviceInterface for
RemoveFromInstallationSpace
 Enhancement to JobInterface for Loading and Saving Different Device Table
Views
 Change in 'SheetInterface' for Creating Sheets with Regions (Checks to make
sure scale is not 0!)
 Enhancement to Return Value in 'SheetInterface' for 'AlignObjects'
 Enhancement to Return Value in 'SheetInterface' for 'PlacePart' and
'PlacePartEx'
 Enhancement to 'ApplicationInterface' for Controlling the Visibility of
Components and Symbols using Table Views
 Enhancement to JobInterface for Resetting Access Control on Structure Nodes
 Enhancement to COM Interface for Querying Locked Objects
 Enhancement to TextInterface for Determining the Height of a Text Box using
an Existing Text and Specified Width
 Enhancement to DeviceInterface for Reading Item Designation without Suffix
 Flags for Position of Text Box for Get/Set Ballooning Now Evaluated Correctly in
TextInterface
 Enhancements to 'ApplicationInterface' and 'DbeApplicationInterface' for
Saving and Restoring the Workspace Configuration
 Enhancement to JobInterface for Exporting Structure Nodes and Their
Attributes
 Enhancement to DeviceInterface for Recognizing the Connector Type 'Feed-
Through Connector'
 Enhancement to Return Values in JobInterface for ImportDrawing and
ImportDrawingEx
 Enhancement to SymbolInterface for Removing Reference Symbols
 Enhancement to 'ApplicationInterface' for Outputs in Output Window Enabling
User to Jump to Variant Tree by Double-Clicking
 Enhancement to 'DeviceInterface' for Determining the Terminal Position on
Mounting
 Enhancement to JobInterface for Checking whether Password Set for
Variant/Option Structure
 Enhancement to Return Value in JobInterface when using 'Save' Informing User
an Open External Document Has Been Closed without Saving the Data
 Enhancement to DeviceInterface 'GetValidComponentCodes()' for Returning the
Desired List Options
 Enhancement to SymbolInterface for Accessing Database Symbol and Reading
Its Attributes
 Change to SymbolInterface for PlaceTable() so that No Table Can Be Placed
Outside Display Area of Sheet
 Enhancement to Return Value in the GroupInterface for Create() and
SetName() because Length of Name Limited to 256 Characters
 Change in Behavior and Return Value for Settings of Variants/Options
 New ClipBoardInterface for Modifying Elements Contained therein before
Transferring to Project
 Change to Return Value in PinInterface for pin.HasDevice
 Enhancement to Return Value in JobInterface for SaveAs and in
ExternalDocumentInterface for CheckIn Informing User an Opened External
Document Was Closed without Saving the Data
 Enhancement to Return Value in SignalClassInterface for Delete and
RemoveSignalId if Error Occurs
 Enhancement to ComponentInterface for Determining Subtype of Component

34
  Enhancement to SymbolInterface for Determining Subtype of Symbol
 Enhancement to PinInterface for Returning Cavity Part on Wire Ends of Wire
 Change to Behavior in PinInterface for SetOuterDiameter

Enhancement to Return Values in JobInterface for ExportPDF and ExportPDFEx

Enhanced return values in JobInterface for ExportPDF and ExportPDFEx

 ret = job.ExportPDF
 ret = job.ExportPDFEx

o -11 outdated external document

o -12 non-existent link to external document

Reference(s): Designer-30225

Enhancement to Return Value in SheetInterface for ImportDxf

Enhancement to return value in SheetInterface for ImportDxf

 ret = sht.ImportDxf ( filename, scale, x, y, rot, font[, inbox] )

o ret item number of sheet; 0 returned in case of error or if maximum value

exceeded.
o inbox This parameter is evaluated differently now:

 TRUE Placed regardless of whether sheet format is suitable or maximum

value exceeded!
 FALSE Checks whether the maximum value has been exceeded!

Reference(s): Designer-30112

Enhancement to Return Value in DeviceInterface for RemoveFromInstallationSpace

Enhancement to return value in DeviceInterface for RemoveFromInstallationSpace

 ret = dev.RemoveFromInstallationSpace

o -3 if a functional unit is locked!

Reference(s): Tz44-00126

Enhancement to 'JobInterface' for Loading and Saving Different Device Table Views

Enhancement to JobInterface for loading and saving different Device Table views

The following new COM calls are in the JobInterface:

35
  ret = job.LoadTableConfiguration ( file, table )
 ret = job.SaveTableConfiguration ( file, table )

o file File name with extension ( *.bdt) and complete path

o table The following values are possible:

 1 Device Table
 >1 For additional tables but not yet implemented!

o ret The following values are possible:

 0 Call was executed correct

 -1 No project opened or no job-item selected
 -2 Wrong file extension
 -3 Unknown table
 -4 Table not found
 -5 File could not be written correctly

Reference(s): Designer-22997

Change in 'Sheetinterface' for Creating Sheets with Regions (Checks to make sure
scale is not 0!)

The behavior of the parameters 'modi' and 'refscale' for the following COM calls has been
adapted in the Sheetinterface:

 ret = sht.CreateFormboard ( modi, .... )

o modi should be 0

 ret = sht.CreateFormboardEx ( modi, .... , refscale )

 ret = sht.CreatePanel ( modi, .... , refscale )
 ret = sht.CreateTopology ( modi, .... , refscale )

o modi should be 0
o refscale Defines the scaling factor for the sheet region. If the refscale is less than
or equal to 0, the scaling factor is set to 1.

Reference(s): Designer-30597

Enhancement to Return Value in 'SheetInterface' for 'AlignObjects'

Enhancement to return value in SheetInterface for AlignObjects

 ret = sht.AlignObjects

o -6 Sheet is locked!

36
Reference(s): Designer-30601

Enhancement to Return Value in 'SheetInterface' for 'PlacePart' and 'PlacePartEx'

Enhancement to return value in SheetInterface for PlacePart and PlacePartEx

 ret = sht.PlacePart
 ret = sht.PlacePartEx

o -4 Sheet is locked!

Reference(s): Designer-30585

Enhancement to 'ApplicationInterface' for Controlling Visibility of Components and

Symbols using Table Views

The following new COM calls are in the ApplicationInterface:

 ret = e3.SetComponentDataView ( name )

o name Name of the component view, whose visibility shall be controlled

o ret The following return values are possible:

 0 The command was executed successfully!

 1 Since the set view doesn't exist, an empty component view is used.
 2 Since the set view doesn't have all the columns of the Component Table,
an empty component view is used.
 3 Neither the set view nor the empty component view exists!
 4 The set view doesn't exist and the empty component view doesn't have all
the columns of the Component Table.
 5 The call is not permitted in the DBE.

 ret = e3.GetComponentDataView

o ret The return value is the set component view.

 ret = e3.SetSymbolDataView ( name )

o name Name of the symbol view, whose visibility shall be controlled

o ret The following return values are possible:

 0 The command was executed successfully!

 1 Since the set view doesn't exist, an empty symbol view is used.
 2 Since the set view doesn't have all the columns of the Symbol Table, an
empty symbol view is used.
 3 Neither the set view nor the empty symbol view exists!
 4 The set view doesn't exist and the empty symbol view doesn't have all the
columns of the Symbol Table.
 5 The call is not permitted in the DBE.

 ret = e3.GetSymbolDataView

o ret The return value is the set symbol view.

37
Reference(s): Designer-30336

Enhancement to JobInterface for Resetting Access Control on Structure Nodes

The following new COM call is in the JobInterface:

 ret = job.RemoveAccessControlInformation

o ret The return value is always 0.

Reference(s): Designer-29724

Enhancement to COM Interface for Querying Locked Objects

There is a new COM call in the following COM interfaces:

 DeviceInterface
 PinInterface
 StructureNodeInterface
 SheetInterface

o ret = obj.IsLockedByAccessControl

 ret The following values are possible:

 0 Object is unlocked!
 1 Object is locked!
 2 Object is locked indirectly by the sheet!
 3 Object is locked and also indirectly by the sheet!

Reference(s): Designer-29724

Enhancement to TextInterface for Determining the Height of a Text Box using an

Existing Text and Specified Width

The following new COM command is in the TextInterface:

 ret = txt.CalculateBoxHeight ( width, text, fontname, fontSize, fontStyle,

wordBreak, recHeight, recWidth, lines )

o width Width of the text field

o text Text; localized text variables are taken from the database and replace the
text values when they are found. There is no warning or error message if a text
variable is not found!
o fontname Text font name
o fontSize Font size
o fontStyle The following values are possible:

 1 bold
 2 italic

38
  4 underline

o wordBreak Value 1 is used to wrap texts in the box. Words which contain
punctuation (.,?!;:-) are wrapped on the point where the punctuation is located to
enable a better fit, regardless of their value.
o recHeight Returns the height of the box.
o recWidth Returns the width of the box.
o lines Returns the number of lines in the box. If this value = 0, the lowest value is
used for the calculation, e.g. width =1
o ret The following values are possible:

 3 No calculation was performed!

 2 when wordBreak = 0 and when the width is too narrow to fit the longest
word, the necessary width will be returned.
 1 The calculation was performed but an alternative default value was used,
e.g. font not found!
 0 The calculation was successful!
 -1 Error occurred due to erroneous width!
 -2 Miscellaneous error

 ret = txt.CalculateBoxHeightEx ( width, text, fontname, fontSize, fontMode,

fontStyle, recHeight, recWidth, lines )

o width Width of the text field

o text Text; localized text variables are taken from the database and replace the
text values when they are found. There is no warning or error message if a text
variable is not found!
o fontname Text font name
o fontSize Font size
o fontMode character spacing. The following values are possible:

 1 Normal
 2 Narrow
 3 Wide

o fontStyle The following values are possible:

 1 bold
 2 italic
 4 underline

o recHeight Returns the height of the box.

o recWidth Returns the width of the box.
o lines Returns the number of lines in the box. If this value = 0, the lowest value is
used for the calculation, e.g. width =1
o ret The following values are possible:

 3 No calculation was performed!

 1 The calculation was performed but an alternative default value was used,
e.g. font not found!
 0 The calculation was successful!
 -1 Error occurred due to erroneous width!
 -2 Miscellaneous error

39
Note: The calculation doesn't take into account if the text is rotated or in ballooning.

Reference(s): Designer-24454

Enhancement to DeviceInterface for Reading Item Designation without Suffix

The following new COM calls are in the DeviceInterface:

 ret = dev.GetNameEx ( flags )

 ret = dev.GetAssignmentEx ( flags )
 ret = dev.GetLocationEx ( flags )

o flags The following values are possible:

 1 GetName without SuffixNumber

 != 1 GetName

o ret The return value is a string if successful, otherwise an empty string.

Reference(s): Designer-25949

Flags for Position of Text Box for Get/Set Ballooning Now Evaluated Correctly in
TextInterface

The following COM call in the TextInterface has been changed:

 ret = txt.GetBallooning

o ret The following values are returned:

 &h0020: Center text box

 &h0040: Bottom text box
 &h0080: Top text box

 ret = txt.SetBallooning ( onoff, type )

o type The following values are returned:

 &h0020: Center text box

 &h0040: Bottom text box
 &h0080: Top text box

Reference(s): Designer-30624

Enhancements to 'ApplicationInterface' and 'DbeApplicationInterface' for Saving and

Restoring the Workspace Configuration

The following new COM calls are in the ApplicationInterface and DbeApplicationInterface:

40
 ret = app.SaveWorkspaceConfiguration ( name )

o Generates or overwrites the workspace configuration. A workspace configuration

file is generated in "%APPDATA%\Zuken\E3.series\<version>\<module>-
default.xml.
If a workspace file exists, it is automatically overwritten without a query dialog.
o name Name of the workspace configuration; default used if no parameter
specified.
o ret The following return values are possible:

 1 The command was executed successfully!

 -1 There is no E3 window!
 -2 There is no active configuration!
 -3 The current configuration cannot be set as active!
 -4 The configuration could not be saved, e.g. the configuration file is read-
only.
 -12 E3 is in full screen mode!

 ret = app.RestoreWorkspaceConfiguration ( name )

o Restores the corresponding workspace configuration

o name Name of the workspace configuration; When no parameter is given, the
currently valid configuration will be restored.
o ret The following return values are possible:

 1 The command was executed successfully!

 -1 There is no E3 window!
 -2 There is no current configuration!
 -3 The current configuration cannot be set as active!
 -4 The configuration file cannot be changed, e.g. the configuration file is
read-only.
 -6 The reference xml file could not be loaded!
 -10 The workspace configuration is not part of the xml file!
 -12 E3 is in full screen mode!

 ret = app.LoadWorkspaceConfigurationFromFile ( name, path )

o Loads a workspace configuration from an XML file and starts the configuration. The
one currently valid is overwritten by the newly loaded one.
It is not merged with the locally valid XML file!
o name Name of the workspace configuration.
o path Name of the configuration file with complete path specification
o ret The following return values are possible:

 1 The command was executed successfully!

 -1 There is no E3 window!
 -6 The reference xml file could not be loaded!
 -7 The specified xml file is not available!
 -8 The xml file in %appdata% could not be loaded!
 -9 The current configuration could not be set as active!
 -10 The transferred workspace configuration is not part of the xml file!
 -12 E3 is in full screen mode!

41
  ret = app.DeleteWorkspaceConfiguration ( name )

o Deletes the corresponding workspace configuration

o name Name of the workspace configuration.
o ret The following return values are possible:

 1 The command was executed successfully!

 -1 There is no E3 window!
 -2 There is no active configuration!
 -3 The current configuration cannot be set as active!
 -4 The configuration could not be saved, e.g. the configuration file is read-
only.
 -5 Treats it as the default configuration; it may not be deleted!
 -10 The workspace configuration is not part of the xml file!
 -12 E3 is in full screen mode!

 ret = app.GetWorkspaceConfigurations ( names, path )

o Lists all defined configurations with path\filename

o names Lists all configuration files with complete path specifications and file
names.
o path Determined from a temporary file.
o ret The following return values are possible:

 >0 Returns the number of defined configurations.

 -6 The reference xml file could not be loaded!
 -7 The specified xml file is not available!
 -8 The xml file in %appdata% could not be loaded!
 -12 E3 is in full screen mode!

 ret = app.GetWorkspaceName

o ret Returns the name of the current configuration.

Reference(s): Designer-10005

Enhancement to JobInterface for Exporting Structure Nodes and Their Attributes

The following COM call in the JobInterface has been enhanced:

 ret = job.ExportDrawing ( file, ids, options )

o options New option:

 131072 Export structure nodes including their attributes. This is only valid
for projects, for clipboards structure nodes can’t be exported.

42
Reference(s): Designer-10808

Enhancement to DeviceInterface for Recognizing the Connector Type 'Feed-Through

Connector'

The following new COM command is in the DeviceInterface:

 ret = dev.IsFeedThroughConnector

o ret The return value is 1 if treated as a feed-through connector, otherwise 0.

Reference(s): Designer-30286

Enhancement to Return Values in JobInterface for ImportDrawing and

ImportDrawingEx

Enhancement to the return values in JobInterface for ImportDrawing and

ImportDrawingEx:

 ret = sht.ImportDrawing
 ret = sht.ImportDrawingEx

o 4 The XML project structure is missing or different!

Reference(s): Designer-10808

Enhancement to SymbolInterface for Removing Reference Symbols

The following new COM command is in the SymbolInterface:

 ret = sym.RemoveFromSheetReference

o ret Return value may contain the following values:

 1 The command was executed successfully!

 0 The command couldn't be executed, e.g. symbol has no reference or an
incorrect reference type!
 -1 Internal error

Reference(s): Designer-30582

Enhancement to 'ApplicationInterface' for Outputs in Output Window Enabling User

to Jump to Variant Tree by Double-Clicking

The following COM commands have been changed in the ApplicationInterface:

 ret = app.PutMessage ( message, item )

 ret = app.PutInfo ( wait, message, item )
 ret = app.PutWarning ( wait, message, item )
 ret = app.PutError ( wait, message, item )

43
 o item New valid item type:

 Variant

Reference(s): Designer-29805

Enhancement to 'DeviceInterface' for Determining Terminal Position on Mounting

The following new COM command is in the DeviceInterface:

 ret = dev.GetSpaceRequirementOnCarrier ( lowerleft, upperright, origin,

carrierid )

o Returns the space requirement of the device on a carrier

If the device is not placed on a carrier, this function returns the lower left, upper
right and origin position of the unrotated device.
If the device is placed on a carrier, this function returns the lower left, upper right
and origin position of the device in relationship to the unrotated carrier.
o lowerleft Array of x/y/z coordinates of the lower left point
o upperright Array of x/y/z coordinates of the upper right point
o origin Array of x/y/z coordinates of the origin point
o carrierid If the parameter is 0 (default), the carrier of the device is evaluated.
o ret Following values are possible:

 0 The call was successful.

 -1 No valid device has been set in the device.
 -2 The given device has no main outline.
 -3 The given carrier id is not valid.

Reference(s): Designer-30070

Enhancement to JobInterface for Checking whether Password Set for Locking

Variant/Option Structure

The following new COM command is in the JobInterface:

 ret = job.IsVariantStructurePasswordProtected

o ret The return value is 1 if a password is set for locking the variant/option
structure, otherwise 0.

Reference(s): Designer-31230

Enhancement to Return Value in JobInterface when using 'Save' Informing User an

Open External Document Has Been Closed without Saving the Data

Enhancement to return value in JobInterface:

 ret = job.Save

44
 o ret The return value is 3 if an open, external document has been closed without
saving the data.

Reference(s): Designer-31156

Enhancement to DeviceInterface 'GetValidComponentCodes()' for Returning the

Desired List Options

The following new COM command is in the DeviceInterface:

 ret = dev.GetValidComponentCodesEx ( names, flags )

o names Returns all valid component codes

o flags X = Valid for component type
o
Flag &H0001 &H0002 &H0004 &H0008 &H0010
Description Expand Match Reduce Components Components
pins/cores pins/cores pins/cores without which can be
structures used as variant

Component
Type

Connectors x x x x x
Normal x x
component
Cable x x x x
Hose/Tube x x x x
Assemblies x x
Overbraid x x x x
x x x x
Part of
overbraid
(only
expandable
overbraids)

Cable duct / x
Mounting rail
Feed-through x x x x
connector
Without x
structure
x x x x x
Block

o ret Number of components found

Example:

Dim e3 : Set e3 = CreateObject("CT.Application") Dim prj : Set prj =

e3.CreateJobObject() Dim dev : Set dev = prj.CreateDeviceObject() devicecnt =
prj.GetAllDeviceIds( deviceids ) For i = 1 to devicecnt dev.setid deviceids(i)
e3.putInfo 0, "Search all components with more, less or equal pins for device "

45
& dev.GetName() cnt = dev.GetValidComponentCodesEx( names, &H0001 or &H0002 or
&H0004 ) For j = 1 to cnt e3.putInfo 0, VBTab & names(j) Next Next

Reference(s): Designer-31324

Enhancement to SymbolInterface for Accessing Database Symbol and Reading Its

Attributes

The following new COM command is in the SymbolInterface:

 ret = sym.GetSymbolTypeId

o ret The return value is the ID of the database symbol if successful, otherwise 0.

Example:

If job.GetSelectedSymbolIds(symbolIds) > 0 Then sym.SetId symbolIds(1) symid =

sym.GetSymbolTypeId() sym.SetId symid MsgBox "Last update:" &
sym.GetAttributeValue(".LAST_UPDATE") End If

Reference(s): Designer-31228

Change to SymbolInterface for PlaceTable() so that No Table Can Be Placed Outside

Display Area of Sheet

The following COM command has been changed in the SymbolInterface:

 ret = sym.PlaceTable ( fromId, x, y, [rot, [scale, [maintaintextsize]]])

o x, y Position of symbol. If the x and/or y coordinates lie outside of the sheet's

visible area, no symbol is placed.
o ret Return value is ID of placed symbol, otherwise 0. If the x and/or y coordinates
lie outside of the sheet's visible area, the return value is also 0.

Reference(s): Designer-31383

Enhancement to Return Value in the GroupInterface for Create() and SetName()

because Length of Name Limited to 256 Characters

The following COM command in the GroupInterface has been enhanced:

 ret = grp.Create ( ids, name )

 ret = grp.SetName ( name )

o ret -10 Name is too long. Only 256 characters are allowed.

Reference(s): Tz44-00560

46
Change in Behavior and Return Value for Settings of Variants/Options

The following COM command has been changed in the Im JobInterface:

 ret = job.GetBooleanState ( expression )

o The return value ignores Variant Display Settings

o ret = -2 No project is open
o ret = -1 If the Boolean expression is invalid (every error case). Reasons can be:

 There is a mistake in the format of the expression

 No expression is given (in other words the value is empty).
 The expression includes new line characters

Note: This function has changed its behavior and thus the results might differ from the already
existing user code. The return value ignores Variant Display Settings.

Reference(s): Designer-31220

New ClipBoardInterface for Modifying Elements Contained therein before

Transferring to Project

Enhancement to JobInterface for creating and requesting a new

ClipBoardInterfaceObject:

 ret = job.CreateClipBoardObject

o ret The return value is a ClipBoardInterface object.

 ret = job.GetClipboardIds ( ids )

o ids Returns the IDs of the clipboard.

o ret Number of IDs if successful, otherwise -1

The new ClipBoardInterface contains the following COM commands:

 ret = clp.GetId

o ret The return value is the ID of the clipboard object if successful, otherwise 0.

 ret = clp.SetId ( id )

o id ID of a clipboard object
o ret The return value is the ID of the clipboard object if successful, otherwise 0.

 ret = clp.GetName

o ret The return value is the name of the clipboard object

 ret = clp.GetAnyIds ( flags, ids )

47
 o ids Returns the elements within a clipboard; using flags it's possible to control
which elements are relevant.
o flags The following values are possible:

 &h01: All structure nodes within the clipboard

 &h02: All devices/cables within the clipboard
 &h04: All sheets within the clipboard
 &h08: All symbols (unassigned symbols, fields...) within the clipboard
 &h10: All wires in the system cable and of dynamic cables
 &h20: All external documents of the clipboard
 &h40: Structure nodes on the first level in the clipboard (&h01 or &h40
returns all structure nodes)

o ret The return value is the number of ids within the clipboard. The return value is
-1 if an error occurs.

 ret = clp.CommitToProject ( flags[, viewnumber])

o flags The following values are possible:

 &h01: Merge all non-colliding

 &h02: Merge by generating new names
 &h04: Merge as original
 &h08: Merge as view
 Note: A combination of 'Merge all non-colliding' and 'Merge by generating
new names' is possible; all other combinations not possible.

o viewnumber View number of the device. For 0 or if no view number is specified,

the next free view number is determined.
o ret The following return values are possible:

 1: The COM command was successfully executed!

 -1: No project / no set clipboard
 -4: No valid merge type
 -5: Invalid combination of different merge types
 -6: Invalid view number

 ret = clp.Delete
 ret = clp.DeleteForced ( as of Version 2018-1900 )

o ret The following return values are possible:

 1: The COM command was successfully executed!

 -1: No project opened or no clipboard item set!
 -2: The clipboard item may not be deleted!
 -3: The clipboard item could not be deleted!

 ret = clp.GetCollidingIds ( flags, ids )

o ids Returns the colliding elements within a clipboard; using flags it's possible to
control which elements are relevant.
o flags The following values are possible:

 0: All colliding devices, sheets, wires (also in dynamic cables)

 &h01: All colliding devices
 &h02: All colliding sheets

48
  &h04: All colliding wires (also in dynamic cables)

o ret The return value is the number of ids within the clipboard. The return value is
-1 if an error occurs.

Reference(s): Designer-30991

Change to Return Value in PinInterface for pin.HasDevice

The following COM command has been changed in the PinInterface:

 ret = pin.HasDevice

o ret The return value for conductors and wires is now always "0" (false).

Reference(s): Designer-24827

Enhancement to Return Value in JobInterface for SaveAs and in

ExternalDocumentInterface for CheckIn Informing User an Opened External
Document Was Closed without Saving the Data

The following COM command has been enhanced in the JobInterface:

 ret = job.SaveAs

o ret The return value is -4 if an opened external document has been closed without
saving the data.

The following COM command has been enhanced in the ExternalDocumentInterface:

 ret = extdoc.CheckIn

o ret The return value is -3 if an opened external document has been closed without
saving the data.

Reference(s): Designer-31459

Enhancement to Return Value in SignalClassInterface for Delete and RemoveSignalId

if Error Occurs

The following COM commands have been changed in the SignalClassInterface:

 ret = sigcla.Delete
 ret = sigcla.RemoveSignalId

o ret The return value is 1 in case an error occurs.

49
Reference(s): Designer-31633, Designer-31634

Enhancement to ComponentInterface for Determining Subtype of Component

The following new COM command is in the ComponentInterface:

 ret = cmp.GetSubType

o ret Successful return values are:

 0 Undefined.
 1 Accessory: A part which represents any non-electrical supplementary
portion of a connector (e.g. cover).
 2 Fixture: A part which fixes the position (e.g. clamp, grommet).
 3 Protection Tube: A tubing part in order to protect the wire from damages
(e.g. corrugated pipe).
 4 Protection Tape: A taping part in order to protect the wire from damages
(e.g. foam rubber strip).
 5 Protector: A part of protective material except for Tube and Tape (e.g.
sheet).
 6 Splice: A part which connects multiple conductors.

o ret Error values are:

 -1 No project is open.
 -2 No component ID set!
 -3 Component is not a standard type (e.g. is a connector).
 -4 The id does not refer to a component (e.g. refers to a cable).
 -5 An internal error has occurred.

Reference(s): Designer-31302

Enhancement to SymbolInterface for Determining Subtype of Symbol

The following new COM command is in the SymbolInterface:

 ret = sym.GetSubType

o ret Successful return values are:

 0 Undefined
 1 Accessory: A part which represents any non-electrical supplementary
portion of a connector (e.g. cover).
 2 Fixture: A part which fixes the position (e.g. clamp, grommet).
 3 MultiHolding
 4 Connector
 5 Detail
 6 Figure

o ret Error values are:

 -1 No project opened!
 -2 No symbol ID set!
 -3 Symbol is not a standard type.

50
  -4 An internal error has occurred.

Reference(s): Designer-31303

Enhancement to PinInterface for Returning Cavity Part on Wire Ends of Wire

The following new COM command is in the PinInterface:

 ret = pin.GetEndCavityPartIds ( which, cavities [, type] )

o which The following values are possible:

 0 Both ends
 1 End 1
 2 End 2

o cavities Returns the IDs of connector pin terminals and wire seals.

o type The following values are possible:

 0 Connector pin terminals and wire seals (default)

 &h01 Only connector pin terminals
 &h02 Only wire seals

o ret The return value is the number of the IDs in cavities. If an error occurs, the
following values are possible:

 -1 No project or valid pin set!

 -2 No conductor or wire information set on pin!

Note: 'Empty' IDs are also returned, i.e. cav.GetValue was returned as an empty string. In
doing do, a cavity can be set with cav.SetValue.
This is also valid for the existing COM command pin.GetCavitiyPartIds.

Reference(s): Designer-31401

Change to Behavior in PinInterface for SetOuterDiameter

When setting the outer diameter of a conductor/wire, only the outer diameter defined in the
database can be used.

The following COM command has been adapted in the PinInterface:

 ret = pin.SetOuterDiameter ( newval )

o newval Defines the outer diameter of a conductor/wire for dynamic cables. Only
those diameters, which are also defined in the database, can be used.

Reference(s): Designer-31644

51
Connections

 Specific Functionality of Inheriting Net Number Can Now Be Deactivated

 Display All Placed Conductors/Wires on Connection Line Ending on Connection
Node with the Property 'Passes wires' using Arrow Symbol
 Control whether the Name Equivalence Shall Also Be Considered in addition to
the Signal Equivalence when Routing Conductors

Specific Functionality of Inheriting Net Number Can Now Be Deactivated

Previously, the functionality of inheriting the net number with the attribute 'net number' was
always active in E3.series.

This functionality for inheriting the net number can now be deactivated.

To do so, there is the new check box 'Specific functionality of inheriting net number' in
the section Net in the Settings under Connection:

The dialog appears as follows in the 'Electric Settings':

The dialog appears as follows in the 'Fluid Settings':

52
Connection

Specific If checked, the specific functionality of inheriting the net number with the
functionality attribute 'net number' is activated.
of inheriting
net number If unchecked, the specific functionality of inheriting the net number with
the attribute 'net number' is switched off.

Note:

 For new projects the check box is switched off by default.

 The following is valid when opening older projects (before E3 versions
17.30, 18.01, 19.00) with the existing attribute 'net number':
o If the attribute has no value, it is deleted.
o If the attribute has a value, a message box appears:
If the functionality of inheriting the net number is not used, it is
recommended to switch off the check box Specific
functionality of inheriting net number.
Note:
o When deactivating, the attribute .NET_NUMBER in

53
 _NET_NUMBER is renamed. If the attribute name
'_NET_NUMBER' already exists, then it is numerically
incremented; in this case _NET_NUMBER1. The
displayed attribute name remains.
o If the check box Specific functionality of inheriting
net number is activated again, the attribute is created
without the displayed name.
o When importing a subcircuit with the existing attribute
.NET_NUMBER (check box Specific functionality of
inheriting net number is switched off), the attribute is
renamed (like when switching off).

For the COM methods prj.GetSettingValue and prj.SetSettingValue the

following setting_name can be used: INHERIT_NET_NUMBER.

This check box is project-specific in a multi-user project.

Reference(s): Designer-27125

Display All Placed Conductors/Wires on Connection Line Ending on Connection Node

with the Property 'Passes wires' using Arrow Symbol

It's now possible to display whether a wire ends on a connection node with the set property
'Passes wires' using an arrow symbol. The arrow symbol must first be created in the
database and can then be selected later in the Settings in project mode.

If all the placed conductors/wires on a connection line end on a connection node with the set
property 'Passes wires', the arrow symbol is displayed on the connection line.

Note: The property 'Passes wires' can be defined for the corresponding nodes in the
Database Editor using the Node Properties.

Preparations

Creating a New Arrow Symbol in the Database Editor

First, a new arrow symbol must be created in the Database Editor. To do so, there is the new
symbol type 'Arrow symbol'.

To create a new arrow symbol of the type 'Arrow symbol':

Note: For creating it is recommended to use a fine grid (definable in the DBE settings under
Database Editor -> Symbol -> Working Grid / Grid View)

 right-click on the header of the symbol or component tree and select the context menu
command New Symbol
 the Database Editor opens with a new symbol template

54
  left-click on the symbol Polygon in the Graphic toolbar
 now draw the desired arrow
Note:
 Using the Graphic Properties a line or fill color can be defined for the arrow. If the color
'Automatic' is selected, the color presently defined in project mode is used for the
connection line.
 The arrow must point to the left (from the direction of the positive x-axis to the origin),
whereby the origin lies at the tip of the arrow:

 right-click on the symbol and select the context menu command Symbol properties...
 select the new symbol type 'Arrow symbol' in the drop-down list Type: in the Symbol
Properties - Symbol dialog:

 save the symbol in the Database Editor.

Note: No nodes and texts can be defined for an arrow symbol.

To assign the property 'Passes wires' to a connection node symbol:

 open the desired splice symbol in the Database Editor

 right-click on the symbol and select the context menu command l Node properties...

55
  activate the check box Passe wires in the Node Properties - Node dialog

Usage in Project

So that the arrow symbol in project mode for wires/conductors can be displayed on a pin with
the property 'Passes wires', this functionality must be activated.

To do so, there is the new check box 'Mark connected wires/conductors at pass wire
node:' in the section Symbol Options in the Settings under General - Display:

Note: This functionality is not available in the Fluid Settings!

56
General - Display

Mark If activated, an arrow symbol can be selected in the drop-down list.

connected
wires/conduct
ors at pass This arrow symbol displays the direction of the connection node on the
wire node: connection line in the project if...

 the connection nodes have the property 'Passes wires'

 all wires/conductors, which lie on the connection line, end on this
connection node

Note:

 If no symbol is defined (<standard>), a default arrow is displayed.

57
  This functionality is not available on formboard sheets.

For the COM methods prj.GetSettingValue and prj.SetSettingValue the

following setting_names can be used:

Check box: PASS_WIRE_MARK

Symbol drop-down list: PASS_WIRE_MARK_SYMBOL

The check box is user-specific in a multi-user project.

The symbol drop-down list is project-specific in a multi-user project.

Example:

Note: If the color is 'automatically' selected, the presently defined color for the connection line
is used:

Reference(s): Designer-30804

58
Control whether the Name Equivalence Shall Also Be Considered in addition to the
Signal Equivalence when Routing Conductors

Previously, the following case might occur when routing a conductor/wire:

A conductor/wire placed on pin A could also be routed to pin B on a schematic sheet, provided
that pins A and B were signal-equivalent.

Now it's possible to control whether the name equivalence shall also be considered for
differentiating between them. In doing so, all potential parts of the name shall be considered:

 pin name
 internal device designation
 port name / terminal strip name

To do so, there is the new check box 'Use name equivalence additionally in the section
Conductor Assignment Procedure in the Settings under Connection - Conductors /
Wires':

59
Connection - Conductors / Wires

Use name Note: This check box can only be activated if the check box Use signal
equivalence equivalence (to select connect pin) is active.
additionally
If activated, the name equivalence is also considered for selecting the
connect pin. In doing so, all potential parts of the name are considered:

 pin name &

 internal device designation &
 port name / terminal strip name

If deactivated, the pins are equivalent if they are signal-equivalent.

For the COM methods prj.GetSettingValue and prj.SetSettingValue the

following setting_name can be used: ROUTING_NAME_EQUIVALENCE

This check box is project-specific in a multi-user project.

Reference(s): Designer-19421

60
Display

 Existing Sheet Area Now Adapted to New Sheet Format when Enlarging Sheet
Format of Formboard or Topology Sheets
 Control whether Grid Points Shall Also Be Enlarged when Zooming
 Component Preview Symbol Can Now Be Displayed in Preview Window when
Selecting Symbol in Schematic

Existing Sheet Area Now Adapted to New Sheet Format when Enlarging Sheet Format
of Formboard or Topology Sheets

When reducing the sheet format of formboard or topology sheets, the existing sheet area is
automatically adapted to the new sheet format.

Note: If the sheet area is subsequently changed in a project, these changes remain.

Previously, this wasn't the case when enlarging the sheet format and will be supported from
now on.

When changing the sheet area to a new sheet format, the old and new coordinates of the
sheet area are displayed. If the sheet area is not changed, a corresponding message appears.

Reference(s): Designer-26184

Control whether Grid Points Shall Also Be Enlarged when Zooming

Previously, grid points remained constant when zooming. From now on it's possible to control
whether grid points shall also be enlarged when zooming.

To do so, there is the new check box 'Enlarge grid points when zooming' in the section
Miscellaneous Options in the Settings under General -> Display:

61
The dialog appears as follows in the 'Electric Settings':

62
The dialog appears as follows in the 'Fluid Settings':

General -> Display

Miscellaneous Options

Enlarge grid If this check box is activated, the grid points can be enlarged by a
points when predefined increment depending on the zoomed area. The enlargement
zooming takes place automatically as soon as the grid points have achieved the
predefined value.

For the COM methods prj.GetSettingValue and prj.SetSettingValue the

following setting_name can be used: ENLARGE_GRID_POINTS.

This check box is user-specific in a multi-user project.

63
.

Furthermore, the check box Enlarge grid points when zooming is also available in the
database settings under Database Editor - Display:

Reference(s): Designer-03885

Component Preview Symbol Can Now Be Displayed in Preview Window when

Selecting Symbol in Schematic

It's now possible to control whether the preview symbol for the currently selected component
shall be displayed in the Preview Window in E3.series. This preview symbol then appears in
the Preview Window if a placed symbol is selected in the schematic.

To do so, there is a new check box 'Display preview symbol for selected component' in
the section Miscellaneous Options in the Settings under General - Display:

64
The dialog appears as follows in the 'Electric Settings':

65
The dialog appears as follows in the 'Fluid Settings':

General -> Display

Miscellaneous Options

Display If the check box is activated, the preview symbol appears in the Preview
preview Window if a placed component symbol is selected in the schematic.
symbol for
selected Note:
component
 If the preview symbol is not unique using multi-select, the sheet view
is displayed in the Preview Window.
 If there is no preview symbol, the first symbol of the component is
displayed.

66
 For the COM methods prj.GetSettingValue and prj.SetSettingValue the
following setting_name can be used:
DISPLAY_PREVIEW_SYMBOL_FOR_SELECTED_COMPONENT.

This check box is user-specific in a multi-user project.

If a component is selected from the Component drop-down list in Device Properties -

Device, the component preview symbol always appears now in the Preview Window:

Reference(s): Designer-31448, Designer-31449

67
Electrical Checks

 Internal Resistance Can Now Be Defined for Individual Connector Pin Terminals
and Pins in the Electrical Checks

Internal Resistance Can Now Be Defined for Individual Connector Pin Terminals and
Pins

Previously in the electrical checks (E3.eCheck), a global default value could be defined for the
internal resistance of connect elements (e.g. connectors and connections) in the settings
(under Settings -> Electrical Checks -> Internal resistance of connect elements
[Ohm]:).

From now on it's possible to define different internal resistance values for individual contact
elements in the project. These different resistance values are considered later for the
calculations.

To define the internal resistance directly on a pin:

 mark the desired device in the workspace and select the command Format -> Device
Properties..., or
 right-click on the symbol, which has been assigned to a component and select the
context menu command Device Properties..., or
 right-click on a single pin or the pin text of a symbol and select the context menu
command Pin Properties..., or
 right-click on the desired device in the project window device tree and select the context
menu command Device Properties...,
 afterward select the Pin tab,
 right-click on the first available cell in the attribute selection list and select the attribute
'Internal resistance on pin [Ohm]'

68
  enter the desired resistance for the internal resistance on the pin in the column Entry:

In doing do, the following rules are valid:

1. If a connector with more than one pin is placed as a complete connector and no wires
are connected to the pins, the default value is used for the calculation.
2. If no internal resistance values are defined on both plugged pins, the default value is
used for the calculation.
3. The internal resistance can only be defined on pins / connector pin terminals, i.e. the
default value is used for the calculation with symbol-oriented work.

69
 4. If wires are connected to a complete connector, a unique current path assignment is
ensured. In this case, the resistances on the pins are used for the calculation.
Note: Only the values of the first pin are used for display! If one wants to see the
voltages and currents of all pins, this must be done using the Pin Properties.
5. If a connector pin terminal is assigned to the connector pin, then the internal resistance
of the connector pin terminal is used.
(The internal resistance for the connector pin terminal can be defined on the component
pin in the Database Editor.)
If no internal resistance is defined on the connector pin terminal, the value from the
connector pin is used.
Note: The rules 2-4 are valid here!

Reference(s): Designer-29384

70
Export

 Enhancement to DXF/DWG Export

 Structure Node Assignments and their Attributes Can Now Be Exported and
Imported

Enhancement to DXF/DWG Export

The assignment of E3.series levels to DXF/DWG levels for DXF/DWG Export has been
enhanced with the addition of the following keys [Explode symbols], [Separate connection
lines by opaque attribute texts], [Join linked connection lines], [Translate
linetype names] and [Export userdefined linetypes].

This can be defined in the DXFExport.CFG assignment file of the installation directory. The
following new settings can now be configured:

Key Format Description

[Explode Using this key exports the symbols

symbols] as dissolved graphics and not as
blocks.
[Separate Using this key separates the
connection connected connection lines by
lines by opaque opaque attribute texts (only the line
attribute of the attribute template).
texts]
[Join linked Using this key merges the linked
connection connection lines into a polyline.
lines] Note:This doesn't make sense
though if the linked connection lines
have different display properties
because only one line can win.
[Translate This key enables E3.series-
linetype names] Example: generated (also customary in
AutoCAD) line type names to be
DASHDOT=STRICHPUNKT "translated".
DASHED=GESTRICHELT

[Export Using this key exports the user-

userdefined defined line types to DXF/DWG.
linetypes]
[Export circle
as polyline] Note:

Circles can only be exported in DXF

as CIRCLES with line width if the…

 DXF version is 2000 or newer

 circle’s line width is smaller
than 2.1 mm

Otherwise, this key must be created.

71
 Circles are always written as
polylines using this key.

Reference(s): Designer-29965, Designer-30457, Designer-30639

Structure Node Assignments and their Attributes Can Now Be Exported and Imported

Previously when importing structure nodes, the structure node assignment as well as their
attributes were not adopted. Furthermore, when exporting structure nodes, the structure node
assignment as well as their attributes were not exported.

With the new functionality already existing structure node assignments as well as their
attributes are adopted when importing structure nodes. Likewise when exporting subcircuits,
it's now possible to export the structure node assignment as well as their attributes.

To do so, there is the new check box 'Export structure nodes' in the section General in the
Settings under Placement - Export / Copy:

The dialog appears as follows in the 'Electric Settings':

72
The dialog appears as follows in the 'Fluid Settings':

73
Placement - Export / Copy

General

Export If this check box is activated, the structure nodes and their attributes are
structure exported.
nodes
Note:

 The structure template file must have the same contents as the file to
be imported.
 If the same structure attributes are available in the subcircuit to be
imported like in the opened project, the following is valid:
o If no entries are defined in the project for the structure node
attribute, the values from the imported subcircuit are inherited
on all sub-elements.
o If entries are defined in the project for the structure node
attribute, these remain.

74
 For the COM methods prj.GetSettingValue and prj.SetSettingValue the
following setting_name can be used: EXPORT_STRUCTURE_NODES

This check box is user-specific in a multi-user project.

The check box Export structure nodes can still be changed for each application in the File -
> Export -> Drawing... dialog.

Reference(s): Designer-10808

75
Fields / Dynamic Symbols

 Now Possible to Edit Corners of Fields (Add / Delete / Move)

Now Possible to Edit Corners of Fields (Add / Delete / Move)

Previously, a field could only be generated as a rectangle. The size of the field could be
changed (made larger or smaller) later by dragging a corner back and forth. However, no
existing corners could be deleted or new corners added.

It's now possible to delete existing corners or move individual corners of a field. Furthermore,
new corners can be added to a field.

To do so, there is the context menu command Edit points, which is already available for
drawing a curve.

To edit the shape of a field:

 right-click on the desired field and select the displayed context menu command Edit
points; it's now possible to edit points in the field.
 The field's border can now be edited with the following context menu commands:
Note: These commands only appear if one clicks on a specific location of the field's
border.

o The context menu command Delete points can be called up by right-clicking on

the corner to be deleted.
The selected corner is deleted.
Note: There must be at least 4 corners for the command to be offered.
o The context menu command Add points can be called up by right-clicking on a
segment of the field's border.
An additional corner is added to the corresponding location on the field.
o The context menu command Close shape can be called up by right-clicking
anywhere on the field's border.
The open field border is closed.
o The context menu command Delete segment can be called up by right-clicking on
the segment of the field border to be deleted.
The selected segment is deleted.
Note: The field's contour must be closed.

 To stop editing points, right-click anywhere on the field border and select the context
menu command Stop editing points.

Note:

For displaying devices the IEC 81346 shortening rules are currently valid. (The check box IEC
81346 is active can be called up in the Settings under Placement -> IEC 81346
standard).

If this option is not set, the Device Properties

 Higher level assignment

 Device designation
 Location

are shortened.

76
Example:

Reference(s): Designer-08994

77
Graphics

 Possible to Control whether Arrowhead of Ballooning Text Points to Graphic of

Corresponding Symbol
 Arrows Can Now Be Placed on the Line Ends of Arcs
 User-Defined Line Types Can Now Also Be Used for Ovals and Curves (with
FONTS.DAT)
 'Japanese Industrial Standards' Line Style Can Now Be Selected

Possible to Control whether Arrowhead of ballooning Text Points to Graphic of

Corresponding Symbol

In E3.series it's now possible to define whether the arrowhead of a ballooning text points to
the graphic of a corresponding symbol.

To do so, there is the new check box 'Subsidiary line to graphic' in the Settings under
Graphic - Text:

The dialog appears as follows in the 'Electric Settings':

The dialog appears as follows in the 'Fluid Settings':

78
Graphic - Text

Effects

Subsidiary line Prerequisite: The check box Display subsidiary line to owner on the
to graphic ballooning text (called up using Text Properties - Text) must be
activated.

If checked, the arrowhead of a ballooning text points to the graphic of the

corresponding symbol:

79
If unchecked, the arrowhead of a ballooning text points to the next corner
or midpoint of the rectangle enclosing the corresponding symbol:

80
 Note:

For the COM methods prj.GetSettingValue and prj.SetSettingValuethe

following setting_name can be used:
SUBSIDIARY_LINE_TO_GRAPHIC

This check box is project-specific in a multi-user project.

Reference(s): Designer-30255

Arrows Can Now Be Placed on the Line Ends of Arcs

Previously, it wasn't possible to place arrows on the line ends of arcs. This can now be
controlled using the Graphic Properties.

 To do so, right click on the arc...

 select the Graphic Properties... command in the displayed context menu and then the
Graphic tab in the Graphic Properties
 select the desired arrow type for the arc in the Arrows: drop-down list:

Reference(s): Designer-29881

User-Defined Line Types Can Now Also Be Used for Ovals and Curves (with
FONTS.DAT)

From now on user-defined line types can be displayed for all graphic elements using the file
FONTS.DAT.

The following line types (line fonts) are possible:

 Line
 Polygon
 Rectangle
 Oval (new)
 Circle

81
  Arc
 Curve (new)

Example (selection):

Reference(s): Designer-12172

'Japanese Industrial Standards' Line Style Can Now Be Selected

In E3.series the line style Japanese Industrial Standards can now be selected.

To do so, there are the new radio buttons 'Default' and 'Japanese Industrial Standards' in
the section Line Style under Graphic in the settings.

The dialog appears as follows in the 'Electric Settings':

82
The dialog appears as follows in the 'Fluid Settings':

83
Graphic

Line Styles:

Default/ Depending on the selected radio button the corresponding line style is
used:
Japanese
Industrial Default line style: Japanese Industrial Standards
Standards line style:

84
 Note: The export formats DXF/DWG,
DGN ,CGS are not fully supported!

Note:

For the COM methods prj.GetSettingValue and prj.SetSettingValue the

following setting_name can be used: LINESTYLE_JIS

 The return value is 0 for the Default line style.

 The return value is 1 for the Japan Industrial Standard line style.

This check box is project-specific in a multiuser project.

Furthermore, there are the new radio buttons 'Default' and 'Japanese Industrial
Standards' in the Database settings under Graphic. Depending on the setting the
corresponding line style is displayed and can be changed later in the project.

85
Reference(s): Designer-30638

86
Placement / Purge

 Clipboard Structures/Structure Nodes with Contents Can Now Be Deleted in the

Tree View
 'Place on Segment' Functionality Now Possible for Curved Connections

Clipboard Structures and Structure Nodes with Contents Can Now Be Deleted in the
Tree View

Previously, it wasn't possible to delete clipboard structures/structure nodes with contents in

the tree view in E3.series.

It's now possible to delete clipboards/structure nodes with contents in the corresponding tree
view or clipboard structure tree.

Note:

 It's not possible to delete clipboards or structure nodes for read-only sheets and locked
elements.
 Grouped elements are only deleted if all elements of the group are contained in the
same clipboard / structure node.

Enhancement to StructureNodeInterface for Deleting Structure Nodes with Contents

The following new COM command is in the StructureNodeInterface:

 ret = struct.DeleteForced
 ret The return value is the ID of the deleted structure node if successful. In case of
error, the following return values are possible:

o 0 Miscellaneous error
o -1 An item was set in the interface, which isn't a structure node.
o -2 A structure node was set but may not be deleted (signal structure node).
o -3 The set structure node is locked.

The existing COM command struct.Delete now has the same return value as
struct.DeleteForced.

Reference(s): Designer-22703

'Place on Segment' Functionality Now Possible for Curved Connections

Previously, the 'Place on Segment' functionality could not be executed on curved connection
lines. It's now possible to execute the command 'Place on Segment' on curved connections.
This takes place using the new symbol graphic 'According connect line'.

In the course of this enhancement the database dialog Symbol Properties - Symbol has
been overhauled.

87
Previously, there was the option field Modify symbol graphic:

 no
 replicate
 yes

Now instead there is the drop-down list Symbol graphic:.

Mapping:

Previous option fields New drop-down list Symbol graphic:

Modify symbol graphic
no Fix
Replicate
 replicate
 yes Dynamic
According connect line (new)

88
Symbol Properties - Symbol

Disp
Symbol graphic: lay
icon
Symbols can be expanded and changed, therefore it is possible to stretch for in
example attribute indicators as well as mounting rails. The graphic can be tree
view

89
replicated to display, for example, corrugated hoses and tubes.

These options are not active with the following symbols:

o Block
o Block fix
o Connector Table
o Grouped symbol for bundles
o Module
o Panel sheet
o Sheet
o Shield symbol
o Terminal plan sheet
o Twisted pair symbol

Check this option if you do not want to modify the symbol graphic. When
Fix selecting the graphic in project mode no handles will be displayed.
Replicate Check this option to replicate the symbol graphic in project mode by
dragging. The complete symbol graphic is bound as free graphic to the
symbol. Pins and texts are not changed. Furthermore, scaling down the
graphic is not possible, at least one element must be displayed. It's either
possible to replicate vertically or horizontally. The symbol space
requirement defines the preferred direction. It's not possible to replicate
beyond the symbol's origin.
Dynamic Check this option to define the symbol graphic as changeable or
expandable. In project mode it is possible to resize, scale down etc. the
symbol graphic.
According
connect Note: The entry "According connect line" only appears if "Attribute text
line template" is set as the symbol type.

Activate this option to place a symbol graphic on a curved connection (e.g.

as segment/protection). This takes place on an E3.formboard sheet using
the command "Place on Segment".

Note:

o The symbol must consist of exactly one graphic line, which is

assigned a user-defined line style.
If the symbol doesn't have exactly one line with an assigned user-
defined line style, it is rejected with a corresponding message when
trying to save it.
o The graphic line, which displays the symbol, must be adjusted
horizontally in the database. The space requirement rectangle of the
line (in the Y-direction) should be enclosed as cleanly as possible
because this is used for the identification.

Example:

90
Devices (in the following application a 'segment/protection') with the symbol type "Attribute
text template" and the property "According connect line" can now be placed on a curved
connection on an E3.formboard sheet.

 right-click on the corresponding device in the Component Tree

 select the context menu command Place on Segment:

 left-click on the desired curved connection:

Reference(s): Designer-16268

91
Symbols

 Defining the Symbol Order for the Component Definition Has Been Simplified
 Table Symbols Now Possible for Normal Devices in Formboard
 Symbol Properties Can Now Be Called Up in Formboard Tables

Defining the Symbol Order for the Component Definition Has Been Simplified

Previously, the symbol order could only be increased beginning with the starting value for the
component definition in the database editor.

The following modes are now available for defining the symbol order:

 Reorder mode
 Insert mode
 Swap mode

Note: These modes are already available for defining the pin order and the text order.

To define the symbol order:

 select the command Tools -> Start Database Editor in the main menu
 open a 'normal component' with several symbols in the database editor
 click on the command Edit -> Order Definition -> Symbols in Component in the
main menu, or
 click on the Symbol Order icon in the Database Component toolbar
 the Symbol Order Definition dialog opens

Symbol Order Definition

Select mode

Reorder mode The symbols are reordered. With Next click is number: it's possible to
specify a starting value that is automatically increased by one with each
click on a symbol. Press <Esc> to abort the command.

Swap mode The symbol with the number specified in Next click is number: is
exchanged with the symbol on which you click.

92
Insert mode The symbol with the number specified in Next click is number: is placed
at the position on which you click. Subsequent symbols are moved back
(renumbered).
Next click is The number can be defined here that is used for the selected mode.
number:

Reference(s): Designer-12294

Table Symbols Now Possible for Normal Devices in Formboard

Previously in formboard, a table symbol could only be created for formboard tables.

Now it's possible to create table symbols for normal devices.

Note: A table symbol can be defined in the section Table under Formboard in the Settings.

Example:

 right-click on the placed device on the formboard sheet

93
  select the context menu command Place Table Symbol

 place the table symbol at the desired location on the formboard sheet:

Enhancement to SymbolInterface with PlaceTable() for All Devices

Enhancement to COM command in SymbolInterface:

94
  ret = sym.PlaceTable ( fromId, x, y, [rot, [scale, [maintaintextsize]]])

o fromId Connector or device from which the table is placed. fromId is the ID of the
device/connector on the formboard and not the original device/connector ID. To
obtain the IDs of the formboard device/connector, use dev.GetFormboardIds()
Note: The call fails if a table is already placed.
o x, y Position of connector or device
o rot, scale Rotation and scale of connector or device
o maintaintextsize If maintaintextsize does not equal 0, the text size is
maintained when scaling, otherwise the texts are also scaled.
o ret The return value is the ID of the placed symbol, otherwise 0. If the x and/or y
coordinates lie outside of the sheet's visible area, the return value is also 0.

Reference(s): Designer-15643

Symbol Properties Can Now Be Called Up in Formboard Tables

In E3.formboard it's now possible to call up the Symbol Properties in tables.

To do so, there is the new tab Table in the Symbol Properties.

Note: The contents of the Table tab are already an element in the Settings (called up in the
section Table under Settings -> Formboard)

To display or change the properties of a table:

 right-click on the placed table symbol

 select the context menu command Symbol Properties... and activate the tab Table

95
Symbol Properties - Table

Table Symbol Defines which table symbol is placed in the project as the formboard view.
The drop-down list contains all table symbols available in the database.

96
Display one row Activate this option to display one row for each conductor. Pins without
for each placed conductors/wires are hidden if the option is active. For example, a
conductor connector with 50 pins with only two wires, the remaining (empty) rows
are not displayed.

If the option is inactive, one row is displayed for each pin. Furthermore,
conductor text types and connection targets are displayed separated by
commas.

Display pins This option independent of the check box Display one row for each
without conductor controls whether pins without placed conductors/wires are
conductors displayed in the table.

If this option is active, at least one row is displayed for each pin in
formboard tables.

If this option is inactive, only pins with placed conductors/wires are

displayed in formboard tables.

Note: This option is active by default.

Break table With multiple pins it is clearer to display the information side-by-side.
after... rows That's why using this option it's possible to specify the number of rows
before there is a table break.

Missing rows are automatically grayed out. The headers and footers are
duplicated:

Enhancement to SymbolInterface for Changing the Properties of Formboard Tables

The following new COM commands are in the SymbolInterface:

 ret = sym.GetTableOneRowForEachCore

o ret The following return values are possible:

 1 The property "Display one row for each core" is set.

97
  0 The property "Display one row for each core" is not set.
 -1 Error: No symbol set or symbol ID is not a table symbol!

 ret = sym.SetTableOneRowForEachCore ( newval )

o newval 0 or 1 for setting the property "Display one row for each core"
o ret The return value is 0 if successful, otherwise -1.

 ret = sym.GetTablePinsWithoutCores

o ret The following return values are possible:

 1 The property "Display pins without cores" is set.

 0 The property "Display pins without cores" is not set.
 -1 Error: No symbol set or symbol ID is not a table symbol!

 ret = sym.SetTablePinsWithoutCores ( newval )

o newval 0 or 1 for setting the property "Display pins without cores"

o ret The return value is 0 if successful, otherwise -1.

 ret = sym.GetTableBreakTableAfter

o ret The following return values are possible:

 1 The property "Break table after" is set.

 0 The property "Break table after" is not set.
 -1 Error: No symbol set or symbol ID is not a table symbol!
 -2 The value for the number of rows for the table break is not set.

 ret = sym.SetTableBreakTableAfter ( newval )

o newval 0 or 1 for setting the property "Break table after"

o ret The return value is 0 if successful, otherwise -1.

 ret = sym.GetTableBreakTableAfterNumberOfRows

o ret Returns the number of rows for the table break.

 ret = sym.SetTableBreakTableAfterNumberOfRows ( newval )

o newval Sets the number of rows for the table break; the value must be between 2
and 1000.
o ret The following return values are possible:

 1 The command was successful!

 0 The command was not successful!
 -1 Error: No symbol set or symbol ID is not a table symbol!
 -2 The value for the number of rows lies outside the permitted range of 2 to
1000.

Reference(s): Designer-31327

98
Terminals

 Location and Assignment Can Now Be Selected for the Internal and External
Sides in the Terminal Plan and Terminal Table

Location and Assignment Can Now Be Selected for the Internal and External Sides in
the Terminal Plan and Terminal Table

For terminal plans and terminal tables the internal and external connections were previously
determined using the existing Assignment/Location combination (Example:=a +intern).
Terminal information was listed in the internal table column with the same
Assignment/Location.

The following selection possibilities are now available for internal/external terminal connections
in addition to Assignment/Location:

 only Assignment (Example:=a)

 only Location (Example:+intern)

To do so, there are radio buttons in the new section Internal / External Definition in the
Settings under Placement -> Terminal plan :

 Assignment/Location
 Assignment
 Location

99
Placement -> Terminal Plan

Internal / External Definition

Assignment/L The status of the radio buttons determines the external / internal terminal
ocation connections. The following display possibilities are available:

 Assignment/Location
Assignment  Assignment
Location  Location

For the COM methods prj.GetSettingValue and prj.SetSettingValue the

following setting_name can be used:
TERMPLAN_INTERN_EXTERN_DEFINITION.

Valid values:

100
 0 = Assignment/Location

1 = Assignment

2 = Location

Invalid values are interpreted as 0.

This check box is project-specific in a multi-user project.

Example:

 Assignment/Location

 Assignment

101
 Location

Furthermore, there is the new section Internal / External Definition in the Settings under
Placement -> Terminal Table:

102
Placement -> Terminal Table

Internal / External Definition

Assignment/Lo The status of the radio buttons determines the external / internal terminal
cation connections. The following display possibilities are available:

 Assignment/Location
Assignment  Assignment
Location  Location

Note:

The new radio buttons are also in the Insert Terminal Plan dialog. The
currently selected radio button is in the default settings under Settings ->
Placement -> Terminal Table.

Depending on the application this setting can be changed in the Insert

Terminal Plan dialog.

For the COM methods prj.GetSettingValue and prj.SetSettingValue the

following setting_name can be used:
TERMTABLE_INTERN_EXTERN_DEFINITION.

Valid values:

0 = Assignment/Location

1 = Assignment

2 = Location

Invalid values are interpreted as 0.

103
 This check box is user-specific in a multi-user project.

Example:

Note:

o Columns with external terminal information are identified by red-colored column

headers.
o Columns with internal terminal information are identified by blue-colored column
headers.
o It is recommended to switch off the autocompress feature (deactivate the check box
Autocompress in the section Options in the Settings under Placement -> Terminal
plan).

 

104
 Assignment/Location

 Assignment

 Location

Enhancement to DeviceInterface and JobInterface for Setting the Sorting of the

Internal/External Designations according to Location and HLA in the Terminal Plan

The following COM commands in the DeviceInterface have been enhanced:

 ret = dev.InsertTerminalPlan ( parameters )

 ret = dev.GetTerminalPlanSettings ( parameters )
 ret = dev.SetTerminalPlanSettings ( parameters )

o parameters The scripting dictionary receives an additional parameter:

 InternalExternalDefinition with the following values:

105
  UseAssignmentLocation
 UseAssignment
 UseLocation

The following COM commands in the JobInterface have been enhanced:

 ret = job.GetTerminalPlanSettings ( parameters )

 ret = job.SetTerminalPlanSettings ( parameters )

o parameters The scripting dictionary receives an additional parameter:

 InternalExternalDefinition with the following values:

 UseAssignmentLocation
 UseAssignment
 UseLocation

Reference(s): Designer-03578

106
Texts

 Text Properties Can Now Be Opened by Double-Clicking on Text

Text Properties Can Now Be Opened by Double-Clicking on Text

The Text Properties can now be opened directly by double-clicking on a text with the left
mouse button.

Previously, the Text Properties could only be opened using the context menu command Text
Properties..., which is still available.

Reference(s): Designer-30697

107
Topology - Overview
In E3.topology it's customary to place numerous devices on one large sheet. To work on this
sheet, one frequently has to use a very high zoom factor. To assist in this process, it's now
also possible to generate shared sheets inE3.topology, like previously in E3.panel or
E3.formboard.

The following chapters describe the new functionality as well as miscellaneous enhancements
to E3.topology:

 New Shared Sheets in Topology

o Multiple Display of Overlapping Regions on Separate Sheets

o Example: Topology Base Sheet and Its Shared Sheets
o Generate Shared Sheets using Specific Values
o Generate Shared Sheets Graphically
o Display Shared Sheets
o Overview of All Shared Sheet
o Restrictions
o COM Enhancement to SheetInterface for Creating Shared Sheets on
Topology Sheets

 Topology - Miscellaneous

o An Installation Space Can Now Be Placed Automatically for a Device when

Placing a Device on a Topology Sheet
o Harness Name Can Now Be Adopted by the Routed Conductors/Wires in
the Harness
o Now Possible to Place/Move Installation Spaces on Open Line Ends
o Several Devices Can Now Be Placed Simultaneously in an Installation
Space

108
New Shared Sheets in Topology

 Multiple Display of Overlapping Regions on Separate Sheets

 Example: Topology Base Sheet and Its Shared Sheets
 Generate Shared Sheets using Specific Values
 Generate Shared Sheets Graphically
 Display Shared Sheets
 Overview of All Shared Sheet
 Restrictions
 COM Enhancement to SheetInterface for Creating Shared Sheets on Topology
Sheets

Multiple Display of Overlapping Regions on Separate Sheets

In E3.topology it's now possible to generate topology sheets, which display the exact same
contents of another topology sheet:

o The scaling and X/Y offset can be different.

o The contents of all shared sheets are exactly the same.

Example: Topology Base Sheet and Its Shared Sheets

Additional sheets displaying the exact contents of the base sheet can be derived from one
topology sheet (base sheet). By specifying a scale and X/Y offset any number of shared sheets
can be created.

In the following example two shared sheets have been created from a base sheet.

Note: Activating the rulers using View -> Rulers can be helpful when defining a topology
share.

109
Generate Shared Sheets using Specific Values

To generate a shared sheet of a topology sheet using specific values:

 click on Insert -> Sheet in the main menu toolbar,

 the following dialog opens:

 select the Type: Topology from the drop-down list in the section Options
 select the sheet from which the shared sheet shall be generated in the section Share
display with sheet:.

110
(All sheets, which either already have the base sheet property or are normal topology sheets,
are displayed in the drop-down list.)

The shared sheet to be displayed can be defined in the same dialog. To do so, select the
desired sheet format under Format: and determine the area to be displayed by defining the
Scale and Reference X/Y for the specified offset.

This area specification can be changed later using Sheet Properties... -> Region.

Generate Shared Sheets Graphically

When generating shared sheets, the desired share can be graphically defined, selected and
modified later.

To do so, proceed as follows:

o Select the Insert -> Shared Sheet command from the main menu bar or the Insert
shared sheet button to define the new shared sheet.
o The Insert New Sheet dialog appears to specify shared sheets definitions such as the
sheet's format or name

o Confirm the dialog box with OK and draw the new shared sheet. Hold the left mouse
button pressed while drawing the rectangle.
o In doing so, the region's scaling is determined. This scaling is increased by the
increments defined using the Scaling increment of region option under Settings ->
Topology.
Note: Using the Shift button this setting can be suppressed.

111
Modify Shared Sheets on the Base Sheet

A shared sheet area on the base sheet can be enlarged or reduced by selecting one of the
handles on the outer contour of the rectangle (Settings... -> Topology -> Display region
overview must be activated). The same specifications are valid here as when generating a
shared sheet.

With the Move command or using Drag & Drop the position of the shared region can be
moved.

Display Shared Sheets

These sheets are identified by an additional letter on the sheet symbol in the sheet view:

o B Base Sheet
o S Shared Sheet(s)

Overview of All Shared Sheets

To do so, there is a new check box Display region overview as well as the numerical field
Scaling increment of region in the new section Shared Sheets in the Settings under
Topology. In doing so, the other shared sheets are displayed as rectangles on the topology
sheet.

112
Topology

Shared sheets

Display region Activate this check box to display the size of other shared sheets as
overview rectangles on the base sheet. This check box must be activated in order to
modify shared sheet areas on the base sheet.

The following is valid for the display:

o The current region is not displayed.

o The sheet name is displayed in the lower left corner of the sheet.
o If the text extends beyond the sheet region's rectangle, the text is
scaled down so that it fits the rectangle.
o The text height is scaled so that the text doesn't overlap the region.
o The border is 3 mm thick.

113
 For the COM methods prj.GetSettingValue and prj.SetSettingValuethe
following setting_name can be used: DISPLAY_TOPOLOGY _REGION

This check box is user-specific in a multi-user project.

Scaling When creating a shared sheet using Insert -> Shared Sheet, a rectangle
increment of must be dragged and dropped. Dragging the area determines the scaling
region: factor. The scaling is increased stepwise. Use the SHIFT key to suppress
this setting.

For the COM methods prj.GetSettingValue and prj.SetSettingValuethe

following setting_name can be used:
TOPOLOGY_REGION_SCALE_STEP

This check box is user-specific in a multi-user project.

Instead of using the Settings..., shared sheets can also be activated using the Display
shared sheets button:

This button doesn't appear in the standard toolbar by default but can be selected from the
category Functional Design/Topology under Tools > Customize -> Commands for
customizing toolbars.

Restrictions

The following restrictions are valid:

o Only one user can modify a shared sheet in multi-user mode.

o If a shared sheet is exported as a subcircuit, only the sheet border data is generated.
The contents of the shared sheet are only exported if the topology base sheet is also
selected.
o If one or more shared sheets are copied without the base sheet being copied, the
contents of the shared sheets are also copied. Only those objects lying completely within
the region are copied.
o With Paste or Paste Extended a base sheet in addition to the shared sheets is generated.
The size of the base sheet corresponds with the upper and lower limits of the sheet
region. (The scale is correspondingly adapted.)

COM Enhancement to SheetInterface for Creating Shared Sheets on Topology Sheets

The following new COM command is in the SheetInterface:

 ret = sht.CreateTopologyEx ( modi, name, symbol, position, before, refx, refy,

refscale, flags )
o This functionality is only available if an E3.topology license exists!
o Creates a new topology sheet.
o modi '0' or ID of hierarchical block to which the sheet should be inserted
o name Name of sheet

114
 o symbol Border symbol for sheet
o position Is the insert position and can be a sheet.
o before Defines whether to insert in front of or behind position:

 0 Specifies that the new sheet is inserted after the sheet position.
 1 Specifies that the new sheet is inserted before the sheet position.

o refx, refy the lower left corner of the sheet region in a 2-D coordinate system
o refscale Scaling factor
o ret The return value is the identifier of the newly created sheet, otherwise 0.

The existing COM command sht.ShareWithID(id) is now also valid for topology sheets.

Example:

Dim e3 : Set e3 = CreateObject("CT.Application")

Dim prj : Set prj = e3.CreateJobObject()
Dim sht : Set sht = prj.CreateSheetObject()

' If E3.formboard licence is available

sht.CreateFormboardEx 0, "Base", "DINA0", 0, 0, 500, 500, 1
baseSheetId = sht.GetId()

sht.CreateFormboardEx 0, "Shared", "DINA0", 0, 0, 500, 500, 20

sht.ShareWithID baseSheetId

' If E3.topology licence is available

sht.CreateTopologyEx 0, "Base", "DINA0", 0, 0, 500, 500, 1
baseSheetId = sht.GetId()

sht.CreateTopologyEx 0, "Shared", "DINA0", 0, 0, 500, 500, 1

sht.ShareWithID baseSheetId

' If E3.panel licence is available

sht.CreatePanel 0, "Base", "DINA0", 0, 0, 500, 500, 1
baseSheetId = sht.GetId()

sht.CreatePanel 0, "Shared", "DINA0", 0, 0, 500, 500, 1

sht.ShareWithID baseSheetId

Reference(s): Designer-17039

115
Topology - Miscellaneous

 An Installation Space Can Now Be Placed Automatically for a Device when

Placing a Device on a Topology Sheet
 Harness Name Can Now Be Adopted by the Routed Conductors/Wires in the
Harness
 Now Possible to Place/Move Installation Spaces on Open Line Ends
 Several Devices Can Now Be Placed Simultaneously in an Installation Space

An Installation Space Can Now Be Placed Automatically for a Device when Placing a
Device on a Topology Sheet

When placing a device on a topology sheet in E3.topology, an installation space can now be
placed automatically for the device. This takes place using the new context menu command
Place within installation space, which can be executed in the Device or Component Tree.

It is necessary to make sure beforehand that a corresponding installation space symbol is

predefined in the Settings.

To do so, there is the new selection field 'Installation space symbol: in the Settings in the
section Symbols under Topology:

116
Topology

Symbols

Installation An installation space symbol can be defined in this field, which is used
space symbol: when executing the command 'Place within installation space'.

Note:

 This setting is not available in E3.functionaldesign.

 The symbol CABBLOCK is predefined by default.

For the COM methods prj.GetSettingValue and prj.SetSettingValuethe

following setting_name can be used:
DEFAULT_INSTALLATION_SPACE_SYMBOL.

This check box is user-specific in a multi-user project.

If an installation space symbol is predefined in the Settings, the device with installation space
can now be placed on a topology sheet.

To place a component or an unplaced device with installation space:

 right-click on the desired unplaced device/component (multi-select also possible) in the

Device or Component Tree
 select the context menu command Place within installation space:
Command in Component Tree:

117
 Command in Device Tree

 now place the installation space with the device(s) at the desired location on the
topology sheet:

Reference(s): Designer-29382

Harness Name Can Now Be Adopted by the Routed Conductors/Wires in the Harness

In E3.topology the new name designation can be used (assigned to) the routed
conductors/wires in the harness when renaming the harness name. It's possible to distinguish
whether the new name shall be adopted only by the harness or for all routed conductors/wires
in the harness.

Preparations:

1st: Define the harness name attribute

So that the routed wires in a harness can be assigned the name, a cable harness name
attribute must be defined.

118
To do so, there is the new field Harness Name: in the Settings under Connection ->
Conductors / Wires. The active harness name attribute is defined in this field:

Note: In the following example the harness name attribute is 'Side'

Connection - Conductors / Wires

Harness Select the desired attribute for the harness name in this field. All attributes
Name: from the configuration database and the project are displayed, which have
the owner 'Cable conductor'.

For the COM methods prj.GetSettingValue and prj.SetSettingValue the

following setting_name can be used: HARNESS_NAME_ATTRIBUTE.

Note:

 If the value prj.SetSettingValue "HARNESS_NAME_ATTRIBUTE"

119
 is empty when setting, it is set to <no entry>.
 If the value prj.SetSettingValue "HARNESS_NAME_ATTRIBUTE"
is not valid, a corresponding message appears in the Output Window.

This check box is project-specific in a multi-user project.

2. Create the harness name attribute for the conductor/wire in the harness

The next step is to create the harness name attribute for the routed conductors/wires in the
harness using the properties dialog (in the example: 'Side'). Define the desired entry for the
harness name attribute!

Create the harness name attribute as follows:

 right-click on the desired conductor/wire

 select the context menu command Device Properties...
 select the Cables/Conductors tab in the (Device Properties dialog
 select the desired conductor/wire in the tree view
 click on the first free cell in the column Name and select the harness name attribute
 define the desired entry under Entry (in the examples: 'RIGHT' or 'LEFT'):

120
Assigning New Harness Names

To assign a new harness name to a harness (all routed conductors/wires in the

harness):

 right-click on a connected connection line in the installation space on the topology sheet
or
 right-click in the Device Tree on...
o the desired harness
o the desired conductor underneath a harness
o the desired wire underneath a harness
o the desired cable underneath a harness
 select the context menu command Assign Harness Name:
 this opens the Assign Harness Name dialog:

Assign Harness Name

Harness name: Select the desired name for the harness from the drop-down list, which
shall be assigned to the harness.

All attribute values for the harness name attribute, which is defined in the
Settings under Connection -> Conductors / Wires -> Harness Name:,
appear in the drop-down list.

Note:

 If there are several selection possibilities, the entry <multiple

values> appears in the drop-down list.
 All attributes, which have the owner 'Cable conductor', appear in the
drop-down list 'Harness name:'.
 Alternatively, the harness name can also be manually entered.

Assign to If checked, the new harness name is assigned as the entry for the selected
wires harness and all routed conductors/wires in the harness, which presently
have the defined harness attribute.

Example: Assigning a new harness name to a harness and all routed

conductors/wires in the harness

121
 New harness name: RIGHT

Note: All routed conductors/wires in the harness with the presently defined
harness name attribute (in the example: 'Side') receive the new harness
name as the entry.

If unchecked, the name harness name is assigned to the selected harness.

Example: Assigning a new harness name to a harness

New harness name: LEFT

Retain If checked, the last defined settings appear when calling up the dialog
Settings again.

Reference(s): Designer-29808

Now Possible to Place/Move Installation Spaces on Open Line Ends

Previously, installation spaces could not be placed or moved on open line ends of a connection
line in E3.topology. Installation spaces can now be placed or moved on open line ends of a
connection line.

Note: Installation spaces cannot be placed or moved on diagonal connection lines.

Reference(s): Designer-29383

122
Several Devices Can Now Be Placed Simultaneously in an Installation Space

Previously, it wasn't possible to place several device simultaneously in an installation space.

This functionality is now possible.

To do so, there is the new context menu command 'Place into installation space' in the tree
view.

To place several devices in an installation space simultaneously:

 select the desired devices in the device tree using multi-select that shall be placed in an
installation space
 right-click and select the context menu command Place into installation space

 then click on the desired installation space where the devices shall be placed.

Note:

 If an already placed device is included in the selection, this device is ignored.

 Assemblies with a component assignment may not be distributed in different installation
spaces.

Reference(s): Designer-18562

123
Tree Views / Bulk Data Management

 Device Table Configuration Can Now Be Saved (and Reloaded)

 Cable End Attributes Can Now Be Added to Cables in the Device Table
 Jump from Different Objects (Device, Symbol, Sheet) to the Database Tree

Device Table Configuration Can Now Be Saved (and Reloaded)

It's now possible to save the current Device Table configuration as a configuration file (*.bdt).
If this configuration file is loaded once again, the last configured arrangement (for example
columns to be added) of the Device Table appears.

To save / load the configuration, there are the following new context menu commands in the
Device Table:

 Save Configuration...
 Load Configuration...

To save the Device Table configuration:

 right-click on the first cell in the first column of the Device Table
 select the context menu command Save Configuration...
 then select a path in the open Device Table Configuration dialog, under which the
configuration files shall be saved

Note:

In the Settings (under Settings -> General -> Default Directories of the column File Type
Device Table Configuration Files) a default directory can be defined for the configuration
file:

124
To load the Device Table configuration:

 right-click on the first cell in the first column of the Device Table
 select the context menu command Load Configuration
 select the configuration in the open Device Table Configuration dialog and click on the
button Open.

Reference(s): Designer-22997

Cable End Attributes Can Now Be Added to Cables in the Device Table

Two columns for displaying cable end attributes (End 1 + End 2) can now be added to cables
in the Device Table.

In order for the columns to be added, a cable end attribute has to be created first in Database
Editor Mode (see under Edit Attribute Names), which has the following owner:

 'Cable type end' for displaying cable ends in the Component Properties -
Cables/Conductors (Database Editor Mode)
 'Cable end' for displaying cable ends in the Device Properties - Cables/Conductors
(Project Mode)

125
Save the cable end attribute in the Database and update the project configuration!

The next step involves defining the cable end attribute for the desired cable.

This can be done in...

 Database Editor Mode using Component Properties - Cables/Conductors, or

 Project Mode using Device Properties - Cables/Conductors.

Defining the cable end attribute on the cable component in Database Editor Mode:

Note: This cable end attribute can only be defined if the cable attribute has been
created with the owner 'Cable type end'.

 right-click on the desired cable(s) in Database Editor Mode,

 select the context menu command Component Properties and then the
Cables/Conductors tab in the Component Properties dialog,
 select the desired cable(s) and define the cable end attribute with entries for End 1 and
End 2:

126
Defining the cable end attribute on the cable device in Project Mode:

Note: This cable end attribute can only be defined if the cable attribute has been
created with the owner 'Cable end'.

 right-click on the desired cable(s) in Project Mode,

 select the context menu command Device Properties and then the
Cables/Conductors tab in the Device Properties dialog,

127
 select the desired cable(s) and define the cable end attribute with entries for End 1 and
End 2:

128
To add the new columns for displaying the cable end attribute:

 right-click on the table column header and select the context menu command Add
Column,
 click on the drop-down list and select the previously created attributes
<Cable_End_Attribute End 1> and <Cable_End_Attribute End 2>.

If a cable end attribute with the owner 'Cable type end' and entry have been defined for the
cable, this entry always appears in the Device Properties. This is irrespective of whether a
cable end attribute with the owner 'Cable end' and entry have been additionally defined:

If a cable end attribute only with the owner 'Cable end' and entry have been defined, this
entry appears in the Device Properties:

Note:

 For non-cable devices these cable end attribute columns (without contents) appear
grayed-out.
 If only the owner 'Cable type end' is defined for the cable, the cable end attribute
columns appear grayed-out. If an entry is only defined for Cable type end, the entry is
read-only and cannot be edited.

Reference(s): Designer-29091

Jump from Different Objects (Device, Symbol, Sheet) to the Database Tree

Previously, it wasn't possible to jump from devices, symbols or sheets to the referenced
location in the database tree.

129
By right-clicking on a placed object or object in the tree a corresponding 'Jump' command can
take place:

 For devices (valid only for placed devices), symbols and sheets there is the 'Jump to
Symbol/Misc Tree' command to jump to the referenced location in the database tree.
 For devices there is the 'Jump to Component Tree' command to jump to the
referenced location in the database tree.

Note: The 'Jump to Symbol/Misc Tree' or the 'Jump to Component Tree' command can
also be defined using a shortcut.

Reference(s): Designer-04338

130
Update in Project / Change Component

 Control whether Signals on Connector Pins of Block Connector Shall Be

Overwritten when Updating Project
 Additional Assignment Now Possible when Changing Component

Control whether Signals on Connector Pins of Block Connector Shall Be Overwritten

when Updating Project

Previously when updating a project in E3.series, the signals on the connector pins of a block
connector were not changed. Now it's possible to control whether the signals on the connector
pins of a block connector shall be overwritten.

To do so, there is the new check box 'Overwrite signals of block connectors' in the section
Signals in the Settings under General - Update in Project:

The dialog appears as follows in the 'Electric Settings':

131
The dialog appears as follows in the 'Fluid Settings':

General - Update in Project

Overwrite If this check box is activated, the signals on the connector pins of a block
signals of connector are overwritten.
block
connectors Note:

 The signal **NC** is only adopted if the pin is not plugged.

 A missing signal value <no Entry> is not adopted.
 Translated texts are supported.

If this check box is deactivated, the signals on the connector pins of a block
connector are not changed.

132
 For the COM methods prj.GetSettingValue and prj.SetSettingValue the
following setting_name can be used: RELOAD_SIGNALS.

This check box is project-specific in a multi-user project.

Reference(s): Designer-17215

Additional Assignment Now Possible when Changing Component

Now there is an additional possibility for influencing the behavior of the new component's
assignment when changing the component.

To do so, there is the new radio button 'Prefer symbol name, pin name and signal' in the
section Assignment in the Settings under Placement - Change Component':

The dialog appears as follows in the 'Electric Settings':

133
The dialog appears as follows in the 'Fluid Settings':

134
Placement - Change Component

Prefer symbol
name, pin If this option is active, the symbol name, pin name and signal are preferred
name and when changing the component.
signal
The following is checked when assigning normal devices:

 Placed symbols of devices must have the same names

(characteristics are permitted)
Note: The name is not checked for master symbols without pins.
 The pin names must be the same.
Note:The format of the pin names is also checked for terminals.
 If an internal device designation exists on the device pin, it must also
exist on the component pin.
 Signals may not be changed when exchanging component (for
example signal equivalence).

135
 The following is checked when assigning connectors:

 Placed pin names must be the same.

 If an internal device designation exists on the connector pin, it must
also exist on the component pin.
 Signals may not be changed when exchanging component (for
example signal equivalence).

For the COM methods prj.GetSettingValue and prj.SetSettingValue the

following setting_name can be used: ASSIGN_GATE_MODE

This check box is project-specific in a multi-user project.

Reference(s): Designer-27684

136
Variants

 Procedure for Placing and Deleting Variant Positions Has Been Modified
 Export Translated Texts from Variant Tree in an XML File
 Assign Different Variants/Options to Pins of Pin Group

Procedure for Placing and Deleting Variant Positions Has Been Modified

Previously when deleting the variant position of a device, the following components were
automatically deleted with it:

 the standard device at the variant position

 all other affiliated variant positions of the standard device

Now it's possible to delete only the variant position of the device.

For a variant position to be deleted, it has to be unplaced. With the existing context menu
command Unplace variant positions placed on a panel sheet can now be unplaced. Afterward,
the unplaced variant position can be deleted from the project.

To do so, there is the new context menu command Delete Variant Position in the Device
Tree

Note: If the command Delete Forced is executed, the standard device together with all
affiliated variant positions is deleted.

Additionally, there are two new context menu commands in the Device Tree:

o 'Place as Variant Position' used for devices or assemblies / assembly elements

o 'Place as Single Variant Position' used for assembly elements

Note:

 A panel sheet must be opened!

 There is no variant position for the currently active variant.

137
  The check box for Variants: must be set to default (called up in the Settings under
Variants / Options -> Display in the section Activation of Variants / Options).
 The standard device must not be forcibly placed.
 It can be devices or assemblies / assembly elements, which can be placed on a panel
sheet.

Place as Variant Position

If the context menu command 'Place as Variant Position' is called up using a device, the
device is placed at the variant position of the currently active variant.

If the context menu command 'Place as Variant Position' is called up using an assembly
element, a variant position is created for every assembly element of the currently active
variant.

In doing so, the assembly elements are placed as plugged with the appropriate slot and
mounting rail descriptions. Assembly elements, which are not plugged together" can be
inserted as 'unplaced' variant positions in the Device Tree.

To execute the command Place as Variant Position:

 right-click in the Device Tree on the...

o device symbol or model of assembly element

o assembly element symbol or on model of assembly element

 select the context menu command Place as Variant Position

Place as Single Variant Instance

It's now possible to place unplaced assembly elements as a single variant position.

To execute the command Place as Single Variant Position:

 right-click on the assembly element symbol or model of assembly element in the Device
Tree

138
  select the context menu command Place as Single Variant Position

Reference(s): Designer-22097

Export Translated Texts from Variant Tree in an XML File

When exporting translated texts in an XML file, the translated texts from the Variant Tree are
now also exported.

Note: To do so, a language must be defined in the Settings under Tools -> Settings ->
General -> Language. If several languages are defined, the first one is used.

139
Reference(s): Designer-30317

Assign Different Variants/Options to Pins of Pin Group

Previously, all pins of a pin group had to have the same variants/options.

Different variants/options can now be assigned to the pins of a pin group.

Reference(s): Designer-28153

140
Views

 'Normal' Device Symbols Can Now Be Defined as Symbol Views on Connectors

in E3
o Preparations in the Database Editor
o Use in Project

 Views Can Now Be Created even if Devices Placed on Locked Sheets

'Normal' Device Symbols Can Now Be Defined as Symbol Views on Connectors in E3

Previously, only connector symbols could be defined for device views of connectors in
E3.series. Now 'normal' device symbols can be defined as device views of connectors (or other
devices).

With the device view it's possible to receive information directly regarding all pins and
connected connections or conductors/wires. The desired information can be easily created for
the device view in the Database Editor using text types.

Preparations in the Database Editor

1st Step: Create/edit symbol for device view

To create or edit a symbol for the device view:

 select the main menu command Tools -> Start Database Editor
 this opens the Database Editor
 right-click on the desired symbol klicken, which shall be used as the (template for) the
device view in the component or symbol view of the database tree
 select the context menu command New or Edit
 this opens the symbol for editing in the workspace
 right-click on the symbol and select the context menu command Symbol Properties...
 select the Symbol tab in the Symbol Properties dialog
 select the Type: 'Normal' in the drop-down list.

Add the desired text types to the symbol (like Pin number, Cross-section, Conductor in
connection) and group the text nodes on the corresponding pin.

Note:

o The corresponding relationships are displayed by using logic lines.

o If necessary, the pin order can be changed in the main menu under Edit -> Order
Definition -> Node.

Save the symbol for the device view in the database!

Example: View symbol as front view

141
Example: View symbol as table symbol

142
2nd Step: Place Device View Symbol on Component

 open the component in the Database Editor, on which the device view(s) shall be placed
 right-click on the created symbol for the device view in the Symbol Tree
 select the context menu command Place as View

Next the symbol pins of the view must be assigned the desired component pins.

 right-click on the device view and select the context menu command View
Assignment...:

Save the component with the device view(s) in the database.

143
Use in Project

The desired device views can now be selected for the device in project mode:

Reference(s): Designer-29889

Views Can Now Be Created even if Devices Placed on Locked Sheets

Previously, no view (device view, formboard view) of a device could be created if the device
was placed on a locked sheet.

It's now possible to create a view of devices placed on locked sheets.

Note:

 This functionality is not possible if the original device is located within a locked structure
node.
 For a locked sheet the new view can only be created from the tree view.

Reference(s): Designer-30813

144
Zoom / Pan / Selection

 Specific Object Types Can Now Be Filtered in a Area Selection

Specific Object Types Can Now Be Filtered in a Area Selection

Previously, all object types in a selected area were selected in E3.series.

The following object types can now be filtered in the selected area:

 Symbols
 Texts
 Graphics
 Connect Lines
 Net Nodes
 Attribute Text Templates
 Dimensions

To do so, there is the new section Area Selection in the Settings under General - Zoom /
Pan / Selection:

145
The dialog appears as follows in the 'Electric Settings':

146
The dialog appears as follows in the 'Fluid Settings':

General - Zoom / Pan / Selection

Area Selection

Select all If activated, the following is valid for the selection area:
elements
inside and  All elements lying within, intersecting or touching the border of the
intersecting or selected rectangle are selected.
touching the
border of the If deactivated, the following is valid regarding the area selection:
selection
rectangle  Only those elements lying completely inside the selected rectangle
are selected.

Note: These options can also be activated/deactivated using the Selection

toolbar.

147
 For the COM methods prj.GetSettingValueand prj.SetSettingValue the
following setting_name can be used: SELECTION_BORDER

This check box is user-specific in a multi-user project.

Included Elements in Area Selection

Symbols
Texts If activated, the corresponding elements are included in the area selection.
Graphics If deactivated, the corresponding elements are not included in the area
Connect Lines selection.
Net Nodes
Note:
Attribute Text
Templates
o The selection takes place depending on the option Select all
Dimensions elements inside and intersecting or touching the border of the
selection rectangle.
o These options can also be activated/deactivated using the Selection
toolbar.

For the COM methods prj.GetSettingValue and prj.SetSettingValuethe

following setting_name can be used:

 SELECTION_SYMBOL
 SELECTION_TEXT
 SELECTION_GRAPHIC
 SELECTION_NETSEG
 SELECTION_NETNODE
 SELECTION_ATTRIBUTE
 SELECTION_DIMENSION

This check box is user-specific in a multi-user project.

148
Furthermore, the section Area Selection has also been added under Zoom / Pan /Selection
in the Database Settings.

These options can also be activated/deactivated using a toolbar.

To do so, there is the new toolbar 'Selection' with the following symbols in project and
database editor modes:

Hinweis: The existing symbol Selection mode has been moved from the toolbar
Standard to the new toolbar Selection.

149
Symbol: Purpose:

Selection mode:
Off: Select all elements completely inside
or
On: Select all elements inside and intersecting or touching the border of
the selection rectangle

Select Symbols
Off: Don't select symbols while selecting an area

On: Select symbols while selecting an area

Select Texts
Off: Don't select texts while selecting an area

On: Select texts while selecting an area

Select Graphics
Off: Don't select graphics while selecting an area

On: Select graphics texts while selecting an area

Select Connect Lines

Off: Don't select connect lines while selecting an area

On: Select graphics connect lines while selecting an area

Select Net Nodes

Off: Don't select net nodes while selecting an area

On: Select graphics net nodes while selecting an area

Select Attribute Text Templates

Off: Don't select attribute text templates while selecting an area

On: Select graphics attribute text templates while selecting an area

Select Dimensions
Off: Don't select dimensions while selecting an area

On: Select graphics dimensions while selecting an area

150
Example:

All elements are included in the selection:

Only symbol elements are included in the selection:

Reference(s): Designer-11612

151
 Europe
Germany
Zuken GmbH (European HQ)
D-85399 Hallbergmoos, Germany
Tel: +49 89 7104059 00

Americas Zuken E3 GmbH

D-89079 Ulm, Germany
North America
Tel: +49 7305 9309 0
Zuken USA Inc.
Westford, MA 01886, USA
Tel: +1 978 692 4900 Zuken E3 GmbH
D-30659 Hannover, Germany
Tel: +49 511 8595 9489
Asia
Japan Switzerland
Zuken (World Wide Head Office) Zuken E3 GmbH
Yokohama, Kanagawa 224-8585, Japan CH-5506 Mägenwil, Switzerland
Tel: +81 45 942 1511 Tel: +41 56 437 08 90

China United Kingdom

CIM-TEAM Software Technology Co., Ltd. Zuken UK Ltd.
Changning District, Shanghai, China, 200336 Bristol, BS32 4RF, UK
Tel: +86-21-52280180 Tel: +44 1454 207 801

Korea France
Zuken Korea Inc. Zuken S.A.
Seoul 135-283, Korea #91974 Les Ulis Cédex, France
Tel: +82 2 5648031 Tel: +33 1 69 29 48 00

Singapore Italy
Zuken Singapore Pte Ltd. Zuken S.r.l.
#22-05 Gateway East, Singapore 189721 20090 Milanofiori Assago, Milan, Italy
Tel: +65 6392 5855 Tel: +39 02 575 921

Taiwan Netherlands
Zuken Taiwan Inc. Zuken GmbH
Taipei 110, Taiwan NL-6075 HA Herkenbosch, The Netherlands
Tel: +886 2 7718 1116 Tel: +31 475 520 998

www.zuken.com/e3
All trademarks mentioned are the property of their respective owners, Copyright © Zuken E3 GmbH