Electrical Wire Routing
Electrical Wire Routing
Overview
Conventions
What's New?
Getting Started
Accessing the Workbench
Creating the Bundle
Selecting Systems with External Data
Routing Wires from External Data
User Tasks
Starting with Electrical Wire Routing
Creating the Session
Creating an Electrical Bundle
Routing
Working with External Data
Selecting Systems
Automatically Routing Wires and Wire Groups
Automatically Routing Equipotentials
Computing Bundle Segment Diameter
Working with Electrical Functional Definition
Selecting the Signal
Manually Creating Wires
Automatically Routing Wires
Modifying a Wire Route
Deleting a Wire
Working with Signal Routes
Reconciling Objects
Creating a Signal Route
Deleting a Signal Route
Working with Wire Connections
Manually Creating a Wire Connection
Moving a Wire Connection
Deleting a Wire Connection
Merging Wire Connections
Splitting a Wire Connection
Accessing Data From Catalog Using Electrical Library
Getting Wire References
Resolving Internal Splices
Exporting Wires and Wire Groups
Managing the Wire Extremities
Page 1
Version 5 Release 15
Page 2
Version 5 Release 15
Page 3
Overview
Welcome to the Electrical Wire Routing User's Guide!
This guide is intended for users who need to become quickly familiar with the product.
This overview provides the following information:
As a scalable product, Electrical Wire Routing can be used in cooperation with other current or future
companion products such as Electrical Library, Electrical Harness Installation, Electrical Harness
Flattening and Electrical System Functional Definition.
Version 5 Release 15
Page 4
Before reading this guide, you should be familiar with basic Version 5 concepts such as document
windows, standard and view toolbars. Therefore, we recommend that you read the Infrastructure
User's Guide that describes generic capabilities common to all Version 5 products. It also describes
the general layout of V5 and the interoperability between workbenches.
You may also like to read the following complementary product guides, for which the appropriate
license is required:
Assembly Design
V4 Integration
Version 5 Release 15
Page 5
Conventions
Certain conventions are used in CATIA, ENOVIA & DELMIA documentation to help you recognize and
understand important concepts and specifications.
Graphic Conventions
The three categories of graphic conventions used are as follows:
Identifies...
estimated time to accomplish a task
a target of a task
the prerequisites
the start of the scenario
a tip
a warning
information
basic concepts
methodology
reference information
information regarding settings, customization, etc.
the end of a task
Version 5 Release 15
Page 6
Version 5 Release 15
Page 7
Methodology
Frequently Asked Questions
Glossary
Index
Text Conventions
The following text conventions are used:
The titles of CATIA, ENOVIA and DELMIA documents appear in this manner throughout the text.
Double-click
Shift-click
Ctrl-click
Drag
Drag
Move
Version 5 Release 15
Page 8
Version 5 Release 15
Page 9
What's New?
This table identifies what new or improved capabilities have been documented in Version 5 Release
15 of the Electrical Wire Routing User's Guide.
Enhanced Functionalities
Performance-related enhancements
Improved performance of bundle segment diameter update: bundle segments are no longer
updated on a continuous basis when routing wires, modifying wire attributes, deleting wires
or modifying wire routes; a list of bundle segments needing updating is now kept and bundle
segments updated together
Routing wire groups
You can now import XML files containing wire group specifications and route wire groups
through an electrical bundle. Any groups referenced in a catalog are instantiated from the
catalog.
Exporting wires
Wire group specifications are now exported alongside wires
Computing bundle segment diameter
Wire groups are integrated into the calculation of bundle segment diameter
Describing the iXF electrical schema
Describes wire group behavior and link, with sample
Customizing Settings
Bundle segment update
A new option lets you disable bundle segment diameter and bend radius update after wire
routing
Version 5 Release 15
Page 10
Getting Started
Before getting into the detailed instructions for using Electrical Wire Routing Version 5, the
following tutorial provides a step-by-step scenario demonstrating how to use key
functionalities.
Before starting this scenario, you should be familiar with the basic commands common to all
workbenches. These are described in the Infrastructure User's Guide.
The main tasks proposed in this section are:
Accessing the Workbench
Creating the Bundle
Selecting Systems with External Data
Routing Wires from External Data
Version 5 Release 15
Page 11
Version 5 Release 15
Page 12
Version 5 Release 15
Page 13
Since the option is set up to enable the external systems interfacing, an additional command
is available in the Electrical Wire Routing workbench.
You are required to identify the path of the:
a. Use
to locate the iXF systems repository.
For this example, the path is: .../online/cfysa_C2/samples/ElectricalIntegration
to locate the catalog path.
b. Use
For this example, the path is:
.../online/cfysa_C2/samples/ElectricalIntegration/ElecIntegration.catalog
Page 14
Version 5 Release 15
The System Selection dialog box displays with the XML files available:
Version 5 Release 15
2. The Wire Routing dialog box opens with connectivity and attribute information:
Page 15
Version 5 Release 15
Page 16
Place the mouse pointer over a wire in the specification tree to highlight in the geometry the bundle segments containing the
selected wire.
Version 5 Release 15
User Tasks
The User Tasks section explains and illustrates how to create various kinds of features.
The table below lists the information you will find.
Starting with Electrical Wire Routing
Creating the Session
Creating an Electrical Bundle
Routing
Working with Wire Connections
Accessing Data From Catalog Using Electrical Library
Exporting Wires and Wire Groups
Managing the Wire Extremities
Simulating the Routing
Managing Pathway/Signal Compatibility with Knowledgeware during Automatic Routing
Filtering Wires Based on External Configuration System
Editing Electrical Properties
Viewing Related Objects
Electrical and Knowledge
Electrical Integration Scenarios
Page 17
Version 5 Release 15
Page 18
You can add the Electrical Wire Routing workbench to your Favorites, using the Tools -> Customize
item. For more information, refer to CATIA V5 - Infrastructure User's Guide.
Version 5 Release 15
Page 19
Version 5 Release 15
Page 20
Version 5 Release 15
Page 21
Version 5 Release 15
Page 22
Routing
To complete the electrical process from end to end, CATIA Electrical products can import
electrical specifications from various data repositories. It is possible to manage links to map
electrical devices positioned in 3D to any format of electrical specifications (textual, list, 2D
schematics). This can be done at various steps of the process (from functional or logical
information) to insure the reliability and integrity of the 3D implementation of your electrical
systems. In Electrical Wire Routing, the connectivity information can also be imported to
route the wires, equipotentials or signals after the component placement in the 3D geometry.
You can either use the import from external data mechanism or the integration with Electrical
System Functional Definition.
Working with External Data
Working with Electrical Functional Definition
Version 5 Release 15
Page 23
Page 24
Version 5 Release 15
Selecting Systems
Since the option is set up to enable the external systems interfacing, an additional command
is available in the Electrical Library and Electrical Wire Routing workbenches.
This task explains how to select the system prior to routing.
Once a system is selected, the list of devices is loaded and ready to use.
1. Open the document.
The System Selection dialog box displays with the XML files available:
4. Click OK to validate.
The component list is filled up with this data and available for routing.
Version 5 Release 15
Page 25
In electrical mapping:
icon.
Note: Each wire group in the illustration contains one wire (indented to the right
under the group).
For the wires and wire groups available in the list, you get the following information:
Name
Identifier
Diameter
Bend radius
Version 5 Release 15
Page 26
Routing options let you choose whether or not to use knowledge rules.
2. Select one or more wires and/or wire groups and click the right arrow.
The selected wires and wire groups shift to the right column: they will be routed.
3. Click Route.
The Automatic Wire Routing Report is displayed.
If the wire or wire group is referenced in the catalog, the report indicates that the
origin is From catalog.
If the wire or wire group is not referenced in the catalog, the report indicates that
the origin is New.
Note that the specification tree icons also show that the first wire group is resolved;
the other wire group and all wires are new.
4. Close the report window.
Version 5 Release 15
Page 27
Selecting an individual wire in a wire group highlights the route of this wire.
To know more about wire routing from external data, refer to Considering External Data Routing
in Greater Depth.
Page 28
Version 5 Release 15
command
command is available.
This task explains how to route equipotentials from an external list into an electrical bundle.
The document must contain at least:
A system.
For the equipotentials available in the list, you get the following information:
The name
The identifier
The diameter
The subtype
Version 5 Release 15
The routing options allow you to use or not the knowledge rule.
4. Select one or more equipotentials and click the right arrow.
The selected equipotentials shift to the right column: they will be routed.
5. Click Route.
The Automatic Equipotential Routing Report is displayed:
Page 29
Version 5 Release 15
Page 30
Version 5 Release 15
Page 31
Note: If you change the diameter of individual wires, this will not affect the diameter of the
wire group and bundle segment.
If all wires in the group are routed together through the bundle segment (BNS 1 in the
illustration below), the bundle segment diameter is based on the wire group.
If wires in a wire group are routed separately through bundle segments (BNS 2 and 3 in
the illustration below), the bundle segment diameter is based on individual wires.
The formula used depends on the number of wire groups and/or wires in the bundle segment.
Version 5 Release 15
After:
The formula used depends on the number of wires in the bundle segment.
Page 32
Page 33
Version 5 Release 15
Formula Used
Number of Wires and/or Wire Groups
no change
2 or 3
2 * Max
4 and above
where:
A typical example:
BNS1
BNS2
2 * diameter of the
largest wire
BNS3
Wire diameter
Version 5 Release 15
Page 34
Deleting a wire
Version 5 Release 15
Page 35
When you release the mouse button, the signal is selected (Signal-A1.C1.B2.C2).
Version 5 Release 15
Page 36
Note that the Rank allows you to choose the selection order during the automatic
routing, taking into account possible Priority orders.
In our example, Signal-A1.C1.B2.C2 will be routed first, then the other signals
according to their ranks.
For more information, please refer to Creating Signals in CATIA - Electrical System
Functional Definition user's guide (step Attributes).
3. Click OK to validate.
You have created the bundle and set up the context.
The Signal Selection dialog box looks like this:
Note that the wire connections and signal extremities are shown in the geometry when one
signal only is selected.
When working in multi-selection, switch the list box to the desired signal to display the wire
connections.
Version 5 Release 15
Electrical wires are created into an electrical bundle that realizes a functional signal.
In this section, you will work with bundles created using CATIA V5.
The next section concerns the space reservation network created within CATIA - Systems Space Reservation.
This command is deactivated when working with external data.
1. Select the Signal-A1.B1.C1 in the Signal list box.
Page 37
Version 5 Release 15
Page 38
After:
N=0
no change
N=1
wire diameter
N = 2 or 3
2 * Max
Version 5 Release 15
Page 39
When the wires are created, the specification tree looks like this:
Wires are always created in the correct bundle: using the signal definition to get the functional extremities, then the
physical extremities, the geometrical bundle may be deduced. Since the electrical bundle has been defined through its
links to the geometrical bundle(s), it's now possible to create the wires in the correct electrical bundle.
Wire extremities are automatically connected to the electrical terminations if it corresponds to the signal extremity.
Wire extremities are automatically connected to the wire connection if one exists as an extremity in the signal.
However, when a signal extremity is an item of equipment with mating connectors, the connection is done on the mating
connectors. See the example using the automating routing.
You can still create wires in a bundle network created with CATIA-ELW Electrical Wire Bundle Installation Version 4.
Version 5 Release 15
Page 40
Route several signals at a time in compliance with a priority and a rank order
Manage separation code for compatibility between signal and bundle segment with a compatibility table and
CATIA knowledgeware
Position automatically the connections at the wire forks.
1. Set up the routing context with two signals:
Note that the Rank allows you to choose the selection order during the automatic routing, taking into
account possible Priority orders. In our example, Signal-A1.C1.B2.C2 will be routed first, then the other
signals according to their ranks.
For more information, please refer to Creating Signals in the CATIA - Electrical System Functional Definition
User's Guide (step Attributes).
2. Select the Automatic Wire Routing icon
After computation, the result looks like this:
Version 5 Release 15
The shortest route has been found and the connections created.
Page 41
Page 42
Version 5 Release 15
Note: The connection created on Signal-A1.C1.B2.C2 is not displayed in multi-signal mode. Switch to
Signal-A1.C1.B2.C2 to view it.
However, when a signal extremity is an item of equipment with mating connectors, the connection is done on the
mating connectors:
1. Open the Electrical-Assembly.CATProduct.
The Wire1 is connected on the cavity Number03 of the connector Single-Connector referenced in the
functional definition (Connector-AX11)
Page 43
Version 5 Release 15
No wire is connected on this side, but Wire3 is connected on the mating connector belonging to the bundle
segment network, on the cavity Number01 corresponding to the functional definition (MatingConnector.2 corresponding with the functional Connector-AX2)
You can still create wires automatically in a bundle network created with CATIA-ELW Electrical Wire Bundle
Installation Version 4.
Version 5 Release 15
Page 44
Version 5 Release 15
Page 45
4. Select the segments you want to remove from the selection, then the segments to
define the new route.
5. Click OK to validate.
Version 5 Release 15
Page 46
You can also modify wires in a bundle network created with CATIA-ELW Electrical Wire Bundle
Installation Version 4.
Version 5 Release 15
Page 47
Deleting a Wire
This task shows you how to delete a wire.
This command works similarly with external or functional data.
1. Select the wire in the specification tree: Signal-A1.C1.B2.C2Wire1
2. Press the Delete key or right-click and select Delete from the contextual menu.
Version 5 Release 15
Page 48
Version 5 Release 15
Page 49
Reconciling Objects
This task prepares the signal route creation on pathways.
In this section, you will work on electrical signals to be routed in a space reservation network (pathways) created within CATIA
Systems Space Reservation Version 5.
You will first reconcile the functional with the physical objects then create the signal route.
Two cases are available:
Version 5 Release 15
Page 50
An alternative is to right-click the functional equipment in the specification tree and select Map With Reservation from the
contextual menu.
Version 5 Release 15
Functional equipment which is not reconciled with a physical connector is shown like this:
After reconciliation, it becomes:
Use the Related Objects viewer to check if the functional equipment is reconciled.
Page 51
Version 5 Release 15
Page 52
Route several signals at a time in compliance with a priority and a rank order
Manage separation code for compatibility between signal and pathway with a compatibility
table and CATIA knowledgeware
Position automatically the connections at the wire forks.
Version 5 Release 15
Page 53
Managing the pathway-signal compatibility through the CATIA knowledgeware optimizes the
automatic routing action.
Version 5 Release 15
Page 54
Version 5 Release 15
Page 55
Version 5 Release 15
Page 56
Version 5 Release 15
Page 57
Version 5 Release 15
4. Click OK to validate.
The connection has been moved to the segments' other extremity and the wires have been
resized.
Page 58
Version 5 Release 15
Page 59
This functionality is also available on bundle network created with CATIA-ELW Electrical Wire Bundle
Installation Version 4.
Version 5 Release 15
Page 60
Version 5 Release 15
Page 61
This functionality is also available on bundle networks created with CATIA-ELW Electrical Wire
Bundle Installation Version 4.
Version 5 Release 15
Page 62
Version 5 Release 15
4. Click OK to validate.
Page 63
Version 5 Release 15
Page 64
Version 5 Release 15
Page 65
Link to First Connection: when at least one wire is selected in the list, this
command becomes available. Clicking connects the wire.
Link to Second Connection: when at least one wire is selected in the list, this
command becomes available. Clicking connects the wire.
Unlink the Wire: clicking this command breaks the link. In the list the wire is
linked to Nothing.
Clear Selection: clicking this command clears the selection of wire(s) in the list.
3. Select the wires you want to link to the same connection and select the corresponding
command.
The result looks like this:
Version 5 Release 15
Page 66
4. Click OK to validate.
The connection has been split and renamed as Wire Connection2Sp1 and Wire
Connection2Sp2.
Version 5 Release 15
Page 67
Version 5 Release 15
Page 68
Version 5 Release 15
Page 69
Wires
Equipments
Connectors
Shells
etc.
This task shows you how to get a wire reference from a catalog.
Note that you can also apply the wire definition onto a functional signal.
Open the StartupSession.CATProduct document for example, and create some wires.
The specification tree looks like this:
Version 5 Release 15
Page 70
5. Drag and drop the icon onto the Wire1 in the specification tree.
The wire is updated and renamed with the catalog wire reference:
the wire is replaced by the reference from the catalog and gets its name, color,
diameter, etc.
the wire retains its contextual properties as length, link to the functional signal,
etc.
Version 5 Release 15
6.
Page 71
When you are satisfied with the result, Close the Catalog Browser.
Version 5 Release 15
Page 72
4. When you are satisfied with the result, Close the Catalog Browser.
The reference wire attributes are listed in a csv file. This file lets you define a mapping between
chapter keywords and the attributes of the wire component type. The default column separator
used by EWR for csv files is the semi-colon ";".
For more information, refer to CATIA - Electrical Library User's Guide
Version 5 Release 15
Page 73
5.
Version 5 Release 15
Page 74
When you are satisfied with the result, Close the Catalog Browser.
A signal: all the wires which make up this signal will be connected through the internal
splice.
An electrical bundle: all the wire connections of the bundle will be replaced.
The wire connection container: all the wire connections of the container will be replaced.
Version 5 Release 15
Page 75
Note that you can choose between html (default format), csv and xml file types.
4. Enter the name of the file.
5. Click OK to validate.
An .html file is created.
At the same time and in the same location the Electrical.css is generated if it doesn't already exist. It is a style
sheet that you can customize. Using the default one, the html file looks like this:
Version 5 Release 15
Page 76
The wire and wire groups list displays the characteristics of any wire groups as well as each wire, its associated
signal, as well as the pin, connector or device connected to it. It is used to build the harness.
The device list (BOM) displays all the elements connected to the extremities of each wire. They are linked to the
wire list.
Example of list containing wire groups:
.dev {display:none}
#Elec_Ref_Des {font-size:smaller}
#Elec_Sub_Type {display:none}
#Contact_PartNumber_From {display:none}
Version 5 Release 15
#Contact_PartNumber_To {display:none}
#Elec_Sep_Code {font-size:smaller}
#Elec_Length {color:yellow}
The html format is only available for CATIA V5 data, that is to say electrical bundle created with CATIA V5.
This format does not use css file and cannot be customized.
However, this format is subject to modification and for the time being the data continuity is not guaranteed.
Page 77
Version 5 Release 15
Page 78
The Wire Extremity Management dialog box opens, displaying the following information:
The list of wires connected to each electrical termination (Termination) of the selected
connector,
In the case of a mating connector, the list of wires respectively connected to each termination of
the mating connector.
Version 5 Release 15
Page 79
In case of the selection of a mating connector, the dialog box looks like this:
The correspondence between the cavities or terminations on each side of the mating connector
is done on the IdNumber.
Version 5 Release 15
Page 80
Affect
Deaffect
Reaffect
5. Select Reaffect.
6. Select the wire in the upper frame: Wire6.1
7. Select the termination/cavity on which you want to connect the wire.
The connection is modified.
Note that the lower frame is disabled.
Version 5 Release 15
8. Select Deaffect.
9. Select the wire in the upper frame: Wire6.1
The wire is "disconnected" and moved to the lower frame.
Note that the lower frame is disabled.
Page 81
Version 5 Release 15
Page 82
All the wires in the lower frame are assigned to empty cavities of the connector
in the same order.
Use Reaffect to modify the connection.
If you select a mating connector, the options let you select on which side you want the bridge wire to be
created.
The dialog box looks like this:
Version 5 Release 15
Page 83
15. To delete the bridge wire, click the Delete Bridge Wire option and select BridgeWire3 in the list.
16. When you are satisfied with your choice, click OK to validate.
Version 5 Release 15
Simulate a signal,
Page 84
Version 5 Release 15
Page 85
The Section and Separation Code fields allow you to define selection criteria.
This information is optional. The compatibility table contains the separation codes of the wires and
is customizable in the settings.
4. Select the second element: a segment or a connector.
The virtual signal may have multiple extremities.
The Compute command is enabled.
5. Click Compute to simulate the route.
The route is highlighted.
6. Click New Extremities to create a new virtual signal.
You are prompted to select other segments or connectors.
7. With these four elements selected for example, click Compute again.
The new route is highlighted.
Version 5 Release 15
Page 86
Through the options, you can choose to route all signals or some of them, and to respect or not the priority. For more
information, see Routing a Wire.
You can define additional rules in the Tools -> Options ... menu.
For more information, see the Customizing section.
These rules are used to define compatibilities between signals or between signals and arcs and to optimize the
automatic routing. For example here is a Signal-Arc rule:
1. Select one arc used by the Power signal and another signal.
2. Set its attributes to WET through Edit, Properties, Attributes.
Version 5 Release 15
Page 87
All pathways located near a connector have their separation code set to ANY, meaning that all signals are allowed to
go through them.
Version 5 Release 15
Page 88
Filtering Wires
Based on External Configuration System
The Filtering Management command is available in the Electrical Wire Routing and the Electrical
Harness Flattening workbenches.
It is dedicated to electro-mechanical designers.
The filtering command is performed from a maximum harness configuration (called 150%)
including all the wires, the bundle segments, the connectors, supports and protective coverings of
the harness.
It retrieves through CAA V5 interfaces the list of filtering criteria depending on the selected
systems, as it is the harness part number.
The user selects a criteria.
The filtering command retrieves from CAA V5 interfaces the list of valid wires for the selected
criteria.
According to the wires routed in the harness for the selected criteria and the filtering options:
Version 5 Release 15
button.
Page 89
Version 5 Release 15
Page 90
It displays:
a. the list of filtering criteria corresponding to the harness part number.
b. the filtering options:
Version 5 Release 15
5. Optional: use the Reset the 3D Mockup button to come back to the original document.
Page 91
Version 5 Release 15
Page 92
Version 5 Release 15
Page 93
electrical bundle
defined in EWR
bundle segment
defined in EHI
Depending on the component you have activated (by double-clicking: blue object) and on the object you
have selected, the properties you will edit may be the ones of the reference or of the instance.
Version 5 Release 15
Page 94
1. In the Equipment.CATProduct, if you edit the properties of the Equipment, you will display the
properties of the reference.
Type and External Reference are attributes of the reference.
2. In the RootProduct.CATProduct, if the RootProduct is active (in blue in the specification tree) and if
you select the Equipment.1 to edit the properties, you will display the properties of the instance:
The instance also has instance attributes: Reference Designator and SubType.
Version 5 Release 15
Page 95
If you modify the attributes of instance, only this instance will be modified.
On the other hand, if you modify the attributes of reference, they will be modified in all the
occurrences and in the reference document.
3. In the RootProduct.CATProduct, if the Equipment.1 is active (double-click Equipment.1) and you
select the Equipment.1 to edit the properties, you will display the properties of the reference:
Version 5 Release 15
Page 96
Notes:
Catalog Path indicates the location of the catalog containing the physical component
Version 5 Release 15
Page 97
Version 5 Release 15
Page 98
Version 5 Release 15
Page 99
Version 5 Release 15
Functional:
Wire:
Page 100
Wire:
Harness:
Harness:
Sub objects:
Sub objects:
Version 5 Release 15
hides the wires contained in the bundle segment, shows the bundle
segments and signals.
hides the children bundle segments, only shows the signals and wires.
Page 101
Version 5 Release 15
Page 102
On a complex electrical system, the 3D view allows you to limit display to a specific area thus enlightening
the information regarding this area.
Open the RelatedObjectsSession.CATProduct document.
1. Select an object: Geometrical Bundle1.1 for example.
2. Click the Related Objects icon
The Related Objects dialog box appears. The geometry area and the specification tree are reframed on
the object selected.
on the right are the children objects (Assembly meaning), connected to the Bundle Segment4.1.
They represent the contents.
Version 5 Release 15
Page 103
the Bundle Segment4.1 contains two wires and their associated signal.
Version 5 Release 15
Page 104
Version 5 Release 15
Page 105
Version 5 Release 15
Page 106
Elec_DistanceCommon
DistanceWireProduct
ListAllOuterLayerObjects
ListDirectlyCoveredObjects
ListDirectlyOuterLayerObjects
VisualMode
To be able to use these functions, you need to activate the ElectricalMeasure package.
To do so:
1. Select Tools -> Options... -> General -> Parameters and Measures and go to the Language tab.
2. Choose the ElectricalMeasure package and click the right arrow:
3. Click OK to validate.
Version 5 Release 15
Page 107
Elec_DistanceCommon
Syntax
Elec_DistanceCommon(Wire1: Wire, Wire2: Wire):Length
Returns the common length of the two wires given as input arguments.
The type of Wire1 and Wire2 is ElecWire.
Example 1
The Elec_DistanceCommon user function can be used in Knowledge Expert to find all the couples of wires in the session that have a common length
greater than a given value.
Version 5 Release 15
Page 108
Example 2
In Knowledge Advisor, it can be used to define a rule giving the common length of two specific wires sharing properties.
Version 5 Release 15
Page 109
Applying the rule displays the following message if the condition is met:
Example 3
Still in Knowledge Advisor, to verify that two wires selected in the specification tree have a common length, the following action can be defined:
Version 5 Release 15
then ran: select two wires in the specification tree and click OK to validate.
Page 110
DistanceWireProduct
Syntax
Version 5 Release 15
Page 111
Version 5 Release 15
Page 112
Example 1
The DistanceWireProduct user function can be used with the f(x) command to display the distance between a wire and a component in the session.
Version 5 Release 15
Page 113
Example 2
The DistanceWireProduct user function can be used in Knowledge Expert to find all the wires in the session that have a minimum distance to
defined components smaller than a critical value chosen by the user. The components can be defined as heat-resistant.
Properties have been added to the product:
Version 5 Release 15
Page 114
Version 5 Release 15
Page 115
Version 5 Release 15
Page 116
Example 3
The DistanceWireProduct user function can be used in Knowledge Advisor to define a rule that displays a warning message if a minimum distance
between a wire and an object is smaller than a critical value chosen by the user.
Example 4
Version 5 Release 15
Page 117
Version 5 Release 15
Page 118
Still in Knowledge Advisor, an action can be defined using the DistanceWireProduct user function, to know the distance between a wire and an
object selected in the specification tree:
Version 5 Release 15
Page 119
ListAllOuterLayerObjects
Syntax
ListAllOuterLayerObjects (ElecBundleSegmentExtremity:Feature,Offset:Real,ListOfAllCoveringProducts(Protections/Supports):out List):Boolean
Returns an ordered list of protective coverings and supports that cover the bundle segment at the point of interest.
The point of interest is defined by specifying from which end of the bundle segment and entering an offset in mm.
Example
A check (in KWE advanced language) to determine the protective coverings and supports at 150 mm from end 1 (Extremity 1) of the bundle segment
is written as follows:
Version 5 Release 15
Page 120
Version 5 Release 15
Page 121
ListDirectlyCoveredObjects
Syntax
ListDirectlyCoveredObjects((Protection/Support):Feature, ListOfCoveredProducts(BundleSegments/Protections/Supports): out List):Boolean
Returns the list of bundle segments, protective coverings and/or supports directly under the component (protective covering or support) you want to
analyze.
If the component you want to analyze is not a protective covering or a support, the list returned will be empty.
Example
Corrugated tubes B and C are linked to the bundle segment, and corrugated tube B covers tube C
A check (in KWE advanced language) to determine the list of bundle segments, protective coverings and supports under corrugated tube C is written
as follows:
Version 5 Release 15
Page 122
Version 5 Release 15
Page 123
ListDirectlyOuterLayerObjects
Syntax
ListDirectlyOuterLayerObjects ((BundleSegment/Protection/Support):Feature, ListOfCoveringProducts(Protections/Supports): out List):Boolean
Returns the list of outer layers of protective coverings and/or supports directly over the component (bundle segment, protective covering or support)
you want to analyze.
If the component you want to analyze is not a bundle segment, protective covering or a support, the list returned will be empty.
Example
Corrugated tubes B and C are linked to the bundle segment, and corrugated tube B covers tube C
A check (in KWE advanced language) to determine the list of outer layers that directly cover the bundle segment in the example is written as follows:
Version 5 Release 15
Page 124
The name of the component analyzed, in our case, the bundle segment.
Only 3 are found because corrugated tube B does not directly cover the bundle segment since it covers corrugated tube C.
Followed by the names of these components:
Version 5 Release 15
Page 125
VisualMode
Syntax
VisualMode (BundleSegment: Feature, Visualization Mode (LIGHT/FULL): String): Boolean
Description
This function is useful to minimize the size of the harness in LIGHT mode. It simplifies the visualization, the curve and the diameter only are
represented, the rib being deleted.
This function is only available for bundle segments belonging to multi-branchable documents.
Example
Version 5 Release 15
Page 126
Version 5 Release 15
Page 127
The rule is reversible: you can load a harness in LIGHT mode and reload the geometry by applying the rule with the FULL parameter:
Version 5 Release 15
Page 128
Working in LIGHT mode allows you to modify the route and route wires but the split, transfer and add branch point commands are not
supported.
To know more about these commands, refer to Electrical Harness Installation - Working with Branches, Splitting Branches and Transferring
Branches.
Page 129
Version 5 Release 15
1. Select Tools -> Options... -> General -> Parameters and Measures and go to the
Language tab.
2. Choose the Electrical package and click the right arrow:
3. Click OK to validate.
This package can be accessed via the object browser and objects, attributes and methods in
the package can be used in expert relations.
You can, for example, write a rule to report in a file all the bundle segments with a diameter
greater than a specified value.
The package contains the following objects:
BackShell
FillerPlug
SignalRoute
BundlePositionPoint
FunctionalConnector
Stud
Bundle
FunctionalEquipment
System
BundleSegment
GroundSignal
Tape
Cavity
GroupSignal
TerminalBlock
CommandSignal
InternalSplice
TerminalStrip
Page 130
Version 5 Release 15
ConnectorShell
OffSheet
Termination
Contact
PowerSignal
Termination_GeoConstraint
ContactPoint
Protection
VideoSignal
CorrugatedTube
ShieldingSignal
Wire
Equipment
SingleConnector
ExternalSplice
Signal
BackShell
Description
Describes the electrical feature of Back Shell type that you create when you select the
the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
icon in
The back shell is a physical component used to guide the bundle segment extremity to the single
insert connector, and to protect the crimping area.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_Extra_Length
Type: Double
Defines the cable extra-length to be added to take into account the wire length inside the back
shell.
Elec_Ref_Des
Type: String
Defines the back shell reference designator attribute, which is the unique identifier for the back
shell in the project.
Elec_Sub_Type
Type: String
Type: Boolean
Defines the back shell attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command.
Is True if modified.
Elec_External_Reference Type: String
Defines the back shell external reference attribute.
It is used in Electrical Harness Flattening for 2D detail graphic replacement in a drawing.
Elec_FullConnected
Type: Boolean
Page 131
Version 5 Release 15
Is True if the back shell is connected to a single insert connector and a bundle segment.
BundlePositionPoint
Description
Describes the electrical feature of Bundle Segment Position Point type.
For more information, refer to the Electrical Harness Installation User's Guide.
The Bundle Segment Position Point type defines the point along a bundle segment at which the local
slack is applied.
Inheritance path: Standard - Feature
Attributes
Elec_Slack
Type: Double
Bundle
Description
Describes the electrical feature of Bundle type that you create when you click the
Electrical Wire Routing workbench.
For more information, refer to the Electrical Wire Routing User's Guide.
icon in the
Attributes
Elec_Ref_Des
Type: String
Defines the bundle reference designator attribute, which is the unique identifier for the bundle in
the project.
Elec_Sub_Type Type: String
Defines the bundle subtype (User defined subtype).
Version 5 Release 15
Page 132
BundleSegment
Description
Describes the electrical feature of Bundle Segment type that you create when you select one of
these icons
or
in the Electrical Harness Installation workbench.
For more information, refer to the Electrical Harness Installation User's Guide.
The BundleSegment type is a segment of a geometrical bundle.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_Bend_Radius
Type: Double
Input data defining the bend radius value that corresponds to the minimum bend radius of the
bundle segment curve.
Elec_Bend_Radius_OK
Type: Boolean
Is True if the bundle segment real bend radius is greater than the Elec_Bend_Radius attribute.
Elec_BundleSegmentExtremities Type: Void
Returns the ends of the bundle segment.
Elec_Creation_Mode
Type: String
Elec_Di_Slack
Type: Double
Input data defining the percentage of distributed slack along the bundle segment.
This attribute induces the value of the Elec_Length attribute.
Elec_Diameter
Type: Double
Type: Boolean
Version 5 Release 15
Page 133
Defines the bundle segment attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Elec_FullConnected
Type: Boolean
Type: Double
Type: String
Defines the bundle reference designator attribute, which is the unique identifier for the bundle in
the project.
Elec_Segreg
Type: String
Defines the bundle segment separation code used by the routing algorithm.
Elec_Sub_Type
Type: String
Type: Double
Attribute used in the fake length context of the extracted data in EHF.
This attribute keeps the bundle segment real length, coming from the 3D data.
In this context, the Elec_Length returns the fake length.
IncludedWires
Type: CATIList
Cavity
Description
Describes the electrical feature of Cavity type that you create when you click this icon
Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
The cavity defines a reservation for a connector.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
in the
Version 5 Release 15
Page 134
Type: String
Defines a unique identifier for the cavity used to map a functional component and the
corresponding physical part.
Elec_Ref_Des
Type: String
Defines the cavity reference designator attribute, which is the unique identifier for the cavity in the
project.
Elec_Sub_Type
Type: String
CommandSignal
Description
Describes the electrical feature of Command Signal type that you create when you click this icon
in the Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
The command signal is a logical connection between two or more components. It will be realized by
a wire in physical world.
Inheritance path: Standard - Feature -> ProductPackage - Product -> Electrical - ElecSignal
Attributes
Elec_Nominal_Part_Num Type: String
Defines the nominal part number of the wire that realizes the command signal.
Elec_Recom_Wire_Type Type: String
Defines the attribute of the wire recommended to realize the signal.
Elec_Routing_Priority
Type: Double
Type: String
Version 5 Release 15
Page 135
Defines the separation code of the command signal used by the algorithm to find out the wire
route.
Elec_Signal_Section
Type: Double
Type: String
ConnectorShell
Description
Describes the electrical feature of Connector-Shell type that you create when you click the
in the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
icon
A connector shell or shell is a non-electrical part which groups one or more electrical connector
parts. It may be part of an equipment.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_Ref_Des
Type: String
Defines the connector shell reference designator attribute, which is the unique identifier for the
connector shell in the project.
Elec_Sub_Type
Type: String
Type: Boolean
Defines the connector shell attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Elec_External_Reference Type: String
Defines the connector shell external reference attribute.
It is used in Electrical Harness Flattening for 2D detail graphic replacement in a drawing.
Contact
Page 136
Version 5 Release 15
Description
Describes the electrical feature of Contact type that you create when you click the
Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
icon in the
A contact is an electrical component used within a termination and a cavity or between bundle
segments.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_Barrel_Diameter
Type: Double
Type: Boolean
Type: String
Defines the contact reference designator attribute, which is the unique identifier for the contact in
the project.
Elec_Sub_Type
Type: String
CorrugatedTube
Description
Describes the electrical feature of Corrugated Tube type that you create when you click the
icon in the Electrical Library workbench. The corrugated tube is then instantiated using the Electrical
Harness Installation workbench.
For more information, refer to the Electrical Library and Electrical Harness Installation User's Guides.
A corrugated tube is an electrical component applied onto bundle segments as a protection.
Inheritance path: Standard - Feature -> ProductPackage - Product
Version 5 Release 15
Page 137
Attributes
Elec_Bend_Radius
Type: Double
Defines the bend radius value, which corresponds to the minimum bend radius of the corrugated
tube curve.
Elec_Bend_Radius_Protection_OK Type: Boolean
Is True if the Elec_Bend_Radius attribute is smaller than the real value of bend radius of the
largest bundle segment linked to the corrugated tube.
Elec_Fmbd_Modify
Type: Boolean
Defines the single connector attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Elec_Inner_Diameter
Type: Double
Type: Double
Type: Double
Type: Double
Defines the corrugated tube linear mass, used for the flattened representation.
Elec_Ref_Des
Type: String
Defines the corrugated tube reference designator attribute, which is the unique identifier for the
corrugated tube in the project.
Elec_Ref_PartNumber
Type: String
Type: String
Type: Double
Page 138
Version 5 Release 15
Equipment
Description
Describes the electrical feature of Equipment type that you create when you click the
the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
icon in
An equipment is an electrical device with one or more associated components: connectors, shells,
contacts, filler plugs, placed in cavities. An equipment can also comprise terminations and bundle
connection points.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_External_Reference Type: String
Defines the equipment reference from an external library.
It is used in Electrical Harness Flattening for 2D detail graphic replacement in a drawing.
Elec_Fmbd_Modify
Type: Boolean
Defines the equipment attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Elec_Ref_Des
Type: String
Defines the equipment reference designator attribute, which is the unique identifier for the
equipment in the project.
Elec_Sub_Type
Type: String
ExternalSplice
Description
Page 139
Version 5 Release 15
Describes the electrical feature of External Splice type that you create when you click the
in the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
icon
An external splice is an electrical connector receiving bundle segments from different geometrical
bundles.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_External_Reference Type: String
Defines the external splice reference from an external library.
It is used in Electrical Harness Flattening for 2D detail graphic replacement in a drawing.
Elec_Fmbd_Modify
Type: Boolean
Defines the external splice attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Elec_Ref_Des
Type: String
Defines the external splice reference designator attribute, which is the unique identifier for the
external splice in the project.
Elec_Sub_Type
Type: String
Type: Boolean
Is True if all the bundle connection points and terminations of the external splice are connected.
FillerPlug
Description
Describes the electrical feature of Filler Plug type that you create when you click the
Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
A filler plug is an electrical component used to block up an unused cavity.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
icon in the
Version 5 Release 15
Elec_Ref_Des
Page 140
Type: String
Defines the filler plug reference designator attribute, which is the unique identifier for the filler plug
in the project.
Elec_Sub_Type Type: String
Defines the filler plug subtype.
ContactPoint
Description
Describes the electrical feature of Contact Point type that you create when you select the
the Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
This contact point is a functional electrical component that defines the point of contact or
attachment for an electrical signal.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_Id_Number
Type: String
Type: Integer
Defines a unique identifier for the contact point used to map a functional component and the
corresponding physical part.
Elec_Ref_Des
Type: String
Defines the contact point reference designator attribute, which is the unique identifier for the
contact point in the project.
Elec_Signal_IO
Type: String
Type: String
icon in
Version 5 Release 15
Page 141
FunctionalConnector
Description
Describes the electrical feature of Functional Connector type that you create when you click the
icon in the Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
This connector is a functional electrical component with one or more associated contact points, for
example, a power or signal transmission connector.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_External_Reference Type: String
Defines the functional connector reference to an external library.
Elec_Id_Number
Type: String
Defines a unique identifier for the functional connector used to map a functional component and the
corresponding physical part.
Elec_Nominal_Part_Num Type: String
Defines the nominal part number of the physical connector that realizes the functional connector.
Elec_Ref_Des
Type: String
Defines the functional connector reference designator attribute, which is the unique identifier for
the connector in the project.
Elec_Sub_Type
Type: String
FunctionalEquipment
Description
Version 5 Release 15
Page 142
Describes the electrical feature of Functional Equipment type that you create when you click the
icon in the Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
This equipment is a functional electrical component with one or more associated connectors, for
example a lamp or a battery.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_External_Reference Type: String
Defines the functional equipment reference to an external library.
Elec_Nominal_Part_Num Type: String
Defines the nominal part number of the physical equipment that realizes the functional equipment.
Elec_Ref_Des
Type: String
Defines the functional equipment reference designator attribute, which is the unique identifier for
the equipment in the project.
Elec_Sub_Type
Type: String
GroundSignal
Description
Describes the electrical feature of Ground Signal type that you create when you click this icon
the Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
in
The ground signal is a logical connection between two or more components. It will be realized by a
wire in physical world.
Inheritance path: Standard - Feature -> ProductPackage - Product -> Electrical - ElecSignal
Attributes
Elec_Ground_Unicity
Type: Boolean
Defines the unicity of the ground signal: True if the signal is unique.
Elec_Nominal_Part_Num Type: String
Version 5 Release 15
Page 143
Defines the nominal part number of the wire that realizes the ground signal.
Elec_Recom_Wire_Type
Type: String
Type: Double
Type: String
Defines the separation code of the ground signal used by the algorithm to find out the wire route.
Elec_Signal_Section
Type: Double
Type: String
GroupSignal
Description
Describes the electrical feature of Group Signal type that you create when you click this icon
the Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
Groups signals will be routed together, for example shielded or twisted signals.
Inheritance path: Standard - Feature -> ProductPackage - Product -> Electrical - ElecSignal
Attributes
Elec_Nominal_Part_Num Type: String
Defines the nominal part number of the wire that realizes the group signal.
Elec_Recom_Wire_Type Type: String
Defines the attribute of the wire recommended to realize the signal.
Elec_Routing_Priority
Type: Double
in
Version 5 Release 15
Elec_Sep_Code
Page 144
Type: String
Defines the separation code of the group signal used by the algorithm to find out the wire route.
Elec_Signal_Section
Type: Double
Type: Boolean
Defines the internal splice attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Elec_Sub_Type
Type: String
InternalSplice
Description
Describes the electrical feature of Internal Splice type that you create when you click the
in the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
icon
An internal splice is a type of connector used to connect two or more wires belonging to the same
bundle.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_External_Reference Type: String
Defines the internal splice reference to an external library.
It is used in Electrical Harness Flattening for 2D detail graphic replacement in a drawing.
Elec_Mass
Type: Double
Type: Double
Defines the distance to the bundle segment extremity selected to place the internal splice.
Elec_Ref_Des
Type: String
Version 5 Release 15
Page 145
Defines the internal splice reference designator attribute, which is the unique identifier for the
internal splice in the project.
Elec_Sub_Type
Type: String
OffSheet
Description
Describes the electrical feature of Off Sheet Connector type that you create when you click the
icon in the Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
An off sheet connector is a marker in the functional definition that is used to establish connections
between different systems.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_Name
Type: String
Type: Integer
Type: String
Stud
Description
Type: String
Page 146
Version 5 Release 15
Describes the electrical feature of Stud type that you create when you click this icon
Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
in the
A stud is an electrical connector receiving bundle segments with one or more wires connected
through a termination. It is used to ground bundle segments or pieces of equipment.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_External_Reference Type: String
Defines the stud reference to an external library.
It is used in Electrical Harness Flattening for 2D detail graphic replacement in a drawing.
Elec_Ref_Des
Type: String
Defines the stud reference designator attribute, which is the unique identifier for the stud in the
project.
Elec_Sub_Type
Type: String
Type: Boolean
Is True only if all the stud bundle connection points are connected.
PowerSignal
Description
Describes the electrical feature of Power Signal type that you create when you click this icon
the Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
in
The power signal is a logical connection between two or more components. It will be realized by a
wire in physical world.
Inheritance path: Standard - Feature -> ProductPackage - Product -> Electrical - ElecSignal
Attributes
Elec_Nominal_Part_Num Type: String
Defines the nominal part number of the wire that realizes the power signal.
Version 5 Release 15
Elec_Nominal_Voltage
Page 147
Type: Double
Type: String
Type: Double
Type: String
Defines the separation code of the power signal used by the algorithm to find out the wire route.
Elec_Sub_Type
Type: String
Type: Double
Protection
Description
Describes the electrical feature of protection type from which both the corrugated tube and the tape
derives.
For more information, refer to the Electrical Library and Electrical Harness Installation User's Guides.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
CoveredBundleSegments Type: CATIList
Returns the list of bundle segments covered by the protection.
Elec_Fmbd_Modify
Type: Boolean
Defines the bundle segment attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Elec_Length
Type: Double
Type: Double
Version 5 Release 15
Page 148
Type: Double
Defines the protection linear mass, used for the flattened representation.
Elec_Ref_Des
Type: String
Type: String
Type: String
ShieldingSignal
Description
Describes the electrical feature of Shielding Signal type that you create when you click this icon
in the Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
The shielding signal is a logical connection between two or more components. It will be realized by a
wire in physical world.
Inheritance path: Standard - Feature -> ProductPackage - Product -> Electrical - ElecSignal
Attributes
Elec_Nominal_Part_Num Type: String
Defines the nominal part number of the wire that realizes the shielding signal.
Elec_Recom_Wire_Type
Type: String
Type: Double
Type: String
Version 5 Release 15
Page 149
Defines the separation code of the shielding signal used by the algorithm to find out the wire route.
Elec_Sub_Type
Type: String
Type: Double
Type: Double
SingleConnector
Description
Describes the electrical feature of Single Insert Connector type that you create when you click this
icon
in the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
A single insert connector is an electrical connector male or female. It's the physical representation
for both the plugs and the sockets.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_External_Reference Type: String
Defines the single insert connector reference to an external library.
It is used in Electrical Harness Flattening for 2D detail graphic replacement in a drawing.
Elec_Ref_Des
Type: String
Defines the single insert connector reference designator attribute, which is the unique identifier for
the single insert connector in the project.
Elec_Sub_Type
Type: String
Type: Boolean
Defines the single connector attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Version 5 Release 15
Elec_FullConnected
Page 150
Type: Boolean
if the single insert connector is integrated into an equipment and connected to another single
insert connector,
if the single insert connector is connected to a bundle segment or a back shell and connected to
another single insert connector.
Signal
Description
Describes the electrical feature of Signal type that you create when you click the
icon in the
Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
A signal is a logical connection between two or more components. May be of the following types:
ground, shielding, video, power, command or grouped.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_Nominal_Part_Num
Type: String
Defines the nominal part number of the physical wire that realizes the signal.
Elec_Recom_Wire_Type
Type: String
Type: Double
Type: String
Defines the separation code of the signal used by the algorithm to find out the wire route.
Elec_Signal_Section
Type: Double
Type: CATIList
Version 5 Release 15
Page 151
SignalRoute
Description
Describes the electrical feature of Signal Route type that you create when you click this icon
the Electrical Wire Routing workbench.
For more information, refer to the Electrical Wire Routing User's Guide.
in
The signal route is computed to find out the optimized way between two or more extremities of a
signal.
Inheritance path: Standard - Feature
Attributes
Elec_Length
Type: Double
Type: String
Defines the nominal part number of the wire that realizes the signal.
Elec_Section
Type: Double
Type: String
System
Description
Describes the electrical feature of System type that you create when you click the
icon in the
Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
A system consists of equipments, connectors and signals. It is an electrical unit, which accomplishes
a specific function.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Version 5 Release 15
Elec_Ref_Des
Page 152
Type: String
Defines the system reference designator attribute, which is the unique identifier for the system in
the project.
Elec_Sub_Type Type: String
Defines the system subtype.
Tape
Description
Describes the electrical feature of Tape type that you create when you click the
icon in the
Electrical Library workbench. The tape is then instantiated using the Electrical Harness Installation
workbench.
For more information, refer to the Electrical Library and Electrical Harness Installation User's Guides.
A tape is an electrical component applied onto bundle segments as a protection.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_Bend_Radius_Delta
Type: Double
Defines the bend radius value, which corresponds to the minimum bend radius of the tape curve.
This value takes into account the bundle segment and tape bend radius rule and ends up to an
increased rigidity due to the tape.
Elec_Bend_Radius_Protection_OK Type: Boolean
Is True if the Elec_Bend_Radius attribute is smaller than the real value of bend radius of the
largest bundle segment linked to the tape protection.
Elec_Covering_Length
Type: Double
Type: Boolean
Defines the bundle segment attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Elec_Length
Type: Double
Type: Double
Version 5 Release 15
Page 153
Defines the tape line type, used for the flattened representation.
Elec_Line_Weight
Type: Double
Type: Double
Defines the tape number of layers applied onto the bundle segment.
Elec_Ref_Des
Type: String
Defines the tape reference designator attribute, which is the unique identifier for the tape in the
project.
Elec_Ref_PartNumber
Type: String
Type: String
Type: Double
Type: Double
Type: Double
Type: Double
Defines the tape length considering the overlapping due to the taping angle, and also the number of
layers.
Elec_Total_Thickness
Type: Double
Defines the tape thickness considering the overlapping due to the taping angle, and also the
number of layers.
TerminalBlock
Description
Version 5 Release 15
Page 154
Describes the electrical feature of Terminal Block type that you create when you select this icon
in the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
A terminal block is an electrical connector receiving bundle segments, each bundle segment being
connected to a termination.
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_External_Reference Type: String
Defines the terminal block reference to an external library.
It is used in Electrical Harness Flattening for 2D detail graphic replacement in a drawing.
Elec_Fmbd_Modify
Type: Boolean
Defines the terminal block attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Elec_Ref_Des
Type: String
Defines the terminal block reference designator attribute, which is the unique identifier for the
terminal block in the project.
Elec_Sub_Type
Type: String
Type: Boolean
Termination
Description
Describes the electrical feature of Termination type that you create when you click this icon
the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
A termination is a sub-element ensuring the electrical signal conduction between any type of
electrical component except the filler plug. It is indissociable from the electrical component and
corresponds to a contact crimped into a cavity.
Inheritance path: Standard - Feature -> ProductPackage - Product
in
Version 5 Release 15
Page 155
Attributes
Elec_Extra_Length Type: Double
Defines the length to be added to the wire routing length.
Elec_Id_Number
Type: String
Defines a unique identifier for the termination used to map a functional component to the
corresponding physical part.
Elec_Ref_Des
Type: String
Defines the termination reference designator attribute, which is the unique identifier for the
termination in the project.
Elec_Sub_Type
Type: String
Termination_GeoConstraint
Description
Describes the electrical feature of Termination type that you create when you click this icon
the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
in
This type of termination only exists for terminal strip and the stud connectors. It has an associated
geometry (a line), which allows the connection to be constrained between the bundle segment and
the connector. The bundle segment can only be connected via this associated geometry (the line).
Inheritance path: Standard - Feature -> ProductPackage - Product
Attributes
Elec_Extra_Length Type: Double
Defines the length to be added to the wire routing length.
Elec_Id_Number
Type: String
Defines a unique identifier for the termination used to map a functional component and the
corresponding physical part.
Elec_Ref_Des
Type: String
Version 5 Release 15
Page 156
Defines the termination reference designator attribute, which is the unique identifier for the
termination in the project.
Elec_Sub_Type
Type: String
TerminalStrip
Description
Describes the electrical feature of Terminal Strip type that you create when you click this icon
in the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
A terminal strip is an electrical connector comprising a strip of terminations.
Inheritance path: Standard - Feature
Attributes
Elec_External_Reference Type: String
Defines the terminal strip reference to an external library.
It is used in Electrical Harness Flattening for 2D detail graphic replacement in a drawing.
Elec_Fmbd_Modify
Type: Boolean
Defines the terminal strip attribute, which makes it possible to know if the component has been
modified during the Electrical Harness Flattening Synchronization command. Is True if modified.
Elec_Ref_Des
Type: String
Defines the terminal strip reference designator attribute, which is the unique identifier for the
terminal strip in the project.
Elec_Sub_Type
Type: String
Type: Boolean
VideoSignal
Page 157
Version 5 Release 15
Description
Describes the electrical feature of Video Signal type that you create when you click this icon
the Electrical System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
in
The video signal is a logical connection between two or more components. It will be realized by a
wire in physical world.
Inheritance path: Standard - Feature -> ProductPackage - Product -> Electrical - ElecSignal
Attributes
Elec_Nominal_Part_Num
Type: String
Defines the part number of the wire that realizes the video signal.
Elec_Recom_Wire_Type
Type: String
Type: Double
Type: String
Defines the separation code of the video signal used by the algorithm to find out the wire route.
Elec_Signal_Section
Type: Double
Type: String
Wire
Description
Describes the electrical feature of Wire type that you create when you click the
Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
Inheritance path: Standard - Feature -> ProductPackage - Product
icon in the
Version 5 Release 15
Page 158
Attributes
Elec_Bend_Radius
Type: Double
Type: String
Type: String
Type: Double
Type: String
Returns the reference designator value of the device to which the first extremity of the wire is
connected.
Elec_FullConnected
Type: Boolean
Type: Boolean
Is True if a route exists between whatever nodes only using the network connected branches.
Elec_IsRouted
Type: Boolean
Type: Double
Type: Double
Type: String
Version 5 Release 15
Elec_Sep_Code
Page 159
Type: String
Defines the separation code of the wire used by the algorithm to find out the wire route.
Elec_Shielding_Signal
Type: String
Type: ElecSignal
Type: String
Defines the identifier of the signal used during the wire routing.
Elec_Sub_Type
Type: String
Type: String
Returns the reference designator value of the connection point to which the second extremity of the
wire is connected.
Elec_ToDevice
Type: String
Returns the reference designator value of the device to which the second extremity of the wire is
connected.
IsSingleInBundleSegment Type: Boolean
Is True when the wire route follows at least one bundle segment containing only this wire.
Version 5 Release 15
Page 160
Version 5 Release 15
Page 161
Version 5 Release 15
Page 162
Environment Settings
Make sure the options are set up as follows:
1. Select the Tools -> Options... command then in the Infrastructure category, click Part
Infrastructure.
2. In the General tab:
Keep link with selected object option must be checked:
This makes possible the contextual links between the bundle segments and the geometry when
creating the harness.
3. Then in the Equipment & Systems category, click the Electrical Harness Installation
workbench. Click the Harness Management tab:
The bundle segment naming rule is set to Parent-Bundle Segment(#PN#)
to help you recognize to which geometrical bundle a bundle segment belongs.
Version 5 Release 15
Page 163
of the working catalog containing the V5 parts which Part Number are referred to in the XML
files.
Click the Browse button to locate the catalog containing the V5 parts, which Part Number
attributes are referred to in the XML files.
Version 5 Release 15
It is now necessary to define the electrical objects mapping regarding the working catalog.
To do so:
then in the Equipment & Systems category, select the Electrical mapping tab.
Page 164
Page 165
Version 5 Release 15
.
2. Click the External Systems
button.
The System Selection dialog box displays with the XML files available:
4. Click OK to validate.
The component list is filled up with these data and available for assisted placement or
routing.
Version 5 Release 15
Page 166
This task explains how to place electrical components from the external device list.
button.
equipments
connectors
internal splices
shells.
Show all devices: the list displays all the devices referenced in the external data file, even if they are not placed in the
geometry.
Show only devices present in session: the list displays only the devices placed in the geometry.
Show only changed devices: the list displays only the devices which part numbers have been changed in the external
data file.
Version 5 Release 15
Page 167
Since a mapping has been defined, the catalog browser has been filtered to display only the object with the same
part number as the object selected in the device list.
If the part number is defined neither in the device list nor in the catalog, you can navigate in the catalog browser to
select the component of your choice.
4. Select this equipment: Battery 6volts and click OK.
The equipment is placed and automatically linked, together with the connector that belongs to it.
They are added to the specification tree under the active product and appear in the geometry at the origin. You can change
their locations using the compass.
The component list is updated: the equipment, connector and pins are shown as linked in the device list.
Version 5 Release 15
Page 168
If all the sub-element part numbers are filled up in the device list and found in the catalog, they are automatically
placed and linked.
For a connector to be correctly placed in the right cavity of an item of equipment:
The equipment and connector PartNumbers in the XML file must correspond to items in the V5 catalog.
The equipment must have a cavity with a defined name in the V5 catalog.
The connector name in the XML file must correspond to a cavity name of the V5 equipment.
For more information, refer to Managing Links from External Data (under Working with External Systems) in the
Electrical Library User's Guide.
5. Repeat these steps for the second equipment: Battery 6Volts.2.
6. Click Close when you are done.
Make sure you have defined the electrical objects mapping regarding the working catalog.
To do so:
then in the Equipment & Systems category, select the Electrical mapping tab.
Version 5 Release 15
button.
again.
button.
Page 169
Version 5 Release 15
Page 170
button.
Select successively the connector connection point of both connectors to link them.
Version 5 Release 15
Page 171
Version 5 Release 15
Page 172
button.
You will now place the internal splices inside the bundle segments.
button.
Version 5 Release 15
Page 173
7. Click Place.
Since a mapping has been defined, the catalog browser opens with the predefined internal splice:
Depending on where you make your selection, the splice is linked to one or other extremity. The choice of the extremity
affects the diameter update of the bundle segment when wires are routed.
Let's see an example: A wire is routed between Connector1 and the splice.
Version 5 Release 15
Page 174
In this case, the splice is linked to Extremity2. The wire is only routed in the BundleSegment1. An extra length is added
to the wire between Extremity2 and the splice: BundleSegment2 diameter is not recalculated.
In this one, the splice is linked to Extremity1. The wire is routed in both BundleSegment1 and BundleSegment2:
BundleSegment2 diameter is recalculated and updated.
Version 5 Release 15
The component list is updated: the splices and pins are shown as linked in the device list.
Page 175
Page 176
Version 5 Release 15
Automatic Routing
Since you have set up the option to enable the external systems interfacing, the Automatic
Routing
This task explains how to route wires from an external wire list into an electrical bundle.
To know more details, refer to Considering External Data Routing in Greater Depth.
The document must contain at least:
a system.
button.
button.
Version 5 Release 15
For the wires available in the list, you get the following information:
The routing options allow you to use or not the knowledge rule.
5. Select one or more wires and click the right arrow.
The selected wires shift to the right column: they will be routed.
6. Click Route.
The Automatic Wire Routing Report is displayed
Page 177
Version 5 Release 15
Page 178
The bundle segments diameter are updated according to the wiring information.
To know more, refer to Customizing - Equipment & Systems - Electrical Wire Routing
documentation.
Version 5 Release 15
Page 179
2. Click the Tools -> Export Wires... menu item and select the Export Wires in iXF Format.
You are prompted to select a node in the specification tree and every electrical bundle belonging to it will be
exported.
3. Click a node in the specification tree.
The File dialog box opens:
Version 5 Release 15
Page 180
4. Navigate to select the folder where you want to store your file and enter the name of the file.
5. Click Save.
An .xml file is created.
Note that wire groups and wires are exported by harness (electrical bundle).
The data exported are:
Wire group properties, particularly the wire group length computed from the 3D geometry.
The wire group length is the length of the longest wire in the wire group (taking into account the extra pin
length). The wire group length takes a wire length coefficient into account (allowing for twisted wires) when the
group is routed between two connectors.
Wire properties, particularly the wire length computed from the 3D geometry.
Version 5 Release 15
Page 181
PowerSupply
HairDryer
HairDryer_Signals
Version 5 Release 15
Page 182
4. Map the functional connectors to the physical ones using the contextual menu:
(connector_M: extension cable connectors to be plugged onto the batteries)
This action makes it possible to predefine for each functional connector what device reference to be used for the 3D
placement. This will simplify the 3D Designer work: he's driven by the functional data, reusing the Electrical System
engineer knowledge to achieve the 3D implantation.
Version 5 Release 15
Page 183
This action makes it possible to define the signal extremities corresponding to the power supply and the hair dryer
systems.
Version 5 Release 15
Page 184
To do so:
Right-click the ElectricalWorkbenchIntegration product and select Components -> Existing Components...
10. Set up the options using the Tools -> Options... menu:
This product will contain the hair dryer itself and later the power cable.
3. Open the Catalog Browser using this icon
Successively:
This action places the component from the catalog at the default location.
Using the compass, you can modify the position of the equipment.
It's a first standard mode of placement.
4. Click the Add Link icon
to link the respective physical and functional equipment (the hair dryer).
Version 5 Release 15
Page 185
This action generates the link between the component and its corresponding functional element.
You can see if a component is connected or not: the equipment icon sign changes and turns from red to green,
meaning that the hair dryer is now electrically linked.
>>
The automatic signal routing will be possible since the signal extremities defined in the functional system can be
transposed in the 3D world using the physical/functional relations.
Right-click the Hair-DryerProd, select Components -> New Product, enter the Part Number for the power
cable in the Properties dialog box and validate.
Right-click the ElectricalWorkbenchIntegration, select Components -> New Product, enter the Part Number
for the extension cable in the Properties dialog box and validate.
Page 186
Version 5 Release 15
Select the power cable and click the Geometrical Bundle icon
You can change the instance name to PowerCable.
Select the extension cable and click the Geometrical Bundle icon
You can change the instance name to ExtensionCable.
again.
The power cable is part of the hair dryer: that's why you create it in the hair dryer product (Hair-DryerProd).
The extension cable is an independent assembly: that's why you create it under the root product assembly.
4. Double-click to activate the Geometrical Bundle2 (the extension cable) in the specification tree.
5. Switch to Electrical Library workbench.
7. Select the first connector in the PowerSupply system. The catalog pops up.
An alternative to steps 6 and 7 is to use the contextual menu, by right-clicking the connector in the
PowerSupply system and choose Place Physical Device.
Select the connector in the catalog and click OK to validate. The connector is added to the specification tree and
appears in the geometry at the origin (0, 0). You can change its location using the compass.
Repeat these steps for the second connector.
The physical connector pre-selection previously performed with Electrical System Functional Definition is used to
automatically get the correct part reference.
The 3D connector is automatically placed in the active product (Geometrical Bundle2) at the product origin.
Version 5 Release 15
Page 187
8. Use the Electrical Assembly Design workbench to create the electrical connection with the batteries.
Select successively in the geometry each connector_M connection point from the Geometrical
Bundle2(ExtensionCable) then the corresponding connector_F connection point of the battery.
1.
2.
The connectors are linked and shifted to the batteries.
This action creates the assembly constraints between connector and battery.
9. Double-click to activate the Geometrical Bundle2 (the extension cable) in the specification tree.
10. From the catalog, drag and drop the connector_F onto the Geometrical Bundle2 for the extension cable. If needed,
Version 5 Release 15
Page 188
position it between the hair dryer and the batteries using the compass (ExtensionCable must be active).
This action places the connector from the catalog onto the extension cable.
11. From the catalog, drag and drop the Backshell_F directly onto the Connector_F in the Geometrical Bundle2.
Version 5 Release 15
Page 189
This action places the back shell from the catalog onto the extension cable connector.
12. Double-click to activate the Geometrical Bundle1 (PowerCable) in the specification tree.
13. From the catalog, drag and drop the Connector_M directly onto the Connector_F of the extension cable.
This action adds the power cable connector (connector_M) from the catalog to the extension cable connector. The
assembly constraints as well as the electrical constraints have been created between the power cable and the extension
cable connectors. When the female connector is selected, the electrical link is displayed in the Related Objects viewer.
14. From the catalog, drag and drop the Backshell_M directly onto the Connector_M of the power cable.
Version 5 Release 15
Page 190
This action places the back shell from the catalog onto the power cable connector. The assembly constraints as well as
the electrical constraints have been created between the connector and the back shell.
You can repeat this step to place back shells on the extension cable male connectors (at the other extremity).
15. Start the Electrical Harness Assembly workbench to create the bundle segments for the power and extension cables.
To do so:
This action creates the bundle segments that will be used to route the wires of the power and extension cables.
Page 191
Version 5 Release 15
Boxes are displayed to help you recognize the extremities of the signal.
5. Click the Automatic Routing icon
The bundle segments diameter are updated according to the signal section.
Version 5 Release 15
Page 192
The specification tree is updated: the wires and wire connections are created.
The length of the wire linked to a back shell is extended with an extra-length, defined as a back shell attribute.
However, an alternative is to connect the bundle segment through the back shell: in this case, the wire length is
equal to the total length of the bundle segments of the wire route.
The bundle segments diameter is updated using the section defined on the signals (with EFD).
When only one signal is selected, the wire connections are displayed (as shown below).
Version 5 Release 15
Page 193
Interoperability
In this section, you will find information about interoperability via VPM Navigator between
CATIA Electrical Applications and other applications listed below:
ENOVIA V5 Interoperability Using VPM Navigator
Using ENOVIA Catalog for Electrical Mapping
Loading an iXF Document with VPM Navigator
Version 5 Release 15
Page 194
ENOVIA V5 Interoperability
Using VPM Navigator
This task explains how to work with electrical data stored in ENOVIA V5, using VPM Navigator:
We recommend that you read the VPM Navigator User's Guide to know more about this product.
This documentation can be found on the ENOVIA LifeCycle Applications Documentation CDROM.
1. Log on to VPM Navigator.
Once the connection has completed successfully, the icons in the ENOVIA V5 toolbar are no longer grayed out.
2. Click the the ENOVIA Search... button
A PRC (referred to as Product Root Class or root in VPM Navigator) is the most basic entity in your Product Structure.
3. In this window, double-click the object you want to open.
The VPM Navigator window displays, looking something like this:
Version 5 Release 15
Page 195
Page 196
Version 5 Release 15
3. Now switch to Electrical Library to connect the plug of the geometrical bundle to the female
socket of the other.
To do so:
Version 5 Release 15
Also refer to Working with ENOVIA V5: Optimal CATIA PLM Usability.
Page 197
Version 5 Release 15
Page 198
If you are using Electrical Harness Flattening, it is the only mode supported to save geometrical bundle extracted data.
Within CATIA connected to ENOVIA V5 through VPM Navigator, if the user selects a new product as a geometrical bundle,
the system automatically knows that this geometrical bundle has to be stored as a workpackage.
Checks are performed when using the Electrical tools to ensure that all entities created or modified will be correctly
stored, using the following rules:
No links to geometry (that is to say external references) can be done from the part inside a workpackage to a part
Version 5 Release 15
Page 199
The context for the external links must be set to a product node inside the workpackage.
Refer to Infrastructure User's Guide - Customizing Part Infrastructure.
Mechanical constraints and electrical connections between parts inside the workpackage and outside the workpackage
must rely on published objects.
To make this possible, the following settings must be applied when working with CATIA connected to ENOVIA V5, to
store the geometrical bundles as workpackage in ENOVIA V5:
a. Select Tools -> Options -> Infrastructure -> Part Infrastructure -> General tab.
Version 5 Release 15
Page 200
b. Select Tools -> Options -> Equipment and Systems -> Electrical Harness Installation -> Harness
Management tab.
In the Contextual Links frame, for Keep link with selected object, choose In geometrical bundle in the
list.
Anyway, the system checks that the rules are not violated and if those options are not set properly, an error message is
displayed:
Moreover, during the electrical connection between devices and/or bundle segments that are not inside the same
workpackage, publications are automatically created on the geometrical bundle stored as workpackage, to ensure that
constraints and connections are correctly stored.
Version 5 Release 15
Page 201
Within CATIA connected to ENOVIA V5 through to VPM Navigator, if the user selects a new component as a geometrical
bundle, the system automatically knows that this geometrical bundle has to be stored in explode mode.
A single check is performed when using the Electrical tools to ensure that all the entities created or modified will be
correctly stored:
The context for the external links must be set to the root product node of the session.
Refer to Infrastructure User's Guide - Customizing Part Infrastructure.
To make this possible, the following settings must be applied when working with CATIA connected to ENOVIA V5, to
store the geometrical bundles in explode mode in ENOVIA V5:
a. Select Tools -> Options -> Infrastructure -> Part Infrastructure -> General tab.
Version 5 Release 15
For the time being, the following commands are not available if CATIA is connected to ENOVIA V5 Database:
Page 202
Version 5 Release 15
Page 203
Version 5 Release 15
button.
Together with:
Page 204
Version 5 Release 15
Page 205
10. Define the mapping as explained in the CATIA - Infrastructure User's Guide - Customizing - Customizing Settings Equipment and Systems - Electrical Mapping.
Version 5 Release 15
Together with:
Page 206
Version 5 Release 15
button.
The System Selection dialog box opens containing the previously selected iXF files:
Page 207
Version 5 Release 15
For more information about external systems, refer to the CATIA - Electrical Library User's Guide - User Tasks Electrical Integration Scenarios - Electrical Integration from External Data
Page 208
Version 5 Release 15
Workbench Description
The Electrical Wire Routing Version 5 application window looks like this:
Click the hotspots to display the related documentation.
Menu Bar
Toolbars
Specification Tree
Page 209
Version 5 Release 15
Page 210
Menu Bar
The Menu Bar and most of the items available in Electrical Wire Routing workbench are the standard
ones. The different commands and tools are described in Infrastructure Version 5.
For more information, refer to the standard Menu Bar section.
However an item is added to the Tools menu: Export Wires...
Refer to Textual Reports and Exporting Data from CATIA.
Version 5 Release 15
Page 211
Version 5 Release 15
Page 212
Version 5 Release 15
Specification Tree
Page 213
Version 5 Release 15
Page 214
Page 215
Version 5 Release 15
Mounting Equipment
Equipment
Shell
Single Insert Connector, External Splice, Internal Splice, Stud, Terminal Strip, Terminal
Block,
Filler Plug
Contact
Back Shell
Electrical container
Cavity
Termination
Connector Connection Point
Bundle Connection Point
Cavity Connection Point
Back Shell Connection Point
Geometrical Bundle
Multi-Branchable Document
Branch
Bundle Segment
Electrical Bundle
Wire
Wire associated to a reference (from a catalog)
Wire group
Wire group associated to a reference (from a catalog)
Wire Connection Container
Wire Connection
Internal Splice
Functional System
Functional Equipment
Not linked to physical
Linked to physical
Partially linked to
physical
Linked to physical
Partially linked to
physical
Functional Connector
Not linked to physical
Page 216
Version 5 Release 15
Linked to physical
Partially linked to
physical
Shielding Signal
Group Signal
Ground Signal
Video Signal
Other
Routed Signal in System Space Reservation (SSR)
Partially routed
Version 5 Release 15
Page 217
Customizing
Before you start your first working session, you can customize the way you work to suit your habits. This type
of customization is stored in permanent setting files. Settings will not be lost if you exit your session.
The Electrical Mapping tab lets you define the catalog and the electrical objects mapping.
The Electrical Process Interfacing tab lets you define the access to external data, the
electrical iXF repository path and the identifier for mapping management. It also displays
the electrical working catalog path that is defined in the Electrical Mapping tab.
Version 5 Release 15
Page 218
This page deals with General options used for wire routing:
Available/Favorites
To add properties to the list, select the property in the Available list and click the --> arrow.
The Favorites list contains the properties displayed in the Interconnection frame of the Wire Extremity
Management dialog box.
To remove properties, do the reverse: select the property from the Favorites list and click the <-- arrow.
By default, the Favorites list is blank.
Version 5 Release 15
Page 219
The Separation Code File area is used to define Separation Code rules to optimize the routing.
Three options, mutually exclusive are available:
The separation codes may also be Rule Based, using the Knowledge language.
Only one rule can be implemented at a time, but this rule may combine several conditions.
The line above the input field is a reminder of the knowledgeware syntax.
The Eraser icon is used to clear the input field.
Click the Edit button to enter a new rule: the Routing Rule Editor is displayed.
Version 5 Release 15
Extremity Color
Page 220
Version 5 Release 15
Page 221
The Color field is used to change the color of the extremity boxes.
Select a color from the list box. the result looks like this:
or
Version 5 Release 15
Page 222
Electrical Mapping
Catalog
Version 5 Release 15
select a family
Page 223
Version 5 Release 15
select a keyword
Page 224
Version 5 Release 15
Page 225
This document lets you define the options to take advantage of external data from partners, through
XML files or from CAA V5 APIs, retrieving information from legacy databases.
This tab shows:
Version 5 Release 15
Page 226
System repository
Identify the folder path in which the XML files available are stored.
To do so, use this button
Catalog path
The catalog path is displayed in this frame. However, it is defined in the Electrical Mapping tab.
Select the Electrical Mapping tab to select the working catalog using the Browse button
Locate the catalog containing the V5 parts, which Part Number attributes are referred to in the
XML files.
By default, this option is cleared.
Identifier Management
Version 5 Release 15
Page 227
Instance Name
Select this option so that the Instance Name will be taken into account instead of the Reference
Designator to insure the mapping between 3D objects and external system's objects.
By default, this option is cleared.
It is also necessary to define the electrical object mapping regarding the working catalog.
To do so, select the Electrical Mapping tab.
Refer to the Customizing - Equipment & Systems - Electrical Mapping documentation.
Version 5 Release 15
Page 228
The first line of the table can be read: Segreg-1 is compatible with type2, type3 and type4.
Note that:
A signal with an empty separation code can be routed on all the network segments
A signal with the same separation code as a segment can be routed on this segment (even with no
compatibility table)
The separation code of the V4 bundle segments (BNS) can only be modified in CATIA V4
(E3MANAGE/MANAGE/Element)
Version 5 Release 15
Page 229
For the pathways, the separation code is modified using Edit -> Properties
For the signals, the separation code is defined using CATIA - Electrical Systems Functional Definition
Page 230
Version 5 Release 15
Cache Management
Cache Activation
, if need be.
Version 5 Release 15
Page 231
a device list containing the device attributes and the assembly connectivity
and a wire or equipotential list containing their attributes and the from-to connectivity.
This information will be used by CATIA Electrical products to implement in the digital mock-up
the electrical systems driven by any electrical authoring tool (schematics or database for
example).
You can either access this information through CAA APIs (refer to CAA documentation) or
through an XML file. This method (using an XML file) is described in Electrical Integration from
External Data.
You will find hereafter the XML schema to create your own interface to CATIA Electrical Tools.
The exchange data model is different from the data model of CATIA Electrical solutions.
Actually, this data model consists of pertinent information that needs to transit between
Electrical specification tools (schematics, etc.) and CATIA. It only aims at implementing those
specifications in the mock-up. So only this pertinent information (objects, attributes and
connectivity) is described in the following XML schema and not all the information stored in
the CATIA electrical product documents.
In the context of CATIA P1, the CAA APIs are not supported.
As well, several objects are not managed in CATIA P1:
equipotential
connector shell
splice
even if defined in the XML file: the same XML schema is shared for P1 and P2 products.
Preamble
iXF is a format defined by Dassault Systmes, which is used for the data exchange in XML
within CATIA.
Succinctly, iXF is based on the SOAP format and relies on the XML and the XML schema
concept. It makes it possible to describe a grammar (a specific data model) expressing the
object, class and behavior concepts as well as documents containing data conforming to the
defined grammar.
A detailed description of the iXF format can be found at the following address:
http://www.ixfstd.org/
Version 5 Release 15
Page 232
Version 5 Release 15
Page 233
Electrical Objects
The following classes with their associated behavior describe the electrical objects within the iXF Electrical Schema.
Harness
Harness
Wire
Wire
Equipment
Equipment
Product
Function
ConnectorShell
ConnectorShell
Product
Splice
Splice
Product
Connector
Connector
Product
Equipotential
Equipotential
Product
Wire group
Wire group
Product
Product
Pin
Pin
Product
Cavity
Cavity
All these classes derived from the Object abstract class. This one is not to be used as is but allows you to define the Name
attribute for all the classes deriving from the Object class.
Version 5 Release 15
Page 234
The units for all the attributes are given in the standard MKS system.
The following behaviors, associated to the electrical objects are defined in the iXF electrical schema (behavior named
ClassBehavior):
Harness
Attribute: SubType
Wire
Attribute: SubType
ConnectorShell
Attribute: SubType
Connector
Attribute: SubType
Pin
Attribute: SubType
Cavity
Attribute: SubType
Product
Attribute: PartNumber
Equipotential
At last, all the objects expressed in a iXF document have an attribute identifying in a unique way each object within the project,
except for the objects of Link type, which have a unique identifier within the document.
To illustrate how to describe an electrical object with the iXF format, let's take the example of an electrical connector:
Version 5 Release 15
Page 235
as subtype: Single Insert Connector (attribute 'SubType' via its Connector behavior)
WireLink
WireGroupLink
EquipotentialLink
DeviceLink
HarnessLink
Version 5 Release 15
Page 236
The relation between two connectors (mating connector, connector) is not managed by a Link type object as above but using a
specific attribute named MatingConnector (behavior attribute of Connector type). This attribute is optional and is valuated
with the identifier of the mating connector on both sides of the connection.
Let see an example where two connectors are connected together. The connectivity between them is described as follows:
Version 5 Release 15
Page 237
the first one: ElectricalSchema.xsd refers to the other three and describes the Electrical Object Classes.
the third one: IXF_CB_NS2.xsd describes the Link type Behaviors (iXF standard reference).
and last but not least, the fourth one: IXF_CB_NS3.xsd describes the Functional Behaviors.
Version 5 Release 15
Page 238
Version 5 Release 15
Page 239
Version 5 Release 15
Page 240
Electrical Behaviors
Version 5 Release 15
Page 241
Version 5 Release 15
Page 242
Version 5 Release 15
Page 243
Functional Behaviors
Version 5 Release 15
Page 244
Version 5 Release 15
Page 245
Version 5 Release 15
Page 246
Glossary
A
assign
affect
B
bill of materials
bridge wire
bundle
bundle segment
A list of connectors and devices referenced by the wire list, displayed with
their characteristics.
A wire between two pins of the same connector to create a bridge and
propagate the connection.
Always refers to an electrical bundle.
A geometrical subdivision of a bundle, also called segment
C
compatibility table
connector
cvs file
D
deaffect
E
electrical bundle
electrical system
G
geometrical bundle
Version 5 Release 15
harness
Page 247
I
internal splice
M
mapping
mating connector
P
pathway
pin
properties
R
rank
reaffect
reconcile
resolve
routing
An operation that computes the optimized wire route between two or more
extremities of a signal.
S
segment
separation code
signal
W
wire
wire connection
wire group
wire list
Version 5 Release 15
Page 248
Version 5 Release 15
Index
A
affect
arrangement box (ArrBox)
automatic routing
equipotentials
wire groups
wires
B
bridge wire
bundle
bundle segment
definition
diameter
recomputing
C
catalog
command
Automatic Equipotential Routing
Automatic Wire Routing
Delete (Wire)
Delete Connection
Delete Signal Route
Export Wires...
Page 249
Version 5 Release 15
Page 250
D
deaffect
deleting
wires
deleting a signal route
deleting a wire
diameter
bundle segment
DistanceWireProduct
distributing
wires
E
ElecDistanceCommon
electrical application interoperability
electrical behavior
electrical bundle
electrical connection point
electrical data exchange format
electrical object class
electrical package
electrical termination
electrical user function
DistanceWireProduct
ElecDistanceCommon
ListAllOuterLayerObjects
ListDirectlyCoveredObjects
ListDirectlyOuterLayerObjects
VisualMode
Electrical.css
equipment
Version 5 Release 15
Page 251
equipotential
automatic routing
definition
exporting
wire groups
wires
external data
management
placing internal splices
working with...
xml files
F
filter management
functional behavior
G
geometrical bundle
getting wire reference
H
html
I
internal splice
iXF electrical schema
Version 5 Release 15
Page 252
Version 5 Release 15
K
knowledge
L
link type behavior
ListAllOuterLayerObjects
ListDirectlyCoveredObjects
ListDirectlyOuterLayerObjects
loading an iXF document with VPM Navigator
M
mapping
mapping with reservation
mating connector
connection
merging wire connections
modifying the wire route
O
optimal CATIA PLM usability
P
pathway
placing internal splices
Page 253
Version 5 Release 15
external data
placing physical devices
PRC
Product Root Class
R
rank
reaffect
recomputing
bundle segment
reconciling objects
related objects
replacing wire connection with external splice
resolving
wires
route
routing simulation
S
selecting system from external data
selecting the signal
separation code
signal
splitting wire connections
style sheet
T
termination
Page 254
Version 5 Release 15
U
using ENOVIA catalog for electrical mapping
V
viewing related objects
VisualMode
W
wire connections
merging
splitting
wire extremity management
wire groups
automatic routing
exporting
wires
automatic routing
creating
deleting
distributing
exporting
Page 255
Version 5 Release 15
getting reference
resolving
working with electrical data using VPM Navigator
working with external data
X
xml
XML file
Page 256