Bulk Data Entry Defines a scalar damper element.


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
CDAMP1 EID PID G1 C1 G2 C2      


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
CDAMP1 2 10 0   26 3      


Field Contents SI Unit Example
EID Unique element identification number.

No default (Integer > 0)

PID A PDAMP property entry identification number.
Specifies an identification number for this property.
Specifies a user-defined string label for this property. 7

Default = EID (Integer > 0 or <String>)

G1, G2 Geometric grid point or scalar point identification number.

Default = 0 (Integer ≥ 0)

C1, C2 Component number in the displacement coordinate system specified by the CD entry of the GRID data.

Default = 0 (0 ≤ Integer ≤ 6)



  1. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a corresponding blank or zero C1 or C2. A grounded terminal is a point whose displacement is constrained to zero.
  2. Scalar points may be used for G1 and/or G2, (with corresponding C1 and/or C2 of zero or blank). If only scalar points and/or grounded terminals are involved, it is more efficient to use the CDAMP3 entry.
  3. The two connection points (G1, C1) and (G2, C2) must be distinct.
  4. A scalar point specified on this entry does not need to be defined on a SPOINT Bulk Data Entry.
  5. When the SPSYNTAX setting on the SYSSETTING I/O Options Entry is set to CHECK (default) or STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank when the grid reference is a scalar point (SPOINT), and that the component be > 1 when the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point (SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank; interpreting all of these as 0 for scalar points and as 1 for structural grids. When the component is greater than 1, the grid reference must always be a structural grid (GRID).
  6. Scalar damper elements are ignored in heat transfer analysis.
  7. String based labels allow for easier visual identification of properties, when being referenced by the elements cards. For more details, refer to String Label Based Input File in the Bulk Data Input File.
  8. This card is represented as a spring or mass element in HyperMesh.