If an ANSYS DesignModeler application feature modifies an instanced body, then the body will no longer be considered an instance. Generally, a feature may be destructive of pre-existing body instance data (existing before the feature is generated).
If there is only a single remaining body instance following the removal of the modified body instance data, then this remaining body will no longer be considered an instance. Note that no observable modifications will be made in the ANSYS DesignModeler application geometric data other than the body instance data being modified.
The Share Topology feature will determine how part instances are formed for the purpose of transferring geometry to ANSYS Mechanical application. Some exceptions are now noted:
Parts with Share Topology method Automatic or Imprint will be retained as instances after the execution of the Share Topology feature only for databases created from version 15.0 onward.
A part which has at least one body with “Edge-Joints” Share Topology type will be de-instanced by the Share Topology feature.
For parts to be instances of each other, it is required that corresponding bodies have the same Shared Topology Method property.
If a Spot Weld or Point Load is present on any instanced body, then any associated part instance data will be ignored during geometry transfer to the ANSYS Mechanical application.
It may be noted that an implicit Share Topology feature will be created, if one doesn’t yet exist, during transfer of geometry from ANSYS DesignModeler application to the ANSYS Mechanical application. The creation of part instances in the ANSYS Mechanical application will be as previously described.
For a better understanding, consider the following examples of the ANSYS DesignModeler application feature modeling and transfer of part instance data to the ANSYS Mechanical application.
| Example 18: Scenario 1 |
| Example 19: Scenario 2 |
| Example 20: Scenario 3 |
| Example 21: Scenario 4 |
The following icons represent the bodies:
|
|
|
|
|
|
|
|
|
For clarity, the part node for singleton parts are shown in the examples below, even though the ANSYS DesignModeler application feature tree does not show the part node for single-body parts.
When displaying body lists, the following shapes denote body states:
Circle: non-instanced imported body or natively
created body |
Box: a body involved in an instanced relationship |
Diamond: a body involved in an instanced relationship
that has since been modified |
User creates a native model in the ANSYS DesignModeler application of a simple multibody part:
Part 1: |
User patterns
to create
bodies
as singletons:
Part 1: |
Part 2: |
Part 3: |
Part 4: |
When transferring this data to the ANSYS Mechanical application, Part 1 will be un-instanced, while Parts 2, 3, 4 will be instances.
In the ANSYS DesignModeler application, you explode Part 1:
Part 1: |
Part 2: |
Part 3: |
Part 4: |
Part 5: |
When transferring this data to the ANSYS Mechanical application, Part 1 would remain un-instanced, while Parts 2, 3, 4, 5 will be instances. This is because there would be no conflict between ANSYS DesignModeler application parts and body instance data.
User creates a native model in the ANSYS DesignModeler application of a simple multibody part:
Part 1: |
User patterns both bodies
and
to create three
copies of each, such that
,
and
are copies of
. Bodies
,
and
are copies of
. The Parts/Bodies feature tree list looks like this
initially:
Part 1: |
Part 2: |
Part 3: |
Part 4: |
Part 5: |
Part 6: |
Part 7: |
The following table illustrates various part layouts in the ANSYS DesignModeler application and results of geometry transfer to the ANSYS Mechanical application.
| Body grouping ANSYS DesignModeler by user | Part instancing in ANSYS Mechanical | Explanation | |||||||||||||||
| 1 |
|
| In the ANSYS Mechanical application { | ||||||||||||||
| 2 |
|
| When Share Topology types of all four parts are the same in the ANSYS DesignModeler application, then the model is transferred as four instanced parts to the ANSYS Mechanical application. | ||||||||||||||
| 3 |
|
| In the ANSYS Mechanical application Part 1 and Part 2 are instances of each other, as will be Part 4 and Part 5. | ||||||||||||||
| 4 |
|
| In the ANSYS Mechanical application Part 1 and Part 2 are instances of each other. Part 4 and Part 5 will be uninstanced. |
User imports a CAD model into the ANSYS DesignModeler application with two singleton part instances:
Part 1: |
Part 2: |
User patterns
to create
bodies
as
singletons:
Part 1: |
Part 2: |
Part 3: |
Part 4: |
Part 5: |
When transferring this data to the ANSYS Mechanical application, five instanced singleton parts are expected:
|
|
|
|
|
Now go back to the ANSYS DesignModeler application and
modify
. Body list now looks
like this:
Part 1: |
Part 2: |
Part 3: |
Part 4: |
Part 5: |
When transferring this data to the ANSYS Mechanical application, four instanced
singleton parts
,
,
,
and an uninstanced singleton part
are expected. This is due to body 2 having
been modified and therefore removed from the ANSYS DesignModeler application instance data.
User creates multibody part in the ANSYS DesignModeler application.
Part 1: |
User patterns
to create
bodies
as singletons:
Part 1: |
Part 2: |
Part 3: |
Part 4: |
The ANSYS DesignModeler application will consider bodies 2, 3, 4, 5 to be instances (without regard to ANSYS DesignModeler application part data).
When transferring this data to the ANSYS Mechanical application, Part 1 will be uninstanced, while Parts 2, 3, and 4 will be instances.
Next, user patterns Part1 (
) to create bodies
in
the ANSYS DesignModeler
application:
Part 1: |
Part 2: |
Part 3: |
Part 4: |
Part 5: |
Part 6: |
The ANSYS DesignModeler application will consider bodies
,
,
,
,
,
as
one set of instanced bodies and bodies
,
,
as another set.
When transferring this data to the ANSYS Mechanical application, there would be
no conflict between the ANSYS DesignModeler application parts
and body instance data. Thus, bodies
,
,
would all be single-body part instances,
and bodies (
,
), (
,
), (
,
) would all be multibody
part instances.