New Features
2019-20.00

Technical Inquiries
Please contact our support department!
E-Mail: e3-support@zuken.com
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: e3-info@Zuken.com
© Copyright 2019, Zuken E3 GmbH
1

3
Date: 6/13/2019
This manual describes the following functions of version:
2019 Build 20.00
!! Please Note when Switching to New Version !!
Projects and databases are converted when opening them with this new E 3 .
series Release.
Please consider that these projects cannot be edited with an older version afterward. 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 E 3 .
series, E 3 .
template projects and E 3 .
example projects. You have most likely used this font to documents for E 3 .
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.
Furthermore, we recommend you change your templates to another font style so that new projects no longer use this font.
•
New Features
See also:
2

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 E 3 .
series 2019:
• 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 E 3 .
series 2019 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 E 3 .
series Version.
The Default Directory is:
\Program Files\Zuken\E3.series_<version>
Therefore, this version can also be used alongside existing versions of E 3 .
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 E 3 .
series 2019, so copies should be used for E 3 .
series
2019.
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 E 3 .
series Version 2019, a project can no longer be opened with an earlier version.
3

Multi-User Installation
Existing multi-user projects from Version 2018 can directly be opened with Version 2019. They are automatically converted upon opening. However, this cannot be undone, and the projects can no longer be opened with Version 2018.
That’s why we recommend installing Version 2019 multi-user projects in parallel to the existing version, so that it’s also possible to still access these project with E 3 .
series Version 2018.
To transfer the projects to Version 2019, these projects must be saved in Version 2018 as
Single-User projects. They can then be stored in the multi-user environment of Version 2019.
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 E 3 .
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.
4

The following functionality is new in Version 2019 Build 20.00:
•
Attributes
o
New Attributes in E3 Database
•
COM
o
COM - Miscellaneous
o
Enhancement to SheetInterface for Reading and Writing the Property
"Product" from/to Sheet
o
Enhancement to SymbolInterface for Moving Symbols to Foreground or Background
o
Enhancement to PinInterface for Returning and Setting Maximum
Number of Wire Crimps on Pins in Project
o
Enhancement to SheetInterface and DbeSymbolInterface for
Determining Size and Scale of DXF Graphics
o
Enhancement to DbeSymbolInterface for Importing DXF File
o
Enhancement to ApplicationInterface for Querying Multi-User Server and Port Currently Being Used
o
Enhancement to PinInterface for Returning Description of 'WireKind' of Wires
o
Enhancement to Return Values in JobInterface for OpenMultiuser ( name )
o
Enhancement to Return Values in the JobInterface for NewMultiuser
()
o
Change to Return Value and Behavior for Several Attribute COM
Commands if Input String Longer than Permitted Length
o
Messages Have Been Inserted in the CavityPartInface for Editing
Attributes of COM Commands
o
Enhancement to Return Values in MuComClient for RenameFolder
o
Enhancement to JobInterface for Determining All Selected Line
Segments
o
Enhancement to JobInterface for Transferring List of Placeholders and Values when Importing Subcircuits
o
Enhancement to DeviceInterface for Assigning Component Name when Creating Connector on Block
o
Enhancement to JobInterface for Setting Value 'AIRLINES'
o
Enhancement to DeviceInterface for Sorting Terminal Strips
o
Enhancement to DeviceInterface for Determining Defined Outer
Diameter of Cables
o
Enhancement to JobInterface for Returning Active Alias Name
o
Enhancement to JobInterface for Placing Inline Connectors on
Connection Lines
o
Enhancement to Functionality of COM Command GetAttributeValue for Returning Attribute from Original for the View
o
Enhancement to JobInterface for Executing an Undo
o
Functionality of COM Command job.GetSymbolIds Changed
o
Enhancement to DeviceInterface for Plugging Model of Device on Slot of Already Placed Model
5

o
Enhancement to OptionInterface for Determining whether Option of
Object Used in Project
o
Enhancement to JobInterface for Activating Pagination with PDF
Export
o
Enhancement to ComponentInterface for Determining the Subtype of
Component
o
COM-Interface - DBE-Interface
o
Enhancement to DbeAttributeInterface for Determining Name or
Internal Name of Attributes
o
Enhancement to DbeAttributeInterface for Determining the Value,
Internal Value or Formatted Value of Attributes
o
Enhancement to SymbolInterface and DbeSymbolInterface for
Determining the Symbol Type
o
Enhancement to ComponentInterface and DbeComponentInterface for Determining the Component Type
o
New COM Interface DbeModelInterface for Importing DXF Graphic on
Model in Database Editor
o
New COM Interface DbeModelPinInterface for Importing DXF Graphic on Model in DBE
o
Enhancement to SheetInterface and DbeSymbolInterface for
Determining Size and Scale of DXF Graphics
o
Enhancement to DbeSymbolInterface for Importing DXF File
•
Connections
o
Change Connection Line Segment of Line to Curved One (and Vice-Versa)
o
Decide whether Pins within a Device May Be Plugged Together
o
Cores/Wires or Hoses/Tubes Remain Connected to One End of Cross-
Reference (Source) when Disconnecting Assignment between Two Signal
Cross-References
•
Connectors
o
Define Connector with Inserts as Mating Connector for Another Connector with Inserts
o
Connectors with Inserts Can Now Be Defined on Several Connector Levels
o
Display Feed-Through Connectors in MIL Standard
o Simplified Procedure for Changing Connector Order in Block Components
•
DBE/Database Definition/Database Search
o
New Search Criteria for Searching in Component Tree and Component
Table
o
Searching for Symbols and Symbols with Defined Characteristics Now
Possible with Help of New Search Criterion <Characteristic>
o
Define Templates for Database Search
o
Search for Slots and Mounting Rails in Database Window
6

•
Display
o
Minimize Degree of Detail for Displaying Sheet Contents and Previewing
Sheets
•
Export / Import
o
AutoCAD Version 2018 and 2019 Now Supported when
Exporting/Importing DXF/DWG Files
•
Multi-User
o
Journal Files Will No Longer Be Created in Multi-User
o
External Documents Can Now Also Be Deleted when Closed in Multi-User
•
Print
o
'Select Print Areas' Dialog Has Been Enhanced for Selecting Print Areas
•
Placement / Purge
o
Now Possible to Control whether Existing Assemblies Can Be Added to or
New Assemblies Shall Be Created
o
Example 1 - (Project with assembly | Clipboard with device)
o
Example 2 - (Project with device | Clipboard with assembly)
•
Projects
o
Additional Start-Up Parameter '/sheets' for Assigning Licenses with
Different numbers of Sheets using License Server for the E3 Module
'SmallProject'
•
Panel
o
Fill Degree Can Now Be Displayed for Cable Duct Inlets/Outlets
•
Selection
o
Selection Process of Object Groups Has Been Simplified
7

•
Structure Nodes
o
Adding, Deleting, Renaming and Moving Structure Nodes in the Tree View
Can Now Be Locked
o
Enhancement to JobInterface for Locking Tree Structure Nodes
•
Tree Views / Bulk Data Management
o
Generate and Logically Plug Appropriate Mating Connector Pin in Device
Tree
o
New Pin Status Symbols
o
New Functions in Tree View
o
Keep Plug after Unplugging Pins
o
Display References with Logical Plugged Devices
o
Enhancements to COM Interface for Plugging and Unplugging
Devices and Connectors in the Tree View
o
Enhancement to DeviceInterface for Plugging and Unplugging
Devices and Connectors
o
Enhancement to DeviceInterface for Assigning Plugs to Devices
o
Enhancement to PinInterface for Plugging and Unplugging Pins
o
Enhancement to PinInterface for Determining Type of Plug
•
Update
o
Exchange Components in Same Order when Exchanging Assemblies with
Same Component Type Structure
•
User-interface (menus, dialogs, position or arrangement of windows/interactive operation/handling)
o
Touch Gestures Optimized for Touch Screens and Touch Pads in E3
•
Variants / Options
o
Search for Variants/Options within a Project
• Blocks o New Setting: Ignore Default Fill Color
• Text Types o Predefined Text Types for Displaying Default Wire Information
8

•
New Attributes in E3 Database
New Attributes in E3 Database
The following attributes have been added to the E 3 .
series database.
New internal attributes for defining the relevant paths and files for add-on programs (e.g.
Harness Designer):
• Variation Folder Path
(.VARIATION_FOLDER_PATH)
of type String with attribute owner
Project
• Variation File Name
(.VARIATION_FILE_NAME)
of type String with attribute owner
Project
• Harness Drawings Folder Path
(.HARNESS_FOLDER_PATH)
of type String with attribute owner Project
New internal attribute for assigning a reference to the pin for the connection target number:
• Route Target Number
(.ROUTE_TARGET_NUMBER)
of type String with attribute owner
Component-Pin. With this attribute a reference can be assigned to the pin.
Reference(s):
Designer-33196
9

Following functionalities are now available in the COM-Interface and are described in these chapters:
•
COM-Interface - Miscellaneous
o
Enhancement to SheetInterface for Reading and Writing the Property
"Product" from/to Sheet
o
Enhancement to SymbolInterface for Moving Symbols to Foreground or
Background
o
Enhancement to PinInterface for Returning and Setting Maximum Number of Wire Crimps on Pins in Project
o
Enhancement to OptionInterface for Determining whether Option of
Object Used in Project
o
Enhancement to JobInterface for Activating Pagination with PDF Export
o
Enhancement to ApplicationInterface for Querying Multi-User Server and
Port Currently Being Used
o
Enhancement to PinInterface for Returning Description of 'WireKind' of
Wires
o
Enhancement to Return Values in JobInterface for OpenMultiuser ( name )
o
Enhancement to Return Values in the JobInterface for NewMultiuser ()
o
Change to Return Value and Behavior for Several Attribute COM
Commands if Input String Longer than Permitted Length
o
Messages Have Been Inserted in the CavityPartInface for Editing
Attributes of COM Commands
o
Enhancement to Return Values in MuComClient for RenameFolder
o
Enhancement to JobInterface for Determining All Selected Line Segments
o
Enhancement to JobInterface for Transferring List of Placeholders and
Values when Importing Subcircuits
o
Enhancement to DeviceInterface for Assigning Component Name when
Creating Connector on Block
o
Enhancement to JobInterface for Setting Value 'AIRLINES'
o
Enhancement to DeviceInterface for Sorting Terminal Strips
o
Enhancement to DeviceInterface for Determining Defined Outer Diameter of Cables
o
Enhancement to JobInterface for Returning Active Alias Name
o
Enhancement to JobInterface for Placing Inline Connectors on Connection
Lines
o
Enhancement to Functionality of COM Command GetAttributeValue for
Returning Attribute from Original for the View
o
Enhancement to JobInterface for Executing an Undo
o
Functionality of COM Command job.GetSymbolIds Changed
o
Enhancement to DeviceInterface for Plugging Model of Device on Slot of
Already Placed Model
o
Enhancement to OptionInterface for Determining whether Option of
Object Used in Project
o
Enhancement to JobInterface for Activating Pagination with PDF Expor t
o
Enhancement to ComponentInterface for Determining the Subtype of
Component
•
COM-Interface - DBE-Interface
o
Enhancement to DbeAttributeInterface for Determining Name or Internal
Name of Attributes
o
Enhancement to DbeAttributeInterface for Determining the Value, Internal
Value or Formatted Value of Attributes
10

o
Enhancement to SymbolInterface and DbeSymbolInterface for
Determining the Symbol Type
o
Enhancement to ComponentInterface and DbeComponentInterface for
Determining the Component Type
o
New COM Interface DbeModelInterface for Importing DXF Graphic on
Model in Database Editor
o
New COM Interface DbeModelPinInterface for Importing DXF Graphic on
Model in DBE
o
Enhancement to SheetInterface and DbeSymbolInterface for Determining
Size and Scale of DXF Graphics
o
Enhancement to DbeSymbolInterface for Importing DXF File
11

•
Enhancement to SheetInterface for Reading and Writing the Property "Product" from/to Sheet
•
Enhancement to SymbolInterface for Moving Symbols to Foreground or
•
Background
Enhancement to PinInterface for Returning and Setting Maximum Number of
Wire Crimps on Pins in Project
•
Enhancement to OptionInterface for Determining whether Option of Object
•
Used in Project
Enhancement to JobInterface for Activating Pagination with PDF Export
•
Enhancement to ApplicationInterface for Querying Multi-User Server and Port
Currently Being Used
•
Enhancement to PinInterface for Returning Description of 'WireKind' of Wires
•
Enhancement to Return Values in JobInterface for OpenMultiuser ( name )
•
Enhancement to Return Values in the JobInterface for NewMultiuser ()
•
Change to Return Value and Behavior for Several Attribute COM Commands if
Input String Longer than Permitted Length
•
Messages Have Been Inserted in the CavityPartInface for Editing Attributes of
COM Commands
•
Enhancement to Return Values in MuComClient for RenameFolder
•
Enhancement to JobInterface for Determining All Selected Line Segments
•
Enhancement to JobInterface for Transferring List of Placeholders and Values when Importing Subcircuits
•
Enhancement to DeviceInterface for Assigning Component Name when Creating
Connector on Block
•
Enhancement to JobInterface for Setting Value 'AIRLINES'
•
Enhancement to DeviceInterface for Sorting Terminal Strips
•
Enhancement to DeviceInterface for Determining Defined Outer Diameter of
Cables
•
Enhancement to JobInterface for Returning Active Alias Name
•
Enhancement to JobInterface for Placing Inline Connectors on Connection Lines
•
Enhancement to Functionality of COM Command GetAttributeValue for
Returning Attribute from Original for the View
•
Enhancement to JobInterface for Executing an Undo
•
Functionality of COM Command job.GetSymbolIds Changed
•
Enhancement to DeviceInterface for Plugging Model of Device on Slot of
Already Placed Model
•
Enhancement to OptionInterface for Determining whether Option of Object
•
Used in Project
Enhancement to JobInterface for Activating Pagination with PDF Export
•
Enhancement to ComponentInterface for Determining the Subtype of
Component
Enhancement to SheetInterface for Reading and Writing the Property "Product" from/to Sheet
The following new COM command is in the Sheetinterface:
• ret = sht.GetProduct o ret The return value is the product name.
• ret = sht.SetProduct ( newproduct ) o newproduct New product name
12

o ret The return value is 1 if successful. If an error occurs, the following return values are possible:
 0 Not successful!
 -1 The product has not been set!
 -3 Sheet locked!
 -4 Sheet is a region!
 -8 Setting IEC 61346 not active!
 -9 Sheet is terminal sheet!
Reference(s):
Designer-31487
Enhancement to SymbolInterface for Moving Symbols to Foreground or Background
The following new COM commands are in the SymbolInterface:
• ret = sym.SendToForeground o ret The following return values are possible:
 0 The command was executed successfully!
 -1 No project opened!
 -2 No symbol ID set!
 -3 No placed symbol set!
 -4 Internal error
 -5 Internal error
• ret = sym.SendToBackground o ret The following return values are possible:
 0 The command was executed successfully!
 -1 No project opened!
 -2 No symbol ID set!
 -3 No placed symbol set!
 -4 Internal error
 -5 Internal error
Reference(s):
Designer-31853
Enhancement to PinInterface for Returning and Setting Maximum Number of Wire
Crimps on Pins in Project
The following new COM commands are in the PinInterface:
• ret = pin.GetMultipleWireCrimps o ret Returns the max. number of wire crimps for this pin. If an error occurs, the following values are possible:
 -1 Incorrect pin type!
 -2 Pin locked!
13

 -3 Pin is pin view!
 -4 No pin data available!
 -6 DBE running!
 -7 Multiple wire crimps allowed is not set!
 -8 Initialization of return value not overwritten!
• ret = pin.SetMultipleWireCrimps ( conncount ) o conncount Sets the max. number of wire crimps for this pin. Value must be between 0 and 999. o ret The return value is 0 if successful. In an error occurs, the following values are possible:
 -1 Incorrect pin type!
 -2 Pin locked!
 -3 Pin is pin view!
 -4 No pin data available!
 -5 Core redistribution not possible with current conncount
 -6 DBE running!
 -7 Multiple wire crimps allowed is not set!
 -8 Initialization of return value not overwritten!
Reference(s):
Designer-31889
Enhancement to OptionInterface for Determining whether Option of Object Used in
Project
The following new COM command is in the OptionInterface:
• ret = opt.IsInUseByObject o ret Returns 1 if the current option is being used, otherwise 0.
Reference(s):
Designer-30989
Enhancement to JobInterface for Activating Pagination with PDF Export
ExportPDF and ExportPDFEx have been enhanced as follows in the JobInterface:
• ret = job.ExportPDF ( file, shtids, options [,password] )
• ret = job.ExportPDFEx ( file, shtids, options, itemListType, items, alternativeColour, imageBrightness [,password] ) o options New bit for activating pagination:
 &h8000: Activates pagination!
Reference(s):
Designer-32834
14

Enhancement to ApplicationInterface for Querying Multi-User Server and Port
Currently Being Used
The following new COM command is in the ApplicationInterface:
• ret = app.GetMultiuserServer o ret Name of the multi-user server in the form Host name: Port or IP Address: Port.
Reference(s):
Designer-30784
Enhancement to PinInterface for Returning Description of 'WireKind' of Wires
The following new COM command is in the PinInterface:
• ret = pin.GetWireKindDescription o ret Returns the description of the 'wire kind' that can be set as an attribute on the body of wires/cores.
Reference(s):
Designer-32358
Enhancement to Return Values in JobInterface for OpenMultiuser ( name )
The following COM command has been supplemented in the Jobinterface:
• ret = job.OpenMultiuser ( name ) o name Name of multiuser project o ret Return value is the project's ID if the project could be opened and E 3 .
series started as multi-user, otherwise the following values are possible:
 0 Unknown error
 -1 No multi-user license!
 -2 Current multiuser server not available!
 -3 Project with the given name does not exist!
 -4 Project is in exclusive mode or project just created or user has no license!
 -5 Project already opened!
 -6 Project locked!
 -7 No project conversion possible in Viewer!
Reference(s):
Designer-32296
Enhancement to Return Values in the JobInterface for NewMultiuser ()
The following COM command has been supplemented in the Jobinterface:
• ret = job.NewMultiuser ( name, ... )
15

o ret Return value is the project's ID if the project could be created and will be set internally, otherwise the following values are possible:
 0 Unknown error
 -1 No multiuser license!
 -2 The current multi-user server is not available!
 -3 Project already opened!
 -4 Project locked!
Reference(s):
Designer-31805
Change to Return Value and Behavior for Several Attribute COM Commands if Input
String Longer than Permitted Length
The COM commands xxx.AddAttributeValue, xxx.SetAttributeValue, att.SetValue and
dev.SetAttributeValueVariant are affected:
• The return value is now always -1 if the permitted length of the input string exceeds
252 characters. o Previously, the attribute ID was returned.
• The behavior has been changed as follows: The input string is no longer saved, i.e. no change has taken place. o Previously, the input string was shortened and saved.
The COM commands xxx.AddAttributeValue and xxx.SetAttributeValue are affected in all interfaces, which are used for handling the attribute.
These COM commands are also affected in the following Interfaces:
• DimensionInterface
• ExternalDocumentInterface
• GraphInterface
• GroupInterface
• TextInterface
The following COM command is also affected in the AttributeInterface:
• att.SetValue
The following COM command is also affected in the DeviceInterface:
• dev.SetAttributeValueVariant
Reference(s):
Designer-23369
16

Messages Have Been Inserted in the CavityPartInface for Editing Attributes of COM
Commands
The COM commands for editing attributes have always been available but had no functionality.
That's why a message with the return value 0 or an empty string now appears in the Output
Window for these COM commands.
The following COM commands in the CavityPartInface are affected:
• ret = cav.AddAttributeValue ( name, value ) o The following message appears in the Output Window:
 CavityPartInterface::AddAttributeValue( BSTR name, BSTR value ) not yet implemented! o ret The return value is always 0!
• ret = cav.SetAttributeValue ( name, value ) o The following message appears in the Output Window:
 CavityPartInterface::SetAttributeValue( BSTR name, BSTR value ) not yet implemented! o ret The return value is always 0!
• ret = cav.GetAttributeValue ( name ) o The following message appears in the Output Window:
 CavityPartInterface::GetAttributeValue( BSTR name ) not yet implemented! o ret The return value is always an empty string!
• ret = cav.DeleteAttributeValue ( name ) o The following message appears in the Output Window:
 CavityPartInterface::DeleteAttributeValue( BSTR name ) not yet implemented! o ret The return value is always 0!
Reference(s):
Designer-32253
Enhancement to Return Values in MuComClient for RenameFolder
The return values for the following COM command in MuComClient have been enhanced:
• ret = oClient.RenameFolder ( path, newPath ) o ret New return values:
17

 -7 Old path and new path are the same!
 -8 The new path already exists!
Reference(s):
Designer-32057
Enhancement to JobInterface for Determining All Selected Line Segments
The following new COM command is in the JobInterface:
• ret = job.GetSelectedConnectLineIds ( ids ) o ids Returns IDs of all selected lines. o ret Number of IDs if successful, otherwise -1.
Reference(s):
Designer-31791
Enhancement to JobInterface for Transferring List of Placeholders and Values when
Importing Subcircuits
The following new COM command is in the JobInterface:
• ret = job.ImportDrawingForProjectGeneration ( name, unique, flags, substitutes, [allowedTexttypes], [allowedAttributenames], [resultArray],
[posx], [posy] ) o Using 'flags' it's possible to specify which placeholder text string ("Wildcard") shall be searched for and replaced with the 'name' of the affiliated text string
("Values"). The replacements are described under 'substitutes' and checked to see if they are permitted. o name File name of subcircuit as *.e3p file o unique If <> 0, then all new sheets generated with unique names! o flags The following values are possible:
 4 The subcircuit is inserted in the clipboard using 'Paste extended'.
 If none of the following values starting here are used, all replacements are activated:
 64 Activates the replacement of changeable texts.
 128 Activates the replacement of values of changeable attributes.
 256 Activates the replacement of signal names.
 512 Activates the replacement of sheet names.
 1024 Activates the replacement of sheet products.
 2048 Activates the replacement of the 'device designation' of devices.
 4096 Activates the replacement of the location of sheets, fields and devices.
 8192 Activates the replacement of the assignment of sheets, fields and devices.
 16384 Activates the replacement of names of structure nodes.
 32768 Activates the replacement of core names.
 65536 Activates the replacement of field products. o substitutes is a two-column table that contains all texts to be replaced; one replacement string pair per row:
 Column 0: Placeholder text string that shall be replaced ("Wildcard")!
18

 Column 1: Destination text string as opposed to text from column 0 that shall be replaced ("Value")!
 The following conditions apply:
 Each placeholder text string ("Wildcard") may appear only once in the table.
 A destination text string ("Value") may not be contained in the table of placeholder text strings ("Wildcard").
 A placeholder text string ("Wildcard") may not appear as a sub-string of another placeholder text string ("Wildcard") in the table. o allowedTexttypes is a single-column table:
 Each row contains the text types for which the replacement is permitted.
 If no text types are specified, the replacement for all permitted text types is executed.
 Basically the text types 1 to 999 are available to the user in E 3 . The following
 internal text types are excluded:
Text
name
Description Tex t typ
e
1 Position Position
3 Pin number Pin number
4 Symbol designat
5 ion
Sequential number of symbols
Compon ent code
Component name from database
6 PCB grid designat ion
Grid designation
7 Signal name Signal on pin
9 Pin symbol text - fix
Pin symbol text - fix
11 Text - fix Fix text on symbol
12 Device designat ion
14 Higher
Device designation of device level assignm ent
15 Location
Higher level assignment of device
Location of device
19

16
Referenc e to master
18
Referenc e to slave
Reference to master symbol
Reference to slave symbol
19 External pin External pin number number
24 Sheet number Sheet name
26 Date
Automatic entry of the system date on creation of a sheet
31 Number of Number of sheets in the project sheets in project
32 Device designat ion
Device designation of the sheet - used for "shortening" or, regarding terminal sheets, for the terminal strip
34 Higher level assignm ent
Higher level assignment of sheet - used for "shortening" or, regarding terminal sheets, for the terminal strip
35
Location Location of sheet - used for
"shortening" or, regarding terminal sheets, for the terminal strip
39 Docume nt type Sheet type, to which this sheet is assigned
203
Connect or pin name
Pin name on connector
Number of representative pins for pin groups
205 Block file Block text type
206 Sheet referenc e
Cross-reference with multiply displayed (split) blocks
212 Block designat ion /
Module designat ion
Project designation of a block / module
20

213
Connect or pin name /
Total number
303 Module port
Pin name on connector / Total number of connector pins
Number of representative pins for pin groups instead of pin name
implemented in E 3 .
logic name
350 Pin number Terminal pin name
351 Signal
Signal on terminal
352 Referenc e to schema
Cross-reference to terminal symbol's placement in the circuit diagram
353 Item designat ion
(ext.)
354 Pin name
(ext.)
355 Core name
(ext.)
Item designation of external device
Pin name of external device
Core / wire name of external cable / wire
356 Item designat ion (int.)
Item designation of internal device
357 Pin name
(int.)
358 Core name
(int.)
Pin name of internal device
Core / wire name of internal cable / wire
370
Compon ent code
Component code of terminal
371 Cable type
(ext.)
372 Cable
Cable type of external cable type
(int.)
373 Item designat ion of cable
(ext.)
374 Item designat ion of
Cable type of internal cable
Item designation of external cable
Item designation of internal cable
21

cable
(int.) o allowedAttributenames is a single-column table:
 Each row contains an attribute name, for whose attribute the replacement shall be allowed.
 If no attribute names are specified, the replacement for all permitted attribute names is executed.
 The following entries are permitted:
 Valid alphanumeric names (without blank spaces, ...)
 An attribute name may not begin with a '.' character. Note: Attribute names with a leading '.' are used to store internal information.
 The following attributes cannot be changed and are ignored when importing:

Attribute
Description
Component
Attribute for a component in the database (defined in the database); In project mode, it is displayed in the Component
View of the Component
Properties and cannot be modified.
Component Pin
Database Symbol
Database Bundle
Cable type
Core type
Attribute for a pin in the database; NOT visible in the project.
Attribute for a symbol in the database; not visible/modifiable in the project.
Attribute for a shield/bundle/twisted pair in the database; cannot be modified in the project.
Attribute for a cable/cable end in the database.
Attribute for a core/core end in the database (not visible in the project).
Database Model
Attribute for a model in the database.
22

Database Hose/Tube type Hose/tube or hose/tube end attribute in the database.
Database Functional
Unit Attribute for functional units in the database.
Database Functional
Port Attribute for functional ports in the database.
Database State
Attribute for functional states in the database. o resultArray is a four-column table that is returned if an error occurs:
 There is one row for each text that could not be replaced.
 The 4 columns contain the following values:

Column
Description
0
What
1
Item
2
Original string (placeholder)
3
Destination text string
 The column 'What' describes the type of error that occurred and can contain the following values:

What Object
Description
10 Text
Text type or text
11
12
13
14
15
16
17
18
Attribute
Signal
Device
Attribute value
Name
Complete item designation
Sheet
Sheet
Sheet
Sheet
Name
Product
Location
Assignment
Structure node Name
23

19
20
21
22
Wire
Field
Field
Field
Name
Product
Location
Assignment
• posx, posy It is possible to optionally define posx and posy. The system determines the reference point of the imported regions (minimum of the regions' lower left corners).
This reference point is then placed at the specified coordinate. o Example: A region with a lower left corner of (100 mm, 0 mm) is imported. The defined position is (500 mm, 0 mm). The new panel reference point of the region is (500 mm, 0 mm). The imported contents are moved by [(500, 0) - (100, 0) =
(400, 0)].
• ret The following values are possible if the import was successful: o 1 All could be replaced! o 2 Not all could be replaced! What was not replaced remains in the resultArray. o 4 The XML project structure is missing or differs. All could be replaced! o 5 The XML project structure is missing or differs. Not all could be replaced! What was not replaced remains in the resultArray.
• ret The following values are possible if the import was not successful and aborted: o -1 No project open or no file found or incorrect version of subcircuit! o -2 Invalid text types defined in allowedTexttypes! The invalid text types remain in the resultArray. o -3 Invalid attribute names defined in allowedAttributenames! The invalid attribute names remain in the resultArray. o -4 The array substitutes is invalid. o -5 Invalid strings are contained in the array substitutes. o -6 Unknown error
Reference(s):
Designer-32519
Enhancement to DeviceInterface for Assigning Component Name when Creating
Connector on Block
The following new COM command is in the DeviceInterface:
• ret = dev.CreateConnectorOnBlockEx ( blkid, name, assignment, location,
cmpname, version ) o blkid Creates a new connector within the block device given by its identifier! o name, assignment, location Item designation of new connector o cmpname Component name of connector o version Component version o ret The following values are possible:
 0 The command was successful!
24

 -1 Error
 -2 Component not found!
 -3 No valid pins found!
 -4 Supply could not be assigned to component!
Reference(s):
Designer-32981
Enhancement to JobInterface for Setting Value 'AIRLINES'
The following COM command has been enhanced in the JobInterface:
• ret = job.SetSettingValue ( name, value ) o name Defines the name of the parameter which is described in the Online Help chapter: 'Reference Manual -> Dialog Reference -> Project Mode ->
Settings -> Settings Overview for COM Interface'. o value The value of the setting 'AIRLINES' is a combination of bit settings from
'Connection -> Cable/Core Logic Lines' and 'Connection -> Signal Logic
Lines' and 'Formboard'. o New: Now it's possible to use your own setting names name instead of bits in
value. These new setting names are taken from the respective chapter of the corresponding COM methods in the Online Help.
Reference(s):
Designer-33343
Enhancement to DeviceInterface for Sorting Terminal Strips
The following new COM command is in the DeviceInterface:
• ret = dev.SortTerminals ( method, sub_method, sort_file ) o method The following methods are possible for the sorting:
 1 Sort by pin name in ascending order
 2 Sort by pin name in descending order
 3 Sort by cable
 4 Sort by placement
 5 Sort by jumper
 6 Sort by sorting file o sub_method The following sub-method must be set for the following methods
method:
 method = 4 Sort by placement:
 1 upward, to the right
 2 upward, to the left
 3 to the right, upward
 4 to the right, downward
 5 to the left, upward
 6 to the left, downward
 7 downward, to the right
25

 8 downward, to the left
 method = 5 Sort by jumper:
 10 Jumper by connections
 11 Jumper by attributes o sort_file File name for the "Sort by file" with method = 6
 Note: In contrast to interactive execution, the selected sorting file is not saved for the terminal strip. o ret The return value is 1 if successful. If an error occurs, the following values are possible:
 -1 No project opened or no valid device object!
 -2 Terminal strip locked from being moved!
 -3 Terminal strip could not be sorted because it's completely or partially placed in the panel and the setting "Panel -> Placement -> Optimize placement after changes" not active!
 -4 Single terminals are placed and grouped in the panel.
 -5 No defined sorting method in method!
 -6 No defined sorting sub-method in sub_method!
 -7 Sorting file doesn't exist or cannot be opened!
 -8 Another error, e.g. Placement collisions when unplacing in panel
Reference(s):
Designer-33061
Enhancement to DeviceInterface for Determining Defined Outer Diameter of Cables
The following new COM command is in the DeviceInterface:
• ret = dev.GetDefinedOuterDiameter o ret The return value is the outer diameter of the cable if defined, otherwise 0.
Reference(s):
Designer-29255
Enhancement to JobInterface for Returning Active Alias Name
The following new COM command is in the JobInterface:
• ret = job.GetActiveAlias ( name ) o name Name of active alias o ret The return value is 1 if successful. If an error occurs, the following return values are possible:
 -1 No project opened!
 -2 No aliases defined in project!
 -3 Aliases defined in project but no alias defined as active!
26

Reference(s):
Designer-31792
Enhancement to JobInterface for Placing Inline Connectors on Connection Lines
The following new COM command is in the JobInterface:
• ret = job.CreateInlineConnectorsOnConnectionLine( newCoreIDs,
newDeviceIDs, flags, LineIDs, CompName, CompVersion, newSymbolIDs ) o newCoreIDs Returns an array with the IDs of the newly generated wires/conductors. o newDeviceIDs Returns an array with the IDs of the newly generated connectors. o flags Not currently in use! o LineIDs Defines an array with connection line IDs! o CompName Name of a connector component in the database, which shall be used for the new inline connector. If the name is an empty string, the default symbol defined in the project is used. o CompVersion Version of connector component in database used for the new inline connector! If an empty string, the current version is used. o newSymbolIDs Defines a multi-dimensional array with the following values:
 fromPinId
 fromSymbolId
 toSymbolId
 Viewnumber o ret The return value is the number of IDs of the newly generated connectors from
newDeviceIDs if successful. If an error occurs, the following values are possible:
 -1 One of the given connection lines is invalid!
 -2 The connector could not be determined from the database or project!
 -3 No mating connector found! The inline connector was placed without a mating connector.
 -4 A connector symbol could not be placed!
 -5 The graphic connection is a curve!
 -6 No graphical connection for placing the default symbol could be determined!
 -7 The given connector doesn't have enough pins!
 -8 Component type was connector with inserts!
 -9 Internal error
 -10 One of the connection lines is not active!
 -11 One of the connection lines, wires or ends is locked!
 -12 No inline connector can be placed in a topology net!
 -13 Sheet, on which connection line is placed, is set to read-only.
Reference(s):
Designer-31792
Enhancement to Functionality of COM Command GetAttributeValue for Returning
Attribute from Original for the View
Enhancement to Functionality of COM Command GetAttributeValue for Returning an Attribute from the Original for the View
27

• ret = any.GetAttributeValue o ret Returns valid values from the original for the view!
Reference(s):
Designer-08359
Enhancement to JobInterface for Executing an Undo
The following new COM command is in the JobInterface:
• ret = job.UndoAfterExecution ( newval ) o To undo changes in the script o newval Optional parameter. If no value set, the last state is executed. The following values are possible:
 -1 Default value; do nothing!
 0 Don't undo changes or reset undo function!
 1 Undo all changes executed in script from beginning or last
UpdateMultiuser/FinalizeTransaction call! o ret 0 or 1 Returns the last state before calling the function
Reference(s):
Designer-33277
Functionality of COM Command job.GetSymbolIds Changed
The COM command in the JobInterface has been changed as follows:
• ret = job.GetSymbolIds ( ids, .... ) o ids Fields no longer returned in ids!
Reference(s):
Designer-10874
Enhancement to DeviceInterface for Plugging Model of Device on Slot of Already
Placed Model
The following new COM commands are in the DeviceInterface:
• ret = dev.PlaceOnPointSlot ( slotid, rotation, pivot, combined, collisionids ) o slotid ID of slot, on which it shall be placed! o rotation (optional) Rotation, which the device should have relative to the slot o pivot (optional) Pivot, which the device should have relative to the slot. The following values are possible:
 0 Normal
 1 On the back
 2 To the right
28

 3 To the left
 4 To the front
 5 To the back o combined (optional) For a value > 0 the mounted elements are also placed if handled as a plugged assembly! o collisionids (optional) Array with collisions and collisions items in the form:
0=collision reason, 1=collision item). The following collision reasons are possible:
 1 Device couldn't be placed because mounting description doesn't fit!
 2 Device couldn't be placed because it doesn't fit the slot!
 3 Device couldn't be placed because it collides with another device!
 4 Collision with restricted area
 5 Collision with cutout
 6 Cutout collides with restricted area
 7 Collision with drill hole
 8 Doesn't fit slot due to current option/variant definitions!
 9 Cannot be placed on sheet! o ret The following values are possible:
 2 Device could be placed but there were warnings from panel checks; reasons can be found in the Collision Array!
 1 Device placed successfully!
 -1 No device or no project!
 -2 No valid slot id specified!
 -3 Given slot not the correct type for this command!
 -4 Slot on which it should be placed, not placed!
 -5 Device already placed!
 -6 No panel data (model)
 -8 Device couldn't be placed due to collisions; reasons can be found in the
Collision Array!
 -9 Device couldn't be placed for unknown reasons!
• ret = dev.PlaceOnLineSlot ( slotid, x, rotation, combined, collisionids ) o slotid ID of slot, on which it shall be placed! o x x-offset, where it shall be placed on the line with reference to the origin o rotation (optional) Rotation, which the device shall have relative to the slot o combined (optional) For a value > 0 the mounted elements are also placed if handled as a plugged assembly! o collisionids (optional) Array with collisions and collisions items in the form:
0=collision reason, 1=collision item). The following collision reasons are possible:
 1 Device couldn't be placed because mounting description doesn't fit!
 2 Device couldn't be placed because it doesn't fit the slot!
 3 Device couldn't be placed because it collides with another device!
 4 Collision with restricted area
 5 Collision with cutout
 6 Cutout collides with restricted area
 7 Collision with drill hole
 8 Doesn't fit slot due to current option/variant definitions!
 9 Cannot be placed on sheet! o ret The following values are possible:
29

 2 Device could be placed but there were warnings from panel checks; reasons can be found in the Collision Array!
 1 Device placed successfully!
 -1 No device or no project!
 -2 No valid slot id specified!
 -3 Given slot not the correct type for this command!
 -4 Slot on which it should be placed, not placed!
 -5 Device already placed!
 -6 No panel data (model)
 -7 Tried to place device outside of the slot!
 -8 Device couldn't be placed due to collisions; reasons can be found in the
Collision Array!
 -9 Device could not be placed for unknown reasons!
• ret = dev.PlaceOnAreaSlot ( slotid, x, y, rotation, pivot, combined, collisionids ) o slotid ID of slot, on which it shall be placed! o x, y x-offset and y-offset, where it shall be placed on the area with reference to the origin o rotation (optional) Rotation, which the device shall have relative to the slot o pivot (optional) Pivot, which the device shall have relative to the slot. The following values are possible:
 0 Normal
 1 On the back
 2 To the right
 3 To the left
 4 To the front
 5 To the back o combined (optional) For a value > 0 the mounted elements are also placed if handled as a plugged assembly! o collisionids (optional) Array with collisions and collisions items in the form:
0=collision reason, 1=collision item). The following collision reasons are possible:
 1 Device could not be placed because mounting description doesn't fit!
 2 Device couldn't be placed because it doesn't fit the slot!
 3 Device couldn't be placed because it collides with another device!
 4 Collision with restricted area
 5 Collision with cutout
 6 Cutout collides with restricted area
 7 Collision with drill hole
 8 Doesn't fit slot due to current option/variant definitions!
 9 Cannot be placed on sheet! o ret The following values are possible:
 2 Device could be placed but there were warnings from panel checks; reasons can be found in the Collision Array!
 1 Device placed successfully!
 -1 No device or no project!
 -2 No valid slot id specified!
 -3 Given slot not the correct type for this command!
 -4 Slot on which it should be placed, not placed!
 -5 Device already placed!
 -6 No panel data (model)
30

 -7 Tried to place device outside of the slot!
 -8 Device couldn't be placed due to collisions; reasons can be found in the
Collision Array!
 -9 Device couldn't be placed for unknown reasons!
Reference(s):
Designer-33024
Enhancement to OptionInterface for Determining whether Option of Object Used in
Project
The following new COM command is in the OptionInterface:
• ret = opt.IsInUseByObject o ret Returns 1 if the current option is being used, otherwise 0.
Reference(s):
Designer-30989
Enhancement to JobInterface for Activating Pagination with PDF Export
The following new COM command is in the JobInterface:
• ret = job.ExportPDF ( file, shtids, options [,password] )
• ret = job.ExportPDFEx ( file, shtids, options, itemListType, items, alternativeColour, imageBrightness [,password] )
options new bit for activation of pagination:
&h8000: Activate pagination
Reference(s):
Designer-32834
Enhancement to ComponentInterface for Determining the 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.
 7 Joint Connector: Joint Connectors are kind of junction like splice (only valid for Blocks)
31

o ret Error values are:
 -1 No project is open.
 -2 No component id is set.
 -3 Component is not a standard type or not block 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-32741
32

•
Enhancement to DbeAttributeInterface for Determining Name or Internal Name of Attributes
•
Enhancement to DbeAttributeInterface for Determining the Value, Internal
•
Value or Formatted Value of Attributes
Enhancement to SymbolInterface and DbeSymbolInterface for Determining the
Symbol Type
•
Enhancement to ComponentInterface and DbeComponentInterface for
•
Determining the Component Type
New COM Interface DbeModelInterface for Importing DXF Graphic on Model in
Database Editor
•
New COM Interface DbeModelPinInterface for Importing DXF Graphic on Model in DBE
•
Enhancement to SheetInterface and DbeSymbolInterface for Determining Size and Scale of DXF Graphics
•
Enhancement to DbeSymbolInterface for Importing DXF File
Enhancement to DbeAttributeInterface for Determining Name or Internal Name of
Attributes
The following new COM commands are in the DbeAttributeInterface:
• ret = dbeatt.GetName o ret Returns the attribute's name as a string.
• ret = dbeatt.GetInternalName o ret Returns the user-defined name as a string.
Enhancement to DbeAttributeInterface for Determining the Value, Internal Value or
Formatted Value of Attributes
The following new COM commands are in the DbeAttributeInterface:
• ret = dbeatt.GetValue o ret Returns the attribute's value as a string.
• ret = dbeatt.GetInternalValue o ret Returns the string attributes, that contain translatable text tokens in their internal representation, that contains token of format "&#num;".
• ret = dbeatt.GetFormattedValue o ret Returns the formatted value as a string. The function returns also 'measure of length' attributes, as they are represented in the plan.
Reference(s):
Designer-32233
33

Enhancement to SymbolInterface and DbeSymbolInterface for Determining the
Symbol Type
The following new COM command is in the SymbolInterface and DbeSymbolInterface:
• ret = sym/dbesym.GetSymbolType o ret The return value is the symbol type. The following symbol types are possible:
 0 Undefined
 1 ArrowSymbol
 2 ASICOrFPGASymbol
 3 AttributeTextTemplateSymbol
 4 BlockSymbol
 5 BlockConnectorSymbol
 6 ConnectorSymbol
 7 ConnectorMasterSymbol
 8 ConnectorTableSymbol
 9 ContactArrangementTemplateSymbol
 10 GeneralTemplateSymbol
 11 BundleSymbol
 12 ModulePortSymbol
 13 NodeTemplateSymbol
 14 NormalSymbol
 15 PadTemplateSymbol
 16 PinTemplateSymbol
 17 ShieldSymbol
 18 SignalCarryingSymbol
 19 TerminalPlanJumperSymbol
 20 TerminalPlanTableSymbol
 21 TwistedPairSymbol
 22 AccessorySymbol
 23 DetailSymbol
 24 MultiHoldingSymbol
 25 FixtureSymbol
 26 FrontviewConnectorSymbol
 27 FigureSymbol
 28 ReferenceSymbol
 29 ModelSymbol
 30 SheetSymbol
 31 TerminalPlanSheetSymbol
 32 PanelSheetSymbol
 33 ConnIOSymbol
 34 BackPlaneEndSymbol
 35 FieldSymbol
 36 DynamicSymbol
 37 HPortOnSheetSymbol
 38 MountSymbol
 39 DeviceSymbol
 40 CableDuctSymbol
 41 CableDuctReferenceSymbol
 If an error occurs, the return value is:
 -1 No project, no symbol id or symbol not found!
34

Reference(s):
Designer-32275
Enhancement to ComponentInterface and DbeComponentInterface for Determining the Component Type
The following new COM command is in the ComponentInterface and
DbeComponentInterface:
• ret = cmp/dbecmp.GetComponentType o ret The return value is the component type. The following component types are possible:
 1 StandardDevice
 2 Connector
 3 ConnectorWithInserts
 4 FeedThroughConnector
 5 Terminal
 6 Block
 7 Assembly
 8 CavityPartGroup
 9 Subcircuit
 10 Cable
 11 WireGroup
 12 Hose
 13 Tube
 14 Overbraid
 15 Accessory
 16 Fixture
 17 ProtectionTube
 18 ProtectionTape
 19 Protector
 20 Splice
 21 CavityPlug
 22 PinTerminal
 23 WireSeal
 24 Mount
 25 CableDuct
 26 CableDuctReference
 27 CableDuctBackplanWire
 28 CableDuctPunchingStrip
 29 EndBracket
 30 EndCover
 31 SeparatingPlate
 32 NoStructureComponent
 33 DynamicComponent
 34 DynamicComponentDeviceStructureComponent
 If an error occurs, the following values are possible:
 -1 No project
 -2 No component ID
 -3 Undefined component type
Reference(s):
Designer-32272
35

New COM Interface DbeModelInterface for Importing DXF Graphic on Model in
Database Editor
Enhancement to DbeApplicationInterface for creating a new DbeModelInterface object:
• ret = e3dbe.CreateDbeModelObject o ret The return value is a DbeModelInterface object!
• ret = e3dbe.GetModelIds ( ids ) o ids Returns the IDs of all models! o ret Number of IDs if successful, otherwise -1!
• ret = e3dbe.GetActiveModelId o ret The return value is the model ID of the active sheet if successful. If an error occurs, the following values are possible:
 -1 If no project or no sheet is opened!
 -2 If the current sheet is not a model sheet!
The new DbeModelInterface contains the following COM commands:
• ret = dbemod.GetId o ret The return value is the ID of the DbeModelInterface object if successful, otherwise 0.
• ret = dbemod.SetId ( id ) o id ID of DbeModelInterface object o ret The return value is the ID of the DbeModelInterface object if successful, otherwise 0.
• ret = dbemod.GetName o ret Name of the model
• ret = dbemod.GetCharacteristic o ret Characteristic of the model
• ret = dbemod.Remove ( save_changes ) o Removes the model from the Dbe o save_changes Default value is 0! If the value is set to 1, not yet saved changes are saved. o ret The return value is 1 if successful. If an error occurs, the following values are possible:
 -1 No project opened or no valid ID defined!
 -2 Database is read-only!
36

 -3 The model could not be deleted!
• ret = dbemod.Save o Saves the current model! o ret The return value is 1 if successful. If an error occurs, the following values are possible:
 -1 No project open or no valid ID defined!
 -2 Database is read-only!
 -3 The model could not be saved!
• ret = dbemod.ImportDXF ( filename, scale, x, y, rot, font, flags ) o filename Imports an Autocad© DXF or DWG file o scale change the overall-size of file o x, y New graphic will be placed at (x,y) o rot is ignored so far. It will be used in later versions o font a special windows font name to format text strings o flags The following values are possible:
 &h01 No check whether contents fit the sheet!
 &h02 Ignore attribute tags!
 &h04 The coordinates don't refer to the symbol origin but the sheet.
 &h08 After placing the DXF graphic, the symbol's space requirement is adapted. o ret Item number of sheet! If an error occurs, the following values are possible:
 -1 No model defined in interface or no open pool
 -2 DXF file not found!
 -3 Rotation not supported!
 -4 Font name not found!
 -5 Content exceeds sheet size!
• ret = dbemod.FitSpaceRequirement o Fits the space requirement so that surrounding rectangle can be manually adjusted! o ret The return value is 1 if successful, otherwise -1.
• ret = dbemod.GetDXFSize ( fileName, font, dx, dy, scale ) o fileName Autocad© DXF or DWG file (path + filename) o font Special windows font name for formatting text strings o dx Returns the size in x o dy Returns the size in y o scale Returns the max. possible scale for this sheet and defined font o ret The following values are possible:
 1 Size and scale could not be determined!
 -1 No sheet opened!
 -2 Invalid DXF file or path!
 -3 No valid font!
• ret = dbemod.ActivateModelView ( modelview )
37

o Activates the desired model view! If this view doesn't exist, it's created! o modelview The following values are possible:
 0 Front
 1 Back
 2 Right
 3 Left
 4 Top
 5 Bottom o ret The return value is 1 if successful, otherwise -1.
• ret = dbemod.GetPinIds ( ids ) o ids Returns the IDs of the model's pins! o ret Number of IDs if successful, otherwise -1 or -4
Reference(s):
Designer-32854
New COM Interface DbeModelPinInterface for Importing DXF Graphic on Model in
DBE
Enhancement to the DbeApplicationInterface for creating a new DbeModelPinInterface object:
• ret = e3dbe.CreateDbeModelPinObject o ret The return value is the DbeModelPinInterface object.
The new DbeModelPinInterface contains the following COM commands:
• ret = dbemodpin.GetId o ret The return value is the ID of the DbeModelPinInterface object if successful, otherwise 0.
• ret = dbemodpin.SetId ( id ) o id ID of a DbeModelPinInterface object o ret The return value is the ID of the DbeModelPinInterface object if successful, otherwise 0.
• ret = dbemodpin.GetCrimpingRules ( rules ) o rules Returns an array with the crimping rules on the pins if available, otherwise an empty array! o ret The return value is the number of array elements if successful, otherwise -1.
• ret = dbemodpin.SetCrimpingRules ( rules ) o rules Array with crimping rules; null pointer (a pointer that doesn't point to any object or function) or empty array deletes the crimping rules on the pin.
38

o ret The return value is 1 if successful. If an error occurs, the following return values are possible:
 -1 No Physpin set!
 -2 Invalid GD (granular design) object!
 -3 Invalid array rules!
Reference(s):
Designer-32416
Enhancement to SheetInterface and DbeSymbolInterface for Determining Size and
Scale of DXF Graphics
The following new COM command is in the SheetInterface and DbeSymbolInterface:
• ret = sht/dbesym.GetDXFSize ( filename, font, dx, dy, scale ) o filename Autocad© DXF or DWG file (path + file name) o font Special windows font name for formatting text strings o dx, dy Return value of size in x and y o scale Max. possible scale for this sheet and defined font! o ret The return value is 1 if successful. If an error occurs, the following values are possible:
 -1 No sheet or no opened pool!
 -2 Invalid DXF file or path!
 -3 No valid font!
Reference(s):
Designer-32348
Enhancement to DbeSymbolInterface for Importing DXF File
The following new COM command is in the DbeSymbolInterface:
• ret = dbesym.ImportDxf ( filename, scale, x, y, rot, font, flags ) o filename Imports Autocad© DXF or DWG file! o scale Changes the overall size of file! o x, y New graphic placed at (x,y)! o rot Not currently in use! Will be used in later versions! o font Special windows font name for formatting text strings o flags The following values are possible:
 &h01 No check whether the contents fit the sheet!
 &h02 Ignore attribute tags
 &h04 Coordinates do not refer to symbol origin but the sheet!
 &h08 After placing DXF graphic, the symbol's space requirement is adjusted! o ret Item number of sheet. If an error occurs, the following values are possible:
 -1 No symbol set in interface or no opened pool!
 -2 DXF file not found!
 -3 Unsupported rotation!
39

 -4 Font name not found!
 -5 Content exceeds sheet size!
Reference(s):
Designer-32223
40

•
Change Connection Line Segment of Line to Curved One (and Vice-Versa)
•
Decide whether Pins within Device May Be Plugged Together
•
Cores/Wires or Hoses/Tubes Remain Connected to One End of Cross-Reference
(Source) when Disconnecting Assignment between Two Signal Cross-
References
Change Connection Line Segment of Line to Curved One (and Vice-Versa)
Previously, it wasn't possible to change a connection line segment of a line into a curved one
(and vice-versa) in E 3 .
series.
This is now possible with the new functionality.
To do so, there are the new context menu commands:
• Change connect line to spline
• Change spline to connect line
This functionality can also be executed using the new symbols:
•
•
Change connect line to spline
Change spline to connect line
Note: These symbols are not predefined in the standard toolbar but can be selected from the category Misc accelerator under Tools > Customize... -> Tab Commands for adapting the toolbar as required.
To change a connection line segment of a line into a curved one:
• Select the desired connection line segment,
• right-click and select the context menu command Change connect line to spline or left-click on the symbol Change connect line to spline
41

Note: After changing the connection segment to a curve, the editing point mode is activated.
By right-clicking on the curve an additional point can be added to the curve using the context menu command Add point. To delete three or more points, use the context menu command
Delete point. With the context menu command Stop editing points or clicking anywhere in the workspace, the editing mode is terminated.
To change a curved connection line segment to a line:
• Select the desired curved connection segment,
• right-click on the context menu command Change spline to connect line or left-click on the symbol Change spline to connect line
Note: The start and end points of the curve are used for the line.
42

Reference(s):
Designer-31381
Decide whether Pins within Device May Be Plugged Together
Now it's possible to decide whether a pin may be plugged to a pin of the same device.
To do so, there is the new check box 'Deny plugging pins of same device' in the section
Pins under Connection in the settings:
The dialog appears as follows in the 'Electric Settings':
The dialog appears as follows in the 'Fluid Settings':
43

Deny plugging pins of same device
If this check box is activated, plugged connections between pins within a device are not possible.
If deactivated, plugged connections between pins within a device are permitted.
Note: Already existing plugged connections remain unchanged.
For the COM methods prj.GetSettingValue and prj.SetSettingValue the following setting_name can be used:
DENY_PLUG_PINS_OF_SAME_DEVICE
44

This check box is user-specific in a multi-user project.
.
Reference(s):
Designer-33281
Cores/Wires or Hoses/Tubes Remain Connected to One End of Cross-Reference
(Source) when Disconnecting Assignment between Two Signal Cross-References
When disconnecting the assignment between two signal cross-references, cores/wires or hoses/tubes remain connected to one end of the source cross-reference.
To do so, there is a new check box 'Connect cores/wires at one end to source cross-
reference if cross-reference is unconnected' in the section Conductors/Wires in the electric settings under Connection or the new check box 'Connect hoses/tubes at one end
to source cross-reference if cross-reference is unconnected' in the section
Hoses/Tubes in the fluid settings under Connection.
As it appears in the 'Electric Settings':
45

Connect cores/wires at one end to source crossreference if crossreference is unconnected
If activated, cores/wires are connected as follows after disconnecting two signal cross-references:
Single Connection
For one connection the cores/wires are connected to the source crossreference, regardless of the wire direction.
46

Two Connections
For two similar connections the second end always moves in the direction, in which the first ends.
Multiple Connections
For connections over multiple sheets the separated connection is always considered.
Note: Cores (conductors) and wires are only unconnected if they have not already been placed (Formboard, Topology, Panel, etc.).
.
As it appears in the 'Fluid Settings':
47

Connect hoses/tubes at one end to source crossreference if crossreference is unconnected
If activated, hoses/tubes are connected as follows after separating two signal cross-references:
Single Connection
For one connection the hoses/tubes are connected to the source crossreference, regardless of the wire direction.
48

Two Connections
For two similar connections the second end always moves in the direction, in which the first ends.
Multiple Connections
For connections over multiple sheets the separated connection is always considered.
Note: Hoses and tubes are only unconnected if they have not already been placed (Formboard, Topology, Panel, etc.).
.
Reference(s):
Designer-33708
49

•
Define Connector with Inserts as Mating Connector for Another Connector with
Inserts
•
Connectors with Inserts Can Now Be Defined on Several Connector Levels
•
Display Feed-Through Connectors in MIL Standard
•
Simplified Procedure for Changing Connector Order in Block Components
Define Connector with Inserts as Mating Connector for Another Connector with
Inserts
The user wants to define a connector with inserts as the mating connector for another connector with inserts. This shall also be placed in the project correctly with the structure (and the frame) when connecting.
Definition in database:
• Connector A has connector B or C defined as inserts.
• Connector X has connector Y or Z defined as inserts.
• Connector A has connector X defined as the active mating connector.
• Connector B has connector Y defined as the active mating connector.
• Connector C has connector Z defined as the active mating connector.
• Connector X has connector A defined as the active mating connector.
• Connector Y has connector B defined as the active mating connector.
• Connector Z has connector C defined as the active mating connector.
Use in project:
• If insert B of connector A is used, then insert Y of connector X must be used.
•
•
If insert C of connector A is used, then insert Z of connector X must be used.
If insert Y of connector X is used, then insert B of connector A must be used.
• If insert Z of connector X is used, then insert C of connector A must be used.
----------------------------------------------------------------------------------------------------------
--------
• The combinations described above can be defined in the database.
• When connecting to a pin of a connector, the correct mating connector is used (see description above)
For a connector with inserts it's now possible to define another connector with inserts as the mating connector.
Reference(s):
Designer-29244
Connectors with Inserts Can Now Be Defined on Several Connector Levels
The E3 user wants to have the possibility of using several nested connectors with inserts.
Previously, only one level could be defined
Connector - Slot - Connector
50

• A connector with inserts can be defined in the database, which can also have a connector with inserts (pin terminal).
• The connector in a project is recognized correctly as a connector in the tree and also displayed over several levels.
Previously in E 3 .
series a connector with inserts could only be defined on one level. Now It's possible to use several nested connectors with inserts.
New symbol in tree view:
Reference(s):
Designer-32689
Display Feed-through Connectors in MIL Standard
The user wants to display feed-through connectors in MIL standard. It wasn't clear to the user why this wouldn't work.
Previously, feed-through connectors could not be displayed in MIL Standard. Now it's possible.
Reference(s):
Designer-19782
Simplified Procedure for Changing Connector Order in Block Components
When editing a block component in the database editor, the connector order can be changed using the Symbol Properties of a connector.
The number of entries in the drop-down list corresponds with the number of connectors.
Reference(s):
Designer-31723
51

•
New Search Criteria for Searching in Component Tree and Component Table
•
Searching for Symbols and Symbols with Defined Characteristics Now Possible with Help of New Search Criterion <Characteristic>
•
Define Templates for Database Search
•
Search for Slots and Mounting Rails in Database Window
•
Search for Components in Database Tree using Attribute Values
New Search Criteria for Searching in Component Tree and Component Table
The following new search criteria are available for searching in the Component Tree and
Component Table in E 3 .
series:
• <Component in Assembly>
• <Model in Component>
• <Symbol in Component>
These search criteria can be used for searching specific symbols or models in components or components in assemblies.
To configure the search criteria '<Component in Assembly>', '<Model in
Component>' and '<Symbol in Component>' in the Component Tree:
• right-click either on upper horizontal line of the database window or on the column headers in the database window
• select the context menu command Component Search Configuration...,
• the Component Search Configuration dialog opens
• select the desired search criteria <Component in Assembly>, <Model in
Component> and <Symbol in Component> in the column Search criteria and then click on the icon :
• The search criteria <Component in Assembly>, <Model in Component> and
<Symbol in Component> appear in the Database field:
52

• After pressing OK the defined search criteria are now available in the component tree:
To configure the search criteria '<Component in Assembly>', '<Model in
Component>' and '<Symbol in Component>' in the Component Table:
• open the Component Table with View -> Database Windows -> Component Table
• right-click anywhere within the area Favorite, Search or Attributes and preview
• select the context menu command Component Table Search Configuration...
• this opens the Component Search Configuration dialog
53

• configure the desired search criteria <Component in Assembly>, <Model in
Component> or <Symbol in Component> with the arrow icon:
• After pressing OK the defined search criteria are now available in the component table:
Reference(s):
Designer-24440
Searching for Symbols and Symbols with Defined Characteristics Now Possible with
Help of New Search Criterion <Characteristic>
To search for symbols and symbols with defined characteristics, the new search criterion
<Characteristic> can be used. This search criterion is available in both the Symbol and Misc tree views.
To configure the search criterion '<Characteristic>' for the Symbol and Misc tree
views:
Note: In both cases the 'Symbol' or 'Misc' tab must be open in the database window.
54

• right-click either on upper horizontal line of the database window or on the column headers in the database window
• select the context menu command Symbol Search Configuration... or Misc Search
•
Configuration... select the search criterion <Characteristic> in the column Search criteria and click on the icon .
Note: The search criterion Characteristic> appears in the Database field:
• After pressing OK the search criterion <Characteristic> is now available in the Symbol or Misc Tree:
Reference(s):
Designer-29130
Define Templates for Database Search
Now it's possible to define templates for searching the database.
To do so, right-click in the Database Component Window header and ...
55

• select the context menu command Favorites -> Configure Favorites... and
• define the favorites for your selection list or if favorites already exist in the database, you can choose them directly from the context menu.
The following dialog is opened:
• Activate: Uses the selected favorite
• Note: To activate a favorite, it must first be saved in the database!
• New: For adding a new favorite
• Rename: For renaming favorites
• Remove: For deleting favorites
• Save: For saving changes to the database
• Cancel: Changes not saved to database
Reference(s):
Designer-18515
Search for Slots and Mounting Rails in Database Window
There are two new search fields in the Database Window for searching components. Slots and mounting rails can now be searched for here.
To configure the search criteria '<Mounting Description>' and '<Slot Description> in
the Component Table:
• open the Component Table using View -> Database Window -> Component Table
• right-click anywhere within the sections Favorite, Search or Attributes and Preview
• select the context menu command Component Table Search Configuration...
• this opens the Component Search Configuration dialog
• configure the desired search criteria <Mounting Description> and <Slot
Description> using the arrow keys
56

Reference(s):
Designer-33710
Search for Components in Database Tree using Attribute Values
A context menu is now available in the database structure, which makes it possible to search for specific components using attribute values.
To search for components using attribute values:
• right-click on the component database window header in the search field area and select the context menu command "Search..."
• enter the search criterion for the attribute value using a wildcard, e.g. *X20*
• press OK!
• This filters the database and displays all components, which have the selected attribute
• value.
To reset the filter, right-click in the header once again and select the command "Reset
Search"
57

References:
Designer-28531
58

•
Minimize Degree of Detail for Displaying Sheet Contents and Previewing Sheets
Minimize Degree of Detail for Displaying Sheet Contents and Previewing Sheets
When opening very large or scaled panel and formboard sheets with numerous texts and symbols, it could take longer to load them until the entire sheet contents are displayed.
It is now possible to specify the display's degree of detail using the new check box: Minimize
details. This check box can be called up in the settings in the section Miscellaneous Options under General - Display.
If this functionality is activated, the placed text elements are displayed as rectangles for a rough sheet view. Only after a specific (system-defined) zoom factor does the text appear again in the normal view. This leads to faster loading times when opening sheets, previewing sheets or moving sheet contents.
If this functionality is switched off, the texts appear in their normal (detailed) form thereby leading to longer loading times.
The dialog appears as follows in the 'Electric Settings':
59

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

Miscellaneous Options
Minimize
details
Note:
This functionality is only valid for: o panel sheets o formboard sheets
When printing and exporting sheets, this functionality is switched off.
If this check box is activated, the placed text elements are displayed as rectangles for a crude sheet view. Only after a specific (system-defined) zoom factor does the text characters appear as normal.
61

Therefore, the loading times when opening the affected sheets, previewing or moving is shortened.
If this check box is deactivated, the text appears in the normal form:
For the COM methods prj.GetSettingValue and prj.SetSettingValue the following setting_name can be used:
DISPLAY_MINIMISE_DETAILS
This check box is user-specific in a multi-user project.
Reference(s):
Designer-30976
62

•
AutoCAD Version 2018 and 2019 Now Supported when Exporting/Importing
DXF/DWG Files
AutoCAD Version 2018 and 2019 Now Supported when Exporting/Importing
DXF/DWG Files
AutoCad version 2018 and 2019 [AC1032] now supported when exporting/importing DXF/DWG files!
The following AutoCAD versions are supported:
AutoCAD Version
R11 / R12
R13
R14
2000 / 2000i / 2002
2004 / 2005 / 2006
2007 / 2008 / 2009
2010 / 2011 / 2012
DWG Header
AC1009
AC1012
AC1014
AC1015
AC1018
AC1021
AC1024
2013 / 2014 / 2015 / 2016 / 2017 AC1027
2018 / 2019 AC1032
Reference(s):
Designer-32373
63

•
Journal Files Will No Longer Be Created in Multi-User
•
External Documents Can Now Also Be Deleted when Closed in Multi-User
Journal Files Will No Longer Be Created in Multi-User
Previously when a conflict occurred, a journal file was created automatically even though the setting Enabled was set on 0.
In the future journal files will no longer be created in the XML configuration file configure.xml
:
<Journal> <Path>C:\Program Files (x86)\Zuken\E3.series_2017-
18.00\MultiUser\export\</Path> <Enabled>0</Enabled> </Journal>
Reference(s):
Designer-30065
External Documents Can Now Also Be Deleted when Closed in Multi-User
Previously, external documents could be deleted when opened.
With the new functionality external documents can also be deleted when closed.
Note: The document cannot be deleted if opened by another user in multi-user. In this case, a corresponding message appears.
Reference(s):
Designer-30485
64

•
Fill Degree Can Now Be Displayed for Cable Duct Inlets/Outlets
Fill Degree Can Now Be Displayed for Cable Duct Inlets/Outlets
Previously, the fill degree could not be displayed for cable duct inlets/outlets.
This is now possible. Since the arrow head cannot display the fill degree, the cable duct inlet symbol has been redefined.
Previously:
The lengths for the cable duct inlets/outlets were defined as follows:
New:
The lengths for the cable duct inlets/outlets are now defined as follows:
Example:
65

The fill degree is now displayed for a cable duct inlet/outlet:
Note: The check box Display fill size (in the Settings under Panel - Cable Duct Symbol -
Display in the section Fill Size) is activated.
Reference(s):
Designer-30246
66

•
Now Possible to Control whether Existing Assemblies Can Be Added to or New
Assemblies Shall Be Created when Importing
•
Example 1 - (Project with assembly | Clipboard with device)
•
Example 2 - (Project with device | Clipboard with assembly)
Now Possible to Control whether Existing Assemblies Can Be Added to or New
Assemblies Shall Be Created when Importing
In E 3 .
series the functionality for merging non-colliding devices and assemblies has been enhanced. This will enable the user to control in the future whether devices with the same device designation (like in the project) can be merged in the clipboard. Merging
(copying/importing) may also take place with defined rules without using the clipboard.
To do so, there is the new check box Add to existing assemblies / create new assemblies in the section Additional Merge Options in the Settings under Placement - Import -
Device.
The dialog appears as follows in the 'Electric Settings':
67

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

Additional Merge Options
Add to existing assemblies / create new
assemblies
Note:
• This check box can only be changed if the check box Use existing
assemblies in the section Merge Device Options is activated.
• This functionality doesn't work with: o Nested assemblies o Assemblies with component description o When executing the command "Merge as View" (for clipboards)
69

o When executing the command "Merge as Original" (for clipboards) o Devices with variant instances in assemblies
• This setting can be changed afterward in the Import Drawing
Options dialog:
If the check box Add to existing assemblies / create new assemblies is activated, assemblies can be merged.
If this check box Add to existing assemblies / create new assemblies is deactivated, it's not possible to merge assemblies.
See examples:
• Example 1 - (Project with assembly | Clipboard with device)
• Example 2 - (Project with device | Clipboard with assembly)
For the COM methods prj.GetSettingValue and prj.SetSettingValue the following setting_name can be used: KEEP_ASSEMBLY_BELONGING
This check box is user-specific in a multi-user project.
.
Example 1 - (Project with assembly | Clipboard with device)
Starting situation:
• There is an assembly in the project with the device designation -A1. In the clipboard there is a device with the same designation -A1.
• Both elements have an identical symbol (ZUK11-60-84).
70

The check box Add to existing assemblies / create new assemblies is deactivated:
The command Merge all non-colliding cannot be executed in the clipboard. This device is correspondingly displayed with a red-colored device designation in the clipboard.
The check box Add to existing assemblies / create new assemblies is activated:
The command Merge all non-colliding can be executed in the clipboard.
After executing the command Merge all non-colliding, the device is added from the clipboard as an additional element in the project assembly.
71

Example 2 - (Project with device | Clipboard with assembly)
Starting situation:
• There is a device in the project with the device designation -A1. In the clipboard there is an assembly with the same designation -A1.
• Both elements have an identical symbol (ZUK11-60-84).
The check box Add to existing assemblies / create new assemblies is deactivated:
The command Merge all non-colliding cannot be executed in the clipboard. Assemblies with assembly elements having the same name in the clipboard are correspondingly displayed by a red-colored device designation.
The check box Add to existing assemblies / create new assemblies is activated:
The command Merge all non-colliding can now be executed in the clipboard.
72

The command Merge all non-colliding was executed in the clipboard:
Reference(s):
Designer-32168
73

•
'Select Print Areas' Dialog Has Been Enhanced for Selecting Print Areas
'Select Print Areas' Dialog Has Been Enhanced for Selecting Print Areas
The dialog Select Print Areas for selecting the print area has been enhanced. In the Select
Print Areas dialog there are now the buttons Fit Width and Fit Height for displaying the complete print areas in the preview window. Furthermore, there is the new check box Display
Drawing, which controls whether the drawing's contents shall be displayed or not.
Note: The Select Print Areas dialog can be opened with Print or Export PDF.
To open the Select Print Areas dialog from the Print dialog:
• select the main menu command File -> Print...
• activate the radio button All in the section Print Range
• activate the radio button Factor: in the section Scale and the check box Split
automatically on printer pages:
74

• click on the button Select pages in the section Options
• the Select Print Areas dialog opens.
The Select Print Areas can also be opened using the PDF Export Dialog. To do so:
• select the main menu command File -> Export -> PDF...
• activate the check boxSplit by Defined Print Area in the section Pagination in the
Adobe Acrobat PDF Files dialog
• click on the button Select Pages... in the section Pagination
• the Select Print Areas dialog opens.
75

New in 'Select Print Areas' Dialog
In the Select Print Areas dialog there is the new check box Display Drawing and the new buttons Fit Width and Fit Height:
Fit Width
Clicking on this button adapts the print preview window to the maximum width of the print area:
76

Fit Height
Clicking on this button adapts the print preview window to the maximum height of the print area:
Display
Drawing
If checked, the drawing's contents are displayed.
77

If unchecked, the drawing's contents are hidden.
.
Also new in the Select Print Areas dialog:
• The individual print areas are numbered.
78

• The selected print areas are highlighted.
Reference(s):
Designer-32832
79

•
Additional Start-Up Parameter '/sheets' for Assigning Licenses with Different numbers of Sheets using License Server for the E3 Module 'SmallProject'
Additional Start-Up Parameter '/sheets' for Assigning Licenses with Different
Numbers of Sheets using License Server for the E3 Module 'SmallProject'
There is now an additional start-up parameter
/sheets
for assigning licenses with different numbers of sheets using the license server for the module E 3 .
SmallProject.
The parameter
/sheets
must be added to the start-up parameter
/sp
(for E 3 .
SmallProject) followed by the corresponding number nnn
of sheets For example:
/sp /sheets 20
).
Note:
• For this functionality to work ECADLM Version 11.14.1.1 or higher must be used!
• When specifying a sheet number, a license with the exact number of sheets must be available.
• Without a specified number of sheets any license may be used along with its number of sheets. If no sheet number is specified, the default value is used for the license (30 sheets).
Example:
1
2
3
1 x E 3 .
SmallProject license with limited number of sheets /sp /sheets 40
Sheets = 40
1 x E 3 .
SmallProject license with limited
/sp /sheets 20 number of sheets
Sheets = 20
1 x E 3 .
SmallProject license without limited number of sheets /sp
Reference(s):
Designer-32796
40 sheets available
20 sheets available
30 sheets available
80

•
Selection Process of Object Groups Has Been Simplified
Selection Process of Object Groups Has Been Simplified
The selection process for selecting object groups has been simplified in E 3 .
series. They can now be selected, deselected or moved. Furthermore, it's now also possible to select an individual object of the object group.
To do so, there are the following new functions for selecting object groups:
To select a group: o Left-click on a symbol, graphic or connection line of the group
To move a group: o Left click and hold the mouse button on a symbol, graphic or connection line of the group o Move the group to the desired position
To deselect a group: o Left-click on a symbol, graphic or connection line of an already selected group
To select an individual object of a group:
Note: This functionality doesn't work if the group has been grouped as a graphic! o Fist select the entire group by left-clicking on a symbol, graphic or connection line of the group o Next right-click on the desired group element and select the new context menu command Select individual group object
Reference(s):
Designer-14656
81

•
Adding, Deleting, Renaming and Moving Structure Nodes in the Tree View Can
Now Be Locked
o
Enhancement to JobInterface for Locking Tree Structure Nodes
Adding, Deleting, Renaming and Moving Structure Nodes in the Tree View Can Now
Be Locked
To prevent unintended changes to the project structure, the project structure can now be locked or unlocked once again in E 3 .
series.
To do so, there are the new context menu commands:
• Lock Structure
• Unlock Structure
The following actions cannot be executed if the project structure is locked:
• adding structure nodes
• deleting structure nodes
• renaming structure nodes
• moving structure nodes
To lock the project structure:
• right-click on the project name in the tree view
• select the context menu command Lock Structure
• Note: If the structure is locked, this is displayed by a lock on the project node.
To unlock the project structure:
• right-click on the project name in the tree view
• select the context menu command Unlock Structure
• Note: If the structure is unlocked, no lock appears on the project name.
Note: The project structure can also be changed indirectly, for example, by:
• changing the attribute values used for the structure
• importing a subcircuit
82

• copying and pasting
• merging a clipboard with the project
• adding devices by placing from Component Tree
If there is a change to the project structure, this change is undone. A corresponding message appears in the Output Window.
Enhancement to JobInterface for Locking Tree Structure Nodes
The following new COM commands are in the JobInterface:
• ret = job.GetProjectStructureLocking o ret The following values are possible:
 0 Project structure not locked!
 1 Project structure locked!
 -1 No project opened!
• ret = job.SetProjectStructureLocking ( lock ) o lock The following values are possible:
 0 Disables locking the project structure!
 1 Enables the project structure to be locked! o ret The following values are possible:
 0 or 1 Returns the last state before calling the function!
 -1 No project opened!
 -2 Unhandled error!
 -3 lock has to be 1 or 0!
The return value has been enhanced at following COM-command within the StructureNodeInterface:
• ret = struct.Create
• ret = struct.DeleteForced
• ret = struct.MoveTo
•
•
ret = struct.SetName
ret = struct.SetStructureNodeIds o ret -4 Project structure is locked
Reference(s):
Designer-32225
83

•
Generate and Logically Plug Appropriate Mating Connector Pin in Device Tree
o
New Pin Status Symbols
o
New Functions in Tree View
o
Keep Plug after Unplugging Pins
o
Display References with Logical Plugged Devices
o
Enhancements to COM Interface for Plugging and Unplugging Devices and
Connectors in the Tree View
o
Enhancement to DeviceInterface for Plugging and Unplugging
Devices and Connectors
o
Enhancement to DeviceInterface for Assigning Plugs to Devices
o
Enhancement to PinInterface for Plugging and Unplugging Pins
o
Enhancement to PinInterface for Determining Type of Plug
Generate and Logically Plug Appropriate Mating Connector Pin in Device Tree
It's now possible to generate and logically plug/unplug the appropriate mating connector pin for a pin in the device tree. To do so, there are the new context menu commands Plug to
Mating Connector Pin / Unplug from Mating Connector Pin. The not yet placed mating connector can be graphically placed a t a later time. Furthermore, two devices can be logically plugged together in the tree view using the new context menu command Plug Together.
With the new pin symbol status in the tree view it's possible to have an overview of the plugged connections. Moreover, the context menu commands Jump to Mating Pin in Tree and Jump to Mating Device in Tree can be used to jump from the pin to the corresponding mating connector pin in the tree view.
Additionally, the new check box function Keep plug after unplugging pins can be defined so that the already plugged connection shall be retained when unplugging pins.
New Pin Status Symbols
The following new status symbols, which display the connection status of individual pins, are in the tree view.
Symbo l:
Function:
Device Pin Symbol
Device Pin inactive (only for variants/options) and placed
Device Pin (& Backshell
Pin)
not placed
84

Device Pin (& Backshell
Pin)
placed
Device Pin (& Backshell
Pin)
can be renamed, not placed
Device Pin (& Backshell
Pin)
can be renamed, placed
Connector Housing Pin Symbol
Connected Pins Can Be Displayed in the
Info Column
It's also possible to display the connected pins for the respective plugged connection in the Info
Column.
To define the new attribute <Connected pin> in the Info Column:
• right-click in the project window device tree and select the context menu command Tree
Control Properties...
• click on the icon in the Info Column opposite Pins in the section Show these
objects in the Tree Control Properties -
Backshell Pin inactive (only for variants/options) and placed
Connector Pin Symbol
Connector Pin inactive (only for variants/options) and placed
Connector Pin not placed
Connector Pin placed
Connector Pin can be renamed, not placed
Connector Pin can be renamed, placed
.
85

General dialog:
• select <Connected Pin> in the field Available in the Info Column dialog and press the icon
Displayed:
. The information <Connected Pin> is moved to the right column
• the mating connector pin of the pin is now displayed in the Info Column:
New Functions in Tree View
The following new context menu commands and functions are now available for plugged connections in the tree view:
New context menu commands:
86

• Plug to Mating Connector Pin
• Unplug from Mating Connector Pin
• Plug Together
• Jump to Mating Pin in Tree
• Jump to Mating Device in Tree
Furthermore, it's possible to have an overview of the connected plugged connections with the new Pin Symbol Status.
Plug to Mating Connector Pin
To generate the appropriate mating connector pin automatically along with the logical connection for a pin in the tree view:
Note: The pin may not yet be plugged.
• right-click on one or more not plugged pin(s) in the device tree or
• right-click on the desired device with at least one unconnected pin in the device tree select the context menu command Plug to Mating Connector Pin:
• the appropriate mating connector pin is automatically generated and logically connected:
87

Unplug from Mating Connector Pin
To unplug the logical connection between a pin and the corresponding mating connector pin in the tree view:
• right-click on one or more logical connected pin(s) in the device tree or right-click on the desired device with at least one plugged pin in the device tree
• select the context menu command Unplug from Mating Connector Pin:
• logical connection on pin and mating pin disconnected:
Plug Together
Note: This command is only displayed when selecting two not yet connected devices.
To plug two not yet connected devices together in the tree view:
• select the two not yet connected devices in the device tree by pressing the left mouse button and the Ctrl key
88

• right-click on one of the selected devices and select the context menu command Plug
Together:
Jump to Mating Pin in Tree
To jump to the mating pin in the tree:
• right-click on a logical connected pin in the device tree
• select the context menu command Jump and then Jump to Mating Pin in Tree:
Jump to Mating Device in Tree
To jump to the mating device in the tree:
• right-click on a device with at least one logically connected pin in the device tree
89

• select the context menu command Jump and then Jump to Mating Device in Tree an:
Keep Plug after Unplugging Pins
It's now possible to control whether the logical plugged connection shall remain after unplugging pins.
To do so, there is the new check box 'Keep plug after unplugging pins' in the new section
Pins in the settings under Connection:
The dialog appears as follows in the 'Electric Settings':
90

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

Pins
Keep plug after unplugging
pins
If this check box is activated, the logical plugged connection remains when unplugging the pins.
If this check box is deactivated, the logical plugged connection is disconnected when graphically unplugging the pins.
Example:
92

The check box Keep plug after unplugging pins is activated:
When graphically unplugging, the logical plugged connection is disconnected.
The check box Keep plug after unplugging pins is deactivated:
When graphically unplugging, the logical plugged connection remains.
Note:
93

• This functionality is not available in E 3 .
logic.
• Alternatively to the check box Keep plug after unplugging pins, this function can also be activated in the settings using the new icon
Keep plug in the Connect toolbar.
For the COM methods prj.GetSettingValue and prj.SetSettingValue the following setting_name can be used:
KEEP_PLUG_AFTER_UNPLUGGING_PINS
This check box is project-specific in a multi-user project.
.
Display References with Logical Plugged Devices
It's now possible to control whether references with logical plugged devices shall be displayed in the schematic.
To do so, there is the new check box 'Display reference with logical plugged devices in the settings under Connection - Reference Format:
The dialog appears as follows in the 'Electric Settings':
94

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

Display reference with logical plugged devices
If this check box is activated, all references with logical plugged devices are displayed in the schematic:
Note: As soon as the device is graphically plugged , the reference disappears.
96

If this check box is deactivated, no references are displayed in the schematic:
For the COM methods prj.GetSettingValue and prj.SetSettingValue the following setting_name can be used:
REFERENCE_BETWEEN_PLUGGED_PINS
This check box is user-specific in a multi-user project.
.
Enhancements to COM Interface for Plugging and Unplugging Devices and
Connectors in the Tree View
•
Enhancement to DeviceInterface for Plugging and Unplugging Devices and
Connectors
•
Enhancement to DeviceInterface for Assigning Plugs to Devices
•
Enhancement to PinInterface for Plugging and Unplugging Pins
•
Enhancement to PinInterface for Determining Type of Plug
Enhancement to DeviceInterface for Plugging and Unplugging Devices and
Connectors
The following new COM command is in the DeviceInterface:
• ret = dev.PlugWithMatingPins ( deviceIds ) o deviceIds Returns a list of counterpart device ids that the device was plugged to.
If the function fails, this list is empty. o ret Returns the number of devices. If an error occurs, the following values are possible:
 -1 No ID assigned via dev.SetId(), no project open or E3 running in Viewer or Logic Mode!
 -2 No mating connector defined!
 -3 Different signals!
 -4 Device or mating device locked!
 -5 All pins already connected!
 -6 Device is an inappropriate type!
 -7 No pins found!
 -8 Trying to plug device view on connector!
 -9 If any other error!
• ret = dev.UnplugFromMatingPins ( deviceIds )
97

o deviceIds Returns a list of disconnected device ids if successful. If the function fails, this list is empty. o ret Returns the number of disconnected devices. If an error occurs, the following values are possible:
 -1 No id assigned via dev.SetId(), no project open or E3 running in Viewer or
Logic Mode!
 -2 Device not connected!
 -3 Device cannot be unplugged (e.g. it's graphically connected)!
 -4 Device or mating device locked!
 -5 No pins found (e.g. on an empty block)!
 -6 Device is an inappropriate type!
 -7 If any other error!
Enhancement to DeviceInterface for Assigning Plugs to Devices
The following new COM command is in the DeviceInterface:
• ret = dev.PlugWith ( id ) o id plugs the device reference by id with the current device id. o ret Function returns 0 if successful, otherwise the following errors are possible:
 -1 No project open or no current device id has been set using SetId()!
 -2 Invalid id parameter value!
 -3 At least one of two devices locked!
 -4 No pins were found on at least 1 of the 2 devices!
 -5 At least one of the two devices is unsuitable for a plug!
 -6 Signals assigned to devices are incompatible with one another!
 -7 Plug not allowed!
 -8 Conductor on at least one of the two devices is already connected!
 -9 No pins available on at least one of the two devices for plugging!
 -10 Another error has occurred.
 -11 ID refers to an inactive device!
Enhancement to PinInterface for Plugging and Unplugging Pins
The following new COM commands are in the PinInterface:
• ret = pin.PlugWithMatingPin o ret Returns the id of the created pin if successful, otherwise:
 -1 No id assigned via pin.SetId(), no project open or E3 running in Viewer or
Logic Mode!
 -2 No mating connector defined!
 -3 Signals of all pins and mating pins are different!
 -4 Pins on a dynamic symbol!
 -5 Device or mating device locked!
 -6 Pin already connected!
 -7 Device is an inappropriate type!
 -8 Trying to plug a device view on a connector!
 -9 Any other error!
• ret = pin.UnplugFromMatingPin ( pinids )
98

o pinids Returns a list of disconnected pin ids if successful. If the function fails this list will be empty. o ret Returns the number of disconnected pin ids. In case of an error following values are possible:
 -1 No id assigned via dev.SetId(), no project open or E3 running in Viewer or
Logic Mode!
 -2 Pin not connected!
 -3 Device cannot be unplugged (e.g. it's graphically connected)!
 -4 Device or mating device locked!
 -5 Device is an inappropriate type!
 -6 Any other error!
 -7 Returned if partially successful (some but not all pins disconnected).
Enhancement to PinInterface for Determining Type of Plug
The following new COM command is in the PinInterface:
• ret = pin.GetPlugStatus o ret The following values are possible:
 -1 No ID assigned, no project open or E3 running in Logic Mode!
 0 Pin not plugged!
 1 Pin logically plugged!
 2 Pin graphically plugged!
Reference(s):
Designer-32367
99

•
Exchange Components in Same Order when Exchanging Assemblies with Same
Component Type Structure
Exchange Components in Same Order when Exchanging Assemblies with Same
Component Type Structure
When exchanging assemblies with the same component type structure in E 3 .
series, it's now possible to specify how the components can be exchanged. The following possibilities are available for exchanging the assemblies:
• Prefer component code (previous functionality)
• Prefer order of devices in assembly (new functionality)
To do so, there are the radio buttons 'Prefer component code' and 'Prefer order of
devices in assembly' in the new section Assembly devices in the settings under
Placement - Change Component:
The dialog appears as follows in the 'Electric Settings':
100

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

Assembly devices
Prefer component code
/ Prefer order of devices in assembly
If the radio button Prefer component code is activated, the component code is preferred when exchanging assemblies with the same component type structure. This means it checks whether the new assembly is available in the database.
All assembly elements, which are not found, are deleted and replaced by assembly elements of the new assembly. (This corresponds with the defined rules, analogous to renaming routed disconnected/swapped conductors/wires.)
If the radio button Prefer order of devices in assembly is activated, the device order in the assembly is preferred when exchanging assemblies with
102

the same component type structure. This means the exchange may only take place for the same component type structure (e.g. a 'connector' may only be exchanged with a 'connector').
A component exchange may only take place if the component code of the assembly is the same. Otherwise, a corresponding warning appears.
Note: o This functionality is only for exchanging a component, not for updating a project. o The following is valid for a different number of devices: o If the new assembly has more devices than the old assembly o or the new assembly has fewer devices than the old assembly, all devices corresponding with the settings are used. Any remaining devices are deleted.
For the COM methods prj.GetSettingValue and prj.SetSettingValue the following setting_name can be used:
ASSIGN_ASSEMBLY_DEVICE_MODE
• The return value is 1 for Prefer component code.
• The return value is 2 for Prefer order of devices in assembly.
This check box is project-specific in a multi-user project.
.
Reference(s):
Designer-32279
103

•
Touch Gestures Optimized for Touch Screens and Touch Pads in E3
Touch Gestures Optimized for Touch Screens and Touch Pads in E3
In E 3 .
series the following touch gestures are now supported for touch screens and touch pads:
Standard Touch Gestures
Sheets, Tree Displays, Tables
Command
Open context menu
Touch and hold
Horizontal scrolling
Scroll with two-finger gesture
Vertical scrolling
Scroll with two-finger gesture
Toolbars, Menu Lists, Selection Fields
Open context menu
Touch and hold
Zoom on Sheet
Zoom in
By expanding two fingers
104

Reference(s):
Designer-24848
Zoom out
By pinching two fingers together
105

•
Search for Variants/Options within a Project
Search for Variants/Options within a Project
In E 3 .
series it's now possible to search for variants, options, harness derivatives and aliases within a project. To do so, there is the new dialog Search And Highlight Variants/Options .
After defining the search criteria and executing the search, the search results are displayed in the Results Window. From the Results Window jump to the corresponding object by doubleclicking.
Note: It's not possible to search for Packages, Configurations and Harness Families.
To search for the desired variants/options within a project:
• right-click in the variant tree view o on the project name
Note: All variants/objects are included in the search. or o on the desired variant(s)/option(s) (multi-select also possible)
Note: All selected variants/options are included in the search.
• select the context menu command Search Objects...
• this opens the Search And Highlight Variants/Options dialog:
106

Objects
All Objects Note: Clicking on the check box All Objects selects or deselects all object types!
The following object types can be searched:
 Device / Cable
 Field
 Conductor/Wire
 Sheet
 Symbol
 Graphic
 Connection
 Text
 Component Code
 Attribute
107

Search Options
Device designation:
The drop-down list displays all existing devices/cables with a device designation in the project.
Higher level assignment:
The drop-down list displays all existing devices/cables with a higher level assignment in the project.
Location: The drop-down list displays all existing devices/cables with a location in the project.
Filter expression:
The desired filter expression can be entered manually or selected from the drop-down list.
Note:
• It's possible to use wild cards. The character '?' (for an individual character) and '*' (for several characters) are used as wild cards for the search. The wild card character '!' (NOT conjunction) is not permitted for the search.
• It can search for AND and OR conjunctions: o Special case 'AND conjunction'
Example: Variant A & Variant B
Note: Both variants (A and B) must be available so that the search is successful. o Special case 'OR conjunction'
Example: Variant A | Variant B
Note: One of the two variants (A or B) must be available so that the search is successful. o Special case nesting ()
Example: (Option 1 | =Option 2) & Option 3
Note: Either Option 1 or 2 annd Option 3 must be available so that the search is successful.
Ignore inactive objects
If this check box is activated, only the currently active variant/option is searched.
If deactivated, inactive variants/options are searched.
108

Retain search and highlight options
If checked, the settings within the section Highlight Options are saved.
If E3 is closed, the search settings are retained.
Highlight
Options
The objects found are graphically highlighted, in case they are displayed.
Note: These options can also be changed in the settings under Settings
-> General -> Highlight and vice-versa.
Color:
Width:
Reset
Defines the color for the marking!
If 'Automatic' is selected, the color defined in the dialog field color is used.
Defines the line width for the marking!
The existing markings are reset. This function is carried out immediately after executing the command.
The results are displayed in the Results Window if successful:
Note: Double-click to jump to the corresponding location in the tree view/workspace.
Reference(s):
Designer-22141
109

North America
Zuken USA Inc.
Westford, MA 01886, USA
Tel: +1 978 692 4900
Japan
Zuken (World Wide Head Office)
Yokohama, Kanagawa 224-8585, Japan
Tel: +81 45 942 1511
China
CIM-TEAM Software Technology Co., Ltd.
Changning District, Shanghai, China,
200336
Tel: +86-21-52280180
Korea
Zuken Korea Inc.
Seoul 135-283, Korea
Tel: +82 2 5648031
Singapore
Zuken Singapore Pte Ltd.
#22-05 Gateway East, Singapore 189721
Tel: +65 6392 5855
Taiwan
Zuken Taiwan Inc.
Taipei 110, Taiwan
Tel: +886 2 7718 1116 www.zuken.com/e3
All trademarks mentioned are the property of their respective owners, Copyright © Zuken E3 GmbH
Germany
Zuken GmbH (European HQ)
D-85399 Hallbergmoos, Germany
Tel: +49 89 7104059 00
Zuken E3 GmbH
D-89079 Ulm, Germany
Tel: +49 7305 9309 0
Zuken E3 GmbH
D-30659 Hannover, Germany
Tel: +49 511 8595 9489
Switzerland
Zuken E3 GmbH
CH-5506 Mägenwil, Switzerland
Tel: +41 56 437 08 90
United Kingdom
Zuken UK Ltd.
Bristol, BS32 4RF, UK
Tel: +44 1454 207 801
France
Zuken S.A.
#91974 Les Ulis Cédex, France
Tel: +33 1 69 29 48 00
Italy
Zuken S.r.l.
20090 Milanofiori Assago, Milan, Italy
Tel: +39 02 575 921
Netherlands
Zuken GmbH
NL-6075 HA Herkenbosch, The Netherlands
Tel: +31 475 520 998