LS-DYNA3D

Interfacing with LS-DYNA3D

Altair HyperMesh 3.1

AltairEngineering

For technical support, contact us by phone or e-mail:

Country Phone E-mail

United States 248.614.2400 [email protected]

Germany 49.7031.6208.22 [email protected]

India 91.80.665.8871 [email protected]

Israel 972.3.5473651 [email protected]

Italy 39.11.900.77.11 [email protected]

Japan 81.3.5396.1341 [email protected]

Korea 822.573.4152 [email protected]

Scandinavia 46.46.286.2052 [email protected]

United Kingdom 44.1327.810700 [email protected]

Copyright (c) 2000 Altair Engineering, Inc. All rights reserved.

Trademark Acknowledgments:

HyperMesh is a registered trademark of Altair Engineering, Inc.ACIS is a registered trademark of SPATIAL TECHNOLOGY, INC.ACIS Geometric Modeler is a registered trademark of SPATIAL TECHNOLOGY, INC.ACIS Kernel is the registered trademark of SPATIAL TECHNOLOGY, INC.ACIS Parametric Surfaces is the registered trademark of SPATIAL TECHNOLOGY, INC.MS-DOS is a registered trademark of Microsoft Corporation.UNIX is a registered trademark of AT&T.MSC/NASTRAN is a registered trademark of MSC.ABAQUS is a registered trademark of Hibbitt, Karlsson, & Sorensen, Inc.ANSYS is a registered trademark of Ansys, Inc.PATRAN is a registered trademark of MSC.LS-DYNA is a registered trademark of LSTC.MARC is a registered trademark of MARC Analysis Research Corporation.PAMCRASH is a registered trademark of Engineering Systems International.FLUENT is a registered trademark of Fluent, Incorporated.I-DEAS is a registered trademark of Structural Dynamics Corporation.Spaceball is a registered trademark of Spacetec IMC Corporation.

Altair Engineering Interfacing with LS-DYNA3D1

LS-DYNA3D Translation Overview

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

Importing DecksVersions 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 ( orDYNASEQ.EXE on PCs). This translator handles both regular and large format decks. Thermalcontrol cards 27 through 30 are not supported.

To import data with the input translator:

1. Select the files panel.

2. Select the import subpanel.

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 forthe translator.

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

6. Click import.

Exporting DecksHyperMesh outputs LS-DYNA3D version 936 input files in both Keyword and Structured formats.

• To output Keyword decks, use the dyna936.key template file

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

• To output large format Structured decks, use the dyna936.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-DYNA3D model to the RADIOSS format, check and updatethe element types prior to writing the converted model to file. Some formulations maynot map correctly, such as RADIOSS SHELL 3N to LS-DYNA3D ACCEL.

Interfacing with LS-DYNA3D Altair Engineering2

To create an analysis deck via a template:


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 thesummary panel. This creates an ASCII text file with the summary information and displays theinformation on the screen.

LS-DYNA3D 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 typecontained 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 themodel. The template lists the name, ID, and material ID for each component. Components that havethe *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 themass panel. See Mass Calculation.

The center_of_gravity summary template calculates the model’s center of gravity based on theprocedure described in the Mass Calculations section.

There are also two templates that perform error checking on LS-DYNA3D models: errorcheck andsharedrigids.

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

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

When either of the error-checking templates check for shared rigids, the template highlights only thesecond element that uses a node. If an element in a rigid material is sharing a node with anotherrigid, 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 CalculationThe 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 materialassociated with the element’s component.

A *PART_INTERIA card uses the supplied mass instead of calculating the mass based on theindividual 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

• 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 isdefined for an element. If an *ELEMENT_SHELL_THICKNESS card is defined, the element valuesoverride the *SECTION_SHELL values.

Integrated beams have an area equal to the average of the two end areas. Resultant beams use thearea entered on the *SECTION_BEAM card. The volume is calculated by multiplying the length of thebeam 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 anelement, then the element values override the *SECTION_BEAM values.

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

Supported CardsThe HyperMesh LS-DYNA3D interface supports the following cards:

Components and Properties Materials

Control and Database Cards Nodes

Curves Other Groups

Elements Output Blocks

Entity Sets Rigid Walls

Equations Systems

HyperMesh Groups Vectors

Load Collectors Working with Comment Cards

Loads, Constraints, and Boundary Conditions


Working with Comment Cards

HyperMesh-defined comment cards included in decks written by HyperMesh. These comments areincluded so that decks can be written and re-read without losing information as well as to reorganizethe database. These comments can be read from any deck and can be inserted into a deck beforeimporting the deck into HyperMesh.

$HM_OUTPUT_DECK

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

$HMNAME Entitytype ID HyperMesh_Name

This comment gives the name of the collector where the information that follows originated. If thiscomment 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.

$HMCOLOR Entitytype ID Color

This comment changes the color of a collector or curve. Entitytype is the collector type, such asCOMP or GROUP. ID is an 8 character integer that identifies the collector. Color is an8-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 createdwhile the templates output the deck. This changes how the set is imported into HyperMesh and howit is associated with groups.

$HMCURVE linetype markertype title

This comment preserves the style information for load curves. linetype is a 5-character integerthat describes the style of the line: solid, dashed, and so on. markertype is a 5-character integerthat 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$HMSURF id collectorid$HMASSOC nodeid surfid index

These comments occur at the end of the data deck and relate to any geometric information containedin the model. The geometric information refers to lines, surfaces, and nodes that are attached tosurfaces.


$HMFIXEDSURFPOINT x y z Suppressed

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

$HMERROR text

This comment is output when the HyperMesh template detects and/or corrects a problem during deckcreation. 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 bothtypes

• Thermal Control Cards are not supported

Keyword

HyperMesh Name LS-DYNA3D Keyword Notes

TitleCard *TITLE

Keyword *KEYWORD This card must be the first block in theKeyword template for HyperMesh to outputa valid Keyword deck.

When the card is active, memoryrequirements may be specified; otherwise itis automatically output on the first line of thefile.

HyperMesh Name *CONTROL Cards Notes

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 onexport.


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

Part Damp _PART_MASS

Part Dmp Stf _PART_STIFFNESS

HyperMesh Name *DATABASE Cards Notes

DBase Opts _OPTION For example, SECFORC, RWFORC,NODOUT, and so on. These can be editedon one panel. The selected values havecards 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 (ModelSize), 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 TIMEHISTORY blocks, are filled. When you edit cards that contain automatically generated fields, it isindicated by the card previewer.

HyperMesh Name Editable Control Cards

1 - Title Card This card has 930 as a versionnumber. LARGE is output when youuse the dyna936.lrg template.

Termination 8 - Termination

Time Step 9 - Time Steps

Beams & Shells 12 - Beams and Shells

Materials 13 - Material Related Input

Damping 14 - Damping/Dynamic Relaxation

Contact 15 - Contact

Paral/Subcyc 16 - Parallel and Subcycling

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



ALE 1 25 - Arbitrary Lagrangian 1

ALE 2 26 - Arbitrary Lagrangian 2

Systems

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

The only supported output format for systems is *DEFINE_COORDINATE_SYSTEM in Keyword ortype 1 in Structured.


Nodes

Node cards are fully input into HyperMesh. Any constraints defined on the node card convert toHyperMesh constraints and are output as *BOUNDARY_SPC/Card 13.

No provision is made for defining constraints on nodes cards that are output.

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

ElementsHyperMesh Type Keyword Structured Notes

Mass 1 *ELEMENT_MASS Card 50

Weld 1 *CONSTRAINED_ SPOTWELD

Card 29c Structured DOF = -1. Failurevalues can be edited on theindividual elements.

2 *CONSTRAINED_RIVET Card 29b Structured DOF = 0

Rigid(two-noded)

1 *CONSTRAINED_NODE_ SET

Card 29a Structured DOF = 1 through7

2 *CONSTRAINED_NODAL_ RIGID_BODY

Card 36a Structured Failure Option 0.Keyword _INERTIA optionsupported.

3 *CONSTRAINED_ GENERALIZED_WELD

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

Spring 1 *ELEMENT_DISCRETE Card 50 Dyna Spring and Damperelements

Joints 1 *CONSTRAINED_JOINT_SPHERICAL

Card 38 Structured type is the sameas the HyperMesh type.

2 *CONSTRAINED_JOINT_REVOLUTE


3 *CONSTRAINED_JOINT_CYLINDRICAL


4 *CONSTRAINED_JOINT_PLANAR


5 *CONSTRAINED_JOINT_UNIVERSAL


6 *CONSTRAINED_JOINT_TRANSLATIONAL


7 *CONSTRAINED_JOINT_LOCKING


Rigid Links(many noded)

1 *CONSTRAINED_NODE_ SET

Card 29a Structured DOF = 1 through7


2 *CONSTRAINED_NODAL_ RIGID_BODY

Card 36a Structured Failure Option 0.Keyword _INERTIA optionsupported.

3 *CONSTRAINED_ GENERALIZED_WELD

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

Bar2 1 *ELEMENT_BEAM Card 8 _THICKNESS optionsupported. Use directionnode option. The actualnode is referenced /read/written by HyperMesh.

Tria3 2 *ELEMENT_SEATBELT_ ACCELEROMETER

Card 51g

Tria3 1 *ELEMENT_SHELL Card 9 _THICKNESS and _BETAoptions supported.

Quad4 1 *ELEMENT_SHELL Card 9 _THICKNESS and _BETAoptions 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 byHyperMesh. 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, anddensity for unsupportedmaterials.

MATL1 ELASTIC Type 1 Fluid option supported. SeeNOTE 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 andShell formulations whenusing the Card Editor. SeeNOTE 2.


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

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

MATL69 SID_DAMPER_DISCRETE_ BEAM

Type 69

MATL71 MAT_CABLE_DISCRETE_BEAM Type 71

MATL77 HYPERELASTIC_RUBBER Type 77

MATL81 PLASTICITY_WITH_DAMAGE Type 81

SB_MAT *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

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

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

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-DYNA3D 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 ontheir 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 andusing 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, hourglassrules, and so on. HyperMesh does not verify that a legal selection was made. If an integrationrule is selected instead of a *SECTION_SHELL card, HyperMesh assumes this a legal operation,while LS-DYNA3D generates an error message.

• The material associated with a component is controlled by HyperMesh functionality and cannotbe 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 isdisplayed at the end of the component card image.

HyperMesh Keyword Structured Notes

Components *PART Card 3 INERTIA andREPOSITION optionssupported.

on Comps *CONSTRAINED_RIGID_BODIES Card 35 Select RigidBodyMergeoption on *PART.

SectBeam *SECTION_BEAM Card 3 Supports all elementformulations.

SectDisc *SECTION_DISCRETE Card 50A Spring/Damper PropertyCard.

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_ EOS Type 7


GROWTH_OF_REACTION_IN_HE

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 onComponent card inStructured.

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.

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 aload card, a new load collector is created. For the comments to be valid, they must follow a loadkeyword or the last line of the previous Structured block. The loads that follow a $HMNAMELOADCOLS 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 separateload collector named Nodal Constraints.

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



InitialVel *INITIAL_VELOCITY Card 30 This card changes the INITVdefinition on Control Card 11.Only the first card defined isvalid for Structured.

LoadBody *LOAD_BODY_X Card 39 Activate the proper option andenter the data. Only the firstcard defined is valid forStructured.

*LOAD_BODY_Y Card 40 Activate the proper option andenter the data. Only the firstcard defined is valid forStructured.

*LOAD_BODY_Z Card 41 Activate the proper option andenter the data. Only the firstcard defined is valid forStructured.

*LOAD_BODY_RX Card 42 Activate the proper option andenter the data. Only the firstcard defined is valid forStructured.

*LOAD_BODY_RY Card 43 Activate the proper option andenter the data. Only the firstcard defined is valid forStructured.

*LOAD_BODY_RZ Card 44 Activate the proper option andenter the data. Only the firstcard defined is valid forStructured.

*LOAD_BODY_PARTS Card 45 Select component set toexclude.

LoadBodyGen *LOAD_BODY_ GENERALIZED

Card 46


Loads, Constraints, and Boundary Conditions

Several HyperMesh load types cause three cards to be output for x, y, and z components. Duringinput, HyperMesh groups these into one load. Loads cannot be applied to sets, components, orboxes. 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 26VAD = 2

Forces 1 *LOAD_NODE_POINT Card 23Point Loads

LS-DYNA3D LoadConfigs 1, 2, and 3.

Moments 1 *LOAD_NODE_POINT Card 23Point Loads

LS-DYNA3D LoadConfigs 5, 6, and 7.

Pressures 2 *LOAD_SHELL_PRESSURE

Card 24Pressure BC

1 *LOAD_SEGMENT

Velocities 1 *BOUNDARY_PRESCRIBED_ MOTION_NODE

Card 26VAD = 0

2 *INITIAL_VELOCITY Card 30INITV = 3

For Structuredoutput, globalvelocity is set to 0.0.For Structuredinput, non-zerovalues for INITV = 1or INITV = 5 createHyperMeshvelocities. INITVvalues of 2, 4, 6, and7 are ignored.

Acceleration 1 *BOUNDARY_PRESCRIBED_ MOTION_NODE

Card 26VAD = 1


HyperMesh Groups

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

The interface panel allows you to define groups with HyperMesh configurations of 1, 2, 3, and 4. Thedifference 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.

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 groupconfiguration holds the additional geometric data for LS-DYNA3D 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 are0, 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 fieldis considered a comment.

• (These are obsolete, but still read) If the line following the keyword (No TITLE option), or the firstline of the Structured card contains $HM_NAME, the name supplied is read and used as thegroup's name. If the string $HM_ID also exists, this is used as the group’s ID. NAME is 16characters, starting in Column 9. ID field is 8 characters, starting in Column 35.

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


HyperMesh Option Keyword *CONTACT_ Structured

SlidingOnly Defines a *CONTACT_SLIDING_ONLY_option card.

Off <nothing> Type 1

On PENALTY Type p1

SurfaceToSurface Defines a *CONTACT_option_SURFACE_TO_SURFACE card.

None <nothing> Type 3

Automatic AUTOMATIC_ Type a3

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

None and OneWay ONE_WAY_ Type 10

Automatic andOneWay

AUTOMATIC_ONE_ WAY_

Type a10

Constraint CONSTRAINT_ Type 17

Eroding ERODING_ Type 14

TieBreak TIEBREAK_ Type 9

Tied TIED Type 2

NodesToSurface Defines a *CONTACT_option_NODES_TO_SURFACE card.

None <nothing> Type 5

Automatic AUTOMATIC Type a5

Constraint CONSTRAINT_ Type 18


TieBreak TIEBREAK_ Type 8

Tied TIED_ Type 6

SingleSurface Defines a *CONTACT_option_SINGLE_SURFACE card.

none <nothing> Type 4

Automatic AUTOMATIC_ Type 13

Airbag AIRBAG_ Type a13


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


To define a Type a5/*CONTACT_AUTOMATIC_NODES_TO_SURFACEinterface:

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 whichthese nodes are added.

• _SET is defined unless only one node is selected. In this case,_NODEis output.

• Only define this using the entity or set selection mechanism on the addsubpanel of the interfaces panel.

CrossSection *DATABASE_CROSS_SECTION Card 21

• Defining the slaves by components adds _PLANE to the card. Masterinformation is ignored.

• Defining slaves by entities or sets allows an entity set of shell elementsto be attached to the card. No provision is made for beams, solids,thick shells or discrete elements.

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

NodalForceGrp *DATABASE_NODAL_FORCE_GROUP Card 28


Rigid Walls

The rigid wall panel supports planes (finite/infinite), prisms (finite/infinite), cylinders, and spheres.Motion options are available for all geometric configurations.

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


RWGeometric *RIGIDWALL_ GEOMETRIC

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

RWPlanar *RIGIDWALL_ PLANAR

Stonewalls Card 27LIMIT = 1 & 2

ORTHO, FINITE,MOVING optionssupported.

ContEntity *CONTACT_ENTITY Geometric Contact Entity Card 58

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

EquationsEquations 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 not supported for Keyword.

• When you define an element output block, select only one type of element, such as shells orbeams. 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 to1000. HyperMesh does not support incremental numbering and LS-DYNA3D only allows 2000numbers to be placed on the cards [start/finish]. HyperMesh outputs each entity number twice.This limit is non-existent in KEYWORD.

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


VectorsHyperMesh Keyword Structured Notes

Vectors *DEFINE_SD_ORIENTATION Card 50C

*DEFINE_VECTOR N/A When DefineVector ischosen.

Entity Sets

• HyperMesh reads the sets defined in an input deck

• Sets are supported on output, except _COLUMN options

• Element sets must be one type of element, determined by the first element in the set

Curves

• Output of curves creates a *DEFINE_CURVE or Structured Card 22 using Option 0

• HyperMesh XY curves that are referenced by a load, material, component, property, and so onare output

• On input, the *DEFINE_CURVE/Card 22 cards are read and placed in a plot called LS-DYNA3DLoad Curves

• During input, references to curves are preserved and are output along with the card, such asmaterial, 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 dyna936templates. The curves templates output the curves that exist in the current model. By using theoutput displayed option and the display panel, a precise set of load curves can be created. Thismethod allows you to create new curves or modify existing curves for LS-DYNA3D entities thatHyperMesh does not support.


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

hmdyna [arguments] <input file> <output file> <model file>

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

Flag Meaning

-t Temperatures

-d Displacements

-v Velocities

-a Accelerations

-xx Sigma xx

-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

-th Thickness

-eld1 Element Dependent Variable 1

-eld2 Element Dependent Variable 2

-ie Internal Energy

-inner Inner Surface

-outer Outer Surface

-mid Mid Surface

-max Maximum of top and bottom surface values

--max Option to turn off Maximum

-902 Version 902

-float Float format

-2s1 2-D Principal Strain 1

-2s2 2-D Principal Strain 2

-2S1 2-D Principal Stress 1

-2S2 2-D Principal Stress 2

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

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

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

-3sh 3-D Maximum Shear Strain


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

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

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

-3Sh 3-D Maximum Shear Stress

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

The following options can be used in conjunction with -force. -force must be specified as anargument and is used for the iff file from LS-DYNA3D. The iff file needs to be requested fromLS-DYNA3D 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. IfN 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 theanalysis machine. One of these parameters may need to be specified to indicate where the analysisresult 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

-sgi SGI

-sun Sun

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

<stress var>, from setN, where <stress var> can be one of Sigmaxx, Sigmayy, Sigmazz, Sigmaxy,Sigmayz, and Sigmazx. N varies from 4 to MAXINT (number of integration points), with an incrementof 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)

Epsilon - xy (mid)

Epsilon - yz (mid)

Epsilon - zx (mid)

Principal Strain 3D1 (mid)



Maximum Shear Strain 3D (mid)

Principal Stress 3D1 (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)



Maximum Shear Strain 3D (inner and outer)

Principal Stress 3D1 (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

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)








Maximum Shear Strain 3D (inner and outer)




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

The supported results for the force database include the following:

nodal

Displacements

Velocities


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-DYNA3D elements and their HyperMesh equivalents for the statedatabase:

LS-DYNA3D HyperMesh

Bricks Hex8

Brick Shells Hex8

Beams Plot

4-noded shells Quad4

The following table lists the LS-DYNA3D elements and their HyperMesh equivalents for the forcedatabase:

LS-DYNA3D HyperMesh

4-noded elements Quad4

3-noded elements Tria3

LS-DYNA3D ASCII results files can be used to create data curves in HyperMesh using the editcurves subpanel on the xy plot panel. See the edit curves documentation in the HyperMesh User’sOn-line Help for instructions on how to input the curves. To set the output for these files, use theDBOpts Control Card.


Import Template LS-DYNA3D Result File

defgeo.tpl DEFGEO Deformed Geometry

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 reactionforces

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/orotations

nodout2.tpl NODOUT2 Nodal Point Data withrotations

sleout.tpl SLEOUT Sliding Interface energy

rwforc.tpl RWFORC Wall forces

rcforc.tpl RCFORC Resultant interface forcesfor only master elements

rcforc2.tpl RCFORC Resultant interface forcesfor master and slaveelements

matsum.tpl MATSUM Material energies withouthourglass

matsum2.tpl MATSUM Material energies withhourglass

glstat.tpl GLSTAT Global Data withouthourglass

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 fileto view the model in HyperMesh.

To import the model file and view the results:

1. Select global from the permanent menu.

2. Click results file = and enter the name of the results file, or click on results file = again tobrowse the directory structure for the correct file.

3. Click return.

4. Select the import subpanel.


6. Click EXTERNAL if it is not already selected.

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

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

9. Click import.

10. 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.

Control Cards

*DATABASE_OPTION cards in Keyword are listed on the DBOpt control card in HyperMesh. Anactive 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 nevercreated or was deleted.

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

Inactive Red A card that has been defined may bedisabled. The attributes for that cardremain; however, the control card isnot 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 oneof the following states:

State Description

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

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

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 fieldsprovided. 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 isbased on weld type selected. Coordinate System ID can be selected.

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

*ELEMENT_DISCRETE/ Card 50Scale 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 elementformulation 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 thicknessand 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.

4. Select the loads to edit.

5. If more than one config or type of load is selected, enter the Config and Type to edit in the fieldsprovided. 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 bedisplayed in the card previewer. See the Loads section above for a complete list of the LS-DYNA3Dentities that HyperMesh treats as loads.

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

*BOUNDARY_SPC_NODE / Card 13A 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, offsetvalues, 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-DYNA3D output blocks cannot beedited.

Sets

Use the card previewer to view the set entity IDs. The default LS-DYNA3D attribute values for the setcan 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.

Tips and TechniquesThe template design in LS-DYNA3D favors Keyword format over Structured. When a choice wasavailable as to how to implement a functionality, most of the decisions were made to suit Keywordrather than Structured. Most of the HyperMesh entity names are derived from Keyword. Themain exception is HyperMesh material names.

When you import a Structured deck or output a Keyword deck, or vice versa, inspect the controlcards for proper values.

Several cards have fields that are displayed as needed, based on other information on the card. Anexample of this is the shell section card. When a positive number of integration points is specified,and ICOMP is set to 1, you can enter material angles in available fields.

All curves defined in a model may not be output. This is because only the curves referenced by aHyperMesh entity are written to a file. This is done so that results curves are not included in ananalysis deck.

To output all curves defined in a model, use the curves templates. If you use the displayed outputoption and have only the necessary curves displayed in the graphics area, you can create a small,simple file.

Element Numbering

Element numbering may be a problem between LS-DYNA3D and HyperMesh. LS-DYNA3D allowsdifferent types of elements, such as *ELEMENT_BEAM and *ELEMENT_SHELL, to have the samenumber. HyperMesh does not allow this and decks may be renumbered during feinput.

When you import a data deck, a message file is created (dynakey.msg or dynaseq.msg) in thedirectory that contains the HyperMesh executable. This is the same directory that stores yourcommand.cmf file. This file contains information generated from the deck input. The unread cardsare identified here, as well as problems that may occur during the input process.

NOTE If you change attribute numbers in the template files, the input deck is invalid. Newnumbers can be added, but existing numbers cannot be changed.


Working with Load Curves

Load curves can be read from disk files or created manually within HyperMesh.

$HMERROR and other error codes in templates

Sometimes, when LS-DYNA3D specific errors are found when outputting a HyperMesh model, thesignal $HMERROR is written to the output deck. An example of this is defining a*CONSTRAINED_NODE_SET with rotational constraints specified. Often, when this signal is written,a user value has been changed, and you are notified of that change.

Another error signal is a field containing a +/- 99. This is the result of a particular field being under- orover-specified. This signal is also displayed if HyperMesh cannot interpret the given information.

Translating Solid and Discrete Sections and Properties

Solid and Discrete Sections and Properties do not translate smoothly between Keyword andStructured.

Solids

A *SECTION_SOLID card is generated and associated with the component’s *PART card if:

• You are writing a Keyword deck

• The component contains solid elements

• A property is not selected

If you are writing a Structured deck, and an invalid solid property is defined for output, the SIDvalue is set to zero and the property is not written to the deck.

Discrete Elements

When writing a Keyword deck, a part is generated if discrete elements exist in the component and a*PART is not defined. The *SECTION_DISCRETE property used by the first element in thecomponent is attached to the *PART card. If you write a Structured deck and a *PART card isdefined for a spring component, the card is not written to the deck.

NOTE $HMERROR messages are added to the deck during these transformations.


RADIOSS Data Transfer

The following limitations exists when working with RADIOSS and LS-DYNA3D:

• Element Config 103 (TRIA3) Type 2 are incompatible

• RADIOSS material types 6, 10, 24, 32, 38, and 40 do not translate to LS-DYNA3D materials

• LS-DYNA3D material types do not translate to RADIOSS

To create load curves manually:

1. Select the xy plots panel on the Post page.

2. Select the edit curves panel.

3. Select the create subpanel.

4. Click plot = and select the plot to which this curve belongs, or create a new plot.

5. Click math to create the curve for both x and y data.

In the x = field, enter a 1-D comma-separated array, surrounded by brackets, {}.

Repeat this for the y = field. Make the arrays for x and y of equal length. For example:

x = {0.0, 0.1, 0.2, 0.3}

y = {2.1, 2.5, 3.7, 4.9}6. The data in a load curve can be assigned to any entity that requires a reference to a curve (loads

or materials), or reviewed in the card previewer.

To read load curves from disk:

1. Load curves can be read from disk by reading a LS-DYNA3D file that contains only load curvedata (*DEFINE_CURVE) via the feinput translator.

2. To read load curves:

Select the xy plots panel on the Post page.

Select the read curves panel.

The data must be in the following format:

Format Example

XYDATA, <curve name> XYDATA, curve1

<x1>,<y1> 0.000000, 2.000000

<x2>,<y2> 1.000000, 3.000000

<x3>,<y3> 2.000000, 4.000000

ENDDATA ENDDATA


To write load curves to disk:

Use the following steps to output a data curve as an XY file (XYDATA ... ENDDATA).1. Select the xy plots panel on the Post page.

2. Select the simple math panel.

3. In the plot =, 1st curve =, and 2nd curve = fields select the plot and curve to be written to disk.

4. Select the external operation to select an external filter to be applied to the curve.

5. In the target = field, select the same curve as the one to be written to disk.

This results in the curve being overwritten by itself. Ignore the warning message when executeis selected.

6. Select the todisk filter in the filter box or use a copy command such as /bin/cp (the path mustbe present).

7. Enter the name of the output file in the params field.

8. Click execute.

9. Click OK to overwrite the curve in the 1st curve = field.

Documents

LS-DYNA3D