You have limited editing capability for imported connection features. These are bulk
features with imported data for more than one connection.
Nastran Data Card |
Field |
Abaqus Keyword |
Notes |
3DEXPERIENCE Feature |
CGAP |
— |
*ELEMENT, TYPE=CONN3D2 |
— |
Mesh CONN3D2 elements |
EID |
Element number |
PID |
Section assignment |
GA, GB |
Node numbers |
GO/(Xi)/CID |
*ORIENTATION |
PGAP |
PID |
Section assignment |
If
, *CONNECTOR SECTION, AXIAL, *CONNECTOR ELASTICITY (KB), and
*CONNECTOR STOP. If
, *CONNECTOR SECTION, AXIAL, *CONNECTOR ELASTICITY (KA), and no
*CONNECTOR STOP. |
Connector |
U0 |
Lower limit for the connector's relative position at *CONNECTOR STOP |
KA, KB |
*CONNECTOR STOP and/or *CONNECTOR SECTION, AXIAL and *CONNECTOR
ELASTICITY |
CELAS1 |
— |
*ELEMENT, TYPE=SPRING1 or SPRING2 |
— |
Mesh Spring1 or Spring2 Elements and Spring Connection |
EID |
Element number |
PID |
Section assignment |
G1, G2 |
Node numbers |
C1, C2 |
Data lines on *SPRING |
PELAS |
— |
*SPRING, COMPLEX STIFFNESS |
— |
Spring Connection |
PID |
Section assignment |
K, GE |
Data lines on *SPRING |
CELAS2 |
— |
*ELEMENT, TYPE=SPRING1 or SPRING2 |
— |
Mesh Spring1 or Spring2 Elements |
EID |
Element number |
K, C1, C2, GE |
Data lines on *SPRING |
G1, G2 |
Node numbers |
CBUSH |
— |
*ELEMENT, TYPE=CONN3D2 |
— |
Mesh Spring1 or Spring2 Elements |
EID |
Element number |
PID |
Section assignment |
GA, GB |
Node numbers |
CID |
*ORIENTATION |
PBUSH |
— |
*CONNECTOR SECTION with CARTESIAN or CARDAN |
— |
Connector |
PID |
Section assignment |
K |
*CONNECTOR ELASTICITY |
K1–K6 |
Data lines on *CONNECTOR ELASTICITY, COMPONENT |
B |
*CONNECTOR DAMPING, TYPE=VISCOUS |
B1–B6 |
Data lines on *CONNECTOR DAMPING, TYPE=VISCOUS, COMPONENT |
GE |
*CONNECTOR DAMPING, TYPE=STRUCTURAL |
GE1–GE6 |
Data lines on *CONNECTOR DAMPING, TYPE=STRUCTURAL, COMPONENT |
MPC |
— |
*EQUATION |
Only those MPCs that are referenced in the Case Control section are
imported. |
Equation |
Gi |
Data line of *EQUATION |
— |
Ci |
Data line of *EQUATION |
Ai |
Data line of *EQUATION |
MPCADD |
— |
— |
Only MPCADD data cards that are referenced in the Case Control section are
imported. |
No 3DEXPERIENCE feature. |
Si |
— |
MPC data cards with SIDs (Si) are mapped to individual *EQUATION
options. |
RBE2 |
— |
*COUPLING and *KINEMATIC |
— |
Coupling |
ALPHA |
*KINEMATIC, ALPHA |
GN |
Node number |
CM |
Data line on *KINEMATIC |
GMi |
Node number |
Orientation fix |
*ORIENTATION reference from *COUPLING |
The imported orientation is dependent on the value in the CM field. For more
information, see Notes About RBE2. |
RBE3 |
— |
*COUPLING and *DISTRIBUTING |
RBE3 is handled differently for special cases. For more information, see Notes About RBE3. |
Coupling |
REFGRID |
*COUPLING, REF NODE |
— |
REFC |
Data line on *DISTRIBUTING |
WTi, Gi, j |
Data lines on *SURFACE, TYPE=NODE |
Orientation fix |
*ORIENTATION reference from *COUPLING |
If REFGRID has a CD field, there is an orientation associated with the
distributed coupling consistent with the referenced coordinate system. |
Ci |
*DISTRIBUTING, COUPLING=CONTINUUM, if all Ci fields contain
translational degrees of freedom only *DISTRIBUTING, COUPLING=STRUCTURAL, if any
Ci field contain rotational degrees of freedom |
— |
Notes About RBE2
The imported orientation is dependent on the value in the CM field. If the CM field is 123,
456, or 123456, there is no orientation associated with the kinematic coupling. If the CM
field is any other value, the imported orientation becomes dependent on which coordinate
systems the cloud GRIDs (GMi) reference:
- If all cloud GRIDs reference the same coordinate system at the respective CD field,
there is an orientation associated with the kinematic coupling consistent with the
referenced coordinate system.
- If all cloud GRIDs do not reference the same coordinate system at the respective CD
field, there is no orientation associated with the kinematic coupling.
Notes About RBE3
If two RBE3 data cards (with the DOF combinations matching the example below) have REFGRIDs
with the same value and the REFGRIDs are also part of a cloud nodes list, the importer
merges the RBE3 data cards and imports only one set of *COUPLING and *DISTRIBUTING
keywords.
RBE3, 10006, ,
8012,
123, .25, 123, 8006, 8007, 8008, 8009, 1.,
456,
8012
RBE3, 10007, ,
8012,
456, .25, 456, 8006, 8007, 8008, 8009, 1.,
123,
8012
After the import, the *COUPLING and *DISTRIBUTING keywords no longer use REFGRID as part of
the cloud nodes, and the COUPLING parameter is set to STRUCTURAL.
If the imported file contains only one RBE3 data card, the *COUPLING and *DISTRIBUTING
keywords no longer use REFGRID as part of the cloud nodes, and the COUPLING parameter is set
to STRUCTURAL.
|