Académique Documents
Professionnel Documents
Culture Documents
Overview
Conventions
What's New?
Getting Started
Entering the Workbench
Setting Up the Options
Creating a Multi-Branchable Document
Creating Construction Points
Defining the Segment Parameters
Defining the Segment Route
Adding a Branch Point
User Tasks
Entering the Workbench
Exiting the Installation Workbench
Creating a Geometrical Bundle
Harness Covering
Instantiating Protective Coverings
About Protective Coverings
Adding Light Protective Coverings
Adding Protective Coverings
Adjusting Relationships between Harness Covering Components
Linking/Unlinking Bundle Segments
Linking Bundle Segments
Unlinking Bundle Segments
Working with Branch Points
Creating/Modifying Segments within a Branch
Removing a Branch Point
Deleting Unused Branch Points
Adding Branch Points
Removing Branch Points
Reference Information
Frequently Asked Questions
Electrical Integration from External Data
Environment Settings
Setting up the Electrical Process Interfacing
Selecting Systems from External Data
Placing Devices from External Data
Creating the Cable Harness
Placing Internal Splices
Automatic Routing
Exporting Data from CATIA
Editing Electrical Properties
Viewing Related Objects
Electrical and Knowledge
Electrical User Functions
Conventions
Certain conventions are used in CATIA, ENOVIA and DELMIA documentation to help you recognize and understand important concepts and
specifications. This page describes:
Graphics Conventions
Text Conventions
Mouse Usage
Navigation compass
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
functionalities that are new or enhanced with this release
allows you to switch back to the full-window viewing mode
Gives access to
Site Map
Split View Mode
What's New?
Overview
Getting Started
Basic Tasks
User Tasks or Advanced Tasks
Interoperability
Workbench Description
Customizing
Administration Tasks
Reference
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.
File > New identifies the commands to be used.
Enhancements are identified by a blue-colored background on the text.
Mouse Usage
The mouse usage differs depending on the type of action you need to perform.
Use this
mouse button
Double-click
Shift-click
Ctrl-click
Check
(check boxes)
Drag
Drag and drop
Drag
Move
Right-click
Navigation Compass
The navigation compass
is located in the guide banner next to the guide name. It lets you navigate through the information in the guide.
What's New?
Enhanced Functionalities
Adding Light Protective Coverings
After customization, the parameters and relations are displayed in a separate node in the specification tree.
Arranging Bundle Segments in Supports
Allows you to show or hide the parameters of the of the bundle segment in the geometry area.
Migrating Step by Step...
The migration mode is automatically switched to As Result when migration causes shape or length modifications in the As Spec mode
in case of a flexible curve of the bundle segment.
Getting Started
Before getting into detailed instructions for using Electrical Harness Installation, the following tutorial provides a step-by-step scenario
1. Select Start > Equipments & Systems > Electrical Harness Discipline > Electrical Harness Assembly.
The Electrical Harness Assembly workbench is displayed and ready to use.
5. Click OK to validate.
The Electrical Harness Assembly workbench automatically switches to the Electrical Harness Installation workbench and the
Branch Definition dialog box appears.
As you will first create a point that will be used to route the bundle segment, close the dialog box.
2.
Click OK.
1. Click Point
4.
This point will be used to build the Flexible Curve geometrical representation.
Any point that has been created in any other workbench can also be used this way.
This task shows you how to define the bundle segment parameters.
1. Click Branch Definition
The dialog box opens:
Connector A1:
o
o
Note that you can reverse the tangent by clicking the red arrow.
The point previously created to define the bundle segment route: Point1
Connector A2: the tangent is automatically created.
3. Click OK to validate.
The Route Definition dialog box closes and the Branch Definition dialog box is displayed afresh.
the
branch
and
bundle
segment
definition.
5.
This task explains how to create a branch point to connect another bundle segment.
The document is still open from the previous task.
1. Click Add Branch Point
.
You are prompted to select a bundle segment.
2. Select the bundle segment.
The Create Branch Point dialog box appears with a pre-selected reference point, allowing you to place the branch point on the
curve:
3. Optionally, click Other Extremity to change the reference point to the other end of the bundle segment.
4. Click Length to define the distance to the reference object and enter 60mm for example.
5. Click OK to validate.
A branch point is created and the branch now contains two bundle segments.
The result looks like this:
6. You can now create another bundle segment to be connected to the branch point:
To do so:
o
o
o
o
7.
You can add a branch point on a bundle segment even if it is covered with a protective covering.
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:
Electrical Harness Assembly which lets you create and handle the Product documents that will contain the geometrical bundles
and/or the bundle segments.
Electrical Harness Installation which allows you to define bundle segments in Part documents. Refer to Exiting the Installation
workbench to switch back to the Electrical Assembly.
You can add the Electrical Harness workbenches to your Favorites, using the Tools > Customize item. For more
information, refer to CATIA V5 - Infrastructure User's Guide.
2.
Customizing
Don't forget to set your options before starting to work (Tools > Options..., Equipment & Systems, > Electrical Harness
Discipline > Electrical Harness Installation).
This task shows you how to quit the Electrical Harness Installation workbench when the bundle segments definition is completed.
1. Click Exit
You are back in Electrical Harness Assembly workbench or the lastly used Product workbench.
You are advised to create a geometrical bundle representing the harness first before any other action like instantiating harness
connectors, creating a multi-branchable document, adding bundle segments or connecting devices, as the geometrical bundle will
become flexible when needed.
By default, you must create a geometrical bundle before creating bundle segments. To change this setting (in the Tools >
Options menu), refer to Electrical Harness Installation Options.
Thanks to the selective loading capabilities, you can work with the cache activated.
Refer to Selective Loading in Electrical Products.
Open the ElectricalBasic.CATProduct document.
It contains devices to be connected together in a geometrical bundle.
You are prompted to select the product you want to become the geometrical bundle.
2. Select the product of interest: Product1
The geometrical bundle is created, with electrical properties.
In the specification tree, the name and icons have been modified.
A product which does not result from the New Part command
A product which does not result from the New Component command (inline product).
3.
You are now ready to start your design. You can create and organize your harness assembly in two different ways. By:
Branch in a multi-branchable document.
A branch is a set of bundle segments that share the same centerline.
To activate this functionality, you need to activate the cache in Tools > Options > Infrastructure:
Choose Product Structure, the Cache Management tab then Cache Activation.
Select the Work with the cache system check box:
You need to launch an electrical workbench to display the branches belonging to a multi-branchable document. They are not visible if your
are not in an electrical context (for example in Product Structure workbench).
At creation, a multi-branchable document contains one part with only one branch (Branchable1) and one bundle segment (Bundle
Segment1). All the geometry is created under this part in the different bodies.
A branch is a set of bundle segments that share the same centerline.
The bundle segment belongs to the part document and has electrical properties.
Note: Editing and modifying a branch created in the previous release versions, converts it into a multi-branchable document.
And...
(no impact)
Selected
Cleared
(no impact)
At least one multi-branchable document exists with one branch fully defined Creates a new branch (Branchable n)
(i.e. geometry associated and route defined)
and, nothing is selected in the geometry area
(no impact)
and remove
A Multi-Branchable document
is created by default. It includes:
o
A Part document (
Multi-Branchable1) which becomes active.
o
A flexible curve (
Flexible Curve.1) created under
ElecRouteBody.1 and belonging to the part. At the moment, there is no
geometrical representation.
o
A branch (
Branchable1) containing a bundle segment (Bundle
Segment1). At the moment, there is no geometrical representation.
If the branch (Branchable1) has several bundle segments, the diameter box becomes unavailable. Use Bundle Segment
Definition to manage the individual diameter.
3. Enter a value in the Diameter field. The Section is automatically computed.
As an alternative, you can enter the Section, the Diameter will be computed.
A message warns you that the bend radius must be at least equal to the Diameter value to insure the correct bundle segment
route computation.
4. Enter
a
value
for
the
Bend
Radius.
The
Bend
Radius
is
the
minimum
bend
radius
allowed
for
the
whole
bundle
segment.
The Bend Radius value must be at least equal to the Diameter value to ensure the correct bundle segment route computation.
As an alternative, you can select the Bend Radius Ratio option and set the ratio: the Bend Radius is automatically computed.
5. Select the Mode: Slack for example and give a percentage of slack.
The different options are the following:
o
Slack(%):
The bundle segment length is increased by the percentage indicated in the Slack(%) field. The Length field is unavailable.
o
Length:
The bundle segment length is indicated in the Length field. The Slack(%) field is unavailable.
o
Bend:
The bundle segment length corresponds to the minimum distance between the points defining its route. The Slack(%) and
Length fields are unavailable.
o
Straight Bend:
The bundle segment length is computed from a centreline curve with a fixed minimum bend radius.
The main purpose of the Straight Bend Algorithm is to compute a global centreline curve with a
minimum fixed bend radius from 3D inputs.
When this mode is selected, both Slack(%), and Length fields are grayed out.
7. Click successively:
a.
The connector on the left - you can reverse the tangent using the red arrow.
b.
CATIA finds the closest bundle connection point or section on supports, according to the selection point.
Note that when you select the points used to route the bundle segment, annotations display:
o
The selection of the construction points in the geometry highlights the point/label and select the routed objects in the
The selection in the Route Definition dialog box highlights the point and the label in the geometry area:
You can also define more options using More >>, see Routing Options
8. Click OK to validate. The bundle segment appears.
9. Click Apply in the Branch Definition dialog box to compute the bend radius.
Status lights show whether or not the computed bend radius satisfies the minimum bend radius entered.
The geometry contains:
o
A new body: Body.2 containing the rib
o
The External References container
o
Bundle Segment Definition is now available. To create other segments, see Creating/Modifying Segments within a Branch.
10.
When the dedicated option (Work with one multi-branchable per geometrical bundle) is selected:
Canceling the branch definition before routing the segment creates Multi-Branchable1 and Branchable1. Note that no geometry
is defined.
If the segment route is defined, clicking Branch Definition again creates a new branch.
Change the value of the parameters if needed and route the bundle segment.
OK
2. Click OK to validate.
Branchable2
3.
Note that if you click Cancel in the Branch Definition dialog box, Branchable2 is deleted from the specification tree as well as the
geometry.
If you did not define the geometry and route of the first branch when you created the multi-branchable document, the system edits the first
branch and does not add a new branch.
The application switches to the Electrical Harness Installation workbench and the Branch Definition dialog box appears.
1. Expand the multi-branchable document in the specification tree, then double-click a bundle segment.
The application switches to the Electrical Harness Installation workbench and the Segment Definition dialog box appears.
2.
Note that it is possible to delete a branch but it is not possible to delete a bundle segment.
Select the Equipment & Systems > Electrical Harness Discipline category
Select the Electrical Harness Installation workbench.
In the Harness Management tab, clear the Work with one multi-branchable per geometrical bundle check
box under Bundle Segment Creation.
o
Click OK when done.
2. Double-click to activate the geometrical bundle
o
o
o
segment.
6.
You can create different profiles, including rectangular and elliptical profiles, within the same branch .
Ensure that the dedicated bundle segment profile option (Any Profile)
Multi-profile branch options are used to know how to update the parameters of the profile when the profile area is directly modified or
again and set branch parameters in the dialog box that opens.
The Electrical Harness Assembly workbench switches to the Electrical Harness Installation workbench. The Branch Definition
dialog box opens.
Select the objects of interest in the geometry area to define the route of the branch
Click OK to validate your choice.
Note: A contextual menu allows you to directly access the Profile Management:
o
o
Change the section parameters: 15mm for Major Axis, for example.
Click Apply.
become unavailable as soon as you have entered information in the Detailed Profile Management. In
this case the section shape can be different along the bundle segment.
Section Parameters
Section Area
Profile Type
It is possible to change the Profile Type at:
o
o
Select the point and click the profile type of your choice.
The elliptical and rectangular profiles can also be orientated by clicking Invert H and V Directions:
If the algorithm cannot compute the bundle segment based on the parameters you chose, you can resolve a
twisted configuration by changing the H axis to -H and the V axis to -V.
becomes
Constant Section
If the Set Area Constant check box is selected, the section parameters are calculated to keep the section
constant all along the bundle segment:
o
If Major Axis or Minor Axis are modified at one point, the section parameters are updated at
the other points or/and extremities to propagate this modification.
o
If Length or Width are modified at one point, the section parameters are updated at the other
points or/and extremities to propagate this modification.
Section Area
Section parameters and area are linked together: if one changes, the others are automatically updated. Section
Area is unavailable if the Set Area Constant check box is cleared.
For information on how section parameters are modified if the section area is changed, see bundle
segment profile options.
at Point.2 of Bundle Segment 2 (rectangular profile), you can import the profile of Bundle
Segment 1
(circular profile):
As a result, you get a circular profile for Bundle Segment 1 instead of the original rectangular
profile.
Import and Link Profile at Junction: copy the profile of the connected
bundle segment at the selected point, and link it to the profile itself, for example:
If the profile of Bundle Segment 1 at Point.2 (circular profile) is modified to ellipse, the
profile of Bundle Segment 2 will automatically change to ellipse.
Copy Profile across the Bundle Segment: copy the profile type of the
selected point to the other definition points of the bundle segment.
On any point which is not a bundle segment extremity, it allows you to:
When profiles have been linked by a previous import and link, it allows you to:
an
The profile at the second extremity of the first bundle segment is the same as the profile of the nearest previous profile.
The profile at the first extremity of the second bundle segment is the same as the profile of the nearest next profile.
And vice versa, when removing a branch point, the profiles at the location of the branch point are removed:
2. Select the bundle segment you want to modify and click Branch Definition
Protective coverings do not handle multiple profiles. They can be applied to circular profiles only.
The radius of the profile for tape is computed this way:
Radius = sqrt(Max(Area)/PI)
where PI = 3.14159...
and sqrt = square root.
Adaptive support formula behaves this way:
ELEC-SUPPORT-RADIUS = sqrt(Area_ave/PI)
If no wires nor wire groups are routed, bundle segment stiffness is based on individual bundle segment flexibility
If wires and wire groups are routed, bundle segment stiffness is based on the properties of the wires and wire groups. In this case,
Legend:
standard algorithm: yellow
Protective coverings add stiffness. This is taken into account by the FLEX algorithm.
Standard algorithm:
FLEX algorithm:
Internal splices add stiffness. The FLEX algorithm takes into account the values for the length and equivalent thickness attributes entered
when defining splices in Electrical Library.
Notes:
You will need to recompute all bundle segments to take into account modifications to length and equivalent thickness of reference
internal splices, and if you replace an internal splice by another.
These functionalities require a FLEX Physical Simulation license.
For more information on this product, see Flex Physical Simulation Overview.
These functionalities are accessed by setting the bundle segment computation mode to FLEX algorithm and adjusting the balance slider.
Systems > Electrical Harness Discipline > Electrical Harness Installation > Harness Management
tab
The Electrical Harness Assembly workbench switches to the Electrical Harness Installation workbench. The Branch Definition
dialog box opens.
For information on standard options in the dialog box, see Creating a New Multi-Branchable Document and First Branch.
Note that the final slack, length and bend values may not exactly correspond to the user input due to the fact that the FLEX
algorithm is a finite-element algorithm. If this is the case, it can be seen when you change the build mode.
6. Click Apply in the Branch Definition dialog box to compute the bend radius.
Another build mode becomes available after you have routed a bundle segment: Constrained length
In this mode, you can set the percent tolerance permitted between the initial and final bundle segment length. For example, if
you set this value to 1 and the bundle segment is 100 mm long, then a final length of 101 mm will be tolerated.
Note: In Constrained Length mode, the default accuracy is set to a very high value so that same bundle segment length can be
maintained. The value set for the balance slider is not taken into account.
A message informs you if the modification in bundle segment length exceeds the tolerance and identifies for which branch
this is the case.
This build mode is recommended once you are well advanced in your design because, in this mode, you cannot:
o
add slack, supports, devices or branch points
o
split bundle segments
o
o
since these actions impact the length of the bundle segment and CATIA cannot figure out how the user intends to modify this
length.
7. Click Bundle Segment Definition and set bundle segment parameters in the dialog box that opens.
The Bundle Segment Definition dialog box opens. A Flexibility slider has been added in the right-hand pane of the dialog box:
This slider lets you set a value between 1 and 5 to define individual bundle segment stiffness. The lower the value, the stiffer the
bundle segment.
Important: This value is not taken into account if wires and/or wire groups have been routed. In this case, bundle segment stiffness
is based on the properties of wires and/wire groups.
8.
If you update branches with internal splices that were designed in earlier releases, the branch shape may be slightly different from
that obtained previously because the FLEX algorithm takes internal splices into account.
Flex Definition
A flex is represented by a:
Cross-Sections
Only orthotropic cross-sections are supported
An orthotropic cross-section has two symmetry planes meaning the shear section has to fit with the centroid of the section.
The images below illustrate the various orthotropic cross-section types:
circular cross-section
rectangular cross-section
annular cross-section
Material properties
Flex Physical Simulation product exhibits particular local deformation modes (behavior) of the flex:
These are examples of more or less flexible flex subjected to gravity with ends imposed to displacements.
Legend:
yellow:
standard algorithm
EHI
Branches
in V5R12 Onwards
This task explains how documents containing branches created in V5R10/R11 are managed:
These branches are edited as in the previous versions.
You will be able to add other branches to such documents as if they were originally multi-branchable documents.
Editing a Branch
Open a document containing branches created in V5R10 or V5R11.
1. Select a branch.
2. Click Multi-Branchable Document
The Branch Definition dialog box opens allowing you to edit the branch selected.
3. Click OK to validate.
Adding a Branch
Open a document containing branches created with V5R10 or V5R11.
Nothing is selected in the geometry.
1. Click Multi-Branchable Document
A branch is created and the dialog box opens allowing you to define the parameters:
The Branchable document becomes a multi-branchable one (although its name is not changed by the application) and the new
branch is created under this one.
A product which doesn't result from the New Component command (inline product).
BundleSegment1 includes:
o
The Bundle Segment1 part that becomes active
o
The Flexible Curve.1 belonging to the part, which at this time, does not have any geometrical representation
o
The Electrical Harness Assembly workbench switches to the Electrical Harness Installation workbench and the Bundle Segment
Definition dialog box opens letting you define segment parameters. The Bundle Segment Definition command
is active.
As an alternative, you can select the Bend Radius Ratio option and set the ratio: the Bend Radius is automatically computed.
5. Select the Mode: for example Slack and give a percentage of slack.
The different options are:
o
Slack:
The bundle segment length is increased by the percentage indicated in the Slack(%) field. The Length box is unavailable.
o
Length:
The bundle segment length is indicated in the Length field. The Slack(%) box is unavailable.
o
Bend:
The bundle segment length corresponds to the minimum distance between the points defining its route. The Slack(%) and
Length boxes are unavailable.
6.
At this stage, bundle segment parameters are defined.
You now need to route the bundle segment to be able to complete the definition. This operation creates the geometrical representation of the
Flexible Curve.
Note that OK and Apply are deactivated.
See Defining the Segment Route which explains how to route bundle segments.
When you create a bundle segment on surfaces (keeping associativity between the bundle segment and the underlying part):
o The Bundle Segment on Surface option is activated and lets you change the side on which the bundle segment will be
created.
To do so, click Reverse.
o The bend radius and the build mode parameters (Mode, Slack(%) and Length) are not taken into account. These parameters
are unavailable.
Local slack management is not taken into account. Hence, this command
is unavailable.
When you create a bundle segment between points created on-the-fly, slack management is not taken into account either.
This section explains the different ways you can route branches and/or bundle segments.
Routing segments between points, devices and supports (branches and single bundle segments)
Routing segments between points created on-the-fly (branches and single bundle segments)
Routing branches along external curves
Routing single bundle segments on surfaces (this method keeps the associativity with the underlying part)
Creating Construction Constraints to know how to create points used when routing segments
Routing Options
Collapsed Geometry for Bundle Segments and Protective Coverings
Associativity
To take advantage of the associativity between the construction points or part and the bundle segment, make sure the following option is selected:
Open the Tools > Options menu.
Select the Infrastructure > Part Infrastructure item.
In the External References frame of the General tab, check the Keep link with selected object option.
shows that the pointed geometry element (i.e a surface, a device) is in visualization mode. Click once the geometry element, to switch to edition
mode.
Note: Working in Cache mode, the bundle segment does not display the icon.
Methodology
More particularly, when you add slack to branches (using Add Local Slack
If the branches are created from the center to the outside of the network
):
Then, when you add slack to one branch (in red below):
This task shows how to define the construction points which will be used when routing the bundle segment to build the Flexible Curve
geometrical representation.
They can be:
Construction points
Points on part surfaces.
The construction points or parts can also be located in another part of the assembly.
Make sure the following check box is selected to take advantage of the associativity between the construction points or part and the bundle
segment.
4.
The construction constraints can be any structure elements (i.e. a plane structure).
You can route branches and single bundle segments using this method. This task focuses on the branch.
Also in this page:
Changing a connector
The multi-support
c.
d.
5. Click OK to validate.
The Route Definition dialog box closes and the Branch Definition is displayed afresh.
You can take advantage of the Related Objects viewer to focus on an object and see how it is constructed via its related objects. The
related objects command identifies the parent, any children or connected objects and the relationship between objects.
When routing between construction points, only bundle segment extremities are published. Intermediate route points along bundle
segments are not published. If these are required, the user should publish them manually in the Part Design workbench (Tools >
Publications).
You cannot route a new branch between intermediate route points of an existing branch. You can only select segment ends of an
existing branch.
The selection is only possible in the geometry: the closest connection point to the selection point is taken into account for the bundle
segment route.
and the selection is possible both in the specification tree and the geometry.
The system automatically selects the bundle connection point (for connectors and back shells) or the entry point (for supports) as if they
were selected in the geometry.
Changing a Connector
When changing a connector in the Route Definition dialog box, it's possible that you modify the branch/bundle segment orientation without
noticing it:
Note that the selected option comes back to the default value: Add after.
Otherwise, the blue connector would be added to the network after Point.1 and the branch/bundle segment orientation would
be changed, as shown below:
Routing Segments
between Points Created On-the-Fly
This task shows you how to route branches between points created on-the-fly. You can also route single bundle segments on surfaces using
this method.
Note that it is possible to route branches/bundle segments on different surfaces preserving the bend radius definition.
Since you are routing the branch/bundle segment on a surface, the associativity is not maintained.
The Bundle segment on surface option is not available with this function.
But you can change the side on which the bundle segment will be created on the surface using the Shift key.
It is possible to add or remove construction points or tangents instantly using the corresponding options. See Routing Options.
This command also works in Visualization Mode so you do not need to load the context in design mode.
Open a new product document.
Select the Insert > Existing Component... item, and choose the FreeEdges1.CATPart document.
The path to this sample is: .../online/cfysm_C2/samples/FreeEdges1.CATPart.
1. Change the Product1 document into a geometrical bundle using Geometrical Bundle
2. Click Multi-Branchable Document
The Electrical Harness Assembly workbench switches to the Electrical Harness Installation workbench.
The Branch Definition dialog box opens.
Enter the value of your choice for the different parameters.
3. Click Route Definition.
The Route Definition dialog box opens:
4. Press the Ctrl key and move the pointer along the geometry to display a manipulator and the tangent direction as shown:
This manipulator follows the surface when you move its position.
It shows a point pre-positioned perpendicularly to the surface, with a distance to this surface equal to:
o
the radius in Automatic mode,
o
the specified value in Manual mode,
the radius increased with the safety margin value in Automatic with safety margin.
These modes are visible on clicking the More >> in the Route Definition dialog box.
a.
Click successively where you want to define the flexible curve.
3. Click OK to validate.
The Route Definition dialog box closes.
The radius of the flexible curve is increased with a safety margin value.
If you want to define the route at a selected point with a different offset.
For example:
a.
You have started to draw the curve with the automatic offset, using the Ctrl key.
c.
Note: You can change the mode for only one point or more.
d.
6. Click
e.
OK to
7.
In Automatic mode, a branch/bundle segment with a circular profile will keep in contact with the surface when the branch/bundle
segment is modified.
For other profile types, the branch/bundle segment offset will be equal to an equivalent radius computed as follows:
In Automatic with safety margin mode, if a protective covering exists, the offset equals the radius (or equivalent radius in the
case of non circular profiles) of the current bundle segment plus the thickness of the protective covering plus the safety margin
entered by the user.
The branch/bundle segment will not keep in contact with the surface if the surface is modified.
Bundle segment geometry is created with the selected curve as center curve.
You can add branch points anywhere along the curve.
Some parameters are unavailable:
o
o
Bend radius
Build mode (slack,
length, bend)
Since the branch center curve is a predefined curve, these parameters are no longer pertinent.
Electrical connections are automatically created if the ends of the external curve correspond to bundle segment extremities.
Electrical connections are created only in the branch definition command.
If the ends of the external curve are modified, no electrical connection update is done.
The Electrical Harness Assembly workbench switches to the Electrical Harness Installation workbench.
The Branch Definition dialog box opens:
3. Click the External Curve box and select the curve in the geometry (Part.1):
Reminder: if you are working in Visualization mode, double-click Part.1 to display the curve.
7. Add other branches to join the branch you just defined to connectors.
Click Branch Definition
.
The dialog box opens. Fill up the parameters of interest.
a.
b.
Click Route Definition and select the objects of interest to define the route of the branch.
c.
Click OK to validate.
d.
8.
This tasks shows you how to route single bundle segments on part surfaces, keeping the associativity with the underlying part.
The FollowOnPart.CATProduct document is open.
The construction constraints have been defined previously.
The Bundle Segment Definition dialog box is still open.
You cannot route branches on part surfaces using this scenario.
Refer to Routing Segments between Points Created On-the-Fly.
The bundle segment route is associated to the part.
As a consequence, if the part is modified, the bundle segment is updated.
It is possible to add, remove or modify construction points or tangents instantly using the corresponding options.
When you create a bundle segment on a part,
o the Bundle Segment on Surface option is activated and lets you change the side on which the bundle segment will be
created.
To do so, click Reverse .
o Bend radius and Build mode parameters (Mode, Slack % and Length) are not taken into account.
o
Local slack management is not taken into account either (Local Slack
is not available).
3. Click successively the three points in the geometry to define the flexible curve.
4. Click OK to validate.
The Route Definition dialog box closes.
The Bundle Segment Definition dialog box is displayed afresh.
Note: At that time, you can use Reverse to create the bundle segment on the other side of the surface.
5. Click OK to validate the bundle segment definition.
Note: Two extra points have been created: they are the bundle segment extremities (Point.5 and Point.6).
The bundle segment is added to the specification tree: the Curve is created.
4.
The bundle segment route is associated to the part. As a consequence, if the part is modified, the bundle segment is updated.
Routing Options
Add a point, a device or a support before or after the object selected in the list, using the corresponding option,
o
Select an object in the list.
o
Select Add before.
o
The object (here a point) is added to the flexible curve before the object selected
in the list (here the multi-support).
Replace a component selected in the list with another one, for example the other connector of the equipment:
o
More >>
options
Select a device:
By default the flexible curve is built with tangency condition. Click the red arrow
to reverse the tangent direction.
You can remove or reverse the tangent using the corresponding command buttons.
Select a support:
Orientation management:
Click Reverse to change the tangent direction.
Positioning management:
Select a point:
Tangent management: Explicit
1. Select Explicit as Constraint type.
2. Click a face as Tangent direction.
The tangent is added.
You can remove or reverse the tangent using the corresponding command buttons.
Slack management:
This option is available when routing bundle segments (branchable or normal ones) on a surface using a manipulator.
the flexible curve follows the surface with an offset equal to the
bundle segment radius. This is the default value.
Automatic:
You can change to Manual if you want to define the route at a selected point
with a different offset.
Collapsed Geometry
for Bundle Segments and Protective Coverings
Before V5R15, it was not possible to design a self-intersecting bundle segment.
The bundle segment geometry using a spline with a minimum bend radius smaller than the diameter of the circle was not supported.
CATIA raised a twisted configuration error during update.
These errors can become very troublesome during harness design for these reasons:
After wire routing, bundle segment parameters (Minimum Bend Radius, Diameter) are updated according to the wire list and the
designer is not able to control the geometry creation.
When an error occurs during update, the system stops updating until the designer repairs the problem found. On a big harness it can
really take long time to fix every single problem.
In some specific design cases, collapsed geometry can represent physical situation.
Hence this capability improves the productivity (no more update errors to solve), eases V4 to V5 migration (V4 bundle segments were
more permissive as not integrated in V4 drawing generation) and also enables some real design cases not supported by previous CATIA
releases.
1. The creation of self-intersecting geometry for bundle segments and protective coverings is possible.
2. As it is now supported, when the Minimum Bend Radius is smaller than Diameter in the branch definition dialog box, a warning
pops up:
Working Method
R14 Protective Covering Instantiated in R15
You first need to properly upgrade the reference part in the catalog.
Otherwise the instantiated protective covering will not support the collapsed geometry.
If the bundle segment creation is impossible because of a violation of the minimum bend radius rule, a message warns you that a
computation error occurred, and shows the construction constraints causing the error.
Nevertheless if you validate the bundle segment creation using these construction constraints, the Flexible Curve icon is modified in the
specification tree to show that it is invalid:
You can then modify the bundle segment parameters or the construction constraints.
Add a support: Click Add Support and select the bundle segment you want to route into a support.
Remove a support: Click Remove Support and select the bundle segment to remove from the support.
Arrange bundle segments in supports: Click Arrange Bundle Segments, select a support then reposition bundle segments.
Copy the bundle segment arrangement: Click Copy Bundle Segment Position, select a support then click anywhere in the geometry area.
Route bundle segments through retainers: Click Route Definition in the Branch Definition dialog box and select a retainer
Adding a Support
This task shows how to route bundle segments through supports.
This command also works on multi-supports and retainers.
This example uses a support, but it works exactly the same with a retainer.
You are prompted to select the bundle segment you want to drive into the support.
CATIA finds the closest bundle segment construction point according to the selection point.
2. Select the bundle segment close to the location of interest.
The extremity or construction point is highlighted:
>>
select a label
If the selected point is not an extremity, the bundle segment will go through the
support between this point and the next one.
The options are therefore unavailable as in this example.
You can change the bundle segment direction through the support by reversing the
arrow.
If an extremity is selected, you can choose where you want to place the support
along the bundle segment route:
o
beyond the selected extremity,
o
Note: In case of a multi-support, if you select the support instead of a label, the section selected is the closest to the selection point
on the support:
>>
4. Change the option if needed.
5. Click to invert the arrow in the geometry or in the dialog box, if needed.
6. Click OK validate your choice.
The bundle segment route is recomputed.
The result looks like this if you select the label of Section1:
7.
You can add a support to a bundle segment even if it is covered with a protective covering.
Removing a Support
This task shows how to remove the bundle segment from the support, therefore modifying its route.
The InSupport.CATProduct document is still open.
You are prompted to select the bundle segment you want to remove from the support.
2. Select Bundle Segment1.
The way through the support is highlighted:
This command cannot be used for retainers and adaptive supports since bundle segments are automatically positioned in these
supports and cannot be re-arranged.
Note: Rotating a support along the support axis does not affect the bundle arrangement. This means, however, that some bundle
segments may be positioned outside the rotated support. If this occurs, you can re-arrange segments manually or, propagate the
arrangement of an un-rotated support.
A message appears to this effect when you select this command. Click OK to continue.
You are prompted to select a support.
2. Select a support.
The Arrange Bundle Segments dialog box appears. Bundle segments routed through the selected support are listed.
When the Reframe button is clicked, the view point is modified so that the user can rearrange the segments more easily by having
a face view of the support.
When you select the support and click on the Arrange Bundle Segments icon, the view point is modified
automatically and at the end of the command, the initial view point is retrieved.
Selecting the Show advanced parameters check box in the Arrange Bundle Segments dialog box displays the parameters of
the bundle segment in the geometry area.This option is selected by default.
o
o
o
If you select a support that has been created previous to V5R17, a warning message is displayed.
If you want to convert a support created previous to V5R17:
Open the support in the Electrical Part Design workbench.
Click Define Support Part
The support does not contain any orientation line. Do you want them to be created
automatically now?
Click Yes to convert the support. Else click No.
Select the Electrical Harness Assembly workbench, and click Arrange Bundle Segments
If the selected support has a Published Ref Line (displayed in the specification tree),
but the bundle segment point on this support is still a Point on Plane, we identify it as a converted
support.
Selecting the converted support should automatically migrate the original arrangement
to the new model.
3. Click Reframe to center the 3D view on the selected support and set the support parallel to the screen.
4. Select the Activate/Deactivate clipping plane check box to better visualize the selected support.
U and V axes are displayed in the geometry area. The origin of the 2D U,V axis system is positioned on the center of the support.
The outer and optimum diameters are also displayed.
When the clipping plane is activated, a circle is displayed to highlight the cross-sections of each passing segments. These crosssections will get the color of their irrespective segment.
When the clipped view is rotated, you can observe that the centre curves of the bundle segments temporarily disappear.
o
o
o
The circles representing each segment sections, will have a diameter equal to the diameter of the larger
covering protection at the support location.
The manipulators move freely in all directions, but the U and V parameters value are still displayed in the 3D
as well as in the dialog box.
The segment geometries are updated only after clicking the Apply button. This improves the overall
performances.
The Outer diameter of all bundle segments routed through the support.
It is computed as follows: Outer diameter = 2*Max (distance (O, Oi) + Ri)
where:
O is the center of the support
Oi is the center of bundle segment i
Ri is the radius of bundle segment i
The outer diameter represents the smallest circle whose center is O that contains all bundle segments routed through
the selected support.
This value is updated each time the U,V parameters are changed.
The Optimal diameter is computed as follows:
This value takes into account the deformation of bundle segments when tied together in a support.
Note that protective coverings are not taken into account for computed diameters.
5. In the geometry area, move the bundle segment to the desired location inside the support.
Use the green tool to assist you move the bundle segment to the desired location along U and V axes. This tool
is positioned on the center of the bundle segment. U, V parameters give the distance of the bundle segment
from the center of the support.
The bundle segment arrangement can only be propagated to other supports in the route provided they
contain the same bundle segments and are of the same type (i.e. same part number). Supports meeting
these conditions are listed in the dialog box. They are also identified by a Propagate ON label in the
geometry area. You can choose to individually propagate the arrangement to some of these supports.
o
Propagate OFF
A contextual menu in the Propagate Arrangement list also lets you toggle the status from ON to OFF and
vice-versa.
9. Optionally, select Propagate to keep the same bundle segment arrangement in all selected supports in the route.
10. Click OK when done.
This task shows how to copy the bundle segment arrangement from one support to other supports in the route.
Note: This functionality applies to multi-branchable documents only.
1. Click Copy Bundle Segment Position
You are prompted to select a support. This support is the reference support; the bundle segment arrangement in this support will be
copied to all other selected supports in the route, provided they contain the same bundle segments and are of the same type (i.e.
same part number).
3D text is displayed in the geometry area to assist you:
o
Green text Propagate ON identifies supports that can be re-arranged. Double-clicking the text changes the label to
; the support will retain the previous arrangement.
Red text Propagate OFF identifies supports that cannot be re-arranged.
Propagate OFF
o
This command does not support retainers and adaptive supports since bundle segments are automatically positioned in
these supports and cannot be re-arranged.
2. Optionally, double-click Propagate ON labels to toggle them to Propagate OFF to retain the original arrangement.
3. Click anywhere in the geometry area to propagate the bundle segment arrangement of the reference support to all other selected
supports, and exit the command.
This task shows how to define a multi-base retainer, then to route bundle segments using it.
Open the multibaseretainer part document.
workbench.
For more information, refer to Electrical Library User's Guide (User Tasks - Creating Supports - Creating Retainers).
Repeat these steps for the second side.
Note: The Second Plane Definition is already set and cannot be changed.
The specification tree shows that the publications are created with the specific retainer parameters: EHISUPPORT-RefBasePlane.1
and EHISUPPORT-RefBasePlane.2.
workbench.
6. Insert your part to this product, using the contextual menu: Components >
Existing Component...
again.
Click OK to validate.
When you select the retainer, CATIA finds the closest entry point for the branch, according to the selection point.
13.
When you route a bundle segment over a retainer:
o
o
o
o
o
o
The formula is automatically generated under the root product of the document, if the EHISUPPORT-RefBasePlane publication is
detected:
When the diameter changes, the bundle segment is re-computed according to this formula, to keep in contact with the retainer base
plane.
Using retainer and protective covering:
If the bundle segment is protected by a protective covering, the formula that computes the distance between A and B takes into
account the thickness of the covering.
AB = bundle segment radius + protective covering thickness
The limit points of the protective covering are modified so that it is added to or removed from the retainer.
Note that:
Only one section of bundle segment can be taken into account to be kept in contact with the retainer base plane, whatever the
diameter is. This means that a branch point created in the middle of the retainer only allows one side of the bundle segment to be
updated with the correct diameter.
It is not possible to hold concurrently the properties of a retainer and a standard support: either the base plane is taken into account
to route the bundle segment or it is the entry point and planes only. The part below cannot be used as a retainer and a standard
support.
The retainer component is fully integrated in the Electrical Harness Flattening workbench.
2. Click the bundle segment where you want to modify the slack:
Two construction points are highlighted: they delimit the portion of the bundle segment selected.
again.
o
o
8.
Slack is always added between the point selected and the following one according to the construction order.
To adjust slack on individual branches without impacting other branches in the same network, see Managing Slack at Junctions.
You can modify a slack at a specific location on a bundle segment even if it is covered with a protective covering.
Harness Covering
Dedicated commands let you to add protective coverings over bundle segments as well as change the default relationships between protective
coverings, adaptative supports, retainers and bundle segments.
Instantiating Protective Coverings
Adjust relationships between harness covering components
workbench.
If you want to privilege performance and ease-of-manipulation, use Light Protective Covering.
If you want to add protective coverings to several branches, or across different multi-branchable documents, use Protective
Covering.
If you want to privilege performance and ease-of-manipulation, use Light Protective Covering.
If you want to add protective coverings to several branches, or across different multi-branchable
documents, use Protective Covering.
There are four types of light protection coverings:
o Fixed Diameter
o Adaptive Diameter
o Corrugated tube
o Tape
There are two types of regular protection coverings:
Corrugated tube
Tape
Tape Parameters:
Parameters specific to the tape type of protective covering:
Note:
The taping angle and the overlapping parameters are mutually exclusive:
either you enter a value for the taping angle and the overlapping will be automatically
computed,
or you enter a value for the overlapping and the taping angle will be automatically computed.
The overlapping value can be negative.
where:
Angle is the taping angle value.
Height is the bundle segment length
NbLayers is the number of layers.
About Supports, Bend Radius, and Integration With Other Electrical Products:
Supports can be added to bundle segments covered with a protective covering. If the support is
adaptative, its parameters will be linked to the protective covering outer diameter.
The protective covering bend radius is not taken into account when computing the bundle
segment using the standard algorithm. It is only used with the FLEX algorithm.
However, this parameter lets you create knowledge rules.
This functionality is integrated with the wire routing (EWR): when routing wires into bundle
segments covered with a protective covering, the bundle segment diameter updates as well as
the protective covering's.
This functionality is also integrated with the drawing extraction (EHF): the protective coverings
are displayed in the drawing sheet.
2. Select the catalog then the Protective covering you want to instantiate.
You can instantiate protective coverings created using both the Define Protection Product and the Define Protection
Part commands in the Electrical Library workbenches. However, if you use Define Protection Part, the customization
of the reference part is not kept when instantiated.
a.
Open the catalog browser:
To do so:
1.
Click
The catalog browser closes and the selected protective covering displays in the upper right corner of the primary window.
If the Enable Sourcing access option is selected in the Tools > Options > Equipment & Systems > Electrical
Harness Discipline > Electrical Assembly Design > General tab, the Collaborative Enterprise Sourcing (CES)
environment is enabled, and the Sourcing Search dialog box is displayed instead of the Catalog Browser dialog
box.
For a given part number defined in iXFElec file, there must be one and only one part found after the query on
Internal Item Number criteria, else there would be an ambiguity.
b.
from the toolbar, select the protective covering then drag and drop
Supports can be added to bundle segments covered with a protective covering. If the support is adaptative, its
parameters will be linked to the protective covering outer diameter.
c.
3. In the specification tree, select one or more bundle segments to be covered with the protective covering.
o
In case of multi-selection, the bundle segments must belong to the same branch.
You can select normal bundle segments, as long as they are contiguous.
Light Protective Covering is a feature of a multi-branchable document, and it covers bundle segments in one
branch only.
The Protective Covering Information is updated in the dialog box, and the protective covering start and end points are
displayed in the geometry.
2.
Drag the Start Extremity or End Extremity label to modify the location of the internal protection.
o
o
o
o
1.
It lets you define the new position for the extremity from the reference point.
2.
3.
2. The light protective covering is added as a separate feature to the specification tree under the multi-branchable feature:
Light Protective Coverings integrate the collapsed geometry behavior (as applicable for external protections).
When you instantiate a customized internal protection (consisting of user defined parameters, relations, or rules), these
parameters, relations or rules are added to the specification tree (under internal protection node). A view of the specification
tree shows these parameters and relations added under the Product1.1 node:
It lets you:
o
o
o
choose the protective covering reference you want to apply, using the catalog browser,
select the bundle segments on which the protective covering will be applied,
remove bundle segments from the selection
You can only instantiate protective coverings created using the Define Protection Part command in the Electrical
Library workbenches.
a.
Open the catalog browser:
To do so:
Click
.../online/cfysm_C2/samples/ElectricalSession/catalog.
The catalog browser closes and the selected protective covering displays in the upper right corner of the primary window.
from the toolbar, select the protective covering then drag and drop it
c.
2. Select one or more bundle segments to be covered with the protective covering:
Notes:
In case of multi-selection, the bundle segments must belong to the same geometrical bundle.
You can select both normal bundle segments and branches , as long as they are contiguous.
The dialog box updates and the protective covering start and end points display in the geometry.
the protective covering turns to red informing you that it needs to be updated.
3. Click OK to validate the re-limitation of the protective covering.
o
Notice that the adaptative support is still placed over the corrugated tube, and under the protective tape.
5. Adjust the adaptative support so that it is placed on top of the protective tape you have just extended.
6.
Important
You cannot place a single protective covering over several bundle segments.
You cannot place supports over other supports.
By default, standard supports and corrugated tubes are the outermost components. However, protective tape can be placed over
these components using the Adjust command.
You can only place light protective coverings over light protective coverings in the same multi-branchable document. You can also
only place regular protective coverings over regular protective coverings.
Protective coverings have a uniform circular shape over the entire length of the covering. This means that:
o
The shape of protective coverings does not change to match the shape of other protective coverings or supports that
are placed over it:
The inner diameter of corrugated tube does not change to match the different diameters of a bundle segment. The
diameter remains constant.
where PI = 3.14159...
and sqrt = square root.
Unlink bundle segments: Click Unlink and select a bundle segment extremity to unlink all the elements.
If the Geometrical link option is not activated, only the electrical link is created.
1. Click Link
You are prompted to select the bundle segment you want to connect.
CATIA finds the closest bundle segment extremity according to the selection point.
CATIA finds the closest bundle connection point according to the selection point.
A message is displayed asking you to confirm the selection.
4. When you are satisfied, click OK validate your choice.
The bundle segment is computed.
The result looks like this:
You are prompted to select the bundle segment you want to connect.
You must choose first the bundle segment which is not following the part.
Otherwise the construction is not possible.
2. Select Bundle Segment1 close to the extremity to be connected.
>>
c.
Click the Tangent direction field and select the bundle segment flexible curve as shown
below:
d.
6.
o
o
in the 3D view:
3.
For more information, refer to Viewing Related Objects.
You can create a connection between a bundle segment and a device, or between two bundle segments even if the
bundle segments are covered with a protection.
This task shows how to delete a connection between bundle segments or between a connector and a bundle segment.
This applies to multi-branchable and single bundle segments. However, you cannot unlink bundle segments within a branch.
Open the Link.CATProduct document.
1. Click Unlink
You are prompted to select the bundle segment extremity you want to disconnect.
o
o
CATIA finds the closest bundle segment extremity according to the selection point.
Move the mouse over the bundle segment that is already linked:
All the bundle segment extremities connected to the selected bundle segment are highlighted.
A yellow circle with a Connected Extremity label is displayed at the extremities.
2. Select the bundle segment you have just disconnected: Bundle Segment1
You can see that the connector is no longer connected.
in Tree view:
in 3D view:
3.
For more information, refer to Viewing Related Objects.
You can delete a connection between bundle segments or between a connector and a bundle segment even if the bundle segments are
covered with a protection.
You can add or remove branch points from branches via commands in the Bundle Segment Definition dialog box and in the Electrical Harness
Assembly Management toolbar. You can also delete unused branch points via the contextual menu.
Connecting Segments
Connect segments at branch points: Click Multi-Branchable Document or Bundle Segment, define segment parameters then when routing
the segment, select a branch point.
and remove
See also Modifying the bundle segment or protective covering geometry and formulas.
Branch points can be added to or removed from the original branch.
The tangent continuity is maintained between the segments.
You can also connect other segments at branch points and manage the bundle segment diameter and color for each section.
You've already created a multi-branchable document.
The Branch Definition dialog box is still open.
1. Click Bundle Segment.
The Bundle Segment Definition dialog box opens:
Name
Diameter
Color.
5. Click a point on the curve where you want to create a branch point.
The bundle segment, here Bundle Segment.2, has been created as well as the branch point, here Point.4.
Note: Since you cannot place a single protective covering over several bundle segments, any protective covering would be trimmed
to cover the original bundle segment (Bundle Segment.1) only.
The Extremity Management becomes available where you can modify the coordinates.
The Visualization Management allows you to reframe the geometry on the selection.
7.
As a branch point has been added, the branch consists of two sub-branches that can have different parameters. Those sub-branches share the
same centerline and are stored into the same CATPart document.
The branch point is not fixed as a bundle segment definition point but placed directly on the centerline. Thus, when modifying the
If you double-click the the selected branch point as shown above, you will activate the Point Definition command of the Generative Shape
Design workbench.
This allows you to modify the point position, but out of the electrical context. In this case, the adaptative support will not be updated to the
new bundle segment parameters.
Using the dedicated command, the extremity management lets you modify the branch point position:
When you validate the entries made, the result looks like this:
A message displays:
3. Click OK to validate.
The branch point is removed and the two bundle segments on both sides of the branch point are merged.
Open a document containing at least two branches connected through a branch point, optionally wires and/or splices.
1. Select the branch you want to delete in the specification tree: here Branch 2.
2. Click Delete Special
Since there are objects in the branch you want to delete, this first dialog box opens:
Otherwise this step is ignored.
Click OK to validate.
The result looks like this:
to remove the unused branch point and indicate which selection you want to keep:
If you select Current side, the bundle segment and the branch point highlight.
Click OK to validate.
The result looks like this:
If you select Other side, the bundle segment and the branch point highlight.
Click OK to validate.
The result looks like this:
The resulting bundle segment keeps the properties of the selected section.
4.
If the branch point is used in a specific case of configuration, the Keep unused branch point option may be useful in order to avoid
unexpected deletion.
For example, if the same branch point is used for different configurations and if you work on a resolved configuration, which does not
include it.
This functionality only works for multi-branchable documents and branches, not for single bundle segments.
You can select a branch to delete even if the branch is covered with a protective covering.
3. Select the reference point either in the specification tree or in the geometry.
Click Other Extremity to change the reference point to the branch other extremity.
4. Define the distance to the reference object either in the dialog box or in the geometry.
In the dialog box you can define the distance:
5. Click OK to validate.
This task shows you how to remove branch points using the dedicated command.
It is also possible to access this function through the Bundle Segment Definition dialog box.
Open a document containing a branch with several branch points.
1. Click Remove Branch Point
.
You are prompted to select a bundle segment.
2. Click the bundle segment close to the branch point you want to remove.
CATIA finds the closest bundle segment extremity according to the selection point.
The branch point is highlighted.
A message displays:
3. Click OK to validate.
The branch point is removed and the two sub-segments on both sides of the removed branch point are merged.
Note that when you select a bundle segment to remove a branch point, the closest one is highlighted and proposed for deletion. When you
validate the merged bundle segments keep the properties of the bundle segment originally selected.
Splitting Branches
This task shows how to split a branch into two. A new branch is created.
This operation may prove useful in the context of the configuration management in ENOVIA: It allows you to prepare the transfer of a
branch to another multi-branchable document.
Refer to Split and Transfer Usage.
This scenario is available for branches in multi-branchable documents only.
Create the necessary branches using the DemoGS.CATProduct document.
It looks like this for example:
1. Click Split
You are prompted to select the bundle segment in order to define the branch point on which you want to split.
2. Select the bundle segment as shown below:
The branch point is highlighted and the Split dialog box opens:
At this step, you can choose to split the branch at the highlighted branch point or to create a new one.
o
o
CATIA finds the closest branch point according to the selection point.
In case there is no branch point available, CATIA proposes to create a new one.
You are prompted to select the bundle segment on which you want to create the branch point.
5. Select the bundle segment as shown below:
6. Enter 0.25 for example for the ratio and click OK to validate.
How is it done?
Before the split, the branch 1 (Branchable 1) is composed of three segments between Connector-A3 and Connector-A1:
Specification tree
During the split, the branch point is isolated from the flexible curve (and becomes a point with coordinates: Point.10).
Branchable 1 is split into two branches:
o Branchable 1, re-limited to Point.10 with two segments (Bundle segment 1 and Bundle segment 2)
o Branchable 1.1 created between Point.10 and Connector-A1 with two segments (Bundle segment 4 coming from
Branchable 1 and a new Bundle segment 5).
Branchable 1
Specification tree
The two branches now have their own curves and parameters such as bend radius, diameter, etc. They can be edited separately for each
branch.
You can split a branch even if it is covered with a protective covering.
1. Click Split
You are prompted to select the bundle segment in order to define the cutting point.
o
The bundle segment will split using a construction point.
o
CATIA finds the closest bundle segment construction point according to the selection point.
o
In case the closest bundle segment construction point is an extremity, CATIA uses the second closest one.
After the split, the tangent continuity between the bundle segments is maintained.
3.
Transferring Branches
This task shows how to transfer a branch (containing one or more bundle segments) to either a new or an existing multi-branchable
document.
This operation may prove useful in the context of the configuration management in ENOVIA: if you want to manage the effectivity at a
more detailed granularity level. Refer to Split and Transfer Usage.
This scenario is available for branches only.
Use the data generated in the Split scenario.
It looks like this:
Automatic: select the branch to transfer. It automatically selects all the branches connected to the closest
extremity of the first selected branch.
Network: select the branch to transfer. It automatically selects all the branches connected to the first selected
branch.
o
the branches to transfer:
To remove a branch from the list, select it and use Remove Selection.
the branch.
Note that OK remains unavailable as long as no multi-branchable document has been selected.
2. Choose the Selection mode, Automatic for example.
3. Select one or more branches you want to transfer: Branchable.1.1 for example
CATIA finds the branch(es) connected to the closest branch point according to the selection point.
4. For the transfer destination:
copy to the same geometrical bundle: keep Same
under a new multi-branchable document: select New.
5. Click OK to validate.
o
o
6.
Transferring all the branches of a multi-branchable document is not possible. At least one branch must be left in the original multibranchable document.
You can select a branch to transfer even if it is covered with a protective covering.
You cannot transfer a branch to another multi-branchable document if it is covered by an internal protective covering.
According to the configuration to be managed, it is then necessary to split the harness and transfer branches from one document to another.
These commands make these operations possible.
some documents are valid for all configurations: the blue document.
some documents are valid for certain configurations:
o for petrol: the blue and green documents
o
Duplicating Harnesses
This task shows you how to duplicate harnesses stored as workpackages (Document kept - Publications Exposed) in ENOVIA.
This command will prove useful for versioning and configuration purposes as well as when re-using existing harnesses.
This command is only available if the document you are editing comes from ENOVIA.
Open a document stored in ENOVIA.
1. Click Duplicate Harness
2. Select the geometrical bundle or the electrical bundle you want to duplicate.
You can select:
o
A geometrical bundle previously stored as a workpackage.
o
An electrical bundle, only if the common parent of the electrical bundle and its associated geometrical bundle
was stored as a workpackage.
If your selection does not meet the appropriate requirement, then an error message is displayed.
3. In the dialog box that appears, enter the suffix to add to new reference harness components.
The suffix is added to geometrical bundles, electrical bundles, multi-branchable documents and protective coverings, but not to
devices and supports.
A new window appears showing duplicated data. The window with the original data is closed.
4.
If you duplicated a geometrical bundle, a new geometrical bundle having the same content is generated.
If you duplicated an electrical bundle, a new document containing an electrical bundle and the associated geometrical bundle is generated.
Notes:
All instances of devices, supports, and wires from catalogs are re-instantiated in the new document.
All instances of multi-branchable documents, adaptive supports, and protective coverings generate new references that are
instantiated in the new document. All relations (constraints, contextual design and electrical connections) are kept.
This task makes use of the Electrical Harness workbench integration together with the 3D Tolerancing and Annotation product. It lets you
easily define and manage 3D tolerance specifications directly on the 3D or flattened harnesses.
This allows the user to add dimension information directly to the 3D mock-up so that they are available for downstream process. For
example, the contents of the 3D session can be sent to a harness supplier for manufacturing purpose and the dimensions to be respected will
be part of the data provided.
Curvilinear Dimensions
Note: To better visualize curvilinear dimensions, set the viewpoint perpendicular to the annotation plane. To
Normal View
do so, click
The new feature appears in the specification tree (xxx.Part for Construction Geometries)
Select Parallel.
Refer to 3D Functional Tolerancing & Annotation User's Guide - Basic Tasks - Creating Annotations - Creating
Curvilinear Dimensions to see the different view option.
Optionally, you can drag the dimension line and/or the dimension value to position them as wanted.
The second spline:
5. Click in the free space to validate and end the dimension creation.
The dimension appears in white.
The semi-arc symbol displayed over the dimension value symbolizes a curvilinear length dimension. You can now handle the
dimension just like any other dimension.
6.
will be proposed).
Selection of the first 3D curve after the selection of a starting point or planar face:
If the user selects a point or a planar face, he will then be prompted to select a harness routing spline.
Associativity
If an object taking part in the curvilinear dimension is moved in the 3D geometry area, the annotation is updated.
Electrical continuity
It is not possible to create a curvilinear dimension for bundle segments belonging to different geometrical bundles.
If you select points or planes, CATIA will find the best solution to compute the length the user intends to annotate:
Selection of a point:
o On the bundle segment centerline: this point will be used as an extremity of the annotated length.
o On a support: the projection of the point on the bundle centerline will be used as an extremity of the annotated length.
o On a connector: a straight line will be added to this point from the bundle centerline extremity.
Selection of a plane:
o On a support: the intersection point between the plane and the centerline will be used as an extremity of the annotated
length. If the selected plane does not intersect with the centerline, the plane is ignored.
o On a connector: a perpendicular line between the bundle centerline extremity and the plane will be added.
4.
command.
The other parameters calculation (center of gravity, inertia matrix, etc.) only depends on the geometry. They are generated by Measure
Inertia
the mass of the bundle segment is the sum of the mass of the wires routed through this bundle segment as well as the sum of the
mass of the internal splices connected to them.
the mass of the wire extra length used in the back shell is added to the mass of the bundle segment to which it is connected.
In case several bundle segments are connected to the same back shell, the mass of the wire extra length is added to the mass of the
bundle segment for each of them.
the mass of the branches is the sum of the mass of the bundle segments it aggregates.
the mass of the protective coverings (corrugated tube or tape) is calculated from the length and the linear mass, if this one is known.
Otherwise, no inertia equivalent is calculated and the default calculation (Measure Inertia command) is applied.
Open a document containing at least a geometrical bundle with wires and possibly protective coverings.
1. Click Measure Geometrical Bundle Inertia
.
This command computes the parameters needed to get the Mass and Inertia of the selected component.
2. Click the geometrical bundle or electrical bundle for which you want to calculate the inertia parameters.
3. Click Measure Inertia
a geometrical bundle,
an electrical bundle: selecting an electrical bundle calculates the equivalent parameters for all the geometrical
bundles linked to it.
The Measure Inertia dialog box expands to display the results for the selected item:
Note that the Equivalent field shows that three elements are taken into account for the inertia calculation.
Inertia Equivalents
This section deals with the following procedures:
If your document contains inertia equivalents set using Knowledgeware capabilities, then the Inertia command will not calculate the inertia
properties of the selected geometry but return the equivalent values.
The Equivalent box of the Measure Inertia dialog box indicates whether or not equivalents have been used:
Equivalent_COGz -25mm
Equivalent_MatGxx 50000gxmm2
Equivalent_MatGyy 50000gxmm2
Equivalent_MatGzz 50000gxmm2
Equivalent_MatGxy 0gxmm2
Equivalent_MatGxz 0gxmm2
Equivalent_MatGyz 0gxmm2
In Excel files, simply list property names and values in two separate columns.
6. Click OK in the Formulas dialog box. You are now ready to run your inertia calculation.
o
Having imported inertia equivalents, you no longer need the representations of the product or sub-products and
you can de-activate them (Edit > Representations). De-activated representations are unloaded. This frees the
geometry area and improves system response time.
o
To display parameters in the specification tree, select the Parameters checkbox Display in Specification Tree in
the Display tab of the Options dialog box (Tools > Options > Infrastructure > Part Infrastructure).
7.
This section explains how an existing CATIA V4 Electrical model is converted into V5 documents.
The conversion of the V4 data is performed using the migration batch.
It is divided into the following chapters:
Methodology
Migrating Step by Step...
V4 - V5 Mapping
Reference Information
Frequently Asked Questions
Methodology
To perform the migration of the electrical data (geometry and technology), you first need to set up options for the:
Migration batch
Bundle segment migration mode
Isolated mock-up solids migration.
Tools > Options... > General > Compatibility > Migration Batch
Tools > Options... > General > Compatibility > Electrical tab
and Tools > Options > General > Compatibility > V4/V5 Space.
tab
Refer to the Infrastructure User's Guide (Customizing Settings - General - Compatibility category).
Using Copy/Paste only copies the geometry and does not migrate the technology.
To do so, you need to access to the Batch Monitor:
1. Select Tools > Utility...
The Batch Monitor window opens.
2. Double-click the PLMV4ToV5Migration utility:
3.
Insure that all objects are set to 'AsSpec'as the migration as the migration is not supported by V4 electrical elements.
c. Select the file to be migrated from the File Selection dialog box and click Open.
d. Click on the Change Target Directory button to specify the location of the Default target directory.
e. Select the Target directory location and click Default button.
PLMV4ToV5Migration
dialog box.
m. Click Next
Multi-branchable document
It is recommended to use this option as it reduces the number of CATPart documents generated during the migration.
o
Isolated Mock-Up Solids (SolidM) means that they have no history nor specifications stored.
For the migration two options are available:
o
as CGR means that you will only get the meshing view (visualization mode).
as PartBody:
the SolidM conversion as PartBody means that you will be able to see the geometry of the solid to edit
it.
Refer to V4/V5 SPACE tab in Infrastructure User's Guide.
(Customizing Settings - General - Compatibility category).
b. Select as PartBody in the context of the electrical migration to be able to add technology.
c.
3. Once you have selected your options, click OK to validate.
You are back in the MigrateV4ToV5 dialog box.
4. Select a target directory (where the V5 documents will be created).
5. Select the V4 documents to be converted.
You are ready to migrate your V4 electrical data.
Select the files to migrate and the path for the result as explained in the utility documentation and run the batch.
For more information, refer to the V4 Integration documentation - User Tasks - Converting CATIA Version 4 Models into CATIA Version
5 in Batch Mode.
In Tools > Options > General > Compatibility > Migration Batch tab, specify CATIE3DMigration in Migration
Interface Name. For more information about this option refer to the Infrastructure User's Guide > Customizing > Migration
Batch.
In Tools > Options > General > Compatibility > V4/V5 SPACE tab, select Isolated Solids Mock-up migration option as as
PartBody . For more information about this option refer to the Infrastructure User's Guide > Customizing > V4/V5 SPACE.
In Tools > Options > General > Compatibility > Electrical tab, select the Shell Migration Mode to No, migrate
geometry only. For more information about this option refer to the Infrastructure User's Guide > Customizing > Electrical
Migration.
In Tools > Options > General > Compatibility > Electrical tab, Select Multi-branchable document option. For
more information about this option refer to the Infrastructure User's Guide > Customizing > Electrical Migration.
Once the options are set up, you can launch the migration batch.
For more information on the Migration Batch, also refer to the V4 Integration User's Guide - User Tasks - Migration in Batch Mode.
1. Select Tools > Utility...
The Batch Monitor window opens.
2. Double-click the PLMV4TOV5Migration utility:
The PLMV4TOV5Migration dialog box opens. Set the migration batch environment and select the document to migrate.
3. Click on the Browse button in the Document Selection section. The File Selection dialog box opens.
4. Click on the Member button.
5. Select the file to be migrated from the File Selection dialog box and click Open.
6. Click on the Change Target Directory button to specify the location of the Default target directory.
7. Select the Target directory location and click Default button.
After the migration of electrical parts from V4 to V5, the part number is stored in the file name of the respective CATPart file.
A screen-shot of the Properties dialog box, after the migration, showing the part number is as shown below:
During the V4 to V5 migration, the migration mode in case of a flexible curve of the bundle segment is automatically switched to
As Result when the migration in the As Spec mode causes modifications in shape or length. This change in migration results in a
datum curve creation in V5 which is not editable. To to edit it you need to reroute the branch.
All the unnecessary files created during the migration process are deleted after the migration from V4 to V5.
If the V4 electrical data to be migrated to V5 contains protections, these are converted to internal protections, and are visible as
Internal Protection under the Multibranchable node in the specification tree.
The Multi-branchable document option under the Tools > Options > Compatibility > Electrical tab should be
selected.
V4-V5 Mapping
The V4 architecture philosophy is quite different from the V5 Product Structure one. As a consequence, the V4 objects are quite different from
the V5 ones. A mapping between V4 and V5 objects can be established.
V4 element V5 element
Object
definition
GBN
Comment
ElecGeoBundle
No attributes
Object
definition
BNS
circular only
ElecBundleSegment
Attributes of BNS
MODE
Elec_Creation_Mode
BENDRAD
Elec_Bend_Radius
DISLACK
Elec_Di_Slack
TLENGTH
Elec_Length
SEGREG
Elec_Segreg
Separation code
Associated objects
Object
definition
BPP
ElecBundleSegmentExtremity
Point used to create the curve
Point
BSJ
Connection
No geometry associated
SIC
ElecSingleConnector
ETN
Electrical Termination
ES
External Splice
IS
Internal Splice
No geometry
TB
Terminal Block
BPP
ElecBundleConnectionPoint
CPP
Attributes
Object
definition
PARTNUM
IDNUM
NUMPIN
SURLONG
(ETN only)
Extra Length
If valuated, set the extra length of the corresponding ETN in all other dittos of the same device in the V4 model to
the same value.
CSL
ElecConnectorShell
Attributes of CSL
PARTNUM
IDNUM
Associated object
Object
definition
BPP
ElecBundleConnectionPoint
EQT
ElecEquipment
Attribute
Object
definition
PARTNUM
SPT
SPS
Attribute
Object
definition
PARTNUM
BSF
Attribute
PARTNUM
The electrical behavior is added to the geometry of the converted equipments, connector shells and single insert connectors.
The BSJs become connections between bundles segments.
The supports (SPT) are converted into mechanical parts to which the bundle segments are linked through publications.
The bundle surface (BSF) becomes a protective covering of tape type.
The terminal strip (TS) is not migrated. Only the geometry appears with no electrical behavior.
The external splice (ES) is migrated as a connector of external splice type.
The internal splice (IS) is migrated as a connector of internal splice type.
The geometry of the bundle junction (BSJ) is migrated as is.
Reference Information
This section gives general information about the V4 to V5 electrical migration.
To know more about V5 devices, refer to Electrical Library User's Guide.
V4 to V5 Document Structure
The V4 MASTER workspace becomes the main V5 CATProduct document while:
The CATPart documents resulting of DETAIL workspaces are instantiated as many times as there are DITTOS in the main document.
In this V4 model, the SIC comes from a V4 library: each SIC instance (DITTO) has the same reference (DETAIL).
In V5, the same structure is created: each connector is an instance of the CATPart.
If a device has been created in V4, using more than one ditto to define its geometry, a CATPart will be created for each original detail.
Library Migration
Even though the electrical applications use catalogs, the migration batch migrates only the components in the models, not in the libraries.
However it is possible to store the devices migrated from V4 model to a V5 catalog.
Refer to How to migrate a V4 library.
Note that it is recommended to limit the number of V4 devices to one hundred per model.
Known Restrictions
About Bundle Segment Migration
The V4 BNS is shown in yellow, the corresponding V5 bundle segment is shown in red.
The bundle segment shape in general might be different because of the algorithm differences.
The number of points on which the curve is built also is different: the supports in CATIA V4 use three points while only two are
used in CATIA V5.
If the V4 BNS bend radius is smaller than the V4 BNS diameter, the bend radius value taken into account will be equal to the
diameter. However, under certain circumstances, you may have a message informing you that the migration of such bundle
segments leads to a "twisted configuration". The resulting V5 bundle segments have an unusable geometry.
Bypass: In this case, modify the radius or the bend radius to be able to create the rib.
Once the migration is performed, the following modifications have to be done manually to get the correct device behavior:
On V5 single insert connectors, the Representation of the connector connection point and the Contact constraint
correspond to the migrated point of the CPP of the V4 SIC.
Coincidence
To connect a single insert connector to an equipment or a connector shell, a cavity connection point must be added to the
single insert connector, using Electrical Library.
Equipment
o
To connect a connector or connector shell to an equipment, a cavity must be added to the equipment for each connector or
connector shell, using Electrical Library.
To connect an equipment to a mounting equipment, a cavity connection point must be added to the mounting equipment,
using Electrical Library.
Connector Shell
o
To connect a connector to a connector shell, a cavity must be added to the connector shell for each connector, using
Electrical Library.
To connect a connector shell to a mounting equipment or an equipment, a cavity connection point must be added to the
mounting equipment or the equipment for each connector shell, using Electrical Library.
Terminal Block
To connect a terminal block a mounting equipment or an item of equipment, a cavity connection point must be added to the
terminal block using Electrical Library.
Multi-section supports are supported. However supports with multi-directional sections do not exist in CATIA V5. As a
consequence, only the first created section will be linked to a bundle segment as well as all other sections that have the same
direction.
The bundle segments using other support section direction in the original V4 model are not linked to the support in the V5
document.
For more information, refer to the V4 Integration Documentation - User Tasks - Converting CATIA Version 4 Models into CATIA Version
5 in Batch Mode.
Copy/Paste
Copy/Paste only copies the geometry and does not migrate the technology.
Use the Migration Batch to take advantage of the electrical technology.
Note: It is recommended to limit the number of V4 devices to one hundred per model.
Multi-directional support
Multi-section supports are supported. However supports with multi-directional sections do not exist in CATIA V5. As a consequence, only the
first created section will be linked to the bundle segment as well as all other sections that have the same direction.
The bundle segments using other support section direction in the original V4 model are not linked to the support in the V5 document.
What happens when migrating at the same time several models containing the same device
They are migrated as two/as many V5 reference documents.
Refer to Reference Information.
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
This makes possible the contextual links between the bundle segments and the geometry when creating the harness.
3. Then in the Equipment & Systems > Electrical Harness Discipline 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.
o
o
ElecIntegration.catalog
Since you have set up the option to enable the external systems interfacing, an additional command
is available in the Electrical Library,
Electrical Wire Routing, and the Electrical Harness Flattening workbenches. This command allows you to select the systems to be
imported.
This task explains how to select the system prior to placing electrical components or routing.
Once a system is selected, the list of devices is loaded and ready to use.
1. Switch to the Electrical Assembly Design workbench
2. Click External Systems
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.
If a system has already been selected, the data is reloaded.
Since you have set up the option to enable the external systems interfacing, Electrical Library commands Place Physical Device
and Add Link
This task explains how to place electrical components from the external device list.
1. Click Manage Links
Connectors
Internal splices
o
o
Shells.
You can filter the list:
o
o
the list displays all the devices referenced in the external data file, even if they are not placed
in the geometry.
Show only devices not 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
o
o
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.
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:
o
o
o
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.
This task explains how to define the cable harness and place the connectors at each extremity.
1. Switch to Electrical Harness Assembly workbench
again.
Select successively the connector connection point of both connectors to link them.
13.
c.
d.
These steps are detailed in the Basic Tasks section of the Electrical Harness Installation User's guide - Creating the Bundle
Segment Document.
The result looks like this:
You will now place the internal splices inside the bundle segments.
7. Click Place.
Since a mapping has been defined, the catalog browser opens with the predefined internal splice:
In this one, the splice is linked to Extremity1. The wire is routed in both BundleSegment1 and BundleSegment2:
BundleSegment2 diameter is recalculated and updated.
The component list is updated: the splices and pins are shown as linked in the device list.
Automatic Routing
Since you have set up the option to enable the external systems interfacing, the Automatic Routing
Routing workbench is modified.
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 geometrical bundle with bundle segments and components at their extremities
A system.
These steps are detailed in the Basic Tasks - Defining the Routing Context - Creating the Bundle.
The electrical bundle is added to the specification tree under the root product.
4. Click Automatic Routing
For the wires available in the list, you get the following information:
o
The wire name
o
The wire reference designator
o
The wire external diameter
o
The wire bend radius
o
Whether or not the wire is routed
o
Whether or not wire extremities have been found, or changed.
Filters can help you make your selection:
o
o
o
The routing options allow you to use or not the knowledge rule.
2. Select one or more wires and click the right arrow.
The selected wires shift to the right column: they will be routed.
3.
Click Route.
The Automatic Wire Routing Report is displayed
4.
The bundle segments diameter are updated according to the wiring information.
To know more, refer to Customizing - Equipment & Systems - Electrical Wire Routing documentation.
5.
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:
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 is:
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.
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.
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.
The instance also has instance attributes: Reference Designator and SubType.
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.
The Reference Designator attribute can be modified in both electrical and mechanical application workbenches. The value is
synchronized by using a knowledgeware rule when it is changed in either one of the two applications.
Create a knowledge rule to keep both the attributes synchronized. The rule should ensure that when one of the duplicate attributes is
modified, the related attribute is updated. You can write the rule such that a message is displayed whenever the attribute is changed.
The rule should be triggered from Edit > Properties against the object being edited.
Triggering the rule is managed by using the Project Resource Management (PRM) command. For more information on Project
Resource Management, see Tubing Design User's Guide: Customizing: Project Resource Management.
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:
4.
Notes:
When a product is activated (by double-clicking), editing the electrical properties operates in the same way as if the electrical
properties were edited in the document in which the root product is the reference of the active product. (i.e. Equipment.1 in the
RootProduct document against Equipment in the Equipment document.)
This definition is recursive within all the levels of instance.
Part Number
When you edit the properties of a group of bundle segments, the Length field indicates the total length of the bundle segments selected.
is active.
Functional:
Wire:
Wire:
hides the wires contained in the bundle segment, shows the bundle segments and signals.
Harness:
Harness:
hides the children bundle segments, only shows the signals and wires.
Sub-Objects:
Sub-Objects:
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 Related Objects
The Current Selection 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.
Elec_DistanceCommon
DistanceWireProduct
ListAllOuterLayerObjects
ListDirectlyCoveredObjects
ListDirectlyOuterLayerObjects
ListUsedSupports
ListUsedSupportWithAbscissa
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 Measure and go to the Knowledge Environment tab.
2. Select ElectricalMeasure from the list of available packages and click the Down arrow to load this package:
Elec_DistanceCommon
Syntax
Elec_DistanceCommon(Wire1: Wire, Wire2: Wire):Length
Returns the common length of the two wires given as input arguments.
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.
Example 2
In Knowledge Advisor, it can be used to define a rule giving the common length of two specific wires sharing properties.
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:
then select two wires in the specification tree and click OK to validate.
DistanceWireProduct
Syntax
DistanceWireProduct(Wire1: Wire, Object: Product):Length
Returns the minimum length between a wire and a product in session. The product must contain at least one part.
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.
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:
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
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:
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:
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
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:
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
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:
ListUsedSupports
Syntax
ListUsedSupports ((BundleSegment/BranchableBundleSegment): Feature, ListOfSupports(Supports): out List): Boolean
Returns the list of supports through which a bundle segment or multi-branchable document is routed.
Example
The example shows a multi-branchable document containing two bundle segments, each routed through seven supports.
A rule (in KWE advanced language) to determine the number and names of the supports through which each bundle segment is routed is written
as follows:
ListUsedSupportWithAbscissa
Syntax
ListUsedSupportWithAbscissa (iBundleSegment:Bundle Segment, oSupportList: List, oEntryPointAbscissa: List, oExitPointAbscissa: List):
Boolean
Returns the list of supports in the order in which they are located along the center curve of the bundle segment from the first extremity of the said
segment. Two other lists are output: entry point coordinates and exit point coordinates of each support.
Syntax
ListUsedSupportWithAbscissa (iBranchableBundle:Branchable Bundle Segment, oSupportList: List, oEntryPointAbscissa: List,
oExitPointAbscissa: List): Boolean
Returns the list of supports in the order in which they are located along the center curve of the branch from the first extremity of the said
segment. Two other lists are output: entry point coordinates and exit point coordinates of each support.
Example
An expert rule (created using Knowledge Expert) to determine the list of all the supports located along all segments in the document that also
outputs support entry and exit point coordinates:
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
Create a rule in Knowledge Expert:
The rule is reversible: you can load a harness in LIGHT mode and reload the geometry by applying the rule with the FULL parameter:
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.
ListIntSpliceWithAbscissa
Syntax
ListIntSpliceWithAbscissa (iBundleSegment:Bundle Segment, oIntSpliceList: List, oEntryPointAbscissa: List, oExitPointAbscissa: List):
Boolean
Returns the list of internal splices in the order in which they are located along the center curve of the bundle segment from the first extremity of
the said segment. Two other lists are output: entry point coordinates and exit point coordinates of each internal splice.
Syntax
ListIntSpliceWithAbscissa (iBranchableBundle:Branchable Bundle Segment, oIntSpliceList: List, oEntryPointAbscissa: List,
oExitPointAbscissa: List): Boolean
Returns the list of internal splices in the order in which they are located along the center curve of the branch from the first extremity of the said
segment. Two other lists are output: entry point coordinates and exit point coordinates of each internal splice.
InstantiateInternalProtection
Syntax
InstantiateInternalProtection (iBundleSegmentExtremity:BundleSegmentExtremity, ProtectionType:String, Length:Length, out
oProtection:InternalProtection): Boolean
Instantiates a light protective covering from a segment extremity with a given length.
The Protection type can be InternalTape (light tape protective covering), InternalAdaptive (light adaptive protective covering), InternalCorrugate
(light corrugated tube) or InternalFixed (light fixed diameter protective covering).
The protective covering is instantiated in the document containing the segment extremity.
CommandSignal
ConnectorShell
Contact
ContactPoint
CorrugatedTube
Equipment
InternalCorrrugatedProtection
InternalProtection
GeometricalBundle
InternalSplice
OffSheet
PowerSignal
Protection
ShieldingSignal
SingleConnector
InternalFixedProtection
Branchable
Mounting Equipment
TerminalStrip
Termination
Termination_GeoConstraint
VideoSignal
Wire
InternalAdaptiveProtection
InternalTapeProtection
MultiInsertConnector
BackShell
Description
Describes an electrical feature of Back Shell type that you create when you select Define Back Shell
For more information, refer to the Electrical Library User's Guide.
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
Defines the cable extra-length to be added to take into account the wire length inside the back shell.
Type: Double
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
Is True if the back shell is connected to a single insert connector and a bundle segment.
Connect (String ConnectionPointName, Product ToConnectObject, String ToConnectionPointName)
Type: Boolean
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
Branchable
Description
Describes an electrical feature of a branch when you click Branch Definition
For more information, refer to the Electrical Harness Installation User's Guide.
Attributes
Elec_ConstructionMode
Type: String
Type: Real
Type: Length
BundlePositionPoint
Description
Describes an 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 an electrical feature of Bundle type that you create when you click New Bundle
For more information, refer to the Electrical Wire Routing User's Guide.
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
BundleSegment
Description
Describes an electrical feature of Bundle Segment type that you create when you select either Bundle Segment
or Multi-Branchable
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_Min_Bend_Radius
Type: Double
Output data defining the actual minimum bend radius value computed on the bundle segment curve.
Elec_BundleSegmentExtremities
Type: Void
Type: String
Length:
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
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
Elec_Length
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 Electrical Harness Flattening.
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
Type: Length
Type: Length
IsElectricalCurve
Type: Boolean
Type: Boolean
Type: Boolean
Checks if the input bend radius is greater than the computed bend radius.
IsResultOK
Type: Boolean
Checks if the segment is not collapsed AND that is has a good bend radius AND that the curve is computed using the electrical algorithm.
DiameterComputedFromWires
Type: Real
Checks whether the assigned diameter of the bundle segment is valid or not.
BundleSegmentExtremity
Description
Describes the end of an electrical feature of Bundle Segment type. When a bundle segment is created, it automatically has two ends.
Inheritance path: Standard - Feature > ProductPackage - Product
Attributes
NumberOfConnectedBundles
Defines the number of bundle segments connected to the selected end of a bundle segment.
Type: Integer
Type: Integer
NumberOfConnectedDevices
IsGeoAndElecConnectionSame:boolean
Checks whether or not the electrical connection and geometrical connection at the bundle segment extremity coincide.
This is useful where networks are not properly created.
Type: String
Elec_LocalSlack
Cavity
Description
Describes an electrical feature of Cavity type that you create when you click Define Cavity
For more information, refer to the Electrical Library User's Guide.
Attributes
Elec_Extra_Length
Type: Double
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 an electrical feature of Command Signal type that you create when you select command signal
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
Type: Double
Type: String
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 an electrical feature of Connector Shell type that you create when you click Define Connector
workbench.
For more information, refer to the Electrical Library User's Guide.
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
String ConnectionPointName is the name of the connection point used on the current device
Product ToConnectObject is the instance to connect to
String ToConnectionPointName is the name of the connection point used on the destination device.
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
Contact
Description
Describes an electrical feature of Contact type that you create when you click Define Contact
For more information, refer to the Electrical Library User's Guide.
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: String
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
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
Checks and retrieves the ID of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
Type: String
Type: String
SpecifiedConnectedId
Checks and retrieves the ID of the device connected to the current device in the loaded specification file (using iXFElec file or CAA APIs).
Type: String
SpecifiedConnectedPartNumber
Checks and retrieves the part number of the device connected to the current device in the loaded specification file (using iXFElec file or CAA
APIs).
Type: String
SpecificationPartNumber
Checks and retrieves the part number of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
CorrugatedTube
Description
Describes an electrical feature of Corrugated Tube type that you create when you click Define Protective Covering
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
Attributes
Elec_Bend_Radius
Type: Double
Defines the bend radius value, which corresponds to the minimum bend radius of the corrugated tube curve.
in the Electrical
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
Equipment
Description
Describes an electrical feature of Equipment type that you create when you click Define Equipment
For more information, refer to the Electrical Library User's Guide.
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
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
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
Type: String
Checks and retrieves the ID of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
SpecificationPartNumber
Type: String
Checks and retrieves the part number of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
ExternalSplice
Description
Describes an electrical feature of External Splice type that you create when you click Define Connector
workbench.
For more information, refer to the Electrical Library User's Guide.
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
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.
Connect (String ConnectionPointName, Product ToConnectObject, String ToConnectionPointName)
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
Output parameters are a list of wire instances and a list of connection point names where wires are connected.
Returns TRUE if information retrieval succeeds, FALSE otherwise.
Type: String
SpecificationId
Checks and retrieves the ID of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
SpecifiedConnectedId
Type: String
Checks and retrieves the ID of the device connected to the current device in the loaded specification file (using iXFElec file or CAA APIs).
SpecifiedConnectedPartNumber
Type: String
Checks and retrieves the part number of the device connected to the current device in the loaded specification file (using iXFElec file or CAA
APIs).
SpecificationPartNumber
Type: String
Checks and retrieves the part number of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
FillerPlug
Description
Describes an electrical feature of Filler Plug type that you create when you click Define Filler Plug
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
Elec_Ref_Des
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
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
ContactPoint
Description
Describes an electrical feature of Contact Point type that you create when you select Contact Points
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: Boolean
Type: String
FunctionalConnector
Description
Describes an electrical feature of Functional Connector type that you create when you select Functional Connectors
System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
in the Electrical
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
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
Describes an electrical feature of Functional Equipment type that you create when you select Functional Equipment
System Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
in the Electrical
This equipment is a functional electrical component with one or more associated connectors, for example a lamp or a battery.
Attributes
Elec_External_Reference
Type: String
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
Geometrical Bundle
Description
Describes an electrical feature of a geometrical bundle when you click Geometrical Bundle
For more information, refer to the Electrical Harness Installation User's Guide.
Inheritance path: Standard - Feature > ProductPackage - Product
GroundSignal
Description
Describes an electrical feature of Ground Signal type that you create when you select Ground Signal
Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
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
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
Internal Protection
Description
Describes the internal protective covering when you click Define Protective Product
For more information, refer to the Electrical Library User's Guide.
Attributes
Elec_Length
Type: Double
Type: String
Type: string
Type List
Type: Double
Type: Double
Attributes
Elec_Thickness
Type: Double
Type: Double
Attributes
Elec_Thickness
Type: Double
Description
Describes the adative protection thickness when you click Define Protective Product
workbench.
For more information, refer to the Electrical Library User's Guide.
Attributes
Type: Double
Elec_Thickness
Elec_Bend_Radius
Attributes
Elec_Tape_Thickness
Type: Double
Elec_Tape_Width
Type: Double
Type: Double
Type: Double
Type: Double
Type: Double
Type: Double
GroupSignal
Type: Double
Description
Describes an electrical feature of Group Signal type that you create when you select Grouped electrical signal
Functional Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
Grouped 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
Type: Double
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 an electrical feature of Internal Splice type that you create when you click Define Connector
For more information, refer to the Electrical Library User's Guide.
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
Type: Double
Type: Double
Defines the distance to the bundle segment extremity selected to place the internal splice.
Elec_Ref_Des
Type: String
Defines the internal splice reference designator attribute, which is the unique identifier for the internal splice in the project.
Elec_Sub_Type
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
Type: String
Type: String
Checks and retrieves the ID of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
SpecifiedConnectedId
Type: String
Checks and retrieves the ID of the device connected to the current device in the loaded specification file (using iXFElec file or CAA APIs).
SpecifiedConnectedPartNumber
Type: String
Checks and retrieves the part number of the device connected to the current device in the loaded specification file (using iXFElec file or CAA
APIs).
SpecificationPartNumber
Checks and retrieves the part number of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Type: String
Mounting Equipment
Description
Describes an electrical feature of Mounting Equipment type that you create when you click Define Mounting
in the Electrical Library workbench.
For more information, refer to the Electrical Library User's Guide.
Equipment
A Mounting Equipment
Inheritance path: Standard - Feature > ProductPackage - Product
Attributes
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
Output parameters are two lists of names, the names and the types of the connection points.
Returns TRUE if information retrieval succeeds, FALSE otherwise.
ListWires (out List ListOfWires, out List ListOfNames)
Attributes
Elec_External_reference
Type: String
Type: String
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
Type: String
Checks and retrieves the ID of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
SpecifiedConnectedId
Type: String
Checks and retrieves the ID of the device connected to the current device in the loaded specification file (using iXFElec file or CAA APIs).
SpecifiedConnectedPartNumber
Type: String
Checks and retrieves the part number of the device connected to the current device in the loaded specification file (using iXFElec file or CAA
APIs).
SpecificationPartNumber
Type: String
Checks and retrieves the part number of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
SpecificationId
OffSheet
Description
Describes an electrical feature of Off Sheet Connector type that you create when you select Offsheet Connector
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
Type: String
Stud
Description
Describes an electrical feature of Stud type that you create when you click Define Connector
For more information, refer to the Electrical Library User's Guide.
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
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.
Connect (String ConnectionPointName, Product ToConnectObject, String ToConnectionPointName)
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
Type: String
Checks and retrieves the ID of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
SpecifiedConnectedId
Type: String
Checks and retrieves the ID of the device connected to the current device in the loaded specification file (using iXFElec file or CAA APIs).
SpecifiedConnectedPartNumber
Type: String
Checks and retrieves the part number of the device connected to the current device in the loaded specification file (using iXFElec file or CAA
APIs).
SpecificationPartNumber
Type: String
Checks and retrieves the part number of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
PowerSignal
Description
Describes an electrical feature of Power Signal type that you create when you select Power Signal
Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
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.
Elec_Nominal_Voltage
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 an 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
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
Type: Double
Defines the protection linear mass, used for the flattened representation.
Elec_Ref_Des
Type: String
Type: String
ShieldingSignal
Type: String
Description
Describes an electrical feature of Shielding Signal type that you create when you select Shielding Signal
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
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 an electrical feature of Single Insert Connector type that you create when you click Define Connector
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
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.
Elec_FullConnected
Type: Boolean
if the single insert connector is connected to a bundle segment or a back shell and connected to another single insert connector.
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
Type: String
Checks and retrieves the ID of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
SpecifiedConnectedId
Type: String
Checks and retrieves the ID of the device connected to the current device in the loaded specification file (using iXFElec file or CAA APIs).
SpecifiedConnectedPartNumber
Type: String
Checks and retrieves the part number of the device connected to the current device in the loaded specification file (using iXFElec file or CAA
APIs).
Type: String
SpecificationPartNumber
Checks and retrieves the part number of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
Signal
Description
Describes an electrical feature of Signal type that you create when you select Signal 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
Elec_Routing_Priority
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
SignalRoute
Description
Describes an electrical feature of Signal Route type that you create when you click Automatic Wire Routing
workbench.
For more information, refer to the Electrical Wire Routing User's Guide.
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 an electrical feature of System type that you create when you select System 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
Elec_Ref_Des
Type: String
Defines the system reference designator attribute, which is the unique identifier for the system in the project.
Elec_Sub_Type
Type: String
Tape
Description
Describes an electrical feature of Tape type that you create when you click Define Protective Covering
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.
Attributes
Elec_Bend_Radius_Delta
Defines the bend radius value, which corresponds to the minimum bend radius of the tape curve.
Type: Double
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
Defines the tape line type, used for the flattened representation.
Elec_Line_Weight
Type: Double
Defines the tape number of layers applied onto the bundle segment.
Type: Double
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
Describes an electrical feature of Terminal Block type that you create when you select Define Connector
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
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
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
Type: String
Checks and retrieves the ID of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
SpecifiedConnectedId
Type: String
Checks and retrieves the ID of the device connected to the current device in the loaded specification file (using iXFElec file or CAA APIs).
SpecifiedConnectedPartNumber
Type: String
Checks and retrieves the part number of the device connected to the current device in the loaded specification file (using iXFElec file or CAA
APIs).
SpecificationPartNumber
Type: String
Checks and retrieves the part number of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
Termination
Description
Describes an electrical feature of Termination type that you create when you click Define Termination
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
Attributes
Elec_Extra_Length
Type: Double
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
Termination_GeoConstraint
Type: String
Description
Describes an electrical feature of Termination type that you create when you click Define Termination
workbench.
For more information, refer to the Electrical Library User's Guide.
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
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
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 an electrical feature of Terminal Strip type that you create when you click Define Connector
For more information, refer to the Electrical Library User's Guide.
Attributes
Elec_External_Reference
Type: String
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
Defines the terminal strip reference designator attribute, which is the unique identifier for the terminal strip in the project.
Type: String
Elec_Sub_Type
Type: String
Type: Boolean
Disconnects a device.
String ConnectionPointName is the name of the connection point where disconnection will be done.
Returns TRUE if disconnection succeeds, FALSE otherwise.
ListConnectedObject (String ConnectionPointName, out Product ToConnectObject, String out ToConnectionPointName)
Type: String
Checks and retrieves the ID of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
SpecifiedConnectedId
Type: String
Checks and retrieves the ID of the device connected to the current device in the loaded specification file (using iXFElec file or CAA APIs).
SpecifiedConnectedPartNumber
Type: String
Checks and retrieves the part number of the device connected to the current device in the loaded specification file (using iXFElec file or CAA
APIs).
SpecificationPartNumber
Type: String
Checks and retrieves the part number of the current device from the loaded specification file (using iXFElec file or CAA APIs).
Returns 'NoSpecificationLink' if not found.
VideoSignal
Description
Describes an electrical feature of Video Signal type that you create when you select video signal
Definition workbench.
For more information, refer to the Electrical System Functional Definition User's Guide.
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
Elec_Sub_Type
Type: String
Wire
Description
Describes an electrical feature of Wire type that you create when you click Define Wire
For more information, refer to the Electrical Library User's Guide.
Attributes
Elec_Bend_Radius
Type: Double
Type: String
Type: String
Type: Double
Type: String
Returns the reference designator value of the connection point to which the from-end of the wire is connected.
Elec_FromContactPartNumber
Type: String
Returns the part number of the contact in the device cavity to which the from-end of the wire is connected.
Elec_FromDevice
Type: String
Returns the reference designator value of the device to which the from-end 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
Elec_Line_Weight
Type: Double
Type: String
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
Elec_ToConnectionPoint
Type: String
Returns the reference designator value of the connection point to which the to-end of the wire is connected.
Elec_ToContactPartNumber
Type: String
Returns the part number of the contact in the device cavity to which the to-end of the wire is connected.
Elec_ToDevice
Type: String
Returns the reference designator value of the device to which the to-end of the wire is connected.
IsSingleInBundleSegment
Type: Boolean
Is True when the wire route follows at least one bundle segment containing only this wire.
Elec_FromConnectionPointName
Type: String
Type: String
This task shows you how to create a catalog assembly that you can use repeatedly in your design.
Main steps are:
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 Catalogs for Electrical Mapping
Loading an iXF Document with VPM Navigator
ENOVIA V5 Interoperability
Using VPM Navigator
This task explains how to work with electrical data stored in ENOVIA V5, using VPM Navigator:
Once the connection has completed successfully, the icons in the ENOVIA V5 VPM Navigator toolbar are no longer grayed out.
2. Using the New VPM Navigator command, view product root class (PRC's).
For more information, see Viewing Product Root Classes (PRC's) in the Basic Tasks, VPM Navigator, in the Navigator User's
guide.
4.
Double-click the PRC you want to open.
5.
This task shows you how to open electrical objects for editing purposes.
Electrical data can be saved in product document (in workpackage) or in component (in explode mode): Geometrical bundles can be saved
with both these modes, when CATPart documents (bundle segments, devices, etc.) and electrical bundles are automatically saved as
workpackage.
The preferred storage mode for electrical design data is workpackage.
Depending on the size of your data, using explode mode can lead to poor performance during save / load actions. To avoid this, it is
recommended that you store geometrical bundles as workpackages, and if you route wires, that you store geometrical bundles and
electrical bundles under the same workpackage. This will optimize storage (and performance) in a PLM environment.
1. In the Product tree, right-click the object you want to open and select Open...
Note that the multi-selection is possible using the Ctrl-key.
3. Now switch to Electrical Library to connect the plug of the geometrical bundle to the female socket of the other.
To do so:
a.
b.
c.
This section explains in greater detail how electrical data designed in CATIA can be stored in ENOVIA V5 using VPM Navigator.
When working with ENOVIA V5, the safe save mode ensures that you only create data in CATIA that can be correctly saved in ENOVIA
V5.
ENOVIA V5 offers two different storage modes: Workpackage (Document kept - Publications Exposed) and Explode (Document not
kept). Electrical products have been configured to work in both Workpackage mode and the Explode mode, depending on the objects
considered.
This safe save mode means that certain commands are unavailable.
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.
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 a part inside a workpackage to a part outside the
workpackage.
Let's see an example:
With a geometrical bundle stored as a workpackage (publication exposed mode), the bundle segments belonging to this geometrical
bundle cannot use, as routing objects, supports, devices or any geometry external to the geometrical bundle while keeping the
contextuality. The external references won't be synchronized and the bundle segment shape won't any longer be contextual to any
object outside the geometrical bundle. Contextual links are kept inside the geometrical bundle.
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.
This functionality is applicable to electrical data created as of Version 5 Release 16 only. It does not support adaptive supports.
The instance name of supports must be unique. The bundle segment-to-support link will not be updated if two or more instances
have the same name in your session.
Modifying the instance name will make the link invalid.
Do not rename geometry created when routing bundle segments through supports.
Updating bundle segment-to-support links is based on a naming convention for support identifiers. Whenever a support is added, support
geometry (published point and two published planes) is copied and renamed as follows:
Name of the geometry= [Instance name of selected support]![Name of the publication]
CATIA Settings
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 the Tools > Options > Infrastructure > Part Infrastructure > General tab.
In the External References frame, clear the Use root context in assembly check box.
b. Select the Tools > Options > Equipment and Systems > Electrical Harness Discipline > Electrical Harness
Installation > Harness Management tab.
Under Contextual Links, in the Keep link with selected object box, select In geometrical bundle.
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.
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 the Tools > Options > Infrastructure > Part Infrastructure > General tab.
Under External References, select the Use root context in assembly check box.
b.
Define Cavity
Define Termination
Define Connector Connection Point
Define Bundle Connection Point
Define Cavity Connection Point
Define Back Shell Connection Point
To be consistent and useable, some electrical data needs to be at a higher load mode than Visualization mode. In ENOVIA V5 context,
loading this needed information implies to transit of the impacted CATParts through the network. So if we only load necessary data, this
transit will be redone for the switch to Design mode. So to optimize the data flow through the network, we just make a transit once for the
catpart and load it into design mode.
This dialog box identifies bundle segments that can be updated as well as any that cannot, indicating why. Reasons why include:
o
o
o
Exporting Reports
To export a report in text format (.txt):
1. Click Export... in the Update Bundle from Moved Support dialog box.
2. In the Export Report dialog box that opens:
a.
Identify the folder in which you want to save your text file.
b.
c.
The report contains the same information as displayed in the dialog box.
You can manually update the bundle segment-to-support link by editing the bundle segment route:
For more information, see Using the Search workbench in Basic Tasks, VPM Navigator, in the Navigator User's guide.
8. In the Result window, select the desired catalog and click Open.
The Electrical Mapping tab is updated.
9. Define the mapping as explained in the CATIA - Infrastructure User's Guide - Customizing - Customizing Settings - Equipment and
The System Selection dialog box opens containing the previously selected iXF files:
Workbench Description
CATIA - Electrical Harness Assembly application window looks like this:
Click the hotspots to display the related documentation.
Menu Bar
Toolbars
Electrical Workbench Specification Tree
Menu Bar
This section presents menu bar tools and commands dedicated to Electrical Harness.
Other items available are the standard ones. These commands and tools are described in Infrastructure Version 5. For more information, refer to
the standard Menu Bar section.
Start
File
Edit
View
Insert
Tools
Tools
Electrical Harness Assembly
For...
See...
Analyze
Window
Help
See...
This section describes the various toolbar commands available in the Electrical Harness workbenches.
The toolbars are located on the right in the default set-up except for the Catalog Browser, the Measure and the Update commands which are
located in the horizontal bottom toolbar.
Creation Toolbar
Geometrical Bundle
Protective Covering
Management Toolbar
Link
Delete Toolbar
Delete Special
Related Objects
Catalogue Toolbar
Catalog Browser
Measure Toolbar
Select Toolbar
Exit
General Toolbar
Point
Delete Toolbar
Delete Special
In this document, you will find the different icons generated in the electrical workbenches.
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
Functional Connector
Not linked to physical
Functional Connection Point
Not linked to physical
Signal, Power Signal
Not routed
Shielding Signal
Group Signal
Ground Signal
Video Signal
Linked to physical
Linked to physical
Linked to physical
Partially routed
Other
Routed Signal in System Space Reservation (SSR)
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: these settings will not be lost if you end your session.
1. Select the Tools > Options command.
The Options dialog box opens.
2. Select the Equipment & Systems > Electrical Harness Discipline category in the left-hand box.
3. Click the Electrical Harness Installation workbench.
The Harness Management tab appears.
General
Display
5. For migration purpose, you may need to customize the Migration Batch, Electrical and V4/V5 SPACE tabs located in the
General > Compatibility category.
o
o
V4/V5 SPACE
Migration Batch
Electrical
6. For inertia calculation, you will need to customize the Tree customization tab located in the Infrastructure > Product Structure
category.
o
o
o
Parameters
7. Set options in these tabs according to your needs.
o
If this option is selected, only one multi-branchable document can be created within a geometrical bundle: a single part contains the full harness,
reducing the size of the document, the number of contextual links and consequently the update time.
However to take advantage of the ENOVIA configuration management, this option needs to be cleared if you want to manage the effectivity at a
more detailed granularity level: the branch.
Select this option if the configuration management does not need to be done at the level of each branch, but at the level of a set of branches
created in a single document.
By default, this option is not selected.
Geometrical link
If this option is selected, when the selection is completed, the bundle segment is extended to the second point selected (which is either a bundle
segment extremity or a bundle connection point).
By default, this option is selected.
the branch point is removed from the route definition of the branch
the branch is unlinked from the branch point with the Unlink command
the last connected branch is deleted using the Delete Special contextual menu.
Contextual Links
For the first option to be taken into account, you must first change options located in the Part Infrastructure > General > External
References frame:
select the Keep link with selected object option, otherwise no external references will be created.
By default, this option is not selected.
clear the Use root context in assembly option. If not, the links will be created to the root of the assembly.
By default, this option is selected.
Never:
Branch/Support Link
If Any profile is selected, the ability to manage profiles is activated: when the user creates a bundle segment, the rib is replaced by a loft
representation. More or different options are available in the dialog boxes for Branch Definition, Bundle Segment Definition and Profile
Management.
This option only works for bundle segments within multi-branchable documents.
By default, Circular profile is selected.
remains unchanged: both values are updated at the same time and keep their ratio constant.
are updated.
Important: If the Set Area Constant check box is selected in the Profile Management dialog box, then the Do not recompute values
option is ignored, and section parameters are updated as per Keep the ratio constant option.
If Allow system to use a small bend radius value is selected, and the standard algorithm does not converge, the bend radius is
optimized to keep the flexible curve and ensure a curve of better quality. Keeping a flexible curve (a specific electrical curve) lets you manage
slack, work in Length mode and ensures good integration with Electrical Harness Flattening.
By default, this option is not selected.
Standard algorithm
If Standard algorithm is selected, the standard algorithm is used for bundle segment creation.
By default, this option is selected.
FLEX algorithm
If this option is selected, the FLEX computation algorithm is used, giving a more realistic shape to the bundle segments. This option is only
available if a FLEX Physical Simulation license is present.
The slider allows you to choose the balance between the calculation time (P) and the accuracy (A).
This option only works for bundle segments within multi-branchable documents.
The Warn user when Branch is collapsed check box should be selected in order to display this message box.
Click here to know more about the Part Infrastructure General options.
Click here to know more about the Part Infrastructure Display options.
External References
If this option is selected, the External References will display in the specification tree.
By default, this option is selected.
Compatibility for
Electrical Harness Installation
This page deals with the options concerning:
V4/V5 SPACE
Click here to know more about the Compatibility > V4/V5 SPACE options.
as CGR: the SolidM conversion as CGR means that you will only get the meshing view (visualization mode)
as PartBody: the SolidM conversion as PartBody means that you will be able to see the geometry of the solid
Migration Batch
Click here to know more about the Compatibility > Migration Batch options.
Interface Name
You need to enter CATIE3DMigration in this field if you want to migrate V4 electrical data to V5.
By default, this option is empty.
Electrical
to edit it.
Click here to know all the details about the Compatibility > Electrical options.
Bundle segments
If this option is selected, each V4 BNS is migrated to a V5 bundle segment (CATPart document).
Multi-branchable document
If this option is selected, all the BNSs of a V4 GBN are migrated to one multi-branchable document in a V5 geometrical bundle. All the V5
bundle segments are stored in a single CATPart, the multi-branchable document.
By default, this option is selected.
Parameters
In the Specification Tree Order, there is a list of CATIA attributes corresponding to the nodes of the specification tree. You can order the
nodes in the specification tree and activate or deactivate their visualization.
In the context of the Measure Geometrical Bundle Inertia command
By default, Parameters is not activated.
Refer to Tree Customization.
Methodology
This section explains how to create other kinds of features.
The table below lists the information you will find:
Protective Coverings of Given Length - Methodology
Creating an Adaptative Part
Be sure to clear the Hide Internal harness geometry check box in the Tools > Options > Equipments & Systems > Electrical
Harness Installation > Harness Management tab.
1. Start the Electrical Part Design workbench.
2. Click Define Protection Part
You are prompted to select a part.
6. Create a point on the joint which will be used for the instantiation:
To do so:
Click Point
.
The dialog box opens to create Point.6.
b.
Enter the following values:
a.
Length: 250mm
Reference point: Point.3
The offset from Point.3, entered in the Length value (250mm) is the parameter which will drive the length of the
protective covering.
c.
Click OK to validate.
Point.6
d.
2. Create a new split on the joint between Point.3 and the newly created Point.6 to define a new centerline between Point.3 and
Point.6.
To do so:
Click Split
.
The dialog box opens to create Split.2.
b.
Enter the following values:
a.
c.
Click OK to validate.
d.
3. Now replace Split.1 in the ElecRouteBody with Split.2, using the contextual menu, to define the rib between Point.3 and
Point.6.
b.
Click OK to validate.
Green line
Grommet
Boot
3. Select the catalog then the protective covering you want to instantiate.
To do so:
o
o
.../online/cfysm_C2/samples/ElectricalSession/catalog/catalog1.catalog.
Double-click the protective covering: Part2
The catalog browser closes and the selected protective covering displays in the upper right corner of the primary window.
o
5. Click OK to validate.
Note: Using this methodology, the covered length indicated in the Protective Covering Information is not correct: it indicates the
distance between the Start extremity and the End extremity of the selected bundle segment when the protective covering is applied
between the Start extremity and for a length of 250mm (Point.4).
This document also contains three formulas that have been defined to re-compute the support geometry after routing:
1 - The support remaining length value is set to:
20mm*(2*PI+1)-(2*PI*Radius)
1. Click Formula
2. Select the Length as Filter Type and click New Parameter of type.
3. Enter the name for it: ELEC-SUPPORT-RADIUS
and a value: 18mm for example
Note: the name must strictly be ELEC-SUPPORT-RADIUS.
A formula will automatically be generated under the root product of the document, if and only if the ELEC-SUPPORT-RADIUS
parameter has been detected:
Support radius = Bundle segment diameter * 0.5
The support will exactly fit the bundle segment diameter. The formulas given above are used to re-compute the support geometry.
Glossary
bend radius
branch
bundle
bundle segment
The bend radius is the minimum bend radius allowed for the bundle segment.
A set of bundle segments that share the same centerline.
For electrical bundle: A document containing wires routed through geometrical bundles.
A geometrical subdivision of a geometrical bundle.
It is the wire graphical representation in the digital mock-up. The bundle segment is created according to several rules:
The bend radius must be superior to half the diameter
In slack mode, an extra-length is added to the bundle segment calculated from a bend length percentage (Slack%).
The bend mode calculates the minimum length through all the constraint points, with regard to the minimum bend
radius.
The length mode uses the length value: this value must be at least equal to the distance between the points.
Where the term single bundle segment occurs in this guide, it refers to a CATPart document created under the active
product that contains just one bundle segment.
C
connector
An electrical component providing an electrical interface between two bundles, an item of equipment and a bundle or
between wires. Comprises one or more electrical terminations. They are of two types: physical connector (from Electrical
Library, Catalog or V4) and functional connector (from EFD application).
D
diameter
device
E
effectivity
electrical bundle
electrical system
electrical
termination
equipment
CATProduct document.
Electrical connection (often called pin) on a connector
Electrical device comprising one or more associated connectors.
G
geometrical bundle A document containing an assembly of connectors, supports and insulation, as well as the geometric representation of a
harness.
H
harness
An assembly of wires, connectors, supports and insulation manufactured together. Represented in CATIA by both
geometrical and electrical bundles.
I
instance
Designation of reference placed in a context, i.e. in design mode. An instance can have additional characteristics that do
not belong to the reference. For example, the instance of a wire has a length attribute in an assembly context when its
reference doesn't out of this context.
As opposed, see reference.
M
multi-branchable
document
A set of branches, themselves containing bundle segments, connected or not, composing the harness. It corresponds to a
CATPart document.
See also single bundle segment document.
P
pin
An electrical termination
properties
Attributes of a component that define its electrical, mechanical, etc. characteristics.
protective covering Covering element wrapping the conductor and possibly the insulating coating bringing out a mechanical protection. It can
be a sleeve, a corrugated tube, a taping, etc.
R
reference
routing
Describes a real object. A reference can be stored in a catalog. In the electrical context a reference corresponds either to:
A CATPart document which has electrical properties and exhibits electrical behavior
or,
A CATProduct document whose root product has electrical properties and exhibits electrical behavior.
See also instance.
An operation that computes the optimized wire route between two or more extremities of a signal.
S
section
segment
single bundle
segment document
sleeve
W
wire
wire connection
Index
Numerics
3D harness tolerancing
A
adaptative part
ELEC-SUPPORT-RADIUS
adaptative supports
adding
branch points
branches
supports
annotation
bend
bend radius
branch
branch points
adding
automatically deleting
connecting segments
distance to reference object
removing
splitting branches
branches
adding branch points
bundle segment
bundle segment definition
creating first
modifying slack
removing branch points
routing
transferring
bundle segment documents
creating
bundle segments
collapsed geometry
computation mode
cutting point
defining parameters
definition in branch
link to supports
linking
modifying slack
multi-profile
profile
routing
routing through retainers
splitting
stiffness
unlinking
C
collapsed geometry
commands
Add Branch Point
Add Support
Adjust
Automatic Wire Routing
Branch Definition
Bundle Segment
Bundle Segment Definition
Catalog Browser
Curvilinear Dimensions
Delete Special...
Delete Useless Elements...
Duplicate Harness
Exit
Formula Editor
Front View/Annotation Plane
Geometrical Bundle
Link
List Broken Publications
Local Slack
Manage Links
Measure Geometrical Bundle Inertia
Multi-Branchable Document
Place Bundle Segments Inside Support
Point
Protective Covering
Recompute All Bundle Segments
Related Objects
Remove Branch Point
Remove Support
Route Definition
Segment Definition
Split
Transfer Branches
Unlink
Update
Update Bundle from Support
computation mode
FLEX algorithm
construction constraints
copying bundle segment arrangement
creating
bundle segment documents
construction constraints
geometrical bundle
multi-branchable documents
curvilinear dimensions
cutting point
D
defining
bundle segment parameters
construction constraints
deleting unused branch points automatically
diameter
dimension visualization mode
DistanceWireProduct
E
effectivity
ELEC-SUPPORT-RADIUS
adaptative part
ElecDistanceCommon
electrical application interoperability
electrical bundle
electrical data migration
migrating step by step
setting options
V4-V5 mapping
electrical mapping
electrical package
electrical user function
DistanceWireProduct
ElecDistanceCommon
ListAllOuterLayerObjects
ListDirectlyCoveredObjects
ListDirectlyOuterLayerObjects
VisualMode
external curve
external data
management
external references
F
FLEX algorithm
flexible curve
front view
G
geometrical bundle
H
harness
covering
duplicating
mass calculation
I
instantiating protective covering
adding light protective covering
K
knowledge assembly template
L
length
linking bundle segments
ListAllOuterLayerObjects
ListDirectlyCoveredObjects
ListDirectlyOuterLayerObjects
local slack
M
mapping
ENOVIA catalogs
measuring geometrical bundle inertia
migrating V4 data to V5
migrating step by step
setting options
V4-V5 mapping
modifying slack
multi-branchable documents
about
adding branches
P
placing
internal splices
physical devices
positioning management
routing options
profile
protective covering
protective coverings
adjusting relationships between
collapsed geometry
instantiating
length
R
ratio
related objects
removing
branch points
supports
retainers
routing bundle segments through
routing
between points on-the-fly
between points, devices and supports
branches
construction constraints
on external curves
on surfaces
options
single bundle segments
through supports
routing options
positioning management
tangent management
S
section
selective loading
single bundle segments
modifying slack
routing
slack
build mode option
build mode option0
managing at junctions
managing local
splitting
branches
bundle segments
stiffness of bundle segments
supports
adding
arranging bundle segment in
copying bundle segment arrangement
removing
removing a bundle segment from
routing through
tangent management
routing options
Tools Options - Compatibility
Electrical
Migration Batch
V4/V5 SPACE
Tools Options - Electrical Harness Installation
Harness Management
Tools Options - Part Infrastructure
External References
Tools Options - Product Structure
Tree Customization
transferring branches
U
unlinking bundle segments
V
V4-V5 migration
migrating step by step
setting options
V4-V5 mapping
viewing related objects
VisualMode