The feature is applied at the Model-level of the tree. To properly define a Condensed Part object, you need to configure the following:
A group of bodies
A set of interfaces
Solution settings
You create a Condensed Part from one or more interconnected bodies. Only 3D bodies (solids and shells) can be included in a Condensed Part.
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 interconnections are supported:
Bonded Contact
Shared topology
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.
Multi-body parts must be fully contained in a single Condensed Part, i.e., 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.
An interface defines the master 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.
The major interface type is Remote Point-Based Interface Entries. These entries refer to the nodes that are attached to the underlying topology. Common examples include the Mobile or Reference side of Joints and Springs and the scoping of a Point Mass and Remote Points.
General interfaces each contribute the number of nodes on their topology and remote interfaces each contribute a single node.
Supported Condense Part Interfaces include:
Joints
Springs
Point Mass
Remote Points
Contacts
When a Condensed Part Interface includes multiple remote points with overlapping faces, edges or vertices, the solver may disqualify master node DOFs in the generation pass. This may interfere with the use pass solve as well as postprocessing later on.
Only interfaces that are based on Remote Points are presently recognized by the Rigid Dynamics solver (Joints, Springs, Point Masses, and Remote Points). In addition, a Remote Point must have all six DOFs with an interface treatment of either or .
Note: When duplicate DOFs are disqualified and eliminated during the Generation Pass, the Rigid Dynamics solver issues an error and aborts the Use Pass.