patran 2008 r1 interface to ls-dyna preference guide

Patran 2008 r1

Interface To LS-DYNA Preference Guide

Worldwide Webwww.mscsoftware.com

DisclaimerThis documentation, as well as the software described in it, is furnished under license and may be used only in accordance with

the terms of such license.

MSC.Software Corporation reserves the right to make changes in specifications and other information contained in this document

without prior notice.

The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not

intended to be exhaustive or to apply to any particular engineering problem or design. MSC.Software Corporation assumes no

liability or responsibility to any person or company for direct or indirect damages resulting from the use of any information

contained herein.

User Documentation: Copyright ©2008 MSC.Software Corporation. Printed in U.S.A. All Rights Reserved.

This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this

document, in whole or in part, without the prior written consent of MSC.Software Corporation is prohibited.

The software described herein may contain certain third-party software that is protected by copyright and licensed from

MSC.Software suppliers. Contains IBM XL Fortran for AIX V8.1, Runtime Modules, (c) Copyright IBM Corporation 1990-2002,

All Rights Reserved.

MSC, MSC/, MSC Nastran, MD Nastran, MSC Fatigue, Marc, Patran, Dytran, and Laminate Modeler are trademarks or registered

trademarks of MSC.Software Corporation in the United States and/or other countries.

NASTRAN is a registered trademark of NASA. PAM-CRASH is a trademark or registered trademark of ESI Group. SAMCEF is

a trademark or registered trademark of Samtech SA. LS-DYNA is a trademark or registered trademark of Livermore Software

Technology Corporation. ANSYS is a registered trademark of SAS IP, Inc., a wholly owned subsidiary of ANSYS Inc. ACIS is a

registered trademark of Spatial Technology, Inc. ABAQUS, and CATIA are registered trademark of Dassault Systemes, SA.

EUCLID is a registered trademark of Matra Datavision Corporation. FLEXlm is a registered trademark of Macrovision

Corporation. HPGL is a trademark of Hewlett Packard. PostScript is a registered trademark of Adobe Systems, Inc. PTC, CADDS

and Pro/ENGINEER are trademarks or registered trademarks of Parametric Technology Corporation or its subsidiaries in the

United States and/or other countries. Unigraphics, Parasolid and I-DEAS are registered trademarks of UGS Corp. a Siemens

Group Company. All other brand names, product names or trademarks belong to their respective owners.

P3*2008R1*Z*DYND*Z* DC-USR

Corporate Europe Asia Pacific

MSC.Software Corporation2 MacArthur PlaceSanta Ana, CA 92707 USATelephone: (800) 345-2078Fax: (714) 784-4056

MSC.Software GmbHAm Moosfeld 1381829 Munich, GermanyTelephone: (49) (89) 43 19 87 0Fax: (49) (89) 43 61 71 6

MSC.Software Japan Ltd.Shinjuku First West 8F23-7 Nishi Shinjuku1-Chome, Shinjuku-Ku Tokyo 160-0023, JAPANTelephone: (81) (3)-6911-1200Fax: (81) (3)-6911-1201

Con t en t s

Patran Interface to LS-DYNA Preference Guide

1 Overview

Purpose 2

LS-DYNA Product Information 4

What is Included with this Product? 5

LS-DYNA Preference Integration with Patran 6

Patran LS-DYNA Preference Components 7

Configuring the Patran LS-DYNA Execute File 10

2 Building A Model

Introduction to Building a Model 12

Coordinate Frames 18

Finite Elements 19

Nodes 20

Elements 21

Multi-Point Constraints 22

Material Library 30

Materials Form 31

Element Properties 62

Element Properties Form 62

Loads and Boundary Conditions 91

Loads and Boundary Conditions Form 92

Object Tables 100

Load Cases 110


==

ii

3 Running an Analysis

Review of the Analysis Form 112

Analysis Form 113

Translation Control 115

Solution Parameters 116

Solution Control 117

Relaxation Parameters 118

Global Damping 119

Material Viscosity Defaults 119

Energy Calculation 120

Shell Control 121

Contact Defaults 122

Select Load Case 123

Output Requests 124

Output Controls 133

Select Groups for Set Cards 134

Setting LSDYNA IDs 135

4 Read Results

Review of the Read Results Form 138

Read Results Form 139

Subordinate Forms 141

Select State File Subordinate Form 141

Select Times 142

Select Results 143

Results Created in Patran 144

Results File Size 145

5 Read Input File

Review of Read Input File Form 148

Read Input File Form 149

Data Translated from the LS-DYNA Input File 152

iiiCONTENTS

Reject and Error File 156

6 Files

Files 158


==

iv

Chapter 1: Overview


1 Overview

� Purpose 2

� LS-DYNA Product Information 4

� What is Included with this Product? 5

� LS-DYNA Preference Integration with Patran 6

� Patran LS-DYNA Preference Components 7

� Configuring the Patran LS-DYNA Execute File 10

Patran Interface to LS-DYNA Preference GuidePurpose

2

Purpose

Patran is an analysis software system developed and maintained by MSC.Software Corporation. The core

of the system is Patran, a finite element analysis pre- and post-processor. The Patran system also includes

several optional products such as advanced postprocessing programs, tightly coupled solvers, and

interfaces to third party solvers. This document describes one of these interfaces.

The Patran LS-DYNA Application Preference provides a communication link between Patran and LS-

DYNA. It also provides customization of certain features that can be activated by selecting LS-DYNA

as the analysis code “Preference” in Patran.

The LS-DYNA Preference is fully integrated into Patran. The casual user will never need to be aware

separate programs are being used. For the expert user, there are four main components of the preference:

a PCL function, load_lsdyna3d(), which will load all LS-DYNA specific definitions, like element

types and material models, into the currently opened database, pat3lsdyna to convert model topology

from the Patran database into the analysis code input file, and to translate model data from an LS-DYNA

input file, and lsdynapat3 to translate results and/or model data from the analysis code results file into

the Patran database.

Selecting LS-DYNA as the analysis code under the “Analysis Preference” menu modifies Patran forms

in five main areas:

1. Materials

2. Element Properties

3. Finite Elements/MPCs and Meshing

4. Loads and Boundary Conditions

5. Analysis forms

The PCL function load_lsdyna3d() can be invoked by simply typing its name into the Patran

command line. It will load LS-DYNA specific definitions into the Patran database currently opened. LS-

DYNA specific definitions can be added to any Patran database (which does not already contain LS-

DYNA specific definitions) at any time. Obviously, a Patran database must be open for

load_lsdyna3d() to operate correctly. See LS-DYNA Preference Integration with Patran (p.4) for

complete information and a description of how to create a new template database.

pat3lsdyna translates model data between the Patran database and the analysis code-specific input file

format. This translation must have direct access to the originating Patran database when an LS-DYNA

input file is being created.

lsdynapat3 translates results and/or model data from the analysis, code-specific results file into the Patran

database. This program can be run so the data is loaded directly into the Patran database, or if

incompatible computer platforms are being used, an intermediate file can be created.

lsdynapat3 executes a program that is written and supported by Ove Arup Computing Systems, 13

Fitzroy Street, London W1P 6BQ (Tel: (44) 020-7465-2500, Fax: (44) 020 7465 2211). Ove Arup

distribute and support LS-DYNA in the UK. They contribute actively to the development,

documentation, and quality assurance of LS-DYNA and develop their own translators between LS-

3Chapter 1: OverviewPurpose

DYNA and third party pre and post processing systems. They have collaborated with MSC to ensure that

LS-DYNA is effectively and efficiently interfaced to Patran.

pat3lsdyna also translates model data from the analysis, code-specific input file into the Patran database.

Reading LS-DYNA Input Files

This release of the Patran LS-DYAN3D interface provides support for reading LS-DYNA input files.

Nodes, elements, coordinate systems, some materials and some properties are read from an input file.

Patran Interface to LS-DYNA Preference GuideLS-DYNA Product Information

4

LS-DYNA Product Information

LS-DYNA is a general-purpose explicit finite element computer program for nonlinear dynamic analysis

of structures in three dimensions.

The program is developed, supported, and maintained by Livermore Software Technology Corporation

(LSTC), 2876 Waverley Way, Livermore, California 94550 (Tel: 925-449-2500, Fax: 925-449-2507).

See the LS-DYNA User’s Manual for a general description of LS-DYNA3D’s capabilities.

5Chapter 1: OverviewWhat is Included with this Product?

What is Included with this Product?

The LS-DYNA Preference product includes the following items:

1. A PCL function contained in p3patran.plb which will add LS-DYNA specific definitions to

any Patran database (not already containing such definitions) at any time.

2. A PCL library called lsdyna3d.plb and contained in the <installation_directory>

directory. This library is used by the analysis forms to produce analysis code specific translation

parameter, solution parameter, etc. forms.

3. On Windows, a library called lsdyna3ddra.dll contained in the

<installation_directory>/bin/exe directory. On Unix, a library called

liblsdyna3ddra in the <installation_directory>/lib.

4. A script file called LsDyna3dExecute is contained in the

<installation_directory>/bin/exe directory on Unix.

5. This Patran LS-DYNA Preference Guide is included as part of the product. An online version is

also provided to allow the direct access to this information from within Patran.

Patran Interface to LS-DYNA Preference GuideLS-DYNA Preference Integration with Patran

6

LS-DYNA Preference Integration with Patran

Creation of an LS-DYNA Template Database

Two versions of the Patran database are delivered with Patran. Both occur in the

<installation_directory> directory and they are named base.db and template.db. The

base.db database is a Patran database into which no analysis code specific definitions, such as element

types and material models, have been stored. The template.db database is a version of the Patran

database which contains every analysis code specific definition needed by the MSC supplied interfaces.

In order to create a template database which contains only LS-DYNA specific definitions, the user should

follow these steps:

1. Within Patran open a new database using base.db as the template.

2. Enter load_lsdyna3d() into the command line.

3. Save this database under a name like lsdyna.db to be your new “LS-DYNA only”

template database

4. From then on, when opening a new database, choose lsdyna3d.db as your template database.

Any databases derived from base.db may not contain the needed LS-DYNA specific definitions

needed to run the LS-DYNA Preference. But, LS-DYNA specific definitions can be added to any

database at any time by simply typing load_lsdyna3d() into the Patran command line while the

target database is the database currently opened by Patran. Due to the savings in size and for the sake of

simplicity it is highly recommended template.db not be used as a template database and that users

create their own unique template database which contains only the analysis code specific definitions

pertaining to the analysis codes of immediate interest. For more details about adding analysis code

specific definitions to a database and/or creating unique template databases, refer to the Patran

Installation and Operations Guide.

7Chapter 1: OverviewPatran LS-DYNA Preference Components

Patran LS-DYNA Preference Components

The diagrams shown below indicate how the functions, scripts, programs and files which constitute the

LS-DYNA Preference affect the Patran environment. Site customization, in some cases, is indicated.

Figure 1-1 shows the process of running an analysis. The lsdyna3d.plb library defines the

Translation Parameter, Solution Type, Solution Parameter, and Output Request forms called by the

Analysis form. When the Apply button is pushed on the Analyze form pat3lsdyna is executed. pat3lsdyna

reads data from the database and creates the LS-DYNA input file. A message file is also created to record

any translation messages. If pat3lsdyna finishes successfully, and the user requests it, the script will then

start LS-DYNA.

Figure 1-1 Forward Translation

Patran Interface to LS-DYNA Preference GuidePatran LS-DYNA Preference Components

8

Figure 1-2 shows the process of reading information from LS-DYNA State or Time History files. When

the Apply button is selected on the Read Results form, either a .jbm or .jbr file is created, depending

on whether model or results data is to be read. The LsdynaPat3Submit script is also started. The

script, in turn, starts the lsdynapat3 results translation. The Patran database is closed while this translation

occurs.

lsdynapat3 reads the data from the LS-DYNA State and Time History Files. If lsdynapat3 can find the

desired database, the results will be loaded directly into it. However, if it cannot find the database (e.g.,

you are running on incompatible platforms), lsdynapat3 will write all the data into a flat file. This flat file

can be taken to wherever the database is, and read by using the read file selections.

Figure 1-2 Results File Translation

Figure 1-3 shows the process of translating information from a LS-DYNA input file into a Patran

database. The behavior of the main Analysis/Read Input File form and the subordinate file select form is

9Chapter 1: OverviewPatran LS-DYNA Preference Components

dictated by the lsdyna3d.plb PCL library. The Apply button on the main form activates the

pat3lsdyna program which reads the specified LS-DYNA input file into the Patran database.

Figure 1-3 LS-DYNA Input File Translation

Patran Interface to LS-DYNA Preference GuideConfiguring the Patran LS-DYNA Execute File

10

Configuring the Patran LS-DYNA Execute File

The LsDyna3dExecute script file controls the execution of the LS DYNA analysis code. Please see the

LS-DYNA documentation and comments in the LsDyna3dExecute script for details of how to configure

this script.

Chapter 2: Building A Model


2 Building A Model

� Introduction to Building a Model 12

� Coordinate Frames 18

� Finite Elements 19

� Material Library 30

� Element Properties 62

� Loads and Boundary Conditions 91

� Loads and Boundary Conditions Form 92

� Load Cases 110

Patran Interface to LS-DYNA Preference GuideIntroduction to Building a Model

12

Introduction to Building a Model

There are many aspects to building a finite element analysis model. In several cases, the forms used to

create the finite element data are dependent on the selected analysis code and analysis type. Other parts

of the model are created using standard forms.

Under Preferences on the Patran main form, is a selection for Analysis that defines the intended analysis

code to be used for this model.

The analysis code may be changed at any time during model creation.This is especially useful if the

model is to be used for different analyses, in different analysis codes. As much data as possible will be

converted if the analysis code is changed after the modeling process has begun. The analysis option

defines what will be presented to the user in several areas during the subsequent modeling steps.

These areas include the material and element libraries, including multi-point constraints, the applicable

loads and boundary conditions, and the analysis forms. The selected Analysis Type may also affect the

allowable selections in these same areas. For more details, see The Analysis Form (p. 8) in the

MSC.Patran Reference Manual.

13Chapter 2: Building A ModelIntroduction to Building a Model

Table 2-1 summarizes the various LS-DYNA commands supported by the Patran LS-DYNA Preference.

Table 2-1 Supported LS-DYNA Entities

CATEGORY KEYWORD

BOUNDARY *BOUNDARY_SPC_SET

*BOUNDARY_CYCLIC

*BOUNDARY_PRESCRIBED_MOTION_SET

*BOUNDARY_PRESCRIBED_MOTION_NODE

CONSTRAINED *CONSTRAINED_EXTRA_NODES_SET

*CONSTRAINED_GENERALIZED_WELD

*CONSTRAINED_GENERALIZED_BUTT

*CONSTRAINED_GENERALIZED_FILLET

*CONSTRAINED_GENERALIZED_SPOT

*CONSTRAINED_JOINT_SPHERICAL

*CONSTRAINED_JOINT_REVOLUTE

*CONSTRAINED_JOINT_CYLINDRICAL

*CONSTRAINED_JOINT_PLANAL

*CONSTRAINED_JOINT_UNIVERSAL

*CONSTRAINED_JOINT_TRANSLATIONAL

*CONSTRAINED_LINEAR

*CONSTRAINED_NODAL_RIGID_BODY

*CONSTRAINED_NODAL_RIGID_BODY_INERTIA

*CONSTRAINED_RIVET

*CONSTRAINED_SHELL_TO_SOLID

*CONSTRAINED_SPOTWELD

*CONSTRAINED_TIE-BREAK

*CONSTRAINED_TIED_NODES_FAILURE


14

CONTACT *CONTACT_AUTOMATIC_ONE_WAY_SURFACE_TO_SURFACE

*CONTACT_AUTOMATIC_SINGLE_SURFACE

*CONTACT_AUTOMATIC_ SURFACE_TO_SURFACE

*CONTACT_CONSTRAINT_NODES_TO_SURFACE

*CONTACT_CONSTRAINT_SURFACE_TO_SURFACE

*CONTACT_NODES_TO_SURFACE

*CONTACT_ONE_WAY_SURFACE_TO_SURFACE

*CONTACT_RIGID_BODY_ONE_WAY_TO_RIGID_BODY

*CONTACT_RIGID_BODY_TWO_WAY_TO_RIGID_BODY

*CONTACT_RIGID_NODES_TO_RIGID_BODY

*CONTACT_SINGLE _SURFACE

*CONTACT_SLIDNG_ONLY

*CONTACT_SLIDING_ONLY_PENALTY

*CONTACT_SURFACE_TO_SURFACE

*CONTACT_TIEBREAK_NODES_TO_SURFACE

*CONTACT_TIEBREAK_SURFACE_TO_SURFACE

*CONTACT_TIED_NODES_TO_SURFACE

*CONTACT_TIED_SURFACE_TO_SURFACE

CONTROL *CONTROL_BULK-VISCOSITY

*CONTROL_CPU

*CONTROL_CONTACT

*CONTROL_COUPLING

*CONTROL_DYNAMIC_RELAXATION

*CONTROL_ENERGY

*CONTROL_HOURGLASS

*CONTROL_OUTPUT

*CONTROL_SHELL

*CONTROL_TERMINATION

*CONTROL_TIMESTEP

DAMPING *DAMPING_GLOBAL

*DAMPING_PART_MASS

*DAMPING_PART_STIFFNESS

DATABASE *DATABASE_BINARY_D3PLOT

*DATABASE_BINARY_D3THDT

*DATABASE_BINARY_XTFILE

*DATABASE_EXTENT_BINARY

*DATABASE_HISTORY_NODE

*DATABASE_HISTORY_BEAM

*DATABASE_HISTORY_SHELL

*DATABASE_HISTORY_SOLID

*DATABASE_HISTORY_TSHELL


CATEGORY KEYWORD


DEFINE *DEFINE_COORDINATE_SYSTEM

*DEFINE_CURVE

*DEFINE_SD_ORIENTATION

ELEMENT *ELEMENT_BEAM

*ELEMENT_DISCRETE

*ELEMENT_MASS

*ELEMENT_SHELL_THICKNESS

*ELEMENT_SOLID_ORTHO

*ELEMENT_TSHELL

INITIAL *INITIAL_MOMENTUM

*INITIAL_VELOCITY

*INITIAL_VELOCITY_NODE

LOAD *LOAD_BEAM_OPTION

*LOAD_BODY_GENERALIZED

*LOAD_NODE_OPTION

*LOAD_SEGMENT

*LOAD_SHELL _OPTION

*LOAD_THERMAL_CONSTANT

*LOAD_THERMAL_CONSTANT_NODE

*LOAD_THERMAL_VARIABLE

*LOAD_THERMAL_VARIABLE_NODE


CATEGORY KEYWORD


16

MAT *MAT_ELASTIC_OPTION

*MAT_PLASTIC_KINEMATIC

*MAT_VISCOELASTIC

*MAT_BLATZ-KO_RUBBER

*MAT_ISOTROPIC_ELASTIC_PLASTIC

*MAT_SOIL_AND_FOAM

*MAT_JOHNSON_COOK

*MAT_STRAIN_RATE_DEPENDENT_PLASTICITY

*MAT_RIGID

*MAT_COMPOSITE_DAMAGE

*MAT_ENHANCED_COMPOSITE_DAMAGE

*MAT_PIECEWISE_LINEAR_PLASTICITY

*MAT_HONEYCOMB

*MAT_MOONEY-RIVLIN_RUBBER

*MAT_RESULTANT_PLASTICITY

*MAT_CLOSED_FORM_SHELL_PLASTICITY

*MAT_FRAZER_NASH_RUBBER_MODEL

*MAT_LAMINATED_GLASS

*MAT_LOW_DENSITY_FOAM

*MAT_COMPOSITE_FAILURE_MODEL

*MAT_VISCOUS_FOAM

*MAT_CRUSHABLE_FOAM

*MAT_RATE_SENSITIVE_POWERLAW_PLASTICITY

*MAT_LINEAR_ELASTIC_DISCRETE_BEAM

*MAT_NONLINEAR_ELASTIC_DISCRETE_BEAM

*MAT_NONLINEAR_PLASTIC_DISCRETE_BEAM

*MAT_SID_DAMPER_DISCRETE_BEAM

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

NODE Gklab

PART Gm̂ oq|lmqflk

RIGIDWALL Gofdfatîi|dbljbqof`|pbsboî=lmqflkp

Gofdfatîi|mi^kô|pbsboî=lmqflkp


CATEGORY KEYWORD

Patran Interface to LS-DYNA Preference GuideCoordinate Frames

18

Coordinate Frames

Coordinate frames will generate unique *DEFINE_COORDINATE_SYSTEM entries.

Only Coordinate Frames which are referenced by nodes, element properties, or loads and boundary

conditions can be translated. For more information on creating coordinate frames see Creating

Coordinate Frames (p. 393) in the Geometry Modeling - Reference Manual Part 2.

19Chapter 2: Building A ModelFinite Elements

Finite Elements

Finite Elements in Patran allows the definition of basic finite element construction. Created under Finite

Elements are the=åçÇÉë, element topology, and multi-point constraints.

For more information on how to create finite element meshes, see Mesh Seed and Mesh Forms (p. 25)

in the Reference Manual - Part III.

Patran Interface to LS-DYNA Preference GuideFinite Elements

20

Nodes

Nodes in Patran will generate unique *NODE entries. Nodes can be created either directly using the Node

object, or indirectly using the Mesh object.


Elements

Finite Elements in Patran assigns element connectivity, such as Quad/4, for standard finite elements. The

type of LS-DYNA element created is not determined until the element properties are assigned. See the

Element Properties Form for details concerning the LS-DYNA element types. Elements can be created

either directly using the Element object or indirectly using the Mesh object.


22

Multi-Point Constraints

Multi-point constraints (MPCs) can also be created from the Finite Elements menu. These elements

define a rigorous behavior between several specified nodes. The forms for creating MPCs are found by

selecting MPC as the Object on the Finite Elements form. The full functionality of the MPC forms are

defined in Create Action (Mesh) (p. 11) in the Reference Manual - Part III.


MPC Types

To create an MPC, first select the type of MPC to be created from the option menu. The MPC types that

appear in the option menu are dependent on the current settings of the Analysis Code and Analysis Type

preferences. The following table describes the MPC types which are supported for LS-DYNA.

Note that the LS-DYNA definition of joints requires the definition of coincident pairs of nodes.

Coincidence is not required of the Patran model. The mean position will be calculated during translation.

Note that some of the LS-DYNA *CONSTRAINED entries are supported as LBC’s rather than MPC’s.

This is generally because they require more data than can be entered for an MPC or for the sake of

consistency with other analysis preferences.

Degrees-of-Freedom

Whenever a list of degrees-of-freedom is expected for an MPC term, a listbox containing the valid

degrees-of-freedom is displayed on the form. A degree-of-freedom is valid if:

1. It is valid for the current Analysis Code Preference.

2. It is valid for the current Analysis Type Preference.

3. It is valid for the selected MPC type.

MPC Type Analysis Type Description

Tied Shell to Solid Structural Defines a tie between a shell edge and solid elements.

Rivet Structural Defines pairs of nodes representing a rivet connection.

Cyclic

Symmetry

Structural Describes cyclic symmetry boundary conditions for a

segment of the model.

Explicit Structural Creates a constraint equation between one degree of

freedom of one node and selected degrees of freedom of

other nodes.

Spherical Joint Structural Creates a spherical joint between two rigid bodies.

Revolute Joint Structural Creates a revolute joint between two rigid bodies.

Cylindrical Joint Structural Creates a cylindrical joint between two rigid bodies.

Planar Joint Structural Creates a planar joint between two rigid bodies.

Universal Joint Structural Creates a universal joint between two rigid bodies.

Translational Joint Structural Creates a translational joint between two rigid bodies.

Extra Nodes Structural Defines extra nodes for a rigid body. These are mainly used

in conjunction with joint definition.


24

In most cases, all degrees-of-freedom, which are valid for the current Analysis Code and Analysis Type

Preferences, are valid for the MPC type. The following degrees-of-freedom are supported for the various

analysis types:

Tied Shell to Solid

This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements

form, and the tied shell to solid type is selected. This form is used to create a

*CONSTRAINED_SHELL_TO_SOLID entry. Note that a shell node may be tied to up to 9 brick

nodes lying along a tangent vector to the nodal fiber. Nodes can move relative to each other in the fiber

direction only.

Degree-of-freedom Analysis Type

UX Structural

UY Structural

UZ Structural

RX Structural

RY Structural

RZ Structural

Note: Care must be taken to make sure that a degree-of-freedom that is selected for an MPC

actually exists at the nodes. For example, a node that is attached only to solid structural

elements will not have any rotational degrees-of-freedom. However, Patran will allow you

to select rotational degrees-of-freedom at this node when defining an MPC.


26

Rivet


form, and the Rivet type is selected. This form is used to create one or more *CONSTRAINED_RIVET

entries. Note that nodes connected by a rivet cannot be members of another constraint set that constrains

the same degree of freedom, a tied interface, or a rigid body.


Explicit


form, and Explicit is the selected type. This form is used to create a *CONSTRAINED_LINEAR entry.

This MPC type is used to define a linear constraint equation.


28

Joint MPCs


form, and one of the joint types is selected. This form is used to create a

*CONSTRAINED_JOINT_TRANSLATIONAL entry. The Relative Penalty Stiffness for this entry is

defined on the main MPC form. The form will differ slightly for the 6 joint types. The spherical type

requires only one dependent and one independent node. The translational joint requires 3 dependent and

3 independent nodes, and the other joint types require 2 dependent and 2 independent nodes.


Extra Nodes MPCs


form, and the Extra Nodes type is selected. This form is used to create a

*CONSTRAINED_EXTRA_NODES_OPTION NODE/SET entry. This is the standard Rigid (Fixed)

MPC type of Patran.

Patran Interface to LS-DYNA Preference GuideMaterial Library

30

Material Library

The Materials form will appear when the Material toggle, located on the Patran application selections, is

chosen. The selections made on the Materials menu will determine which material form appears, and

ultimately, which LS-DYNA material will be created.

The following pages give an introduction to the Materials form, and details of all the material property

definitions supported by the Patran LS-DYNA preference.

Only material records which are referenced by an element property region or by a laminate lay-up will

be translated. References to externally defined materials will result in special comments in the LS-DYNA

input file, with material data copied from user identified files. This reference allows a user not only to

insert material types that are not supported directly by the LS-DYNA preference, but also to make use of

a standard library of materials.

31Chapter 2: Building A ModelMaterial Library

Materials Form

This form appears when Materials is selected on the main menu. The Materials form is used to provide

options to create the various LS-DYNA materials.


32

The following table outlines the options when Create is the selected Action.

Isotropic

Linear Elastic

This subordinate form appears when the Input Properties button is selected on the Materials form when

Isotropic is the selected Object, and when Linear Elastic is the selected Constitutive Model on the Input

Options form.

Object Option 1 Option 2

Isotropic • Linear Elastic • Linear Elastic (MAT 1)

• Elastoplastic • Plastic Kinematic (MAT 3)

• Iso. Elasto Plastic (MAT 12)

• Strain Rate Dependent (MAT 19)

• Piecewise Linear (MAT 24)

• Rate Sensitive (MAT 64)

• Resultant (MAT 28)

• Closed Form (MAT 30)

• Viscoelastic • Viscoelastic (MAT 6)

• Rigid • Material Type 20

• Johnson Cook • Material Type 15

• Rubber • Frazer Nash (MAT 31)

• Blatz-Ko (MAT 7)

• Mooney Rivlin (MAT 27)

• Foam • Soil and Foam (MAT 5/14)

• Viscous Foam (MAT 62)

• Crushable Foam (MAT 63)

• Low Density Urethane (MAT 57)

2D Orthotropic • Glass (laminated) • Laminate Glass (MAT 32)

3D Orthotropic • Honeycomb • Composite Honeycomb (MAT 26)

• Composite • Composite Damage (MAT 22)

• Composite Failure (MAT 59)

Composite • Laminate

Option 1 Option 2 Option 3

Linear Elastic Linear Elastic (MAT1) Solid

Fluid


Use this form to define the data for LS-DYNA Material Type 1 (*MAT_ELASTIC). If the “Material” is

set as “Fluid” the parameters required are: Density, Bulk Modulus, Viscosity Coefficient, and

Cavitation Pressure.

Elastoplastic

This subordinate form appears when the Input Properties button is selected on the Materials form, when

Isotropic is the selected object, Elastoplastic is the selected Constitutive Model, and the following is the

selected Implementation.

Option 1 Option 2

Elastoplastic Plastic Kinematic (MAT 3)


34

Use this form to define the data for LS-DYNA Material Type 3 (*MAT_PLASTIC_KINEMATIC).

Elastoplastic




Option 1 Option 2

Elastoplastic Isotropic Elastic Plastic


Use this form to define the data for LS-DYNA Material Type 12

(*MAT_ISOTROPIC_ELASTIC_PLASTIC).


36

Elastoplastic





(*MAT_STRAIN_RATE_DEPENDENT_PLASTICITY).

Option 1 Option 2

Elastoplastic Strain Rate Dependent Plasticity


Elastoplastic


Isotropic is the selected object, and one of the following combinations is selected.

Use the form on the next page to define the data for LS-DYNA Material Type 24

(*MAT_PIECEWISE_LINEAR_PLASTICITY). The contents of the form will vary depending upon

which option is selected. If the bilinear option is selected then the tangent modulus is required. The

linearized option requires definition of a strain dependent field. If the General rate model is selected

instead of the Cowper Symonds model then the Yield Stress is defined as a strain rate dependent field.

Option 1 Option 2 Option 3 Option 4

Elastoplastic Piecewise Linear Plasticity Bilinear Cowper Symonds Rate Model

General Rate Model

Linearized Cowper Symonds Rate Model

General Rate Model


38


Elastoplastic





(*MAT_RATE_SENSITIVE_POWERLAW_PLASTICITY).

Option 1 Option 2

Elastoplastic Rate Sensitive Power Law


40

Elastoplastic




Use this form to define the data for LS-DYNA Material Type 28 (*MAT_RESULTANT_PLASTICITY).

Option 1 Option 2

Elastoplastic Resultant


Elastoplastic




Option 1 Option 2

Elastoplastic Closed Form Shell


42


(*MAT_CLOSED_FORM_SHELL_PLASTICITY).


Viscoelastic

This subordinate form appears when the Input Properties button is selected on the Materials form,

Isotropic is the selected Object, and the Viscoelastic Constitutive model is selected. Use this form to

define the data for LS-DYNA Material Type 6 (*MAT_VISCOELASTIC).


44

Rigid


Isotropic is the selected Object, and the Rigid Constitutive model is selected. Use this form to define the

data for LS-DYNA Material Type 20 (*MAT_RIGID).


Johnson Cook


Isotropic is the selected Object, and one of the following combinations is selected.


Johnson Cook Material Type 15 No Iterations Minimum Pressure

No tension, Minimum Stress

No tension, Minimum Pressure

Accurate Minimum Pressure

No tension, Minimum Stress

No tension, Minimum Pressure


46


(*MAT_JOHNSON_COOK). The contents of the form do not vary.

Additional data for this form are: Effective Plastic Strain rate, Specific Heat, Failure Stress/Pressure, and

5 Failure Parameters.


Rubber


Isotropic is the selected Object, Rubber is the selected Constitutive Model, and the following is the


Use this form to define the data for LS-DYNA Material Type 7 (*MAT_BLATZ-KO_RUBBER).

Option 1 Option 2

Rubber Blatz-Ko


48

Rubber


Isotropic is the selected Object, Rubber is the selected Constitutive Model, and the following is the



(*MAT_MOONEY_RIVLIN_RUBBER).


Rubber Mooney Rivlin Coefficients

Least Square


Rubber


Isotropic is the selected Object, Rubber is the selected Constitutive Model, and one of the following

combinations is selected.


(*MAT_FRAZER_NASH_RUBBER_MODEL). The contents of the form varies depending on the

option selected for defining the material response. If the model is defined as least squares fit then

specimen data and a field defining force versus change in gauge length are required instead of the

coefficients that appear on the form below. Note that a strain field must be defined, although this is

interpreted by the translator as force versus actual change in the gauge length. If the strain limits are to

be ignored then maximum and minimum strain limits are not required.


Rubber Frazer-Nash Coefficients Respect

Ignore

Least Squares Fit Respect

Ignore


50


Foam


Isotropic is the selected Object, Foam is the selected Constitutive Model, and one of the following



(*MAT_LOW_DENSITY_FOAM). The contents of the form does not vary.


Foam Low Density Urethane Bulk Viscosity Inactive No Tension

Maintain Tension

Bulk Viscosity Active No Tension

Maintain Tension


52


Foam


Isotropic is the selected Object, Foam is the selected Constitutive Model, and the following is the selected

Implementation.

Use this form to define the data for LS-DYNA Material Type 62 (*MAT_VISCOUS_FOAM).

Option 1 Option 2

Foam Viscous Foam


54

Foam


Isotropic is the selected Object, Foam is the selected Constitutive Model, and the following is the selected

Implementation.

Use this form to define the data for LS-DYNA Material Type 63 (*MAT_CRUSHABLE_FOAM).

Option 1 Option 2

Foam Crushable


Foam


Isotropic is the selected Object, Foam is the selected Constitutive Model, and one of the following



(*MAT_SOIL_AND_FOAM) or Material Type 14 (*MAT_SOIL_AND_FOAM_FAILURE). Choice

between the Type 5 and Type 14 is solely on the basis of whether failure is permitted when pressure meets

the failure pressure.


Foam Soil and Foam Inactive

Inactive

Active

Active

Allow Crushing

Reversible

Allow Crushing

Reversible


56

2D Orthotropic

Laminated Glass

This subordinate form appears when the Input Properties button is selected on the Materials form, 2D

Orthotropic is the Selected Object, and when Laminated Glass is the selected Constitutive Model on the

Input Options form. Use this form to define the data for LS-DYNA Material Type 32

(*MAT_LAMINATED_GLASS).


3D Orthotropic

Honeycomb


3D Orthotropic is selected on the Material form, and when the Honeycomb Constitutive model is


58

selected. Use this form to define the data for LS-DYNA Material Type 26 (*MAT_HONEYCOMB).


Composite


3D Orthotropic is the selected Object, Composite is the Selected Constitutive Model, and the following

is the selected Implementation.

Use the subordinate form on the following page to define the data for LS-DYNA Material Type 22

(*MAT_COMPOSITE_DAMAGE).

Option 1 Option 2

Composite Damage


60

Composite Failure

This subordinate form appears when the Input Properties button is selected on the Materials form, 3D

Orthotropic is the selected Object, Composite is the Selected Constitutive Model, and the following is

the selected Implementation.


Composite Failure Ellipsoidal

Faceted


Use the subordinate form on the following page to define the data for LS-DYNA Material Type 58

(*MAT_COMPOSITE_FAILURE_MODEL).

Patran Interface to LS-DYNA Preference GuideElement Properties

62

Element Properties

The Element Properties form appears when the Properties toggle, located on the Patran main form, is

chosen.There are several option menus available when creating element properties. The selections made

on the Element Properties menu will determine which element property form appears, and ultimately,

which LS-DYNA element will be created.

The following pages give an introduction to the Element Properties form, and details of all the element

property definitions supported by the Patran LS-DYNA Preference.

Element Properties Form

This form appears when Properties is selected on the main menu. There are four option menus on this

form, each will determine which LS-DYNA element type will be created and which property forms will

appear. The individual property forms are documented later in this section. For a full description of this

form, see Element Properties Forms (p. 67) in the Patran Reference Manual.

63Chapter 2: Building A ModelElement Properties


64

The following table outlines the option menus when Analysis Type is set to Structural.

Object Type Option 1 Option 2

0D • Mass

• Grounded Spring Linear

Non-Linear

Elastoplastic

General Non-Linear

Viscoelastic

Inelastic

• Grounded Damper Linear

Non-Linear

1D • Beam General Section

Dimensioned Section

• Rod

• Spring Linear Scalar

Follower

Non-linear Scalar

Follower

Elastoplastic Scalar

Follower

General Non-Linear Scalar

Follower

Viscoelastic Scalar

Follower

Inelastic Scalar

Follower

• Damper Linear Scalar

Follower

Non-Linear Scalar

Follower

Side Impact

• Discrete beam Linear

Non-Linear

Non-Linear Plastic

• Weld Spot Standard

General

• Fillet


Mass

This subordinate form appears when the Input Properties button is selected on the Element Properties

form when the following options are chosen.

• Butt

• Integrated Beam Rectangular Hughes Liu

Belytschko Schwer

Tubular Hughes Liu

Belytschko Schwer

• Part Inertia 1D General Section

Dimensioned Beam

2D • Shell Homogeneous Hughes Liu

Belytschko Tsay

BCIZ Tri Shell

Co Tri

S/R Hughes Liu

S/R Co-rotational

Belytschko Levialthan

Bely Wong Chiang

Fast Hughes Liu

Laminate Hughes Liu

S/R Hughes Liu

Fast Hughes Liu

Default

• Membrane Bely T Membrane

Fully Integrated

• Part Inertia 2D

3D • Solid Constant Stress

S/R 8 Node

Quadratic 8 Node

S/R Tetrahedron

• Thick Shell 1 Point

2 x 2 point

• Part Inertia 3D

Action Dimension Type Topologies

Create 0D Mass Point

Object Type Option 1 Option 2


66

Use this form to create an *ELEMENT_MASS entry. This defines a lumped mass element of the

structural model.

Grounded Spring



Use this form to create a *ELEMENT_DISCRETE entry and one of the *MAT_SPRING_type and

*SECTION_DISCRETE data entries. This defines a scalar spring element of the structural model. Only

one node is used in this method. The other node is defined to be grounded. The data on this form will

vary upon the spring type.

Action Dimension Type Option(s) Topologies

Create 0D Grounded Spring Linear, Non-Linear, Elastoplastic,

General Non-Linear, Viscoelastic,

Inelastic

Point/1


Grounded Damper



Use this form to create an *ELEMENT_DISCRETE entry=and one of the *MAT_DAMPER_type and

*SECTION_DISCRETE data entries. This defines a scalar damper element of the structural model. Only

one node is used in this method. The other node is defined to be grounded.The data on this form will vary

upon the damper type.


Create 0D Grounded Damper Linear/Non-Linear Point/1


68

Beam (General Section)



Use this form to create an *ELEMENT_BEAM entry together with its associated *SECTION_BEAM

and *INTEGRATION_BEAM data entry. This defines a simple beam element of the structural model.

Action Dimension Type Option(s) Option 2 Topologies

Create 1D Beam General Section Bar/2


This is a list of Input Properties, available for creating a resultant beam that were not shown on the

previous page. Use the menu scroll bar on the input properties form to view these properties.

Beam (Dimensioned Section - Hughes-Liu)



Property Name Description

Axial Damping Defines the axial damping factor. This property is optional.

Mass Damping Defines the mass damping factor. This property is optional.

Stiffness Damping Defines the stiffness damping factor. This property is optional.

Bending Damping Defines the bending damping factor. This property is optional.


Create 1D Beam Dimensioned Section Hughes -Liu Bar/2


70









Beam (Dimensioned Section - Belytschko-Schwer)






Create 1D Beam Dimensioned Section Belytschko Schwer Bar/2


72



Rod



Use this form to create *ELEMENT_BEAM and *SECTION_BEAM data entries. This defines a

tension-compression-torsion element of the structural model.


Axial Damping Defines the axial damping factor. This property is optional.



Bending Damping Defines the bending damping factor. This property is optional.


Create 1D Rod Bar/2


Scalar Spring



Use this form to create an *ELEMENT_DISCRETE entry and one of the *MAT_SPRING_type and

*SECTION_DISCRETE data entries. This defines a scalar spring element of the structural model. The

data on this form will vary upon the spring type. Additional parameters are available to define the

dynamic values based on static data.

Action Dimension Type Option 1 Option 2 Topologies

Create 1D Spring Linear, Non-Linear, Elastopastic,

General Non-Linear, Viscoelastic,

Inelastic

Scalar, Bar/2


74

Scalar Damper




Create 1D Damper Linear, Non-Linear Scalar Bar/2


Use this form to create an *ELEMENT_DISCRETE entry and one of the *MAT_DAMPER_type and

*SECTION_DISCRETE data entries. This defines a scalar damper element of the structural model. The

data on this form will vary upon the damper type.

Follower Damper




Create 1D Damper Linear, Non-Linear Follower Bar/2


76

Use this form to create an *ELEMENT_DISCRETE entry and one of the *MAT_DAMPER_type and

*SECTION_DISCRETE data entries. This defines a follower damper element of the structural model.

The data on this form will vary upon the damper type.

Side Impact Damper



Use this form to create an *ELEMENT_BEAM entry and *MAT_SID_DAMPER_DISCRETE_BEAM

and *SECTION_BEAM data entries. This defines a side impact damper element of the structural model.

Additional properties required to fully define the damper behavior are input by scrolling down the form.

Action Dimension Type Option Topologies

Create 1D Damper Side Impact Bar/2


Discrete Beam



Use this form to create an *ELEMENT_BEAM entry together with its associated

*MAT_type_DISCRETE_BEAM and *SECTION_BEAM data entries. This defines a simple beam

element of the structural model. The data on this form will vary upon the beam type.


Create 1D Discrete Beam Linear, Non-Linear, Non-Linear Plastic Bar/2


78

Spot Weld



Use this form to create a *CONSTRAINED_SPOTWELD or

*CONSTRAINED_GENERALIZED_WELD_SPOT entry. This defines a spot weld connecting two

nodes of the model. The data on this form will vary upon the weld type.


Create 1D Weld Spot Standard/General Bar/2


Fillet Weld



Use this form to create a *CONSTRAINED_GENERALIZED_WELD_FILLET entry. This defines a

fillet weld between two parts of the model.


Create 1D Weld Fillet Bar/2


80

This is a list of Input Properties available for creating a Fillet Weld that were not shown on the previous

page. Use the scroll bar on the Input properties form to view these properties.


Width of Flange, w Define width of flange. This property is required.

Width of Weld, a Define width of fillet weld. This property is required.

Weld Angle, Alpha Define the weld angel, Alpha. This property is required.


Butt Weld



Use this form to create a *CONSTRAINED_GENERALIZED_WELD_BUTT entry. This defines a butt

weld between two parts of the model.


Create 1D Weld Butt Bar/2


82

Integrated Beam



Use this form to create an *ELEMENT_BEAM together with its associated *SECTION_BEAM and

*INTEGRATION_BEAM data entries. This defines a simple beam element of the structural model. The

data entry will vary upon the formulation option.


Create 1D Integrated Beam Rectangular,

Tubular

Belytschko Schwer,

Hughes -Liu

Bar/2


Part Inertia 1D







Create 1D Part Inertia 1D Bar/2


84

Shell



Use this form to create an *ELEMENT_SHELL_OPTION entry together with the associated

*SECTION_SHELL entry. The data varies upon the type of element formulation.

Action Dimension Type Option Formulation Topologies

Create 2D Shell Homogeneous Hughes Liu, Belytschko-Tsay,

BCIZ Tri Shell, Co-Tri, S/R

Hughes Lui, S/R Co_rotational,

Belytschko Levialthan, Bely

Wong Chiang, Fast Hughes Liu.

Tri/3, Quad/4

Laminate Hughes Liu, S/R Hughes Liu,

Fast Hughes Liu, Default.


Membrane



Use this form to create an *ELEMENT_SHELL_OPTION entry together with the associated

*SECTION_SHELL entry.


Create 2D Membrane Bely T Membrane,

Fully Integrated

Tria/3, Quad/4


86

Part Inertia 2D









Solid



Use this form to create an *ELEMENT_SOLID entry together with the associated *SECTION_SOLID

entry.

Action Dimension Type Option 1 Topologies

Create 3D Solid Constant Stress, S/R 8 Node, Quadratic

8 Node, S/R Tetrahedron

Hex/8


88

Thick Shell



Use this form to create an *ELEMENT_TSHELL entry together with the associated

*SECTION_TSHELL entry.

Action Dimension Type Option 1 Topologies

Create 3D Thick Shell 1 Point

2x2 Point

Hex/8


Part Inertia 3D



Note: The correct node numbering is essential for correct use. To ensure proper orientation,

extreme care must be used in defining the connectivity. (See the LS-DYNA User’s Manual

for further details.)




90




91Chapter 2: Building A ModelLoads and Boundary Conditions

Loads and Boundary Conditions

The Loads and Boundary Conditions form will appear when the Loads/BCs toggle, located on the Patran

application selections, is chosen. When creating a loads and boundary conditions there are several option

menus. The selections made on the Loads and Boundary Conditions menu will determine which loads

and boundary conditions form appears, and ultimately, which LS-DYNA loads and boundary conditions

will be created.

The following pages give an introduction to the Loads and Boundary Conditions form, and details of all

the loads and boundary conditions supported by the Patran LS-DYNA Analysis Preference.

Patran Interface to LS-DYNA Preference GuideLoads and Boundary Conditions Form

92

Loads and Boundary Conditions Form

This form appears when Loads/BCs is selected on the main form. The Loads and Boundary Conditions

form is used to provide options to create the various LS-DYNA loads and boundary conditions. For a

definition of full functionality, see Loads and Boundary Conditions Form (p. 27) in the Patran Reference

Manual.

93Chapter 2: Building A ModelLoads and Boundary Conditions Form

The following table outlines the options when Create is the selected action.

Static (Not Time Varying)

This subordinate form appears when the Input Data button is selected on the Loads and Boundary

Conditions form when the Current Load Case Type is Static. The Current Load Case Type is set on the

Load Case form, for more information see Loads and Boundary Conditions Form. The information on the

Input Data form will vary depending on the selected Object. Defined below is the standard information

found on this form. Note that this form is not used with the LS-DYNA Preference.

Object Type

Displacement Nodal

Force Nodal

Pressure Element Uniform

Temperature Nodal

Initial Velocity Nodal

Velocity Nodal

Acceleration Nodal

Initial Momentum Element Uniform

Contact Element Uniform

Geometric Rigid Wall Nodal

Planar Rigid Wall Nodal

Tied Shells Element Uniform

Tied Shell Edges Element Uniform

Nodal Rigid Body Nodal

Nodal Inertial Load Nodal


94

Transient (Time Varying)

This subordinate form appears when the Input Data button is selected on the Loads and Boundary

Condition form when the Current Load Case Type is Time Dependent. The Current Load Case Type is

set on the Load Case form, for more information see Loads and Boundary Conditions Form and Load

Cases. The information on the Input Data form will vary, depending on the selected Object. Defined

below is the standard information found on this form.


Contact Toolkit

Introduction

This section describes the user interface provided by Patran to access the contact features of explicit

dynamics finite element codes. This interface is used during definition of the Contact LBC types: Self

Contact, Master/Slave Surface, Master/Slave Node, and Subsurface.


96

Tools have been provided to enable the user to quickly and easily define contact conditions. Specification

of contact is conceptually simple, involving either one or two contact surfaces, and a set of contact

parameters which control the interaction of the surfaces.

Contact Types

A contact condition in which a single logical surface may come into contact only with itself is described

as self-contact, and requires the specification of a single Application Region. A contact condition in

which two logical surfaces may contact each other is described as Master/Slave contact, and requires

specification of two Application Regions. Master/Slave contact is further subdivided by the definition of

Master/Slave Surface and Master/Slave Node. Master/Slave Surface describes the condition in which

both the master and slave surfaces are described using element faces, whereas Master/Slave Node

describes the condition in which the Slave surface is described using only nodes.

Contact Construction

Tools are provided to enable the construction of contact surfaces, using the standard Patran select tool

mechanisms (2D elements, 3D element faces), or groups. Contact subsurfaces can also be constructed

using these tools, and later used to define a complete logical contact surface. This functionality allows

the user to use the select tool to specify application regions on Patran geometry or the associated FEM

entities or to define a more complex contact surface that is assembled from a mixture of 2D and 3D

element faces, and to simply combine groups of 2D elements taking into account the direction of the

contact outward normal. (For 2D elements, the outward normal can be reversed for contact purposes

without modifying the underlying element topology.) Use of the group select mechanism is restricted to

FEM entities only. Visualization of the specified contact condition is provided by graphically previewing

but is not currently supported for geometry entities.

“Simple” contact surfaces include surfaces which may be described entirely by the faces of 3D elements,

or by 2D elements whose outward normals are aligned with the desired contact normal direction. These

contact surfaces may be constructed entirely using a single select mechanism (either Select Tool or Group

method). Simple contact surfaces may not include a mixture of 3D element faces and 2D elements, or 2D

elements whose outward normals are not all aligned with the desired contact normal direction.

“Complex” contact surfaces are defined as those surfaces which consist of a mixture of 2D elements and

3D element faces, or all 2D elements but with some of the outward normal incorrectly aligned. Contact

conditions which include complex contact surfaces must be constructed using “Subsurfaces,” where each

subsurfaces is a “Simple” contact surface. Definition of contact surfaces is limited to one method; i.e., it

is not permissible to mix “Select Tool,” “Group,” or “Subsurface” within the definition of a contact

surface.

The following section describes how each of the contact surface creation methods is used to describe a

simple contact surface.

Use of the Select Tool

The select tool is use to graphically select the desired entities from the model. When this method is

selected, the user must specify which dimensionality the intended object has, i.e. 3D, 2D or Nodal. If the

selected dimensionality is 2D, then the user can further specify whether the top, bottom or both surfaces


are required. Selection of top will result in a contact surface whose outward normal is coincident with the

element outward, whereas selection of bottom will result in a contact surface whose outward normal is

in the opposite direction to the element outward normal. The user can toggle between Top, Bottom or

Both at any time during selection, however all of the selected entities will be assigned the same logical

direction. Selection of 3D allows the user to select either all or all free faces of 3D elements. No user

specification of the contact normal direction is required for 3D elements since the program automatically

specifies this direction. No contact direction is applicable to Nodal contact surfaces.

It is not permissible to mix 3D, 2D and Nodal entities within a single Application Region. (This

functionality is provided through the use of contact subsurfaces). The select tool can be used to select on

the basis of either FEM or Geometry entities.

Use of the Group Tool

The Group tool is used to define simple contact surfaces on the basis of Patran group names. When this

method is selected, the user must specify which dimensionality the intended object has, i.e. either 3D, 2D

or Nodal. The entities which will be selected for use in the contact surface in this case are either all 3D

free surfaces in the group, all 2D elements or all nodes contained in the selected group. In the case of 2D

elements, the user may specify whether the contact normal direction is coincident with the element top,

bottom or both faces. Multiple groups may be selected. However, it should be noted that both the selected

element dimensionality and contact normal direction apply across all selected groups.

Use of the Subsurface Tool

Contact Subsurfaces may be defined using either of the above methods. Subsurfaces may then be used in

the specification of Master, Slave or Self contact surfaces. When this option is used, the user may not

specify element dimensionality or contact normal direction since this information has already been

defined during subsurface definition. As many sub-surfaces as required may be selected to form the

desired complex contact subsurface.

Contact: Application Region

This form is used to define contact surfaces. The form will vary depending upon which options are

selected, however two basic configurations are used depending on whether the contact condition requires

specification of a single contact surface or two contact surfaces.


98

Single Application Region

The following form is used to define a single surface contact or a subsurface.


Dual Application Region

The following form is used to define either of the master-slave contact types.


100

Contact: Input Data

The Input Data form is used to specify parameters which control the behavior of the contact condition.

The contents of the form will vary depending upon which option is selected. No Input Data is required

for the Subsurface option since subsurfaces do not constitute a contact condition on their own.

Object Tables

There are areas on the static and transient input data forms where the load data values are defined. The

data fields which appear depend on the selected load Object and Type. In some cases, the data fields also

depend on the selected Target Element Type. The following Object Tables outline and define the various

input data that pertains to a specific selected object:


Displacement

If the displacement/rotational component is zero, it will result in generation of a

*BOUNDARY_SPC_OPTION NODE/SET entry, which defines translational and rotational constraints

in the prescribed coordinate system. If the values are non-zero then this will result in generation of a

*BOUNDARY_PRESCRIBED_MOTION_OPTION NODE/SET entry.

Force

This defines a *LOAD_NODE_OPTION POINT/SET entry. For transient load cases an auxiliary

*DEFINE_CURVE entry is defined from the time dependent field selected.

Pressure

Creates a *LOAD_SHELL_OPTION ELEMENT/SET entry depending upon whether one or more shell

elements are selected.

Object Type Analysis Type

Displacement Nodal Structural

Input Data Description

Translations (T1,T2,T3) Defines the enforced translational displacement values in the specified

coordinate system. These are in model length units.

Rotations (R1,R2,R3) Defines the enforced rotational displacement values in the specified

coordinate system. These are in degrees.


Force Nodal Structural


Force (F1,F2,F3) Defines the applied forces in the translation degrees-of-freedom in the specified

coordinate system.

Moment (M1,M2,M3)

Defines the applied moments in the rotational degrees-of-freedom in the

specified coordinate system.

Object Type Analysis Type Dimension

Pressure Element Uniform Structural 2D


102

Creates a *LOAD_SEGMENT.

Temperature

When the load case type is static this creates a *LOAD_THERMAL_CONSTANT or a

*LOAD_THERMAL_CONSTANT_NODE entry depending upon the application region. When the load

case type is transient this creates a *LOAD_THERMAL_VARIABLE or a

*LOAD_THERMAL_VARIABLE_NODE entry depending upon the application region.

Initial Velocity


Top Surf Pressure Defines the top surface pressure load on shell elements.

Bot Surf Pressure Defines the bottom surface pressure load on shell elements.

Edge Pressure Defines the edge pressure load on shell elements.


Pressure Element Uniform Structural 3D


Pressure Defines the face pressure value on solid elements. If a spacial field is referenced,

it will be evaluated once at the center of the applied region.


Temperature Nodal Structural


Temperature Defines the temperature which will be constant if the load case is static or

scaled by the load curve if the load curve is transient.


Initial Velocity Nodal Structural


Creates a *INITIAL_VELOCITY or *INITIAL_VELOCITY_NODE entry (The latter when there is

only a single node). The exempted node option is not supported for the former entry as Patran provides

more natural methods of defining nodal sets. Note that is an Analysis coordinate frame is specified the

values are transformed into the global coordinates system.

Velocity

If the load case type is transient this will result in generation of a

*BOUNDARY_PRESCRIBED_MOTION_OPTION NODE/SET entry. There is no corresponding data

for static load cases.

Acceleration

If the load case type is transient this will result in generation of a

*BOUNDARY_PRESCRIBED_MOTION_OPTION NODE/SET entry. There is no corresponding data

for static load cases.


Trans Veloc (v1,v2,v3) Defines the Velocity fields for translational degrees-of-freedom.

Rot Veloc (w1,w2,w3) Defines the Velocity fields for rotational degrees-of-freedom.


Velocity Nodal Structural


Trans Veloc(v1,v2,v3) Defines the enforced translational velocity values in the specified

coordinate system. These are in model length units per unit time.

Rot Veloc (w1,w2,w3) Defines the enforced rotational velocity values in the specified coordinate

system. These are in degrees per unit time.


Acceleration Nodal Structural


104

Initial Momentum

Creates a *INITIAL_MOMENTUM entry. Note that global coordinates apply only. This applies only for

solid elements.

Contact

Four types of contact exist. Three of these are complete definitions and have associated input data. The

fourth is the subsurface type which is used to define part of a contacting surface.


Trans Accel (A1,A2,A3) Defines the enforced translational acceleration values in the specified

coordinate system. These are in model length units per unit time squared.

Rot Accel (a1,a2,a3) Defines the enforced rotational acceleration values in the specified

coordinate system. These are in degrees per unit time squared.


Initial Momentum Element Uniform Structural 3D


Momentum (m1,m2,m3) Defines the Velocity fields for translational degrees-of-freedom.

Deposition Time Time at which energy is deposited in solid elements.

Object Type Option 1

Contact Element Uniform Self Contact

Subsurface

Master-Slave Srrface

Master-Slave Node


The contact options for each of the contact types are defined in the following table.

Input Data OptionSelf

Contact

Master Slave

Surface

Master Slave Node

Contact Type Single Surface (4) x

Surface to Surface (3) x

One-way Surface to Surface(10) x

Tied surface to Surface (2) x

Tie break Surface to Surface(9) x

Sliding Only (1) x

Sliding Only Penalty (p1) x

Rigid Body One way(21) x

Rigid body Two way(19) x

Nodes to Surface (5) x

Tied nodes to Surface (6) x

Tie break Nodes to Surface (8) x

Rigid Nodes to Body(20) x

Contact Method Automatic x x x

Standard x x x

Constrain x x

Constraint(Only available when Contact Method = Constrain)

Fully Symmetric x x

Constrain to Slave x x

Constrain to Master x x

Thickness definition Define x x x

Scale x x x

Surface Behavior Penalty x x x

Soft-Constraint x x x

Small penetration check

On x x x

Off x x x

Diagonal x x x

Interface output None x x x

Slave x x x

Master x x

Both x x


106

The contact input parameters are defined in the following table.

Geometric Rigid Wall

Four types of geometric rigid wall exist:

1. Flat

2. Prismatic

3. Cylindrical

4. Spherical

The options are as follows:

1. Motion: Static/Defined Velocity/Defined Displacement

2. Friction: Frictionless/No Slip/Frictional

Input Data Self ContactMaster Slave

SurfaceMaster Slave

Node

Static Friction Coefficient x x x

Dynamic Friction Coefficient x x x

Exponential Decay Coefficient x x x

Viscous Friction Coefficient x x x

Viscous Damping Coefficient x x x

Birth Time x x x

Death Time x x x

Scale Factor on Slave Stiffness x x x

Scale Factor on Master Stiffness x x

Master Surface Thickness x x

Slave Thickness Scale Factor x x x

Scale Factor to Constraint Forces x x x

Max. Param Coord in Search x x x

Cycles between Bucket Sorts x x x

Cycle between Force Updates

Maximum Penetration x


Planar Rigid Wall Nodal Structural


The input data for geometric rigid walls are as follows:

Note that the user must select a local coordinate system that is used when generating the geometry of the

wall. The local z axis is always the n axis in the LS-DYNA definition. The velocity is defined as a time

field in the local z direction.

Planar Rigid Wall

Two types of planar rigid wall exist:

1. Finite

2. Infinite

The options are as follows:

1. Motion: Static/Moving

2. Friction: No Slip/Frictionless/Isotropic Frictional/Orthotropic Frictional

Note that the orthotropic frictional behavior is available only for a static rigid wall.

The input data for planar walls is as follows:


Friction Coefficient For frictional behavior only.

Length of l (x) edge Applies for prism cylindrical and flat surface.

Length of m (y) edge Applies for prism and flat surface.

Length n (z) Applies for prism.

Radius Applies for cylinder and sphere.

Motion Time History Defines motion in the coordinate system of the geometric entity.

Applies for moving walls only.


Planar Rigid Wall Nodal Structural


Friction Coefficient(s) Only for Isotropic & Orthotropic frictional (Option 2)

Mass Only for moving walls.

Initial Velocity (Vo) Only for moving walls (Option 1). Defined relative to the local

coordinate system used to define the wall.


108

Note that the user must select a local coordinate system that is used when generating the geometry of the

wall. The local z axis is always the n axis in the LS-DYNA definition. The velocity is defined as a time

field in the local z direction.

Tied Shells

This defines a *CONSTRAINED_TIED_NODES_FAILURE data entry. Edges of shell elements

be selected.

Tied Shell Edges

This defines a *CONSTRAINED_TIE-BREAK data entry. This requires a dual application region. Both

master (primary) and slave (secondary) must be the edges of shells.

Nodal Rigid Body

Length of l (x) Edge Length of the l edge of a finite plane.

Length of m (y) Edge Length of the m edge of a finite plane.


Tied Shell Nodes Element Uniform Structural 2D


Plastic Strain at Failure The tied nodes, which must be coincident at the corners of each shell,

separate when the average weighted plastic strain reaches this value.


Tied Shell Nodes Element Uniform Structural Dual Application


Plastic Strain at Failure The tied nodes separate when the average weighted plastic strain

reaches this value.


Nodal Rigid Body Nodal Structural



This defines a *CONSTRAINED_NODAL_RIGID_BODY entry. Note that the user must define a local

coordinate system with origin at (0,0,0) on the wall and x direction normal to the wall and pointing into

the body. The option INERTIA will be generated if the second or third of the following options are

selected:

1. Computed (no input data required)

2. Defined Globally

3. Defined Locally (Local analysis coordinate frame selected).

The input data is tabulated below.

Nodal Inertial Load

Creates *LOAD_BODY_OPTION or *LOAD_BODY_GENERALIZED entries depending upon

whether the condition is applied to the complete body or some subset of the body. Note that only one

scale factor can be applied to the loads. Note also that the selected coordinate system defines the centre

of rotation for angular velocity.


Mass Translational mass of rigid body.

Inertia Ixx xx component of inertia tensor.

Inertia Ixy Not required if a local coordinate system is defined.

Inertia Ixz Not required if a local coordinate system is defined.

Inertia Iyy yy component of inertia tensor.

Inertia Iyz Not required if a local coordinate system is defined.

Inertia Izz zz component of inertia tensor.

Trans. Veloc (v1,v2,v3) Translational velocity.

Rot Veloc (w1,w2,w3) Rotational velocity.


Nodal Inertial Load Nodal Structural


Trans Accel (A1,A2,A3) Defines the base acceleration.

Rot Velocity (w1,w2,w3) Defines the angular velocity.

Patran Interface to LS-DYNA Preference GuideLoad Cases

110

Load Cases

Load cases in Patran are used to group a series of load sets into one load environment for the model. Load

cases are selected when preparing an analysis, not load sets. The usage for LS-DYNA is consistent,

however only one loadcase can be selected for translation. For information on how to define static and/or

transient load cases, see Overview of the Load Cases Application (p. 162) in the Patran Reference

Manual.

Chapter 3: Running an Analysis


3 Running an Analysis

� Review of the Analysis Form 112

� Translation Control 115

� Solution Parameters 116

� Select Load Case 123

� Output Requests 124

� Output Controls 133

� Select Groups for Set Cards 134

Patran Interface to LS-DYNA Preference GuideReview of the Analysis Form

112

Review of the Analysis Form

The Analysis form appears when the Analysis toggle, located on the Patran switch, is chosen. To run an

analysis, or to create an LS-DYNA input file, select Analyze as the Action on the Analysis form. Other

forms brought up by the Analysis form are used to define and control the analysis to be conducted and to

set global defaults, where appropriate. These forms are described on the following pages. For further

information see The Analysis Form (p. 8) in the MSC.Patran Reference Manual.

113Chapter 3: Running an AnalysisReview of the Analysis Form

Analysis Form

This form appears when the Analysis toggle is chosen on the main form. When preparing for an analysis

run, select Analyze as the Action.

Patran Interface to LS-DYNA Preference GuideReview of the Analysis Form

114

The following table outlines the selections for the Analyze action.

The Object indicates which part of the model is to be analyzed.

• Entire Model is selected if the whole model is to be analyzed.

• Select Group allows one or more groups to be selected from a form and written to the deck.

The Method indicates how far the translation is to be taken.

• Analysis Deck is selected if an analysis file translation is to be done, plus all load case, analysis

type and analysis parameter data are to be translated. A complete input file, ready for LS-DYNA,

should be generated.

• Full Run is selected if, in addition to writing an analysis file, LS-DYNA is to be executed.

Object Method

Entire Model Analysis Deck

Full Run

Select Group Analysis Deck

Full Run

115Chapter 3: Running an AnalysisTranslation Control

Translation Control

The translation parameters form allows the user to control the manner in which the LS-DYNA input file

is generated.

Patran Interface to LS-DYNA Preference GuideSolution Parameters

116

Solution Parameters

The solution parameters form provides access to subordinate forms upon which are defined the

parameters controlling execution of an LS-DYNA analysis.

117Chapter 3: Running an AnalysisSolution Parameters

Solution Control

The solution control subordinate form defines data to be written to the *CONTROL_CPU,

*CONTROL_TERMINATION and *CONTROL_TIMESTEP entries.


118

Relaxation Parameters

The solution control subordinate form defines data to be written to the *CONTROL_DYNAMIC

RELAXATION entry.


Global Damping

The solution control subordinate form defines data to be written to the *DAMPING_GLOBAL entry

with defines mass weighted nodal damping that applies globally to all deformable bodies.

Material Viscosity Defaults

The solution control subsidiary form defines data to be written to the *CONTROL_BULK_VISCOSITY

and *CONTROL_HOURGLASS entries.


120

Energy Calculation

The solution control subsidiary form defines data to be written to the *CONTROL_ENERGY entry.


Shell Control

The solution control subsidiary form defines data to be written to the *CONTROL_SHELL entry.


122

Contact Defaults

The solution control subsidiary form defines data to be written to the *CONTROL_CONTACT entry.

123Chapter 3: Running an AnalysisSelect Load Case

Select Load Case

This form appears when the Select Load Case button is selected on the Analysis form. Use this form to

select the load case to be included in this run.

Patran Interface to LS-DYNA Preference GuideOutput Requests

124

Output Requests

This form allows the definition of what results data is desired from the analysis code. The settings can be

accepted, as altered, by selecting the OK button on the bottom of the form. If the Cancel button is selected

instead, the form will be closed without any of the changes being accepted. Selecting the Defaults button

resets the form to the initial default settings.

125Chapter 3: Running an AnalysisOutput Requests

The following table outlines the selections for the Results Types and selection possibilities.

Object Type

Binary State File *DATABASE_BINARY_D3PLOT


Binary History File

Cross Section Forces

Wall Forces

Global Data

Subsystem Data

Discrete Elements

Material Energies

Nodal Interface Force

Result Interface Force

Deformed Geo File

SPC Reaction Force

Nodal Const Reaction

Air Bag Statistics

Nodal Force Group

BC Forces and Energy

Rigid Body Data

Geo Contact Entities

Sliding Int Energy

Joint Force File

Seat Belt Output

AVS Database

Movie

MPGS

Trace Particle History

Thermal Output








*DATABASE_SECFORC

*DATABASE_CROSS_SECTION_SET

*DATABASE_RWFORC

*DATABASE_GLSTAT

*DATABASE_SSSTAT

*DATABASE_EXTENT_SSSTAT

*DATABASE_DEFORC

*DATABASE_MATSUM

*DATABASE_NCFORC

*DATABASE_RCFORC

*DATABASE_DEFGEO

*DATABASE_SPCFORC

*DATABASE_SWFORC

*DATABASE_ABSTAT

*DATABASE_NODFOR

*DATABASE_BNDOUT

*DATABASE_RBDOUT

*DATABASE_GCEOUT

*DATABASE_SLEOUT

*DATABASE_JNTFORC

*DATABASE_SBTOUT

*DATABASE_AVSFLT

*DATABASE_EXTENT_AVS

*DATABASE_MOVIE

*DATABASE_EXTENT_MOVIE

*DATABASE_MPGS

*DATABASE_EXTENT_MPGS

*DATABASE_TRHIST

*DATABASE_TRACER

*DATABASE_TPRINT


126

To define the *DATABASE_EXTENT_BINARY entry associated with a

*DATABASE_BINARY_D3PLOT record the following subordinate form is used. This form is invoked

when Input Data is selected and Binary State File is the active Result Type. Note that the first data item,

“Exclude Discrete Springs and Dampers” is written to the *DATABASE_BINARY_D3PLOT record.


To define the *DATABASE_HISTORY_option entry associated with a

*DATABASE_BINARY_D3THDT record the following subordinate form is used. This form is invoked

when Input Data is selected and Binary History File is the active Result Type. Note that the last data item,

“Extra Time History Data” results in generation of a *DATABASE_BINARY_XTFILE record.


128

To define the *DATABASE_CROSS_SECTION_SET entry associated with a

*DATABASE_SECFORC record, the following subordinate form is used. This form is invoked when

Input Data is selected and Cross Section Forces is the active Result Type.


To define the *DATABASE_OPTION entry, the following subordinate form is used, when Input Data is

selected and one of the following options is the active Result type: Wall Forces, Global Data, Discrete

Element Material Energies, Nodal Interface Force, Result Interface force, Deformed Geo File, SPC

Reaction Force, Nodal Const. Reaction, Air Bag Statistics, Nodal force group, Geo contact entities,

Sliding Int Energy, Joint Force file, Seat Belt output, Thermal Output.

To define the *DATABASE_EXTENT_OPTION entry associated with a *DATABASE_OPTION

record, the following subordinate form is used,. This form is invoked when Input Data is selected and

AVS Database,Movie or MPGs is the active Result Type.


130

To define the *DATABASE_TRACER entry associated with a *DATABASE_TRHIST record, the

following subordinate form is used,. This form is invoked when Input Data is selected and Trace Particle

History is the active Result Type.

Table 3-1

Variable TypeComponent

Number Quantity

Nodal 1-3 x,y,z-displacements

4-6 x,y,z-velocities

7-9 x,y,z-accelerations

10 temperature

Brick Element 1 x-stress

2 y-stress

3 z-stress

4 xy-stress

5 yz-stress

6 zx-stress

7 effective plastic strain


Beam element 1 x-force resultant

2 y-force resultant

3 z-force resultant

4 x-moment resultant

5 y-moment resultant

6 z-moment resultant

Shell and Thick Shell 1 midsurface x-stress

2 midsurface y-stress

3 midsurface z-stress

4 midsurface xy-stress

5 midsurface yz-stress

6 midsurface zx-stress

7 midsurface effective plastic strain

8 innersurface x-stress

9 innersurface y-stress

10 innersurface z-stress

11 innersurface xy-stress

12 innersurface yz-stress

13 innersurface zx-stress

14 innersurface effective plastic strain

15 outer surface x-stress

16 outer surface y-stress

17 outer surface z-stress

18 outer surface xy-stress

19 outer surface yz-stress

20 outer surface zx-stress

21 outer surface effective plastic strain

22 bending moment-mxx (4-node shell)

23 bending moment -myy(4-node shell)

24 bending moment-mxy (4-node shell)

25 shear resultant-qxx (4-node shell)

26 shear resultant-qyy (4-node shell)

27 normal resultant-nxx (4-node shell)

28 normal resultant-nxx (4-node shell)

29 normal resultant-nxy (4-node shell)

30 thickness

Table 3-1 (continued)


Number Quantity


132

Shell and Thick Shell (continued)

31 element dependent variable

32 element dependent variable

33 innersurface x-stress

34 innersurface y-stress

35 innersurface z-stress

36 innersurface xy-stress

37 innersurface yz-stress

38 innersurface zx-stress

39 outer surface x-stress

40 outer surface y-stress

41 outer surface z-stress

42 outer surface xy-stress

43 outer surface yz-stress

44 outer surface zx-stress

45 internal energy

46 midsurface effective stress

47 inner surface effective stress

48 outer surface effective stress

49 midsurface max. principal strain

50 through thickness strain

51 midsurface min. principal strain

52 lowersurface effective strain

53 lowersurface max. principal strain


55 lower surface min.principal strain

56 lowersurface effective strain

57 lower surface min.principal strain


59 upper surface max.principal strain

60 upper surface effective strain

Table 3-1 (continued)


Number Quantity

133Chapter 3: Running an AnalysisOutput Controls

Output Controls

This form provides control over data generated during execution. Most of this data is entered on the

*CONTROL_OUTPUT entry. The settings can be accepted, as altered, by selecting the OK button on the

bottom of the form. If the Cancel button is selected instead, the form will be closed without any of

thechanges being accepted. Selecting the Defaults button resets the form to the default settings.

Patran Interface to LS-DYNA Preference GuideSelect Groups for Set Cards

134

Select Groups for Set Cards

The Select Group for Set Cards form allows you to select any of the groups in the model and write them

to the deck.

135Chapter 3: Running an AnalysisSetting LSDYNA IDs

Setting LSDYNA IDs

Normally the LSDYNA ID is set using the corresponding Patran entity ID. EG If a material is created

that has a Patran ID of 1, then the ID of 1 will be used for the LSDYNA *MAT card in the deck.

However, the user can set the ID by using the naming convention "Name.ID" for the Patran entity. This

applies for materials, property sets, fields and LBCs. If, for example, the user wants to manually set the

IDs of the materials, then he/she must make sure that every Patran material name is followed by a unique

ID ( 0 is not allowed ). Otherwise the IDs will not be changed. When the IDs are changed, a message is

printed by the translator to the xterm.

Patran Interface to LS-DYNA Preference GuideSetting LSDYNA IDs

136

Chapter 4: Read Results


4 Read Results

� Review of the Read Results Form 138

� Subordinate Forms 141

� Results Created in Patran 144

� Results File Size 145

Patran Interface to LS-DYNA Preference GuideReview of the Read Results Form

138

Review of the Read Results Form

The Analysis form will appear when the Analysis toggle, located on the Patran control panel, is chosen.

Read State File, as the selected Action on the Analysis form, allows the model and/or results data to be

accessed from within Patran or read into the Patran database, from an LS-DYNA State file. Subordinate

forms of the Analysis form define the data to be accessed, and the files from which to fetch the data.

These forms are described on the following pages.

139Chapter 4: Read ResultsReview of the Read Results Form

Read Results Form

Setting the Action option menu to Read State File indicates that results are to be accessed.

Patran Interface to LS-DYNA Preference GuideReview of the Read Results Form

140

Options on the Read Results Form

The following table defines the options that can be exercised from the Read Results Form.

Action Object Method Subsidiary Forms

Read State File Results Entities Attach Select State File

Translate Select State File

Select Times

Select Results

Model Data Attach Select State File


Both Attach Select State File


Select Times

Select Results

141Chapter 4: Read ResultsSubordinate Forms

Subordinate Forms

The subordinate forms accessed from the “Read Results Form” will depend upon the “Action” and

“Object” selected. The various possibilities are described in this subsection.

Select State File Subordinate Form

The subordinate State file selection form allows the user to select a LS-DYNA state file from which data

is to be extracted.

Querying State File

There is no subordinate y form associated with querying the state file. The query is done automatically

once the user has selected the state file. The data returned is required by the subsequent forms.

Patran Interface to LS-DYNA Preference GuideSubordinate Forms

142

Select Times

The subordinate “Select Times” form allows the user to select the cycle(s) for which results are to be

imported from a state file (“Translate” method only).

143Chapter 4: Read ResultsSubordinate Forms

Select Results

The subordinate “Select Results” form allows the user to select the results to be imported (“Translate”

method only). When results are being imported from a history file the entity selection acts as a filter on

the information imported.

Patran Interface to LS-DYNA Preference GuideResults Created in Patran

144

Results Created in Patran

The following table indicates all the possible results quantities which can be loaded into the Patran

database from an LS-DYNA state file.

Table 4-1 Results Supported During Model Importation

Primary Label Type Description

Displacement Nodal x, y, z displacements of nodes, in global coordinate frame.

Velocity Nodal x, y, z velocity of nodes, in global coordinate frame.

Acceleration Nodal x, y, z acceleration of nodes, in global coordinate frame.

Temperature Nodal Nodal temperature.

Forces Nodal Resultant beam forces and moments, in local beam coordinates.

Stress Element 6 components of stress tensor, at element centre and gaussian

points - top, middle, and bottom for shells.

Stress Resultants Element Stress Resultants at elements

Strain Element 6 components of strain tensor, at element centre and gaussian

points - top, middle, and bottom for shells.

Eff. Plastic Strain Element Effective plastic strain, at element centre and gaussian points -

top, middle, and bottom for shells.

145Chapter 4: Read ResultsResults File Size

Results File Size

The default results file size for Patran LS-DYNA is 7 Megabytes. If the results have been created using

a different file size, then an environment variable must be set in the Patran shell before reading the results.

This environment variable is ’FAM_SIZE’. This should be calculated as follows:

1. Find the biggest ".ptf" results file, and divide its size in bytes by 1MB (1048576 bytes). If this

gives an exact result, use that, otherwise round up by one.

2. Set the environment variable accordingly prior to running the translator. Thus if the file size is

24819794 bytes, this gives 23.67MB, thus

setenv FAM_SIZE 24 (C Shell syntax)

FAM_SIZE=24; export FAM_SIZE (Bourne/Korn shell syntax)

Note: The ‘FAM_SIZE’ environment variable is not needed with the “Attach” method, which is

designed to work with arbitrary file sizes.

Patran Interface to LS-DYNA Preference GuideResults File Size

146

Chapter 5: Read Input File


5 Read Input File

� Review of Read Input File Form 148

� Data Translated from the LS-DYNA Input File 152

� Reject and Error File 156

Patran Interface to LS-DYNA Preference GuideReview of Read Input File Form

148

Review of Read Input File Form

The Analysis form will appear when the Analysis toggle, located on the Patran main form, is chosen.

Read Input File as the selected Action on the Analysis form allows some of the model data from an LS-

DYNA input file to be translated into the Patran database. A subordinate File Selection form allows the

user to specify the LS-DYNA input file to translate.

149Chapter 5: Read Input FileReview of Read Input File Form

Read Input File Form

This form appears when the Analysis toggle is selected on the main form. Read Input File, as the selected

Action, specifies that model data is to be translated from the specified LS-DYNA input file into the

Patran database.

Patran Interface to LS-DYNA Preference GuideReview of Read Input File Form

150

Selection of Input File

This subordinate form appears when the Select Input File button is selected on the Analysis form when

Read Input File is the selected Action. It allows the user to specify which LS-DYNA input file to

translate.

151Chapter 5: Read Input FileReview of Read Input File Form

Set Card Read Options

This subordinate form appears when the Set Card Read Option button is selected on the Analysis form

when Read Input File is the selected action. It allows you to specify which set of cards of the LS-DYNA

input file to translate.

Patran Interface to LS-DYNA Preference GuideData Translated from the LS-DYNA Input File

152

Data Translated from the LS-DYNA Input File

The Patran LSDYNA3D input file translator currently translates the model topology, some materials and

some properties from an input file. The following is a list of the data supported.

Table 5-1 Input File Translation Data

Category Keyword

BOUNDARY *BOUNDARY_CYCLIC

*BOUNDARY_PRESCRIBED_MOTION_NODE

*BOUNDARY_PRESCRIBED_MOTION_SET

*BOUNDARY_SPC_SET

CONSTRAINED *CONSTRAINED_EXTRA_NODES_SET*CONSTRAINED_GENERALIZED_WELD_BUTT*CONSTRAINED_GENERALIZED_WELD_FILLET*CONSTRAINED_GENERALIZED_WELD_SPOT*CONSTRAINED_JOINT_*CONSTRAINED_JOINT_CYLINDRIAL*CONSTRAINED_JOINT_PLANAR*CONSTRAINED_JOINT_REVOLUTE*CONSTRAINED_JOINT_SPHERICAL

*CONSTRAINED_JOINT_TRANSLATIONAL*CONSTRAINED_JOINT_UNIVERSAL*CONSTRAINED_LINEAR*CONSTRAINED_NODAL_RIGID_BODY*CONSTRAINED_NODAL_RIGID_BODY_INERTA*CONSTRAINED_RIVET*CONSTRAINED_SHELL_TO_SOLID*CONSTRAINED_SPOTWELD

*CONSTRAINED_TIED_NODES_FAILURE

CONTACT *CONTACT_AUTOMATIC_ONE_WAY_SURFACE_TO_SURFACE

*CONTACT_AUTOMATIC_SINGLE_SURFACE

*CONTACT_AUTOMATIC_SURFACE_TO_SURFACE

*CONTACT_AUTOMATIC_NODES_TO_SURFACE

*CONTACT_CONSTRAINT_NODES_TO_SURFACE

*CONTACT_CONSTRAINT_SURFACE_TO_SURFACE

*CONTACT_NODES_TO_SURFACE

*CONTACT_ONE_WAY_SURFACE_TO_SURFACE

*CONTACT_RIGID_NODES_TO_RIGID_BODY

*CONTACT_TIEBREAK_NODES_TO_SURFACE

*CONTACT_TIED_NODES_TO_SURFACE

CONTROL *CONTROL_BULK_VISCOSITY

*CONTROL_CPU

*CONTROL_CONTACT

*CONTROL_COUPLING

*CONTROL_DYNAMIC_RELAXATION

*CONTROL_ENERGY

*CONTROL_HOURGLASS

*CONTROL_OUTPUT

*CONTROL_SHELL

*CONTROL_TERMINATION

*CONTROL_TIMESTEP

DAMPING *DAMPING_GLOBAL

*DAMPING_PART_MASS

*DAMPING_PART_STIFFNESS

Note: The Property and Material ID in the analysis file are used as a numeric extension to the Property Set name and Material name in the Patran database.

153Chapter 5: Read Input FileData Translated from the LS-DYNA Input File

DATABASE *DATABASE_ABSTAT

*DATABASE_AVSFLT

*DATABASE_BNDOUT

*DATABASE_DEFGEO

*DATABASE_DEFORC

*DATABASE_GCEOUT

*DATABASE_GLSTAT

*DATABASE_JNTFORC

*DATABASE_MATSUM

*DATABASE_MOVIE

*DATABASE_MPGS

*DATABASE_NCFORC

*DATABASE_RWFORC

*DATABASE_SBTOUT

*DATABASE_SECFORCE

*DATABASE_SLEOUT

*DATABASE_SPCFORC

*DATABASE_SSSTAT

*DATABASE_SWRFORC

*DATABASE_TPRINT

*DATABASE_TRHIST

*DATABASE_RBDOUT

*DATABASE_RWFORC

*DATABASE_BINARY_D3PLOT



*DATABASE_CROSS_SECTION_SET

*DATABASE_EXTENT_AVS


*DATABASE_EXTENT_MOVIE

*DATABASE_EXTENT_MPGS

*DATABASE_EXTENT_SSSTAT






*DATABASE_TRACER

DEFINE *DEFINE_COORDINATE_NODES

*DEFINE_COORDINATE_SYSTEM

*DEFINE_CURVE

*DEFINE_SD_ORIENTATION

*DEFINE_VECTOR

ELEMENT *ELEMENT_BEAM

*ELEMENT_BEAM_THICKNESS

*ELEMENT_DISCRETE

*ELEMENT_MASS

*ELEMENT_SHELL_BETA

*ELEMENT_SHELL

*ELEMENT_SHELL_THICKNESS

*ELEMENT_SOLID

*ELEMENT_SOLID_ORTHO

*ELEMENT_TSHELL

END *END

Table 5-1 Input File Translation Data (continued)

Category Keyword


Patran Interface to LS-DYNA Preference GuideData Translated from the LS-DYNA Input File

154

INITIAL *INITIAL_MOMENTUM

*INITIAL_VELOCITY

*INITIAL_VELOCITY_NODE

LOAD *LOAD_BODY_GENERALIZED

*LOAD_NODE_POINT

*LOAD_NODE_SET

*LOAD_SEGMENT

*LOAD_SEGMENT_SET

*LOAD_SHELL_ELEMENT

*LOAD_SHELL_SET

*LOAD_THERMAL_CONSTANT

*LOAD_THERMAL_CONSTANT_NODE

*LOAD_THERMAL_VARIABLE

*LOAD_THERMAL_VARIABLE_NODE

MAT *MAT_BLATZ-KO_RUBBER

*MAT_CLOSED_FORM_SHELL_PLASTICITY

*MAT_COMPOSITE_DAMAGE

*MAT_COMPOSITE_FAILURE_MODEL

*MAT_CRUSHABLE_FOAM

*MAT_ELASTIC

*MAT_ELASTIC_FLUID

*MAT_FRAZER_NASH_RUBBER_MODEL

*MAT_HONEYCOMB

*MAT_ISOTROPIC_ELASTIC_PLASTIC

*MAT_JOHNSON_COOK

*MAT_LAMINATED_GLASS

*MAT_LINEAR_ELASTIC_DISCRETE_BEAM

*MAT_LOW_DENSITY_FOAM

*MAT_MOONEY-RIVLIN_RUBBER

*MAT_NONLINEAR_ELASTIC_DISCRETE_BEAM

*MAT_NONLINEAR_PLASTIC_DISCRETE_BEAM

*MAT_PIECEWISE_LINEAR_PLASTICITY

*MAT_PLASTIC_KINEMATIC

*MAT_RATE_SENSITIVE_POWERLAW_PLASTICITY

*MAT_RESULTANT_PLASTICITY

*MAT_RIGID

*MAT_SID_DAMPER_DISCRETE_BEAM

*MAT_SOIL_AND_FOAM

*MAT_SOIL_AND_FOAM_FAILURE

*MAT_SPRING_ELASTOPLASTIC

*MAT_SPRING_GENERAL_NONLINEAR

*MAT_SPRING_MAXWELL

*MAT_STRAIN_RATE_DEPENDENT_PLASTICITY

*MAT_VISCOELASTIC

*MAT_VISCOUS_FOAM

NODE *NODE

PART_OPTION *PART

*PART_INERTIA

*PART_REPOSITION


Category Keyword


155Chapter 5: Read Input FileData Translated from the LS-DYNA Input File

RIGIDWALL *RIGIDWALL_GEOMETRIC_

*RIGIDWALL_GEOMETRIC_CYLINDER

*RIGIDWALL_GEOMETRIC_FLAT

*RIGIDWALL_GEOMETRIC_PRISM

*RIGIDWALL_GEOMETRIC_SPHERE

*RIGIDWALL_GEOMETRIC_CYLINDER_MOTION

*RIGIDWALL_GEOMETRIC_FLAT_MOTION

*RIGIDWALL_GEOMETRIC_PRISM_MOTION

*RIGIDWALL_GEOMETRIC_SPHERE_MOTION

*RIGIDWALL_PLANAR_

*RIGIDWALL_PLANAR_FINITE

*RIGIDWALL_PLANAR_ORTHO_FINITE

*RIGIDWALL_PLANAR_MOVING

SECTION *SECTION_BEAM

*SECTION_DISCRETE

*SECTION_SHELL

*SECTION_SOLID

*SECTION_TSHELL

SET *SET_NODE_COLUMN

*SET_BEAM

*SET_BEAM_GENERATE

*SET_DISCRETE

*SET_DISCRETE_GENERATE

*SET_NODE_LIST

*SET_NODE_LIST_GENERATE

*SET_SEGMENT

*SET_SHELL_COLUMN

*SET_SHELL_LIST

*SET_SHELL_LIST_GENERATE

*SET_SOLID

*SET_SOLID_GENERATE

*SET_TSHELL

*SET_TSHELL_GENERATE

TITLE *TITLE


Category Keyword


Patran Interface to LS-DYNA Preference GuideReject and Error File

156

Reject and Error File

The input file reader places all unsupported LsDyna keywords in a reject file which has the extension .rej.

Also keywords that cannot be read due to incorrect data are placed in an error file with a line describing

the error. The error file has the extension .err

Chapter 6: Files


6 Files

� Files 158

Patran Interface to LS-DYNA Preference GuideFiles

158

Files

The Patran LS-DYNA Preference uses or creates several files.The following table outlines each file, and

its uses. In the file name definition, jobname will be replaced with the jobname assigned by the user.

File Name Description

*.db This is the Patran database. During an analyze pass, model data is read

from, and during a Read Results pass, model and/or results data is written

into. This file typically resides in the current directory.

jobname.key This is the LS-DYNA input file created by the interface. This file typically

resides in the current directory

jobname.ptf This is the LS-DYNA state file (family) which is read by the Read Results

pass. This file typically resides in the current directory.

jobname.his This is the LS-DYNA time history file. This file typically resides in the

current directory.

jobname.flat This file may be generated during a Read Results pass. If the results

translation cannot write data directly into the specified Patran database it

will create this jobname flat file. This file typically resides in the current

directory.

LsDyna3dExecute This is a UNIX script file which is called on to submit the analysis file to

LS-DYNA after translation is complete. This file might need customizing

with site specific data. The file contains many comments and should be

easy to edit. Please see the LS-DYNA documentation for more details on

how to edit this file. Patran searches its path to find this file, but it typically

resides in the <installation_directory>/bin/exe directory. Either use the

general copy in <installation_directory>/bin/exe, or place a local copy in a

directory on the file path which takes precedence over the

<installation_directory>/bin/exe directory.

LsdynaPat3Submit This is a UNIX script which is called on to submit the results translation

program lsdynapat3. This file does not need site specific customization.

However, this file can be modified to meet specific needs. Patran searches

its file path to find this file, but it typically resides in the

<installation_directory>/bin/exe directory. Use the general copy in the

<installation_directory>/bin/exe/ directory, or use a local version by

placing this local version in a directory higher on the Patran file path.

jp`Kc~íáÖìÉ=nìáÅâ=pí~êí=dìáÇÉ

I n dex


fåÇÉñ

Index

Bbulk data file, 148

Ccoordinate frames, 18

Eelastoplastic, 33, 34, 36, 37, 39, 40, 41

element properties, 62

elements

grounded scalar damper, 67

grounded scalar spring, 66, 73, 75, 76

scalar damping, 75, 76

scalar mass, 65

scalar spring, 73, 74

solid, 88

standard homogeneous plate, 84

standard membrane, 85

Ffiles, 158

finite elements, 19, 21

Iinput file, 148

Lload cases, 110

loads and boundary conditions, 91

Mmaterials, 30

multi-point constraints, 22

Nnewlink butt_weld, 81

newlink fillet_weld, 79

newlink spot_weld, 78

nodes, 20

Ppreferences, 12

properties, 62

Rread input file, 148

results

supported entities, 144

Ssupported entities, 13

Ttemplate database, 6


160

patran 2008 r1 interface to ls-dyna preference guide

Documents

software corporation

registered trademarks

registered trademark

software japan

registered trademark

software gmbh

software suppliers

registered trademarks