Altair HyperMesh Interfacing with...

of 68/68
Altair HyperMesh Interfacing with LS-DYNA Version 5.1
  • date post

    26-Aug-2018
  • Category

    Documents

  • view

    274
  • download

    13

Embed Size (px)

Transcript of Altair HyperMesh Interfacing with...

  • Altair HyperMesh Interfacing with LS-DYNA

    Version 5.1

  • Contact Altair Engineering at:

    Web site www.altair.com

    FTP site Address: ftp.altair.com or ftp2.altair.com

    Login: ftp

    Password:

    Location Telephone e-mail

    North America 248.614.2425 [email protected]

    Germany 49.7031.6208.22 [email protected]

    India 91.80.658.8540 91.80.658.8542

    [email protected]

    Italy 39.0832.315.573 39.800.905.595

    [email protected]

    Japan 81.3.5396.1341 [email protected]

    Scandinavia 46.46.286.2052 [email protected]

    United Kingdom 44.1327.810.700 [email protected]

    2002 Altair Engineering, Inc. All rights reserved.

    Trademark Acknowledgments:

    HyperWorks, HyperMesh, OptiStruct, HyperForm, MotionView, HyperView, HyperGraph, HyperOpt, HyperShape/Pro, StudyWizard, HyperView Player and Templex are registered trademarks of Altair Engineering, Inc.

    All other trademarks and registered trademarks are the property of their respective owners.

  • Altair Engineering Interfacing with LS-DYNA 1

    LS-DYNA Translation Overview

    This section describes the HyperMesh LS-DYNA interface. HyperMesh can read existing LS-DYNA decks, create a model, display and edit LS-DYNA cards as they will look in the deck, and write a deck for analysis. HyperMesh also processes LS-DYNA binary and ASCII results files so that the results can be viewed in HyperMesh. HyperMesh treats LS-DYNA as a card image code.

    See Also

    Components and Properties Nodes

    Control Volumes Other Groups

    Creating Cards Output Blocks

    Curves Results Translation

    Elements Rigid Walls

    Entity Sets Sensors

    Equations Summary Templates

    Exporting Decks Supported Cards

    HyperMesh Groups Systems

    Importing Decks Tips and Techniques

    Load Collectors Vectors

    Loads, Constraints, and Boundary Conditions Viewing the Results

    Materials Working with Comment Cards

    Supported Dyna Keywords LS DYNA KEY Macro Menu

    Recommended Process

    Importing Decks

    Versions of Keyword files are read using the DYNAKEY input translator (or DYNAKEY.EXE on PCs).

    Structured files of version 920 and higher are read using the DYNASEQ input translators ( or DYNASEQ.EXE on PCs). This translator handles both regular and large format decks. Thermal control cards 27 through 30 are not supported.

    To import data with the input translator:

    1. Select the files panel.

    2. Select the import subpanel.

  • Interfacing with LS-DYNA Altair Engineering 2

    3. Click EXTERNAL.

    4. Click translator = and enter /LS-DYNA/DYNAKEY(.EXE) or /LS-DYNA/DYNASEQ(.EXE), or click translator = again to browse the directory structure for the translator.

    5. Click filename = and enter the name of your LS-DYNA file, or click filename = again to browse the directory structure for your file.

    6. Click import.

    Exporting Decks

    HyperMesh outputs the following LS-DYNA files:

    LS-DYNA v960 input files in Keyword format

    LS-DYNA v936 input files in Structured format

    To output Keyword decks, use the dyna.key template file

    To output regular format Structured decks, use the dyna.seq template file

    To output large format Structured decks, use the dyna.lrg template file

    Two templates are also provided to output the defined curves in the database:

    To output curves in Keyword format, use the curves.key template

    To output curves in Structured format, use the curves.seq template

    NOTE When converting an LS-DYNA model to the RADIOSS format, check and update the element types prior to writing the converted model to file. Some formulations may not map correctly, such as RADIOSS SHELL 3N to LS-DYNA ACCEL.

    To create an analysis deck via a template:

    1. Select the files panel.

    2. Select the export subpanel.

    3. Click filename = and enter the name of the output file.

    4. Click TEMPLATE.

    A new input field, template = is displayed if not already displayed.

    5. Click template = and specify the file name of the template file.

    6. Click write.

    Summary Templates

    To obtain a concise list of entities in the current model, use the template file = option on the summary panel. This creates an ASCII text file with the summary information and displays the information on the screen.

  • Altair Engineering Interfacing with LS-DYNA 3

    LS-DYNA has four summary template files: elements, properties, center_of_gravity, and errorcheck. They are located in the template/summary/ls-dyna directory.

    The elements summary template provides a listing of element types and the number of each type contained in the current model. It also indicates the total number of elements in the model.

    The properties summary template describes the components and their properties contained in the model. The template lists the name, ID, and material ID for each component. Components that have the *PART card image loaded also list the Section ID, the card option (for example *PART_INERTIA), and the mass contained in that component. The mass is calculated using the same procedure as the mass panel. See Mass Calculation.

    The center_of_gravity summary template calculates the models center of gravity based on the procedure described in the Mass Calculations section.

    There are also two templates that perform error checking on LS-DYNA models: errorcheck and sharedrigids.

    Use the errorcheck template in the summary panel. This template gives a brief overview of problems that exist in the model.

    Use the sharedrigids template in the element check panel. This template highlights the elements with nodes that are shared among rigids.

    When either of the error-checking templates check for shared rigids, the template highlights only the second element that uses a node. If an element in a rigid material is sharing a node with another rigid, only the first element in that component is highlighted.

    Possible errors messages:

    Elements in components pointing to a *SECTION card of the wrong type Zero or negative thickness Rigid elements, components, or interfaces sharing nodes Components do not have a *SECTION card selected Components do not have a necessary *PART card defined Components do not have a material selected

    Mass Calculation

    The mass of each element is the calculation of density * volume. When calculating model mass, several assumptions are made for the element volume. Densities are retrieved from the material associated with the elements component.

    A *PART_INTERIA card uses the supplied mass instead of calculating the mass based on the individual elements.

    Mass calculations include the mass supplied on the *CONSTRAINED_NODAL_RIGID_BODY_INERTIA cards.

    A shell element thickness is one of the following:

    the thickness on the first node for uniform thickness shells

  • Interfacing with LS-DYNA Altair Engineering 4

    the average of three or four nodes for non-uniform thickness shells

    The values come from the *SECTION_SHELL card, unless a *ELEMENT_SHELL_THICKNESS card is defined for an element. If an *ELEMENT_SHELL_THICKNESS card is defined, the element values override the *SECTION_SHELL values.

    Integrated beams have an area equal to the average of the two end areas. Resultant beams use the area entered on the *SECTION_BEAM card. The volume is calculated by multiplying the length of the beam by the *SECTION_BEAM card area. Discrete beams use the volume supplied by the *SECTION_BEAM card. In all cases, if an *ELEMENT_BEAM_THICKNESS card is defined for an element, then the element values override the *SECTION_BEAM values.

    Only element masses are considered. Other mass specifications, such as on a rigid wall card, are ignored.

    Supported Cards The HyperMesh LS-DYNA interface supports the following cards:

    Components and Properties Materials

    Control and Database Cards Nodes

    Control Volumes Other Groups

    Curves Output Blocks

    Elements Rigid Walls

    Entity Sets Sensors

    Equations Systems

    HyperMesh Groups Vectors

    Load Collectors Working with Comment Cards

    Loads, Constraints, and Boundary Conditions Supported Dyna Keywords

    Working with Comment Cards HyperMesh-defined comment cards included in decks written by HyperMesh. These comments are included so that decks can be written and re-read without losing information as well as to reorganize the database. These comments can be read from any deck and can be inserted into a deck before importing the deck into HyperMesh.

    $HM_OUTPUT_DECK

    This comment signals that the deck was created by HyperMesh. It also gives the date and time the deck was written.

    $HMNAME Entitytype ID HyperMesh_Name

    This comment gives the name of the collector where the information that follows originated. If this comment is present, HyperMesh_Name, a 32-character string value, is used as the collector name. The ID, an 8 character integer, is also passed to HyperMesh. Entitytype is the collector type, such as COMP or GROUP.

  • Altair Engineering Interfacing with LS-DYNA 5

    $HMCOLOR Entitytype ID Color

    This comment changes the color of a collector or curve. Entitytype is the collector type, such as COMP or GROUP. ID is an 8 character integer that identifies the collector. Color is an 8-character integer that specifies the new color of the collector.

    $HMSET

    This comment signifies that you created the following set in HyperMesh, and that it was not created while the template outputs the deck. This changes how the set is imported into HyperMesh and how it is associated with groups.

    $HMCURVE linetype markertype title

    This comment preserves the style information for load curves. linetype is a 5-character integer that describes the style of the line: solid, dashed, and so on. markertype is a 5-character integer that describes the style of the point marker on the curve: square, round, and so on. title is an 80-character string used to save the curve label.

    $HMLINE id collectorid

    The geometric information not exported and imported back into HyperMesh.

    $HMFIXEDSURFPOINT x y z Suppressed

    These comments describe weld points for the automesher. X, Y, and Z are 16-character real numbers describing the x, y, z location of the fixed point. suppressed is an 8-character integer describing the type of fixed point.

    $HMERROR text

    This comment is output when the HyperMesh template detects and/or corrects a problem during deck creation. This informs you of possible problems with the deck.

    $HM text

    This comment writes an informational message. It does not write error messages.

    Control and Database Cards Accessed via the Control Card Editor

    Keyword and Structured have different cards, but sometimes, the same data is valid for both types

    Thermal Control Cards are not supported

    Keyword

    HyperMesh Name LS-DYNA Keyword Notes

    ReadMe Comment cards All lines before *KEYWORD are read as comment cards. These can be modified in HyperMesh.

    TitleCard *TITLE

    Keyword *KEYWORD This card must be the first block in the Keyword template for

  • Interfacing with LS-DYNA Altair Engineering 6

    HyperMesh to output a valid Keyword deck.

    When the card is active, memory requirements may be specified; otherwise it is automatically output on the first line of the file.

    HyperMesh Name *CONTROL Cards Notes

    Accuracy _ACCURACY

    Adaptive _ADAPTIVE

    ALE 1 _ALE

    BulkVisc _BULK_VISCOSITY

    Contact _CONTACT

    Coupling _COUPLING

    CPU _CPU

    Dyn Relax _DYNAMIC_RELAXATION _DAMPING is read in, but not supported on export.

    Energy _ENERGY

    Hourglass _HOURGLASS

    Output Ctrl _OUTPUT

    Parallel _PARALLEL

    Shells _SHELL

    Subcycle _SUBCYCLE

    Solution _SOLUTION

    Structured _STRUCTURED

    Termination _TERMINATION

    Time Step _TIMESTEP

    Global Damp _GLOBAL

    ImplicitAuto

    ImplicitDyna

    ImplicitEigen

    ImplicitGen

    ImplicitSolver

    ImplicitSoln

    ImplicitStab

    Rigid

    _IMPLICIT_AUTO

    _IMPLICIT_DYNAMICS

    _IMPLICIT_EIGENVALUE

    _IMPLICIT_GENERAL

    _IMPLICIT_SOLVER

    _IMPLICIT_SOLUTION

    _IMPLICIT_STABILIZATION

    _RIGID

  • Altair Engineering Interfacing with LS-DYNA 7

    HyperMesh Name *DATABASE Cards Notes

    DBase Opts _OPTION For example, SECFORC, RWFORC, NODOUT, and so on. These can be edited on one panel. The selected values have cards output.

    DB Bin PLOT _BINARY_D3PlOT

    DB Bin THDT _BINARY_D3THDT

    DB Bin DRLF _BINARY_D3DRLF

    DB Bin DUMP _BINARY_D3DUMP

    DB Bin RUNRS _BINARY_RUNRSF

    DB Bin INTFO _BINARY_INTFOR

    DB Bin XTFILE _BINARY_XTFILE

    DB Xtnt AVS _EXTENT_AVS

    DB Xtnt MPG _EXTENT_MPGS

    DB Xtnt MOV _EXTENT_MOVIE

    DB Xtnt BIn _EXTENT_BINARY

    DB Spr Fwd _SPRING_FOWARD

    Super Plast _SUPERPLASTIC_FORMING

    DB Tracer _TRACER

    Structured

    Cards auto-generated:

    Cards 1 (Model Size), 2 (Model Size), 3 (Model Size), 4 (Model Size), 5 (Model Size), 6 (Model Size), 7 (Model Size), 10 (Loading Options), and 11 (Input Control)

    Additional fields that specify the number of items in the deck, such as the number of TIME HISTORY blocks, are filled. When you edit cards that contain automatically generated fields, it is indicated by the card previewer.

    HyperMesh Name Editable Control Cards

    1 - Title Card This card has 930 as a version number. LARGE is output when you use the dyna936.lrg template.

    Termination 8 - Termination

    Time Step 9 - Time Steps

    Beams and Shells 12 - Beams and Shells

    Materials 13 - Material Related Input

    Damping 14 - Damping/Dynamic Relaxation

    Contact 15 - Contact

    Paral/Subcyc 16 - Parallel and Subcycling

  • Interfacing with LS-DYNA Altair Engineering 8

    Coupling 17 - Coupling

    OutputCtrl 18 - Output

    Energy Out 19 - Output Energy

    TAURUS I 20 - TAURUS Database Control 1

    TAURUS II 21 - TAURUS Database Control 2

    ASCII Out 1 22 - ASCII Output Control 1

    ASCII Out 2 23 - ASCII Output Control 2

    ASCII Out 3 24 - ASCII Output Control 3

    ALE 1 25 - Arbitrary Lagrangian 1

    ALE 2 26 - Arbitrary Lagrangian 2

    Systems

    HyperMesh reads all LS-DYNA system formulations. Defined coordinate systems using three nodes or two vectors are converted so that they use three points, based on the LS-DYNA definition of those systems.

    The supported output format for systems is *DEFINE_COORDINATE_SYSTEM and *DEFINE_COORDINATE_NODES in Keyword or type 1 in Structured.

    Nodes

    Node cards are fully input into HyperMesh.

    Structured nodes are output using a 3E20.0 format. Other formats are input, based on the definition on Control Card 11.

    Elements

    HyperMesh Type Keyword Structured Notes

    Mass 1 *ELEMENT_MASS Card 50

    2 *ELEMENT_SEATBELT_ RETRACTOR

    3 *ELEMENT_SEATBELT_ SLIPRING

    4 *ELEMENT_INERTIA

    5 *ELEMENT_SEATBELT_ PRETENSIONER

    Weld 1 *CONSTRAINED_ SPOTWELD

    Card 29c Structured DOF = -1. Failure values can be edited on the

  • Altair Engineering Interfacing with LS-DYNA 9

    individual elements.

    2 *CONSTRAINED_RIVET Card 29b Structured DOF = 0

    Rigid (two-noded)

    2 *CONSTRAINED_NODE_ SET

    Card 29a Structured DOF = 1 through 7

    1 *CONSTRAINED_NODAL_ RIGID_BODY

    Card 36a Structured Failure Option 0. Keyword _INERTIA option supported.

    3 *CONSTRAINED_ GENERALIZED_WELD

    Card 36a _SPOT (structured 1), _FILLET (2), _BUTT (3) options supported.

    Spring 1 *ELEMENT_DISCRETE Card 50 Dyna Spring and Damper elements

    Joints 1 *CONSTRAINED_JOINT_ SPHERICAL

    Card 38 Structured type is the same as the HyperMesh type.

    2 *CONSTRAINED_JOINT_ REVOLUTE

    Card 38 Structured type is the same as the HyperMesh type.

    3 *CONSTRAINED_JOINT_ CYLINDRICAL

    Card 38 Structured type is the same as the HyperMesh type.

    4 *CONSTRAINED_JOINT_ PLANAR

    Card 38 Structured type is the same as the HyperMesh type.

    5 *CONSTRAINED_JOINT_ UNIVERSAL

    Card 38 Structured type is the same as the HyperMesh type.

    6 *CONSTRAINED_JOINT_ TRANSLATIONAL

    Card 38 Structured type is the same as the HyperMesh type.

    7 *CONSTRAINED_JOINT_ LOCKING

    Card 38 Structured type is the same as the HyperMesh type.

    Rigid Links (many noded)

    2 *CONSTRAINED_NODE_ SET

    Card 29a Structured DOF = 1 through 7

    1 *CONSTRAINED_NODAL_ RIGID_BODY

    Card 36a Structured Failure Option 0. Keyword _INERTIA option supported.

    3 *CONSTRAINED_ GENERALIZED_WELD

    Card 36a _SPOT (structured 1), _FILLET (2), _BUTT (3) options supported.

    Bar2 1 *ELEMENT_BEAM Card 8 _THICKNESS option supported. Use direction node option. The actual node is referenced /read/ written by HyperMesh.

    _PID option is supported. When running the Dyna solver. This is helpful in limiting the search for the nearest elements to attach

  • Interfacing with LS-DYNA Altair Engineering 10

    the beam element (Elform type 9).

    Rod 1 *ELEMENT_SEATBELT N/A

    Tria3 2 *ELEMENT_SEATBELT_ ACCELEROMETER

    Card 51g

    Tria3 1 *ELEMENT_SHELL Card 9 _THICKNESS and _BETA options supported.

    Quad4 1 *ELEMENT_SHELL Card 9 _THICKNESS and _BETA options supported.

    Tetra4 1 *ELEMENT_SOLID Card 7

    Penta6 1 *ELEMENT_SOLID Card 7

    Hex8 1 *ELEMENT_SOLID Card 7

    2 *ELEMENT_TSHELL Card 10

    Materials A material is created to maintain existing numbering for material type input not supported by

    HyperMesh. This material is called NOMAT in HyperMesh.

    Materials without a loaded card image are not output.

    HyperMesh Keyword *MAT_ Structured Notes

    NOMAT UNSUPPORTED Type 999 Holds ID, name, type, and density for unsupported materials.

    MATL1 ELASTIC Type 1 Fluid option supported. See NOTE 1.

    MATL2 ORTHOTROPIC_ELASTIC Type 2

    MATL3 PLASTIC_KINEMATIC Type 3

    MATL5 SOIL_AND_FOAM Type 5

    MATL6 VISCOELASTIC Type 6

    MATL7 BLATZ-KO_RUBBER Type 7

    MATL9 NULL Type 9 Choose between Solid and Shell formulations when using the Card Editor. See NOTE 2.

    MATL10 ELASTIC_PLASTIC_HYDRO Type 10

    MATL12 ISOTROPIC_ELASTIC_PLASTIC Type 12

    MATL14 SOIL_AND_FOAM_FAILURE Type 14

    MATL15 JOHNSON_COOK Type 15

    MATL18 POWERLAW_PLASTICITY Type 18

    MATL19 STRAIN_RATE _DEPENDANT_PLASTICITY

    Type 19

  • Altair Engineering Interfacing with LS-DYNA 11

    MATL20 RIGID Type 20

    MATL22 COMPOSITE_DAMAGE Type 22

    MATL24 PIECEWISE _LINEAR_PLASTICITY

    Type 24

    MATL26 HONEYCOMB Type 26

    MATL27 MOONEY-RIVLIN_RUBBER Type 27

    MATL28 RESULTANT_PLASTICITY Type 28

    MATL29 FORCE_LIMITED Type 29

    MATL30 CLOSED_FORM_SHELL_ PLASTICITY

    Type 30

    MATL31 FRAZER-NASH_RUBBER Type 31

    MATL32 LAMINATED_GLASS Type 32

    MATL34 FABRIC Type 34

    MATL37 TRANSVERSELY_ANISOTROPIC_ ELASTIC_PLASTIC

    Type 37

    MATL39 MAT_FLD_TRANSVERSELY_ ANISOTROPIC

    Type 39

    MATL52 BAMMAN_DAMAGE Type 52

    MATL53 CLOSED_CELL_FOAM Type 53

    MATL54 MAT_ENHANCED_COMPOSITE _DAMAGE

    Type 54

    MATL55 MAT_ENHANCED_COMPOSITE _DAMAGE

    Type 55

    MATL57 LOW_DENSITY_FOAM Type 57

    MATL59 MAT_ENHANCED_FAILURE_ SHELL_MODEL

    Type 59

    MATL59 MAT_ENHANCED_FAILURE_ SOLID_MODEL

    Type 59

    MATL62 VISCOUS_FOAM Type 62

    MATL63 CRUSHABLE_FOAM Type 63

    MATL64 RATE_SENSITIVE_ POWERLAW_PLASTICITY

    Type 64

    MATL66 LINEAR_ELASTIC_DISCRETE_ BEAM

    Type 66

    MATL68 NON_LINEAR_PLASTIC_DISCRETE_ BEAM

    Type 68

    MATL69 SID_DAMPER_DISCRETE_ BEAM

    Type 69

    MATL71 MAT_CABLE_DISCRETE_BEAM Type 71

  • Interfacing with LS-DYNA Altair Engineering 12

    MATL72 MAT_CONCRETE_DAMAGE Type 72

    MATL73 MAT_LOW_DENSITY_VISCOUS_FOAM

    Type 73

    MATL77 HYPERELASTIC_RUBBER Type 77

    MATL77B OGDEN_RUBBER Type 77B

    MATL81 PLASTICITY_WITH_DAMAGE Type 81

    MATL83 FU_CHUNG_FOAM

    Type 83

    MATL88 MTS Type 88

    MATL89 PLASTICITY_POLYMER

    MATL90 ACOUSTIC Type 90

    MATL96 BRITTLE_DAMAGE Type 96

    MATL100 SPOTWELD Type 100

    MATL103 ANISOTROPIC_VISCOPLASTIC Type 103

    MATL124 PLASTICITY_COMPRESSION_ TENSIONS

    Type 124

    MATL126 MODIFIED_HONEYCOMB Type 126

    SB_MAT SEATBELT Card 51A

    SDMat1 SPRING_ELASTIC Spring Type 1

    SDMat2 DAMPER_VISCOUS Spring Type 2

    SDMat3 SPRING_ELASTOPLASTIC Spring Type 3

    SDMat4 SPRING_NONLINEAR_ELASTIC Spring Type 4

    SDMat5 DAMPER_NONLINEAR_VISCOUS Spring Type 5

    SDMat6 SPRING_GENERAL_NONLINEAR Spring Type 6

    SDMat7 SPRING_MAXWELL Spring Type 7

    SDMat8 SPRING_INELASTIC Spring Type 8

    MATLT-1 THERMAL_ISOTROPIC

    MATLT-2 THERMAL_ORTHOTROPIC

    MATLT-10 THERMAL_ISOTROPIC_TD_LC

    NOTE 1 If flag = 1.0 and there is information in columns 31 - 40 of Card 3, the fluid option is activated for Structured.

    NOTE 2 When you import from Structured, it is assumed that it is for solids. HyperMesh also reads the shell material information.

  • Altair Engineering Interfacing with LS-DYNA 13

    Components and Properties

    The following list contains information about translating components and properties:

    No ID shifting is performed. Define components and properties so that valid LS-DYNA cards are generated. For

    example, shells and solid elements cannot be defined in the same component.

    During Structured input, beam and discrete elements are placed into components based on their property.

    Mass, rigid, and weld elements are placed into separate components during input. The recommended order for creating components, properties, and materials is shown below:

    1. Load curves

    2. Materials

    3. Properties

    Integration rules Hour Glass definitions Equations of State Section properties

    4. Components

    This is the most efficient way to create the HyperMesh collectors. By following this order and using the Create/Edit function, you have to view and edit each card only once.

    When you edit the *PART (component) card, select the necessary *SECTION cards, hourglass rules, and so on. HyperMesh does not verify that a legal selection was made. If an integration rule is selected instead of a *SECTION_SHELL card, HyperMesh assumes this a legal operation, while LS-DYNA generates an error message.

    The material associated with a component is controlled by HyperMesh functionality and cannot be changed in the card previewer.

    Collectors that do not have loaded card images are not output. Component card hourglass information in Structured does not translate to Keyword decks. When you edit component cards with a section property selected, an image of that card is

    displayed at the end of the component card image.

    HyperMesh Keyword Structured Notes

    Components *PART Card 3 INERTIA, CONTACT and REPOSITION options supported. Also, the _PRINT and _MOVE options are supported.

    on Comps *CONSTRAINED_RIGID_BODIES Card 35 Select RigidBodyMerge option on *PART.

    Create the LSDYNA_key for *CONSTRAINED_RIGID_BODIES in HyperMesh

    on Comps *DAMPING_PART_MASS

  • Interfacing with LS-DYNA Altair Engineering 14

    on Comps *DAMPING_PART_STIFFNES

    SectBeam *SECTION_BEAM Card 3 Supports all element formulations.

    SectDisc *SECTION_DISCRETE Card 50A Spring/Damper Property Card.

    SectShll *SECTION_SHELL Card 3 See NOTE.

    SectSld *SECTION_SOLID Card 3 Support for _ALE option.

    SectTShl *SECTION_TSHELL Card 3 See NOTE.

    EOS1 *EOS_LINEAR_POLYNOMIAL EOS Type 1

    EOS2 *EOS_JWL EOS Type 2

    EOS3 *EOS_SACK_TUESDAY EOS Type 3

    EOS4 *EOS_GRUNEISEN EOS Type 4

    EOS5 *EOS_RATIO_OF_POLYNOMIALS EOS Type 5

    EOS6 *EOS_LINEAR_POLYNOMIAL _WITH_ENERGY_LEAK

    EOSType 6

    EOS7 *EOS_IGNITION_AND_ GROWTH_OF_REACTION_IN_HE

    EOS Type 7

    EOS8 *EOS_TABULATED_ COMPACTION

    EOS Type 8

    EOS9 *EOS_TABULATED EOS Type 9

    EOS10 *EOS_PROPELLANT_ DEFLAGRATION

    EOS Type 10

    EOS11 *EOS_TENSOR_PORE_ COLLAPSE

    EOS Type 11

    IntBeam *INTEGRATION_BEAM Card 4

    IntShell *INTEGRATION_SHELL Card 5

    HourGlass *HOURGLASS N/A Data is entered on Component card in Structured.

    JointStff *CONSTRAINED_JOINT _STIFFNESS

    Card 38B Generalized and Flexion-Torsion options.

    NOTE To define material angles, enter the number of integration points and set ICOMP = 1.

    To create the LSDYNA_key for *CONSTRAINED_RIGID_BODIES in HyperMesh:

    1. Create an entity set of comps that are to be slave for a single master.

    2. In the collectors panel:

    Select create.

    Click create/edit and select the master comp.

  • Altair Engineering Interfacing with LS-DYNA 15

    or

    Select card image.

    Click load/edit and select the master comp.

    3. Select RigidBodyMerge in the card image panel.

    4. Click Slave_SID and select the entity set with slave comps.

    Load Collectors

    Load collector information is specified with a required $HMNAME comment card and an optional $HMCOLOR comment card. If an input translator encounters one of these comments while reading a load card, a new load collector is created. For the comments to be valid, they must follow a load keyword or the last line of the previous Structured block. The loads that follow a $HMNAME LOADCOLS comment are read into that collector. If there is a new Keyword or Structured block, HyperMesh ignores the previous load collector information.

    For non-HyperMesh generated input decks, loads are divided into collectors based on classification. The following load collectors are created:

    Mechanical loads for forces and moments Constraints/Displacements Velocities Accelerations Pressures

    If translational or rotational constraints are defined in the input model, they are placed in a separate load collector named Nodal Constraints.

    Load collectors are not used by LS-DYNA, but are useful for visualization in HyperMesh. Additional load collectors can be defined to describe other entities.

    HyperMesh Keyword Structured Notes

    InitialVel *INITIAL_VELOCITY

    *INITIAL_VELOCITY_GENERATION

    Card 30 This card changes the INITV definition on Control Card 11. Only the first card defined is valid for Structured.

    LoadBody *LOAD_BODY_X Card 39 Activate the proper option and enter the data. Only the first card defined is valid for Structured.

    *LOAD_BODY_Y Card 40 Activate the proper option and enter the data. Only the first card defined is valid for Structured.

  • Interfacing with LS-DYNA Altair Engineering 16

    *LOAD_BODY_Z Card 41 Activate the proper option and enter the data. Only the first card defined is valid for Structured.

    *LOAD_BODY_RX Card 42 Activate the proper option and enter the data. Only the first card defined is valid for Structured.

    *LOAD_BODY_RY Card 43 Activate the proper option and enter the data. Only the first card defined is valid for Structured.

    *LOAD_BODY_RZ Card 44 Activate the proper option and enter the data. Only the first card defined is valid for Structured.

    *LOAD_BODY_PARTS Card 45 Select component set.

    LoadBodyGen *LOAD_BODY_ GENERALIZED

    Card 46

    LoadRbody *LOAD_RIGID_BODY

    PrcrbRgd

    *BOUNDARY_PRESCRIBED _MOTION_RIGID

    RIGID_LOCAL and _SET options are supported.

    Dform2Rigid *DEFORMABLE_TO_RIGID

    *DEFORMABLE_TO_RIGID AUTOMATIC

    Select an arraycount for the PSID and MRB pairs.

    Change the option to automatic and card edit. In the D2R fields enter the number of PIDs that need to be converted to Rigid. Create an entity set of comps of the slave PIDs and select the set.

    Dform2RgdInertia *DEFORMABLE_TO_RIGID_ INERTIA

    BoundSPCset *BOUNDARY_SPC_SET

  • Altair Engineering Interfacing with LS-DYNA 17

    Loads, Constraints, and Boundary Conditions

    Several HyperMesh load types cause three cards to be output for x, y, and z components. During input, HyperMesh groups these into one load. Loads cannot be applied to sets, components, or boxes. Load curves are input and output. Use the Card Editor to select load curves.

    HyperMesh Panel

    Type Keyword Structured Notes

    Constraints 1 *BOUNDARY_SPC Card 13 SPC

    2 *BOUNDARY_ PRESCRIBED _MOTION_NODE

    Card 26 VAD = 2

    DOF 4, -4, 8, -8, 9, -9, 10, -10, 11, -11 are not supported

    Forces 1 *LOAD_NODE_POINT Card 23 Point Loads

    LS-DYNA Load Configs 1, 2, 3 and 4

    Moments 1 *LOAD_NODE_POINT Card 23 Point Loads

    LS-DYNA Load Configs 5, 6 7 and 8.

    Pressures 2 *LOAD_SHELL_PRESSURE Card 24 Pressure BC

    1 *LOAD_SEGMENT

    Velocities 1 *BOUNDARY_PRESCRIBED_ MOTION_NODE

    Card 26 VAD = 0

    DOF 4, -4, 8, -8, 9, -9, 10, -10, 11, -11 are not supported

    2 *INITIAL_VELOCITY Card 30 INITV = 3

    For Structured output, global velocity is set to 0.0. For Structured input, non-zero values for INITV = 1 or INITV = 5 create HyperMesh velocities. INITV values of 2, 4, 6, and 7 are ignored.

    Acceleration 1 *BOUNDARY_PRESCRIBED_ MOTION_NODE

    Card 26 VAD = 1

    DOF 4, -4, 8, -8, 9, -9, 10, -10, 11, -11 are not supported

    HyperMesh Groups

    HyperMesh groups are created from the interfaces and rigid wall panels. An LS-DYNA entity that utilizes a *SET_ [NODE,SHELL,PART, etc.] Keyword card belongs to a HyperMesh group, with the exception of Rigid Bodies/RBE2s.

    The interface panel allows you to define groups with HyperMesh configurations of 1, 2, 3, and 4. The difference among these configurations is the type of entities contained within the group.

    Config 1 Holds master and slave elements.

    Config 2 Holds master elements and slave nodes.

  • Interfacing with LS-DYNA Altair Engineering 18

    Config 3 Holds slave elements.

    Config 4 Holds slave nodes.

    The rigid wall panel allows you to define a group with the HyperMesh configuration 5. This group configuration holds the additional geometric data for LS-DYNA rigid wall definitions.

    Sliding Interfaces

    Accessed via the interfaces panel. The Keyword _TITLE option is supported. The _THERMAL(IREAD==3) option is not

    supported.

    Use the additional cards option in Keyword decks to select number of lines of data. If this is on, two additional cards are available.

    In Structured, additional cards are controlled by using the IREAD variable. Valid values are 0, 1, and 2.

    Boxes, part sets, and sets are supported. The $HMNAME fields are used for names. When using the _TITLE option, the 70-character

    field is considered a comment.

    If the line following the keyword (No TITLE option), or the first line of the Structured card contains $HM_NAME, the name supplied is read and used as the groups name. If the string $HM_ID also exists, this is used as the groups ID. NAME is 16 characters, starting in Column 9. ID field is 8 characters, starting in Column 35.

    The HyperMesh interface type defines the general type of the LS-DYNA Sliding Interface. Use the card previewer to make changes to the DYNA type.

    HyperMesh Option Keyword *CONTACT_ Structured

    SlidingOnly Defines a *CONTACT_SLIDING_ONLY_option card.

    Off Type 1

    On PENALTY Type p1

    SurfaceToSurface Defines a *CONTACT_option_SURFACE_TO_SURFACE card.

    None Type 3

    Automatic AUTOMATIC_ Type a3

    The None and Automatic options have an additional option to define a OneWayInterface. If this option is on, the following cards are created.

    None and OneWay ONE_WAY_ Type 10

    Automatic and OneWay AUTOMATIC_ONE_ WAY_

    Type a10

    Constraint CONSTRAINT_ Type 17

    Eroding ERODING_ Type 14

    TieBreak TIEBREAK_ Type 9

    The Tied option has an additional option to define

  • Altair Engineering Interfacing with LS-DYNA 19

    OFFSET.

    Tied TIED Type 2

    Tied and offset TIED_OFFSET

    Tiedshell TIED_SHELL_EDGE

    Tiedshell and offset TIED_SHELL_EDGE_OFFSET

    NodesToSurface Defines a *CONTACT_option_NODES_TO_SURFACE card.

    None Type 5

    Automatic AUTOMATIC Type a5

    Constraint CONSTRAINT_ Type 18

    Eroding ERODING_ Type 16

    TieBreak TIEBREAK_ Type 8

    The Tied option has an additional option to define OFFSET.

    Tied TIED_ Type 6

    Tied and offset TIED_OFFSET

    SingleSurface Defines a *CONTACT_option_SINGLE_SURFACE card.

    none Type 4

    Automatic AUTOMATIC_ Type 13

    Airbag AIRBAG_ Type a13

    Eroding ERODING_ Type 15

    RgdBodyToRgd Body

    Defines a *CONTACT_RIGID_BODY_option_TO RIGID_BODY card

    Off ONE_WAY_ Type 21

    On TWO_WAY_ Type 19

    RgdNodeToRgd Body

    N/A RIGID_NODES_TO_ RIGID BODY

    Type 20

    DrawBead N/A DRAW_BEAD Type 23

    Interior Defines a *CONTACT_INTERIOR card.

    AutomaticGeneral Defines a *CONTACT_AUTOMATIC_ GENERAL card.

    ForceTransducer Defines a *CONTACT_FORCE_ TRANSDUCER_option card

    On PENALTY

    Off CONSTRAINT

  • Interfacing with LS-DYNA Altair Engineering 20

    ContactSpotweld Defines a *CONTACT_SPOTWELD card

    none

    Torsion WITH_TORSION

    ContactSIngEdge Defines a *CONTACT_SINGLE_EDGE card

    To define a Type a5/*CONTACT_AUTOMATIC_NODES_TO_SURFACE interface:

    1. Select the NodeToSurface type.

    2. Click create.

    3. Edit the card.

    4. Click Automatic.

    Note that the Keyword or Type field will change.

    Other Groups

    Groups are accessed from the interfaces panel.

    HyperMesh Keyword Structured

    XtraNode *CONSTRAINED_EXTRA_NODES Card 37

    Use the card previewer to select the rigid body component to which these nodes are added.

    Only define this using the entity or set selection mechanism on the add subpanel of the interfaces panel.

    Xsectionset *DATABASE_CROSS_SECTION_SET

    Import of this card will be in Xsectionsetnew. This definition will be made obselete in the future versions

    Card 21

    For better visualization, the _PLANE option is now on the ridigwalls panel.

    The slave definition also controls the card displayed in the card editor.

    NodalForceGrp *DATABASE_NODAL_FORCE_GROUP Card 28

    IntercompSegment *INTERFACE_COMPONENT_SEGMENT

    IntercompNode *INTERFACE_COMPONENT_NODE

    InterlinkSegment *INTERFACE_LINKING_SEGMENT

    InterlinkNode *INTERFACE_LINKING_EDGE

  • Altair Engineering Interfacing with LS-DYNA 21

    *INTERFACE_LINKING_DISCRETE_NODE

    Xsectionsetnew *DATABASE_CROSS_SECTION_SET

    New definition allows the user to select multiple element sets simulatenously.

    Card 21

    Rigid Walls

    The rigid wall panel supports planes (finite/infinite), prisms (finite/infinite), cylinders, and spheres. Motion options are available for all geometric configurations. For finite rigidwalls the negative numbers for LengthL and LengthM are treated as Infinite in the Dyna solver. If defined negative, HyperMesh moves the coordinates of the base node to make LengthL and LengthM positive during export.

    The described geometry determines the completion of the keywords and/or structured options.

    HyperMesh Keyword Structured Notes

    XsectionPlane *DATABASE_CROSS_ SECTION_PLANE

    Previously on the interfaces panel.

    RWGeometric *RIGIDWALL_ GEOMETRIC

    Stonewalls Card 27 LIMIT = 4, 5, 6, and 7

    RWPlanar *RIGIDWALL_ PLANAR

    The _FORCES option is also available.

    Stonewalls Card 27 LIMIT = 1 and 2

    ORTHO, FINITE, MOVING options supported.

    ContEntity *CONTACT_ENTITY Geometric Contact Entity Card 58

    Support for GEOTYPs 1, 2, 3, 6, 7, and 10.

    Equations Equations are used to define linear constraints in local and global coordinate systems.

    HyperMesh Keyword Structured

    Equations CONSTRAINED_LINEAR Section 66

    Output Blocks

    Used to define output requests via time history blocks. The _SET option is supported for Keyword (feinput only). When you define an element output block, select only one type of element, such as shells or

    beams. The first element of the output block defines the keyword or output order for the block.

    When you define a time history block for a Structured deck, limit the number of entities to 1000. HyperMesh does not support incremental numbering and LS-DYNA only allows 2000 numbers to be placed on the cards [start/finish]. HyperMesh outputs each entity number twice. This limit is non-existent in KEYWORD.

  • Interfacing with LS-DYNA Altair Engineering 22

    HyperMesh Entity Keyword Structured

    Nodes DATABASE_HISTORY_NODE Card 17

    Solid Elems DATABASE_HISTORY_SOLID Card 18a

    Beam Elems DATABASE_HISTORY_BEAM Card 18b

    Shell Elems DATABASE_HISTORY_SHELL Card 18c

    TShell Elems DATABASE_HISTORY_TSHELL Card 18d

    sets DATABASE_HISTORY_NODE_SET

    sets DATABASE_HISTORY_SOLID_SET

    sets DATABASE_HISTORY_BEAM_SET

    sets DATABASE_HISTORY_SHELL_SET

    set DATABASE_HISTORY_TSHELL_SET

    Vectors HyperMesh Keyword Structured Notes

    Vectors *DEFINE_SD_ORIENTATION Card 50C

    *DEFINE_VECTOR N/A When DefineVector is chosen.

    Entity Sets

    HyperMesh reads the sets defined in an input deck Sets are supported on output, except _COLUMN and _GENERALoptions Element sets must be one type of element, determined by the first element in the set.

    HyperMesh Entity Keyword

    Nodes *SET_NODE_LIST

    *SET_NODE_LIST_GENERATE on the card editor

    Solid Elems *SET_SOLID

    *SET_SOLID_GENERATE on the card editor

    Beam Elems *SET_BEAM

    *SET_BEAM_GENERATE on the card editor

    Shell Elems *SET_SHELL_LIST

    *SET_SHELL_LIST_GENERATE on the card editor

    TShell Elems

    *SET_TSHELL

    *SET_TSHELL_GENERATE on the card editor

  • Altair Engineering Interfacing with LS-DYNA 23

    Discrete

    Comps

    *SET_DISCRETE

    *SET_DISCRETE_GENERATE on the card editor

    *SET_PART_LIST

    *SET_PART_LIST_GENERATE on the card editor

    Curves

    Output of curves creates a *DEFINE_CURVE or Structured Card 22 using Option 0 *DEFINE_CURVE can be changed to *DEFINE_TABLE in the card previewer. When

    DEFINE_CURVE is changed to DEFINE_TABLE, the number of curves the table should contain depends on the HyperMesh XY curves that are referenced by a load, material, component, property, and so on are output

    Upon input, the *DEFINE_CURVE and *DEFINE_TABLE/Card 22 cards are read and placed in a plot called LS-DYNA Load Curves

    Upon input, references to curves are preserved and are output along with the card, such as material, component, property, load and so on

    Curves that are not referenced by HyperMesh entities can be output using the curves.key/ curves.seq templates. These curves can then be pasted into the deck created by the dyna936 templates. The curves templates output the curves that exist in the current model. By using the output displayed option and the display panel, a precise set of load curves can be created. This method allows you to create new curves or modify existing curves for LS-DYNA entities that HyperMesh does not support.

    Sensors

    The sensors panel allows you to create and review and modify sensors. The *ELEMENT_SEATBELT_SENSOR card can be created from this panel. Sensors can be referenced in the Retractor or Pretensioner cards.

    Control Volumes

    The control volume panel allows you to control volume objects within a model. The *AIRBAG_OPTION card is output from this panel. The POP option is supported for WANG_NEFSKE options.

    The following options are supported:

    SIMPLE_PRESSURE_VOLUME

    SIMPLE_AIRBAG

    WANG_NEFSKE

    WANG_NEFSKE_JETTING

  • Interfacing with LS-DYNA Altair Engineering 24

    HYBRID

    HYBRID_JETTING

    To create the above airbag cards in the control vol panel:

    1. Select the airbag subpanel.

    2. Enter a name for the airbag.

    3. Select card image = airbag.

    There are three different ways to select entities that are defined in an airbag.

    Create a contact surf (*SET_SEGMENT) from the contact surfs panel and select that contact surf.

    Create an entity set of components (*SET_PART) in the entity sets panel and select that comp set.

    Select elements. This also exports at *SET_SEGMENT whose id is defined during export using the Dyna keyword template.

    4. Click create.

    5. Once an airbag is created with the selected entities, click edit to bring up the card image.

    6. Select the required OPTION of *AIRBAG_OPTION.

    The following reference geometry card is supported:

    *AIRBAG_REFERENCE_GEOMETRY_OPTION_OPTION

    BIRTH _RDT

    To create a reference geometry card in the control vol panel:

    1. Select the reference geometry subpanel.

    2. Enter a name for the reference geometry.

    3. Select card image = airbagRefGeom.

    4. Select the nodes that define the reference geometry.

    5. Click create.

    After you create the reference geometry, you can manipulate the original mesh (i.e., rotate, deform, scale, or translate the mesh to simulate airbag folding or other conditions). When you review the reference geometry, it displays the original nodal locations at the time that reference geometry was created. In this way, the reference geometry definition can be used to preserve IMM locations of the nodes. Once the reference geometry is created, click on edit to bring up the card image. Select the required OPTION of _BIRTH or/and _RDT

  • Altair Engineering Interfacing with LS-DYNA 25

    Supported DYNA Keywords

    *AIRBAG_SIMPLE_PRESSURE_VOLUME_{Optional ID}

    *AIRBAG_SIMPLE_AIRBAG_MODEL_

    *AIRBAG_WANG_NEFSKE_

    *AIRBAG_WANG_NEFSKE_POP_

    *AIRBAG_WANG_NEFSKE_JETTING_

    *AIRBAG_WANG_NEFSKE_MULTIPLE_JETTING_

    *AIRBAG_HYDBRID_

    *AIRBAG_HYDBRID_JETTING_

    *AIRBAG_REFERENCE_GEOMETRY_BIRTH_

    *AIRBAG_REFERENCE_GEOMETRY_BIRTH_RDT_

    *BOUNDARY_PRESCRIBED_MOTION_NODE

    *BOUNDARY_PRESCRIBED_MOTION_RIGID

    *BOUNDARY_PRESCRIBED_MOTION_RIGID_LOCAL

    *BOUNDARY_PRESCRIBED_MOTION_SET

    *BOUNDARY_SPC_NODE

    *BOUNDARY_SPC_SET

    *CONSTRAINED_EXTRA_NODES_NODE

    *CONSTRAINED_EXTRA_NODES_SET

    *CONSTRAINED_GENERALIZED_WELD_BUTT

    *CONSTRAINED_GENERALIZED_WELD_FILLET

    *CONSTRAINED_GENERALIZED_WELD_SPOT

    *CONSTRAINED_JOINT_CYLINDRICAL_{option = LOCAL}

  • Interfacing with LS-DYNA Altair Engineering 26

    *CONSTRAINED_JOINT_PLANAR_

    *CONSTRAINED_JOINT_REVOLUTE_

    *CONSTRAINED_JOINT_SPHERICAL_

    *CONSTRAINED_JOINT_TRANSLATIONAL_

    *CONSTRAINED_JOINT_LOCKING_

    *CONSTRAINED_JOINT_UNIVERSAL_

    *CONSTRAINED_JOINT_STIFFNESS_FLEXION-TORSION

    *CONSTRAINED_JOINT_STIFFNESS_GENERALIZED

    *CONSTRAINED_LINEAR

    *CONSTRAINED_NODAL_RIGID_BODY_{option = INERTIA}

    *CONSTRAINED_NODE_SET

    *CONSTRAINED_RIGID_BODIES

    *CONSTRAINED_RIVET

    *CONSTRAINED_SPOTWELD

    *CONTACT_OPTION1_OPTION2_OPTION3

    Currently we support OPTION1 and OPTION3= TITLE

    *CONTACT_AIRBAG_SINGLE_SURFACE

    *CONTACT_AUTOMATIC_NODES_TO_SURFACE

    *CONTACT_AUTOMATIC_ONE_WAY_SURFACE_TO_SURFACE

  • Altair Engineering Interfacing with LS-DYNA 27

    *CONTACT_AUTOMATIC_SINGLE_SURFACE

    *CONTACT_AUTOMATIC_SURFACE_TO_SURFACE

    *CONTACT_CONSTRAINT_NODES_TO_SURFACE

    *CONTACT_CONSTRAINT_SURFACE_TO_SURFACE

    *CONTACT_DRAWBEAD

    *CONTACT_ERODING_NODES_TO_SURFACE

    *CONTACT_ERODING_SINGLE_SURFACE

    *CONTACT_ERODING_SURFACE_TO_SURFACE

    *CONTACT_NODES_TO_SURFACE

    *CONTACT_ONE_WAY_SURFACE_TO_SURFACE

    *CONTACT_RIGID_NODES_TO_RIGID_BODY

    *CONTACT_RIGID_BODY_ONE_WAY_TO_RIGID_BODY

    *CONTACT_RIGID_BODY_TWO_WAY_TO_RIGID_BODY

    *CONTACT_SINGLE_SURFACE

    *CONTACT_SLIDING_ONLY

    *CONTACT_SLIDING_ONLY_PENALTY

    *CONTACT_SURFACE_TO_SURFACE

    *CONTACT_TIEBREAK_NODES_TO_SURFACE

    *CONTACT_TIEBREAK_SURFACE_TO_SURFACE

    *CONTACT_AUTOMATIC_GENERAL

    *CONTACT_FORCE_TRANSDUCER_PENALTY

    *CONTACT_FORCE_TRANSDUCER_CONSTRAINT

    *CONTACT_{option4=OFFSET} for TIED contacts

    *CONTACT_TIED_SHELL_EDGE_TO_SURFACE

    *CONTACT_SPOTWELD

    *CONTACT_SPOTWELD_WITH_TORSION

    *CONTACT_SINGLE_EDGE

  • Interfacing with LS-DYNA Altair Engineering 28

    *CONTACT_ENTITY

    *CONTACT_INTERIOR

    *CONTROL_ACCURACY

    *CONTROL_ADAPTIVE

    *CONTROL_ALE

    *CONTROL_BULK_VISCOSITY

    *CONTROL_CONTACT

    *CONTROL_COUPLING

    *CONTROL_CPU

    *CONTROL_DAMPING (Old dyna card for input only)

    *CONTROL_DYNAMIC_RELAXATION

    *CONTROL_ENERGY

    *CONTROL_HOURGLASS

    *CONTROL_IMPLICIT_AUTO

    *CONTROL_IMPLICIT_DYNAMICS

    *CONTROL_IMPLICIT_EIGENVALUE

    *CONTROL_IMPLICIT_GENERAL

    *CONTROL_IMPLICIT_SOLVER

    *CONTROL_IMPLICIT_SOLUTION

    *CONTROL_IMPLICIT_STABILIZATION

    *CONTROL_OUTPUT

    *CONTROL_PARALLEL

    *CONTROL_SHELL

    *CONTROL_SOLUTION

  • Altair Engineering Interfacing with LS-DYNA 29

    *CONTROL_STRUCTURED

    *CONTROL_STRUCTURED_TERM

    *CONTROL_SUBCYCLE

    *CONTROL_TERMINATION

    *CONTROL_TIMESTEP

    *CONTROL_RIGID

    *DAMPING_GLOBAL

    *DAMPING_PART_MASS

    *DAMPING_PART_STIFFNESS

    *DATABASE_OPTION

    *DATABASE_BINARY_D3DRLF

    *DATABASE_BINARY_D3DUMP

    *DATABASE_BINARY_D3PLOT

    *DATABASE_BINARY_D3THDT

    *DATABASE_BINARY_INTFOR

    *DATABASE_BINARY_RUNRSF

    *DATABASE_BINARY_XTFILE

    *DATABASE_CROSS_SECTION_PLANE

    *DATABASE_CROSS_SECTION_SET

    *DATABASE_EXTENT_AVS

    *DATABASE_EXTENT_BINARY

    *DATABASE_EXTENT_MOVIE

    *DATABASE_EXTENT_MPGS

  • Interfacing with LS-DYNA Altair Engineering 30

    *DATABASE_HISTORY_BEAM

    *DATABASE_HISTORY_BEAM_SET

    *DATABASE_HISTORY_NODE

    *DATABASE_HISTORY_NODE_SET

    *DATABASE_HISTORY_SHELL

    *DATABASE_HISTORY_SHELL_SET

    *DATABASE_HISTORY_SOLID

    *DATABASE_HISTORY_SOLID_SET

    *DATABASE_HISTORY_TSHELL

    *DATABASE_HISTORY_TSHELL_SET

    *DATABASE_NODAL_FORCE_GROUP

    *DATABASE_SPRING_FORWARD

    *DATABASE_SUPERPLASTIC_FORMING

    *DATABASE_TRACER

    *DEFINE_BOX

    *DEFINE_COORDINATE_SYSTEM

    *DEFINE_COORDINATE_NODES

    *DEFINE_COORDINATE_NODES (Only for input)

    *DEFINE_CURVE

    *DEFINE_TABLE*DEFINE_SD_ORIENTATION

    *DEFINE_VECTOR

    *DEFORMABLE_TO_RIGID

    *DEFORMABLE_TO_RIGID_AUTOMATIC

    *DEFORMABLE_TO_RIGID_INERTIA

  • Altair Engineering Interfacing with LS-DYNA 31

    *ELEMENT_BEAM

    *ELEMENT_BEAM_THICKNESS

    *ELEMENT_BEAM_PID

    *ELEMENT_DISCRETE

    *ELEMENT_INERTIA

    *ELEMENT_MASS

    *ELEMENT_SEATBELT_ACCELEROMETER

    *ELEMENT_SEATBELT

    *ELEMENT_SEATBELT_SENSOR

    *ELEMENT_SEATBELT_RETRACTOR

    *ELEMENT_SEATBELT_PRETENSIONER

    *ELEMENT_SEATBELT_SLIPRING

    *ELEMENT_SHELL

    *ELEMENT_SHELL_BETA

    *ELEMENT_SHELL_THICKNESS

    *ELEMENT_SOLID

    *ELEMENT_SOLID_ORTHO

    *ELEMENT_TSHELL

    *EOS_GRUNEISEN

    *EOS_IGNITION_AND_GROWTH_OF_REACTION_IN_HE

    *EOS_JWL

    *EOS_LINEAR_POLYNOMIAL

    *EOS_LINEAR_POLYNOMIAL_WITH_ENERGY_LEAK

    *EOS_PROPELLANT_DEFLAGRATION

    *EOS_RATIO_OF_POLYNOMIALS

    *EOS_SACK_TUESDAY

  • Interfacing with LS-DYNA Altair Engineering 32

    *EOS_TABULATED

    *EOS_TABULATED_COMPACTION

    *EOS_TENSOR_PORE_COLLAPSE

    *END

    *HOURGLASS

    *INCLUDE

    *INITIAL_VELOCITY

    *INITIAL_VELOCITY_NODE

    *INITIAL_VELOCITY_GENERATION

    *INTEGRATION_BEAM

    *INTEGRATION_SHELL

    *INTERFACE_COMPONENT_NODE

    *INTERFACE_COMPONENT_SEGMENT

    *INTERFACE_LINKING_SEGMENT

    *INTERFACE_LINKING_EDGE

    *INTERFACE_LINKING_DISCRETE_NODE_SET

    *KEYWORD*LOAD_BODY_GENERALIZED

    *LOAD_BODY_PARTS

    *LOAD_BODY_RX

    *LOAD_BODY_RY

    *LOAD_BODY_RZ

  • Altair Engineering Interfacing with LS-DYNA 33

    *LOAD_BODY_X

    *LOAD_BODY_Y

    *LOAD_BODY_Z

    *LOAD_RIGID_BODY

    *LOAD_NODE_POINT

    *LOAD_SEGMENT

    *LOAD_SHELL_ELEMENT*MAT_UNSUPPORTED

    *MAT_ELASTIC

    *MAT_ELASTIC_FLUID

    *MAT_ORTHOTROPIC_ELASTIC

    *MAT_ANISOTROPIC_ELASTIC

    *MAT_PLASTIC_KINEMATIC

    *MAT_SOIL_AND_FOAM

    *MAT_VISCOELASTIC

    *MAT_BLATZ-KO_RUBBER

    *MAT_NULL

    *MAT_ISOTROPIC_ELASTIC_PLASTIC

    *MAT_SOIL_AND_FOAM_FAILURE

    *MAT_JOHNSON_COOK

    *MAT_POWER_LAW_PLASTICITY

    *MAT_STRAIN_RATE_DEPENDENT_PLASTICITY

    *MAT_RIGID

    *MAT_COMPOSITE_DAMAGE

    *MAT_PIECEWISE_LINEAR_PLASTICITY

    *MAT_HONEYCOMB

  • Interfacing with LS-DYNA Altair Engineering 34

    *MAT_MOONEY-RIVLIN_RUBBER

    *MAT_RESULTANT_PLASTICITY

    *MAT_FORCE_LIMITED

    *MAT_CLOSED_FORM_SHELL_PLASTICITY

    *MAT_FRAZER_NASH_RUBBER_MODEL

    *MAT_LAMINATED_GLASS

    *MAT_FABRIC

    *MAT_TRANSVERSELY_ANISOTROPIC_ELASTIC_PLASTIC

    *MAT_FLD_TRANSVERSELY_ANISOTROPIC

    *MAT_BAMMAN_DAMAGE

    *MAT_CLOSED_CELL_FOAM

    *MAT_ENHANCED_COMPOSITE_DAMAGE

    *MAT_LOW_DENSITY_FOAM

    *MAT_COMPOSITE_FAILURE

    *MAT_COMPOSITE_FAILURE_SHELL

    *MAT_COMPOSITE_FAILURE_SOLID

    *MAT_COMPOSITE_FAILURE_MODEL

    *MAT_VISCOUS_FOAM

    *MAT_CRUSHABLE_FOAM

    *MAT_RATE_SENSITIVE_POWERLAW_PLASTICITY

    *MAT_LINEAR_ELASTIC_DISCRETE_BEAM

    *MAT_SID_DAMPER_DISCRETE_BEAM

    *MAT_CABLE_DISCRETE_BEAM

    *MAT_HYPERELASTIC_RUBBER

    *MAT_OGDEN_RUBBER

    *MAT_PLASTICITY_WITH_DAMAGE

    *MAT_MODIFIED_HONEYCOMB

  • Altair Engineering Interfacing with LS-DYNA 35

    *MAT_SPRING_ELASTIC

    *MAT_DAMPER_VISCOUS

    *MAT_SPRING_ELASTOPLASTIC

    *MAT_SPRING_NONLINEAR_ELASTIC

    *MAT_DAMPER_NONLINEAR_VISCOUS

    *MAT_SPRING_GENERAL_NONLINEAR

    *MAT_SPRING_MAXWELL

    *MAT_SPRING_INELASTIC

    *MAT_SEATBELT

    *MAT_NONLINEAR_PLASTIC_DISCRETE_BEAM

    *MAT_CONCRETE_DAMAGE

    *MAT_LOW_DENSITY_VISCOUS_FOAM

    *MAT_FU_CHANG_FOAM

    *MAT_MTS

    *MAT_ACOUSTIC

    *MAT_BRITTLE_DAMAGE

    *MAT_SPOTWELD

    *MAT_ANISOTROPIC_VISCOPLASTIC

    *MAT_PLASTICITY_COMPRESSION_TENSION

    *MAT_ELASTIC_PLASTIC_HYDRO

    *MAT_THERMAL_ISOTROPIC

    *MAT_THERMAL_ORTHOTROPIC

    *MAT_THERMAL_ISOTROPIC_TD_LC

    *NODE

    *PART

  • Interfacing with LS-DYNA Altair Engineering 36

    *PART_INERTIA

    *PART_REPOSITION

    *PART_INERTIA_CONTACT

    *PART_REPOSITION_CONTACT

    *PART_{option = PRINT}

    *PART_MOVE

    *RIGIDWALL_GEOMETRIC_CYLINDER_{OPTION2 = MOTION}

    *RIGIDWALL_GEOMETRIC_FLAT_

    *RIGIDWALL_GEOMETRIC_PRISM_

    *RIGIDWALL_GEOMETRIC_SPHERE_

    *RIGIDWALL_PLANAR

    *RIGIDWALL_PLANAR_ORTHO

    *RIGIDWALL_PLANAR_ORTHO_FINITE

    *RIGIDWALL_PLANAR_FINITE_MOVING

    *RIGIDWALL_PLANAR_FINITE_MOVING_FORCES

    *SECTION_BEAM

    *SECTION_DISCRETE

    *SECTION_SEATBELT

    *SECTION_SHELL

    *SECTION_SOLID

    *SECTION_SOLID_ALE

    *SECTION_TSHELL

    *SET_NODE_LIST

  • Altair Engineering Interfacing with LS-DYNA 37

    *SET_NODE_LIST_GENERATE

    *SET_PART_LIST

    *SET_PART_LIST_GENERATE

    *SET_SHELL_LIST

    *SET_SHELL_LIST_GENERATE

    *SET_SOLID

    *SET_SOLID_GENERATE

    *SET_DISCRETE

    *SET_DISCRETE_GENERATE

    *SET_BEAM

    *SET_BEAM_GENERATE

    *SET_TSHELL

    *SET_TSHELL_GENERATE

    *SET_SEGMENT*TITLE

    Results Translation

    hmdyna translates files from the force database and state database to HyperMesh binary results files. To translate force database files, use the command line option -force. To translate state database files, use the command line option -state. -state is the default and is used for translating d3plot files. If neither -force nor -state is specified in the command line, state database files are translated by default. The syntax to run the translator is:

    hmdyna [arguments]

    The following options can be used in conjunction with -state.

    Flag Meaning

    -t Temperatures

    -d Displacements

    -v Velocities

    -a Accelerations

    -xx Sigma xx

  • Interfacing with LS-DYNA Altair Engineering 38

    -yy Sigma yy

    -zz Sigma zz

    -xy Sigma xy

    -yz Sigma yz

    -zx Sigma zx

    -von von Mises stress

    -ps Plastic Strains

    -ebv Extra brick variables

    -esv Extra shell variables

    -epxx Epsilon xx

    -epyy Epsilon yy

    -epzz Epsilon zz

    -epxy Epsilon xy

    -epyz Epsilon yz

    -epzx Epsilon zx

    -af Axial force

    -srs Shear Resultant-s

    -srt Shear Resultant-t

    -bms Bending Moment-s

    -bmt Bending Moment-t

    -tr Torsional Resultant

    -bmxx Bending Moment-mxx

    -bmyy Bending Moment-myy

    -bmxy Bending Moment-mxy

    -qxx Shear Resultant-qxx

    -qyy Shear Resultant-qyy

    -nxx Normal Resultant-nxx

    -nyy Normal Resultant-nyy

    -nxy Normal Resultant-nxy

  • Altair Engineering Interfacing with LS-DYNA 39

    -th Thickness

    -eld1 Element Dependent Variable 1

    -eld2 Element Dependent Variable 2

    -ie Internal Energy

    -inner Lower Surface

    -outer Upper Surface

    -mid Mid Surface

    -max Maximum of top and bottom surface values

    --max Option to turn off Maximum

    -902 Version 902

    -float Float format

    -3s1 3-D Principal Strain 1 (Minimum 3-D Principal Strain)

    -3s2 3-D Principal Strain 2 (Maximum 3-D Principal Strain)

    -3s3 3-D Principal Strain 1 (Second 3-D Principal Strain)

    -3sh 3-D Maximum Shear Strain

    -3S1 3-D Principal Stress 1 (Minimum 3D Principal Stress)

    -3S2 3-D Principal Stress 2 (Maximum 3D Principal Stress)

    -3S3 3-D Principal Stress 3 (Second Principal Stress 3D)

    -3Sh 3-D Maximum Shear Stress

    -stepN Step increment. If N is 1, translation is performed for steps 1, 2, 3, and so on. If N is 2, translation is performed for steps 2, 4, 6, and so on.

    -h3d Outputs file to an H3D file instead of to an hmresults file. The file includes model and results information that was translated. The model must contain geometry for it to be output to an H3D file.

  • Interfacing with LS-DYNA Altair Engineering 40

    The following options can be used in conjunction with -force. -force must be specified as an argument and is used for the iff file from LS-DYNA. The iff file needs to be requested from LS-DYNA using the command line syntax S=iff.

    Flag Meaning

    -d Displacements

    -v Velocities

    -nip Normal Interface Pressure

    -miss Maximum Interface Shear Stress

    -ssr Shear stress in local r-direction of segment

    -sss Shear stress in local s-direction of segment

    -xfe X-Force on element (4-noded elements only)

    -yfe Y-Force on element (4-noded elements only)

    -zfe Z-Force on element (4-noded elements only)

    The following options are common to both the -state and -force options:

    Flag Meaning

    -stepN Step increment. If N is 1, translation is performed for steps 1, 2, 3, etc. If N is 2, translation is performed for steps 2, 4, 6, and so on.

    -disk Translation is performed on disk (default off)

    -size Number of entities (10000 default)

    -file Scratch file name (default off)

    The following parameters are also available when the results translation is not performed on the analysis machine. One of these parameters may need to be specified to indicate where the analysis result file was created:

    Parameter Analysis File Created On

    -cray Cray

    -dec Dec 5000

    -decalpha Dec Alpha

    -hp Hewlett Packard

    -ibm IBM RS\6000

    -pc PC

  • Altair Engineering Interfacing with LS-DYNA 41

    -sgi SGI

    -sun Sun

    When the number of integration points is more than 3, in the case of shell elements, LS-DYNA outputs as many sets of stresses as the number of integration points. The first three sets of these stresses are the midsurface, inner surface and outer surface stresses. The remaining stresses in the d3plot files are output in the following form in HyperMesh:

    , from setN, where can be one of Sigmaxx, Sigmayy, Sigmazz, Sigmaxy, Sigmayz, and Sigmazx. N varies from 4 to MAXINT (number of integration points), with an increment of 1.

    The same rule applies to the plastic strains and additional history variables for shell elements.

    The supported results for the state database include:

    nodal

    Temperatures

    Displacements

    Velocities

    Accelerations

    bricks

    Sigma - xx (mid)

    Sigma - yy (mid)

    Sigma - zz (mid)

    Sigma - xy (mid)

    Sigma - yz (mid)

    Sigma - zx (mid)

    von Mises Stress (mid)

    Effective plastic strain (mid)

    History variables (mid)

    Epsilon - xx (mid)

    Epsilon - yy (mid)

    Epsilon - zx (mid)

  • Interfacing with LS-DYNA Altair Engineering 42

    Epsilon - xy (mid)

    Epsilon - yz (mid)

    Epsilon - zx (mid)

    Principal Strain 3D1 (mid)

    Principal Strain 3D2 (mid)

    Principal Strain 3D3 (mid)

    Maximum Shear Strain 3D (mid)

    Principal Stress 3D1 (mid)

    Principal Stress 3D2 (mid)

    Principal Stress 3D3 (mid)

    Maximum Shear Stress 3D (mid)

    brick shells

    Sigma - xx (inner, outer, mid and max)

    Sigma - yy (inner, outer, mid and max)

    Sigma - zz (inner, outer, mid and max)

    Sigma - xy (inner, outer, mid and max)

    Sigma - yz (inner, outer, mid and max)

    Sigma - zx (inner, outer, mid and max)

    von Mises stress (inner, outer, mid and max)

    Effective Plastic Strain (inner, outer, mid and max)

    Additional history variables (inner, outer and mid)

    Epsilon - xx (inner and outer)

    Epsilon - yy (inner and outer)

    Epsilon - zz (inner and outer)

    Epsilon - xy (inner and outer)

    Epsilon - yz (inner and outer)

    Epsilon - zx (inner and outer)

    Principal Strain 3D1 (inner and outer)

  • Altair Engineering Interfacing with LS-DYNA 43

    Principal Strain 3D2 (inner and outer)

    Principal Strain 3D3 (inner and outer)

    Maximum Shear Strain 3D (inner and outer)

    Principal Stress 3D1 (inner, outer and mid)

    Principal Stress 3D2 (inner, outer and mid)

    Principal Stress 3D3 (inner, outer and mid)

    Maximum Shear Stress 3D (inner, outer and mid)

    beams

    Axial Force

    Shear resultant - s

    Shear resultant - t

    Bending moment - s

    Bending moment - t

    Torsional resultant

    4-noded shells

    Sigma - xx (inner, outer, mid, max and at integration points 4, 5 etc up to MAXINT)

    Sigma - yy (inner, outer, mid, max and at integration points 4, 5 etc. up to MAXINT)

    Sigma - zz (inner, outer, mid, max and at integration points 4, 5 etc. up to MAXINT)

    Sigma - xy (inner, outer, mid, max and at integration points 4, 5 etc. up to MAXINT)

    Sigma - yz (inner, outer, mid, max and at integration points 4, 5 etc. up to MAXINT)

    Sigma - zx (inner, outer, mid, max and at integration points 4, 5 etc. up to MAXINT)

    von Mises Stress (inner, outer, mid and max)

    Effective Plastic Strain (inner, outer, mid, max and at integration points 4, 5 etc up to MAXINT)

    Additional history variables (inner, outer, mid and at integration points 4, 5 etc. up to MAXINT)

    Bending moment - mxx

    Bending moment - myy

    Bending moment - mxy

  • Interfacing with LS-DYNA Altair Engineering 44

    Shear resultant - qxx

    Shear resultant - qyy

    Normal resultant - nxx

    Normal resultant - nyy

    Normal resultant - nxy

    Thickness

    Element Dependent Variable1

    Element Dependent Variable2

    Internal Energy

    Epsilon - xx (inner and outer)

    Epsilon - yy (inner and outer)

    Epsilon - zz (inner and outer)

    Epsilon - xy (inner and outer)

    Epsilon - yz (inner and outer)

    Epsilon - zx (inner and outer)

    Principal Strain 3D1 (inner and outer)

    Principal Strain 3D2 (inner and outer)

    Principal Strain 3D3 (inner and outer)

    Maximum Shear Strain 3D (inner and outer)

    Principal Stress 3D1 (inner, outer and mid)

    Principal Stress 3D2 (inner, outer and mid)

    Principal Stress 3D3 (inner, outer and mid)

    Maximum Shear Stress 3D (inner, outer and mid)

    The supported results for the force database include the following:

    nodal

    Displacements

    Velocities

  • Altair Engineering Interfacing with LS-DYNA 45

    4-noded elements

    Normal interface pressure

    Maximum interface shear stress

    Shear stress in local r-direction of segment

    Shear stress in local s-direction of segment

    X-force on element

    Y-force on element

    Z-force on element

    3-noded elements

    Normal interface pressure

    Maximum interface shear stress

    Shear stress in local r-direction of segment

    Shear stress in local s-direction of segment

    The following table lists the LS-DYNA elements and their HyperMesh equivalents for the state database:

    LS-DYNA HyperMesh

    Bricks Hex8

    Brick Shells Hex8

    Beams Plot

    4-noded shells Quad4

    The following table lists the LS-DYNA elements and their HyperMesh equivalents for the force database:

    LS-DYNA HyperMesh

    4-noded elements Quad4

    3-noded elements Tria3

    LS-DYNA ASCII results files can be used to create data curves in HyperMesh using the edit curves subpanel on the xy plot panel. See the edit curves documentation in the HyperMesh Users On-line Help for instructions on how to input the curves. To set the output for these files, use the DBOpts Control Card.

    Import Template LS-DYNA Result File

    defgeo.tpl DEFGEO Deformed Geometry

  • Interfacing with LS-DYNA Altair Engineering 46

    rbdout.tpl RBDOUT Rigid Body Data

    gceout.tpl GCEOUT Geometric Contact Entities

    nodfor.tpl NODFOR Nodal force groups

    deforc.tpl DEFORC Discrete elements

    ncforc.tpl NCFORC Nodal interface forces

    swforc.tpl SWFORC Nodal Constraint reaction forces

    sbtout.tpl SBTOUT Seat Belt output file

    jntforc.tpl JNTFORC Joint Force file

    abstat.tpl ABSTAT Airbag Statistics

    secforc.tpl SECFORC Cross Section Forces

    spcforc.tpl SPCFORC SPC reaction forces

    nodout.tpl NODOUT Nodal Point data w/o rotations

    nodout2.tpl NODOUT2 Nodal Point Data with rotations

    sleout.tpl SLEOUT Sliding Interface energy

    rwforc.tpl RWFORC Wall forces

    rcforc.tpl RCFORC Resultant interface forces for only master elements

    rcforc2.tpl RCFORC Resultant interface forces for master and slave elements

    matsum.tpl MATSUM Material energies without hourglass

    matsum2.tpl MATSUM Material energies with hourglass

    glstat.tpl GLSTAT Global Data without hourglass

    glstat2.tpl GLSTAT Global Data with hourglass

    elout.tpl ELOUT Element data

    Viewing the Results

    If the model file option is selected, an ASCII model file is created. You can use this ASCII model file to view the model in HyperMesh.

    To import the model file and view the results:

    1. Select the files panel.

  • Altair Engineering Interfacing with LS-DYNA 47

    2. Select the results subpanel.

    3. Click file = and enter the name of the results file, or click on file = again to browse the directory structure for the correct file.

    4. Select the import subpanel.

    5. Click EXTERNAL if it is not already selected.

    6. Click translator = and enter hmascii [.exe], or click translator = again to browse the directory structure for the translator.

    7. Click filename = and enter the name of the model file, or click filename = again to browse the directory structure for the file.

    8. Click import.

    9. Go to the Post page, which contains the contour and the transient panels.

    The results can be viewed as a contour or assign plot, or as a transient animation.

    Creating Cards Control Cards

    *DATABASE_OPTION cards in Keyword are listed on the DBOpt control card in HyperMesh. An active field is output as the appropriate individual card in the data deck.

    A control card can be in one of three states:

    State Color Explanation

    Undefined Gray The control card was either never created or was deleted.

    Defined (See NOTE) Green Any control card viewed in the card previewer is activated.

    Inactive Red A card that has been defined may be disabled. The attributes for that card remain; however, the control card is not output.

    NOTE Those control cards that are defined (green in the control card editor) are output.

    Default values for attributes are common throughout the card previewer. A default value field has one of the following states:

    State Description

    Default = ON In this state, the field label color is yellow and no data entry is allowed.

    Default = OVERRIDDEN To override a default value field, pick the yellow field label. When you override a default value field, the label text color changes to cyan and allows you to enter data in the field.

  • Interfacing with LS-DYNA Altair Engineering 48

    Systems

    The systems cards can be previewed, but not edited.

    Nodes

    These cards can be previewed, but not edited.

    Elements

    1. To edit these cards, select card from the permanent menu.

    2. Select the elements to edit.

    3. If more than one config or type of element is selected, enter the Config and Type to in the fields provided. Only one config and type of element can be edited simultaneously.

    *CONSTRAINED_SPOTWELD/Card 13

    Normal and shear failure values can be edited.

    *CONSTRAINED_GENERALIZED_WELD/Card 36

    Spot(default)/type 1, Fillet/type 2, and Butt/type 3 failure modes are supported. Failure information is based on weld type selected. Coordinate System ID can be selected.

    No Failure/Type 0 Card 36 entities are defined as *CONSTRAINED_NODAL_RIGID_BODIES in Keyword. They are a separate element type in HyperMesh.

    *ELEMENT_DISCRETE/ Card 50 Scale factor, printing flags, and offset values can be edited. *ELEMENT_BEAM / Card 8

    Thickness option can be added. This allows you to edit the parameters based on the element formulation in the property to which the beam points.

    *ELEMENT_SHELL / Card 9

    Thickness and beta options can be added singularly or together. This allows you to edit the thickness and material angles to override the SECTION card.

    Components, Properties, and Materials

    These are edited using the card image subpanel on the collectors panel. See Supported Cards.

    Loads

    1. To edit these cards, select card on the permanent menu.

    2. Select the loads to edit.

    3. If more than one config or type of load is selected, enter the Config and Type to edit in the fields provided. Only one config and type of load can be edited simultaneously.

    Editable Fields

    If a load is not mentioned below, it does not have any editable fields. However, that load can still be displayed in the card previewer. See the Loads section above for a complete list of the LS-DYNA entities that HyperMesh treats as loads.

    *LOAD_NODE_POINT / Card 23 A load curve can be selected for these loads.

  • Altair Engineering Interfacing with LS-DYNA 49

    *BOUNDARY_SPC_NODE / Card 13 A local coordinate system can be selected. *BOUNDARY_PRESCRIBED_MOTION_NODE / Card 26 A loading condition release time can be specified. A load curve can also be specified.

    Curves Edit by selecting card on the permanent menu. Editable values include stress initialization, offset values, and data type.

    Groups Edit using the card image subpanel on the Interfaces or Rigid Walls panels.

    Output Blocks Use the card previewer to view block entity IDs. Data on LS-DYNA output blocks cannot be edited.

    Sets Use the card previewer to view the set entity IDs. The default LS-DYNA attribute values for the set can be edited. Individual values cannot be edited.

    To set the Scale Factor on a spring element:

    1. Select card on the permanent menu.

    2. Select the elements to be edited.

    3. Click spring in the config = box.

    4. Click edit.

    5. Change the values on the cards and press return.

    LS-DYNA KEY Macro Menu

    The LS-DYNA KEY macro menu, dyna_key.mac, contains shortcuts and tools that can help simplify LS-DYNA tasks.

    To load the LS-DYNA KEY macro menu:

    1. Load a valid LS-DYNA keyword template.

    2. Click options on the permanent menu.

    3. Select the menu config subpanel.

    4. Click macro menu= and select ~altairhome/hm/version/scripts/dynakey/dyna_key.mac.

    5. Click retrieve.

    The LS-DYNA KEY macro menu contains the following submenus:

    Disp menu

    Tools menu

  • Interfacing with LS-DYNA Altair Engineering 50

    A-D menu

    D-R menu

    To create an LS-DYNA weld:

    6. Select options from the permanent menu.

    7. Select the menu config panel.

    8. Retrieve the macro file, scripts\dynakey\dyna_key.mac.

    9. Click return.

    10. From the files panel, load a HyperMesh model.

    11. Click Tools on the macro menu.

    12. Click Spot welds in the macro menu.

    13. Click Spot welds.

    The Ls-Dyna weld Creation dialog is displayed.

    Attach to shell elems is off by default.

    14. Using the browser, select the Master Weld File (MWF).

    This file provides information regarding the weld locations and the parts that are to be connected.

    15. Select the specific part option (By ID or By Name) depending on the part information in master weld file. If the master weld file has part IDs, select By ID.

    Currently supported master weld files can have either part IDs or part names but not a combination of both.

    16. Select one of the following options from the weld element type list.

    Bar2 Rod

  • Altair Engineering Interfacing with LS-DYNA 51

    Gap Spring

    Plot Weld

    Rigid

    Note: For Bar2:

    The script creates components named NTweldComponents where N = 2, 3, 4 for 2T/3T/4T welding. Therefore, all 2T welds would be put into the 2TweldComponents collector. The script also creates a property card named mat100_prop of type Section_Beam and sets the attribute ELFORM of the *Element_Beam option to TYPE 9.

    The SID attribute of the NTweldComponents components in the PART card is then updated with the Property card ID.

    17. Check Attach to shell elems, if required.

    18. Click Create welds.

    Notes: Create welds reads in the MWF with all the weld location information and parts to be connected, and creates points at those locations. The specified weld is then created between the parts specified in the weld location file.

    If Attach to shell elems is checked, 1-D connection elements are created that attach the welds to neighboring shell elements by internally remeshing the surrounding shell elements.

    The tolerance factor is not the actual search tolerance but a factor that determines the search tolerance. The search tolerance is calculated as shown below:

    Search Tolerance = Tolerance Factor * max_component_thickness

    The max_component_thickness is determined by obtaining the thickness of parts/components specified in the weld location file for a given location. HyperMesh searches for the thickness of a component from the *Section_Shll card defined for each component. If the card is not defined or if the thickness of components being connected at a location is zero, the search tolerance will be the tolerance factor.

    Any additions required to create specific weld element types other than beams can be done using the script. The script can be modified to create and define contacts or other requirements for Ls-Dyna solver requirements.

    Disp Menu

    The Disp menu is identical to the Disp menu found in the HyperMesh default macro menu. It contains tools that allow you to control display options.

    Light Source allows you to change the direction of the source of the light. Nine locations for the light source are available:

    Light source is located at the upper left corner, upper middle, and upper right corner of the screen, respectively.

  • Interfacing with LS-DYNA Altair Engineering 52

    Light source is located on the left side of the screen, normal to the screen, and right of the screen, respectively.

    Light source is located at the lower left corner, lower middle, and lower right corner of the screen, respectively.

    Specularity Allows you to modify the specularity or reflectiveness of the model. Four different levels of specularity are available: none, high, medium and low.

    Display Geom Turn on/off the geometry in the model.

    Elems Turn on/off the elements in the model.

    Shrink Shrink the elements in the model by 20%.

    Gfx Display the model either in performance or standard graphics mode.

    vis opts Select the topology visualization mode for displaying the model. Four modes are available:

    0 Standard mode.

    1 Component color. The model is always displayed with the edges the same color as the associated component, even in the automesh panel.

    2 Topology mode. The surface edges are displayed according to connectivity, as in the geom cleanup panel.

    3 Shaded mode. Allows you to view the model in shaded mode regardless of which panel you are currently using.

    surf line Place surface lines on a model. You can place one, two, three, or no lines on each surface.

    mask ln Masks all of the displayed lines in the model.

    mask nod Removes all of the displayed temporary nodes.

    only comps Turns off every type of collector except component collectors.

  • Altair Engineering Interfacing with LS-DYNA 53

    Tools Menu

    The Tools menu contains tools that can help simplify safety tasks. The following macros are included:

    Find free Finds the welds (*Constained_Spotweld), rigids (*Constrained_Node_Sets & *Constrained_Nodal_RigidBody), and rigidlinks (*Constrained_Node_Sets & *Constrained_Nodal_RigidBody), and checks if any of its nodes are free (not connected to any other entities). The display is cleared and then only free 1d elements are displayed.

    Find_fix free Finds the welds, rigids, and rigidlinks that are free as described above (Find free macro). These elements are corrected as follows:

    All 2-noded rigid and weld elements that have one free node are deleted. For the rigidlink elements that have free nodes, those nodes are removed from the rigidlink element. A check is performed for any rigidlinks with only one node and they are deleted.

    Fix incorrect Finds:

    19. Rigid elements (rigids, welds) that are connected to other rigids and combines them into one rigid element. If the connected rigids are of different types (*constrained_node_set or *constrained_nodal_rigidbody) it retains the type of the first rigid element it encounters.

    20. Rigid elements that are connected to other xtra_nodes_to_rigidbodies and converts them to xtra_nodes.

    21. Rigid elements connected directly to rigid component (MAT 20) will be converted to xtra_nodes.

    SpotWelds An automation tool that generates mesh independent MAT100 weld elements from a Master Weld File (MWF).

    Input: Master Weld File; Tolerance factor (TF)

    Process: For each weld point in the MWF, HyperMesh determines all the elements of the given components that fall within the search tolerance of the point. Search tolerance = Tolerance factor*higher of the thickness of the welding components. HyperMesh then projects the weld point onto these elements and creates a beam element (MAT100). It then connects these beam elements to the corresponding shell structural elements with plots. (These plot elements are for easy review purposes only and are not exported to the dyna deck). The beam elements are sorted into various components depending on the number of parts they connect (2TweldComponent, 3Tweldcomponent etc). A *Section_Beam property named mat100_prop is created with element formulation 9 and this property is assigned to all the weld components. A *Contact_SpotWeld is created with all the connected structural parts in the master component set and the weld components in

  • Interfacing with LS-DYNA Altair Engineering 54

    the slave component set.

    Output: Beam elements (representing MAT100 Spotwelds). Plot elements connecting the beams to structure (will not be exported to dyna). Weld component (2TweldComponent, 3Tweldcomponent, etc.) that contains the beams and plots, and has a beam section assigned to it. Beam property a mat100_prop Beam section property. Set_contact_part_list component set that contains all the comp ids in the MWF. Set_contact_Spotwelds component set that contains the weld components (2TweldComponent, 3Tweldcomponent, etc.). Contact_Spotweld group created with Set_contact_part_list as master set and Set_contact_Spotwelds as slave set.

    RLs with Sets HyperMesh 5.1 supports a rigid element that can have a node set attached to it. This type of rigid element improves the entity correspondence between HyperMesh and LS-DYNA. In LS-DYNA, a rigid element is a *Constrained card with a node set attached to it. When such an entity is imported into HyperMesh 5.0 (or earlier) all the nodes in the node set are converted to connectivity nodes of the rigid element and the node set is not imported. When a dyna file is exported, a new non-conflicting ID is selected and a node set is created with the connectivity nodes of the rigid element. This could result in varying node set ids for these *Constrained cards. Even though this would not affect the validity of the dyna file itself, it could cause confusion if you are trying to compare multiple dyna files. This new rigid element resolves that issue by allowing a set to be assigned to the rigid element where the nodes in the set are the dependent nodes of the rigid element. In HyperMesh 5.1, when a dyna file is imported, the *Constrained cards are converted to rigids with sets where the set id is obtained from the dyna file. But if you read in a Hypermesh 5.0 file that contains the old type of rigid elements, a set is not assigned to it.

    This macro finds all the rigid and rigidlink elements that are not attached to a set and converts them to attach to a set. This results in the creation of a node set for each rigid element that has been converted.

    Content table Displays a tabular list of all the components that exist in the model. For each component, the following items are displayed:

    ID Component ID

    NAME Component Name

    SECT ID ID of the property assigned to the component

    SECT NAME Name of the property assigned to the component

  • Altair Engineering Interfacing with LS-DYNA 55

    SECT TYPE Type of the property assigned to the component

    THICKNESS If SECT TYPE is *SECTION_SHELL, the thickness of that section

    MAT ID ID of the material assigned to the component

    MAT NAME Name of the material assigned to the component

    MAT TYPE Type of the material assigned to the component

    Of the above listed items, Comp NAME, SECT NAME, THICKNESS, and MAT NAME are editable fields. You can modify these fields and click update to change them in the HyperMesh database.

    Note: If multiple components have the same section or material assigned to them, changing the SECT NAME field at one location updates it wherever that section is used.

    A-D Menu

    The A-D menu contains shortcuts to HyperMesh panels used for creating various dyna entities.

    Macro: To create:

    *Airbag *AIRBAG_Option cards

    Tools page Safety module control vol panel

    *Boundary_prsbd_node *BOUNDARY_PRESCRIBED_MOTION_NODE card with velocity

    BCs page load types panel update velocity to prcrb Vel BCs page velocities panel

    *Boundary_prsbd_rigid *BOUNDARY_PRESCRIBED_MOTION_RIGID

    BCs page collectors panel load collectors set type to PrcrbRigid

    *Boundary_SPC *BOUNDARY_SPC_NODE card

    BCs page load types panel update constraints to BoundSPC BCs page constraints panel

    *Constrained_Nrigid *CONSTRAINED_NODAL_RIGID_BODY card

    1D page element types panel update rigids to RgdBody 1D page rigids panel

    *Constrained_Nset *CONSTRAINED_NODE_SET card

    1D page element types panel update rigids to ConNode 1D page rigids panel

  • Interfacing with LS-DYNA Altair Engineering 56

    *Constrained_XtraN *CONSTRAINED_EXTRA_NODES_SET card

    BCs page interfaces panel - set type to XtraNode

    *Constrained_Spotw *CONSTRAINED_SPOTWELD card

    1D page element types panel update welds to SpotWeld 1D page spotweld panel

    *Constrained_ Rivet *CONSTRAINED_RIVET card

    1D page element types panel update welds to Rivet 1D page spotweld panel

    *Constrained_ Gweld Create *CONSTRAINED_GENERALRIZED_WELD card

    1D page element types panel update rigids to Gweld 1D page rigids panel

    *Constrained_Joint *CONSTRAINED_JOINT_type card

    1D page fe joints panel

    *Constrained_Linear *CONSTRAINED_LINEAR card

    BCs page equations panel

    *Contact_ S_Surf *CONTACT_option_SINGLE_SURFACE card

    BCs page interfaces panel - set type to SingleSurface

    *Contact_ S_to_S *CONTACT_option_ SURFACE_TO_SURFACE card

    BCs page interfaces panel - set type to SurfaceToSurface

    *Contact_ N_to_S *CONTACT_option_ NODES_TO_SURFACE card

    BCs page interfaces panel - set type to NodesToSurface

    *Contact_ Slide *CONTACT_option_ SLIDING_ONLY card

    BCs page interfaces panel - set type to SlidingOnly

    *Contact_ Inter *CONTACT_ INTERIOR card

    BCs page interfaces panel - set type to Interior

    *Contact_ Entity *CONTACT_ENTITY card

    BCs page rigid walls panel - set type to ContEntity

    *Contact_ Rb_Rb *CONTACT_RIGID_BODY_TO_RIGID_BODY card

    BCs page interfaces panel - set type to

  • Altair Engineering Interfacing with LS-DYNA 57

    RgdBodyToRgdBody

    *Contact_ RN_Rb *CONTACT_RIGID_NODES_TO_RIGID_BODY card

    BCs page interfaces panel - set type to RgdNodeToRgdBody

    *Contact_ A_Gen *CONTACT_AUTOMATIC_GENERAL card

    BCs page interfaces panel - set type to AutomaticGeneral

    *Contact_ForceT *CONTACT_FORCE_TRANSDUCER card

    BCs page interfaces panel - set type to ForceTransducer

    *Contact_DrawBd *CONTACT_DRAWBEAD card

    BCs page interfaces panel - set type to DrawBead

    *Database_Ascii *DATABASE_option cards

    BCs page control cards panel Dbase Opts

    *Database_Bin *DATABASE_BINARY_option cards

    BCs page control cards panel

    *Database_Sec_P *DATABASE_CROSS_SECTION_PLANE cards

    BCs page rigid walls panel - set type to XSectionPlane

    *Database_Sec_N *DATABASE_CROSS_SECTION_NODE cards

    BCs page interfaces panel - set type to XSection_Set

    *Database_Hist_N *DATABASE_HISTORY_NODE cards

    BCs page output block panel

    *Database_NFG *DATABASE_NODAL_FORCE_GROUP cards

    BCs page interfaces panel - set type to NodalForceGrp

    D-R Menu

    The D-R menu contains shortcuts to HyperMesh panels used for creating various dyna entities.

    Macro: To create:

    *Define_Curve *DEFINE_CURVE card

    Post page xy plots model edit curves panel

  • Interfacing with LS-DYNA Altair Engineering 58

    *Define_Sytem *DEFINE_COORDINATE_SYSTEM card

    Geom page systems panel

    *Define_Vector *DEFINE_VECTOR card

    1D page vectors panel

    *Define_SD *DEFINE_SD_ORIENTATION card

    1D page vectors panel

    *Deform_2_rigid *DEFORMABLE_TO_RIGID_option card

    BCs page collectors panel load collectors - set type to Dform2Rigid

    *Element_beam *ELEMENT_BEAM card

    1D page bars panel

    *Element_dscret *ELEMENT_DISCRETE card

    1D page springs panel

    *Element_inert *ELEMENT_INERTIA card

    1D page element types panel set mass to Inertia and then 1D page masses panel

    *Element_mass *ELEMENT_MASS card

    1D page element types panel set mass to Mass and then 1D page masses panel

    *Element_sbelt *ELEMENT_SEATBELT card

    Tools page Safety module seatbelt panel

    *Element_accel *ELEMENT_SEATBELT_ACCELEROMETER card

    2D page element types panel set tria3 to Accel and then 2D page edit elements panel

    *Element_preten *ELEMENT_SEATBELT_PRETENSIONER card

    Tools page Safety module element types panel set mass to Retractor

    Tools page Safety module 0-D elems panel

    *Element_retrac *ELEMENT_SEATBELT_RETRACTOR card

    Tools page Safety module element types panel set mass to

  • Altair Engineering Interfacing with LS-DYNA 59

    Retractor

    Tools page Safety module 0-D elems panel

    *Element_slipr *ELEMENT_SEATBELT_SLIPRING card

    Tools page Safety module element types panel set mass to Slipring

    Tools page Safety module 0-D elems panel

    *Element_sensr *ELEMENT_SEATBELT_SENSOR card

    Tools page Safety module sensors panel

    *Initial_Velocity *INITIAL_VELOCITY card

    BCs page collectors panel load collectors - set type to InitialVel

    node *INITIAL_VELOCITY_NODE card

    BCs page load types panel update velocity to InitVel and then BCs page velocities panel

    gen *INITIAL_VELOCITY_GENERATION card

    BCs page collectors panel load collectors - set type to InitialVel

    *Interface_cmp_S *INTERFACE_COMPONENT_SEGMENT card

    BCs page interfaces panel - set type to InterCompSegment

    *Interface_cmp_N *INTERFACE_COMPONENT_NODE card

    BCs page interfaces panel - set type to InterCompNode

    *Interface_link_S *INTERFACE_LINKING_SEGMENT card

    BCs p