You insert a Condensed Geometry object via the Model object in the Outline and then insert and define Condensed Part objects. To properly define a Condensed Part, you need to configure the following:
A group of bodies
A set of interfaces
Solution settings
Condensed Part Bodies and Interconnections
You create a Condensed Part from one or more interconnected bodies.
Important: Because the resulting superelement is linear, any nonlinearities in the Condensed Part elements, materials, and interior connections are ignored.
When defining a Condensed Part using multiple bodies, the following connections may be included:
Bonded Contact
Shared topology
- General Restrictions for Part Bodies and Interior Connections
Cyclic Symmetry is not supported.
Rigid bodies may be used, but it is best for at least one body to be flexible.
Elements cannot use Lagrange multipliers. For example, interior contact regions cannot use the Formulation.
- Part Bodies and Interconnection Solver Restrictions (Ansys Rigid Dynamics Solver)
Multi-body parts must be fully contained in a single Condensed Part, that is, partial selections are invalid. You may however use several multi-body parts in a single Condensed Part.
The single connected component must produce six rigid modes. An insufficient number of modes will cause the Use Pass not to converge. An excess of modes can usually be remedied by breaking the Condensed Part into smaller rigidly connected components.
Interfaces
An interface defines the primary nodes for the resulting superelement and therefore suggests how a Condensed Part could connect to the rest of the model. In Mechanical, an interface table lists each of these connections, detailing their Type, Side, and Name. Supported interface types are based on:
Geometry: Geometry interfaces directly expose all nodes on a particular topology, for example, on a vertex, face or edge. These primary nodes are therefore suitable for the application of boundary conditions such as contacts and supports.
Remote Points. These entries expose remote points as primary nodes, while hiding interior nodes on the underlying topology that attach to them. Common examples include the Mobile or Reference side of Joints and Springs and the scoping of Point Masses and Remote Points. This is the only type of interface supported for the Ansys Rigid Dynamics Solver.
Named Selections: Named Selections can be used to expose any node as a primary node, with the help of criterion-based Named Selection. For example, selected internal nodes within a condensed part volume could be relegated to the interface in order to produce a higher resolution of the structure's inertial or flexibility behavior
Connections: Contact Region, Joint, etc.
Note: For a Contact Region interface of a Condensed Part, when the Trim Contact property is set to , the generation of the trims the contact nodes on the interface and uses the trimmed nodes as the Master Degrees of Freedom for the generation pass. The reduction of the number of nodes can significantly improve the performance of the generation pass. When you select the Condensed Part object after the generation pass, the application displays the trimmed nodes in the Geometry window for the Contact Region Interface instead of the actual Contact Region scoping.
Loads and Supports: Fixed Supports, Displacements, etc.
Point Masses
General interfaces each contribute the number of nodes on their topology and remote interfaces each contribute a single node.
Important: When a Condensed Part Interface includes faces, edges, vertices, or nodes that overlap with other interfaces where constraint equations are applied, such as remote points, boundary conditions scoped to remote points, MPC-based contact, etc.), the solver may remove some master node DOFs in the generation pass. This may interfere with the use pass solve as well as postprocessing.
Note: When duplicate DOFs are disqualified and eliminated during the Generation Pass, the Rigid Dynamics solver issues an error and aborts the Use Pass.
- Interface Solver Restrictions (Ansys Rigid Dynamics and Motion Solvers)
Only interfaces that are based on Remote Points are presently recognized by the Rigid Dynamics and Motion solvers (Joints, Springs, Point Masses, and Remote Points). In addition, a Remote Point must have all six DOFs with an interface treatment of either or .