PAM-CRASH 2G Interface

Overview of the PAM-CRASH 2G interface.

HyperMesh provides a complete pre-processing environment for preparing PAM-CRASH 2G data decks for analysis. HyperMesh can read existing PAM-CRASH 2G decks, create a model, display and edit PAM-CRASH 2G cards as they will look in the deck, and write a deck for analysis. Although HyperMesh also offers limited post-processing capabilities in results translation, you are encouraged to exclusively use HyperView. To create PAM-CRASH 2G decks in HyperMesh, you must load the PAM-CRASH 2G user profile with the appropriate template to access the full pre-processing capability.

Import and Export

  • HyperMesh supports PAM-CRASH solver versions VPS 2015 to VPS 2021.
  • Keyword attribute comments are written in the exported deck for PAM-CRASH 2G versions 2012 to 2021.
  • Solver-specific import options are available during import in the Solver Options tab.
  • The PAM-CRASH interface supports a smart, reliable FE input reader that warns you when your input deck contains unsupported fields and unsupported data lines.
  • Most IDs in the solver deck are preserved in HyperMesh. If a keyword is not supported in a dedicated HyperMesh entity to ensure its unique ID-Pool, thenHyperMesh renumbers those keywords when ID conflicts are detected. The new IDs are posted during the import process.
  • PAM-CRASH 2G interface supports Modular (MMAT and MPART) and its associated LOOKU and NUMPAR keywords in HyperMesh 2021.1 and onwards.
  • HyperMesh supports parameterized IDs for SENSOR, DELEM, FUNCSW, FUNCT, SECURE_FUNCT, FRAME, RUPMO, CDATA, CHEM, CNTPTY, DMPEW, FRICT, LAYER, NLAVE, OPTLIS.
  • HyperMesh supports undefined entities. These are entity IDs that are referenced in keywords (for example, a Material ID in a Part) but are not defined in the deck. In these cases, HyperMesh creates a default card in order to preserve the ID. For example, a material of type MATER Type 100 is created. This keyword has the Defined checkbox toggled off and is not automatically exported.
  • During import, all the GES associated with the solver keywords are mapped to entity sets in HyperMesh and associated with the solver entity. They are exported back as GES during export.
  • The PAM-CRASH 2G input translator also supports reading older PAM-CRASH 2G files 2002 - 2014 and map into the loaded template.
  • PAM-CRASH and PAM-CRASH 2G 2002 - 2014 templates are available in the installation and can be loaded. However, they are no longer maintained.

Mass Calculations

  • The mass of each element is calculated by density * volume. Density is retrieved from the material associated with the element’s component. Several assumptions are made in mass calculation based on PAM-CRASH 2G solver.
  • For rigid bodies (RBODY) of type 3 with a user-imposed center of gravity and mass and inertia properties, the structural mass of the PART components are replaced by the rigid body mass. All other keywords besides the PART keyword are neglected in the RBODY type 3 mass calculation.
  • The following table summarizes how each supported element in the HyperMesh PAM-CRASH 2G interface, except shells and solids, performs these calculations:
PAM-CRASH 2G Keyword Area Volume Mass Notes
MASS / 0 0 M= M x 2 + M y 2 + M z 2
SLIPR / 0 0 0
RETRA / 0 0 0
SENPT / 0 0 0
PLINK / 0 0 0
RBODY / 0 0 $RBODY_MASS Rigid body type 3.
NODCO / 0 0 0
SPRING / 0 0 Material type 220.
SPRGBM / 0 0 Material type 223.
BAR / 0 V= A bar *Length V 205 =0.0 M=p*V M 205 =Length* Mass Length Material types 200, 201, 202, 203, 204, and 205.
JOINT / 0 0 0
KJOIN / 0 0 0  
NSMAS 0 0 MASS Non-Structural Mass Definition - Standard Input Format
NSMAS2 0 0 MASS / MLEN /MARE / MVOL Non-Structural Mass Definition - Alternate Mass Distribution Method
MTOCO / 0 0 MMTO MTOCO / Type 1: User-imposed mass of MTOCO