
CMATRIX=id | Specifies the identifier of the MATRIX that the NFORCE uses as its damping matrix. The CMATRIX is a matrix (n is the number of I markers) that defines the linear relationships between the I marker velocities relative to the J marker and the viscous forces generated by the NFORCE. The CMATRIX is derived in the J marker’s coordinate system. If neither CMATRIX nor CRATIO is given, the NFORCE is undamped. Marker translational and rotational velocities appear sequentially in Vx, Vy, Vz, x, y, z order, while the markers appear in the same sequence as in the IMARKER argument. |
CRATIO=r | Specifies the proportional damping ratio for the NFORCE. The elements of the damping matrix are determined by multiplying the corresponding stiffness element value by this number. If direct input of the damping properties is desired, the CMATRIX may be used. If neither CMATRIX nor CRATIO is given, the NFORCE is undamped. |
FORCE | Specifies the identifier of the MATRIX that contains the forces and torques that the NFORCE would produce if all the I markers were at the positions given in LENGTH. FORCE is a matrix (n is the number of I markers) of forces and torques, appearing sequentially for each marker in Fx, Fy, Fz, Tx, Ty, Tz order, while the markers appear in the same sequence as in the IMARKER argument. The force and torque components are expressed in the J marker’s coordinate system. When LENGTH is used to specify the system’s free lengths, FORCE gives the preloads. If FORCE is not given, the NFORCE acts as though a matrix of zeros are input. |
IMARKERS=id1,...,idn | Lists the markers (except for the J marker) between which the NFORCE forces and torques act. Number of values: 1 to 350 |
J=id | Specifies the identifier of the marker that determines the reference frame in which the relative velocities and all of the forces associated with the NFORCE are calculated and the coordinate system in which all the components and LENGTHs are evaluated. The NFORCE automatically applies the proper reaction forces at the J marker. |
KMATRIX=id | Specifies the identifier of the MATRIX that the NFORCE uses as its stiffness matrix. The KMATRIX is a matrix (n is the number of I markers) that defines the linear relationships between the I marker displacements relative to the J marker and elastic forces generated by the NFORCE. The KMATRIX is specified in the J marker’s coordinate system. Marker translational and rotational displacements appear sequentially in Dx, Dy, Dz, Ax, Ay, Az, order, while the markers appear in the same sequence as in the IMARKER argument. |
LENGTH=id | Specifies the identifier of the MATRIX that defines a reference location for each of the I markers with respect to the J marker, measured in the J marker’s coordinate system. LENGTH is a column matrix (n is the number of I markers) of translational displacements only, in Dx, Dy, Dz order. Usually, LENGTH is used to specify the system’s free (no internal force) lengths when they differ from the input positions. If LENGTH is not given, the NFORCE assumes that the input positions of the I markers are at the reference locations. |
+ FORCE
matrix of forces exerted on the I markers.
truncated stiffness matrix, created by striking out the rows and columns associated with the J marker’s degrees-of-freedom.
matrix of the translational and angular displacements of the I markers with respect to the J marker, expressed in the J marker’s coordinate system.
matrix of the reference displacements of the I markers with respect to the J marker, expressed in the J marker’s coordinate system. The translational displacements in L are the elements of LENGTH, while the angular reference displacements are always zero.
truncated damping matrix, created by striking out the rows and columns associated with the J marker’s degrees-of-freedom.
is the
matrix of the translational and linearized angular velocities of the I markers with respect to the J marker, and expressed in the J marker’s coordinate system.
matrix of the reference forces on the I markers; that is, the forces on the I markers when their displacements relative to the J marker are specified by L. When LENGTH contains the free lengths, FORCE is the preload.

Tip: | ■When importing stiffness and damping matrices that are developed using finite element methods, the LENGTH and FORCE arguments are most easily thought of as the system free lengths (zero internal stress) and preloads. You can, however, specify any consistent set of reference lengths and resulting forces, just as for the SPRINGDAMPER element. ■Physically meaningful NFORCES have positive semi-definite KMATRIX and CMATRIX matrices. That is, the diagonal entries of the matrices have positive value. Adams Solver only accepts NFORCES having positive semi-definite matrices. |
Caution: | ■Like the BEAM, the NFORCE is a linear element, so that the forces computed are generally valid only for small displacements. When the applied loading is such that the small displacement limits are exceeded (a good estimate is ten percent of lengths and less than 0.2 radian rotations), the NFORCE results may be less accurate. In cases where the structure undergoes large overall deflections but remains linearly elastic (small local deflections), you can use more NFORCE elements, so that each NFORCE element remains locally within small displacement limits. Note that because of the way that Adams Solver computes angular displacements, the absolute magnitude of this inaccuracy due to overly large displacement may depend on the instantaneous spatial orientation of the system. ■A two-point NFORCE is not identical to a field, although it is very similar. The following differences make it difficult to create exactly equivalent NFORCEs and FIELDs. ■The FIELD defaults reference lengths to zero, while the NFORCE assumes by default that the input positions of the I markers are at the reference locations. ■The FIELD allows you to specify reference angles for the rotational displacements, while the NFORCE assumes the reference angles are always zero. |


finite element grid (36 elements), which are then reduced to a
grid using super-element condensation before importing it into Adams Solver as an NFORCE. Because of formulational differences between FEA and Adams’ multibody systems analysis, it is generally not possible to have a one-to-one correspondence between Adams Solver PARTs and FEA nodes, unless the FEA model is very small.