HW11 AbaqusInterface Final PPT

Copyright © 2009 Altair Engineering, Inc. Proprietary and Confidential. All rights reserved.

HyperWorks 11.0 for Abaqus

Using HyperMesh and HyperView


Chapter 1: Foundation for Abaqus Modeling



Foundation for Abaqus Modeling

Topics Presented

•

User Profile

•

Utility menu

•

Input file format

•

Abaqus equivalent in HyperMesh

•

Solver Specific Online Help


Abaqus User Profile

•

3 User Profiles•

Standard2D•

Standard3D•

Explicit

•

User Profile aids in workflow

•

Provides tools for working effectively with the Abaqus interface

•

Configuration of panels

•

Loads specific Utility Menu

•

Loads input reader and output templates


Abaqus Utility Menu

Contains Abaqus specific macros•

Solid Face alignment•

Change and review of stack direction•

Align S1 faces of solid elements (Tetra/Hexa

Elements)l•

Tools•

Component Browser: Organization of the Model•

Step Manager: Create initial conditions and step definitions including output requests

•

Contact Manger: Define Abaqus

contacts, tie and pretension section


Abaqus input file format

MODEL DATA•

Heading•

Nodes•

Elements•

Sets•

Section properties•

Materials•

Boundary conditions, Loads (Initial conditions)•

Coordinate systems•

Contacts (Standard)

HISTORY DATA•

Steps•

Boundary conditions, Loads•

Output requests•

Contacts (Explicit)



Model Data

•

Heading control card

•

Nodes nodes

•

Elements elements

•

*ELSET, *NSET entity sets

•

Section properties component collectors

•

Materials material collectors

•

Constraints 1D elements

•

Initial conditions Step Manager

•

Coordinate systems systems in system collectors

•

Contacts (for Standard) Contact Manager



History Data

•

Step Step Manager

•

Boundary conditions, Loads Step Manager

•

Output requests Step Manager

•

Contacts (for Explicit) Add to step in Step Manager


HyperMesh Online Help for Abaqus

How to launch online help•

Help pulldown

menu HyperWorks Desktop•

Press h on keyboard

How to access ABAQUS topics•

Contents tab: HyperMesh > HyperMesh Interfacing with External Products > Abaqus Solver Interface

•

Index tab: Search for specific topic

How to access ABAQUS online tutorial•

Contents tab: Tutorials > HyperMesh Solver Interfaces > Abaqus•

Tutorials #: HM-4300, HM-4310, HM-4320, HM-4330, HM-4340, HM-4350, HM-

4360


Chapter 2: Introduction to Defining ABAQUS Model Data



Introduction to Defining Abaqus Model Data

Topics Presented

•

Defining model data (components, properties, materials)

•

Element property assignment and include files

•

Converting a Nastran model to Abaqus

•

3D Visualization of 1D Elements with Abaqus models


Model Organization: Tools

Model Browser•

View collectors and assemblies in a hierarchical tree format

•

Create, delete, and rename collectors•

Edit cards•

Edit collector attributes•

Organize collectors into assemblies•

Drag and drop•

And more …


Model Data - Organization

material collector (mats)

card image: ABAQUS_MATERIAL

...

Property collector (props)

card image: SOLIDSECTIONSHELLSECTION

BEAMSECTION...

component collector (comps)

load collector (loadcols)

card image: (INITIAL_CONDITION)

HISTORY

groupscard image: CONTACT_PAIR

SURFACE_ELEMENT

FASTENER

...

property collector (props)

card image: SURFACE_INTERACTION

FASTENER_PROPERTY

...

Elements

outputblocks*EL FILE *EL PRINT *OUTPUT ...

loadstep*STEP ... *END STEP


Sectional properties moved from component to property level

Components no longer have card images

Modeling Options•

Assign property to component (one property per component)•

Assign property to elements (multiple properties per component)

Element assignment takes precedence over component assignment

ComponentCollector

PropertyCollector 1

MaterialCollector 1

PropertyCollector 2

MaterialCollector 2

PropertyCollector 3

MaterialCollector 3

Element 2

Element 1

Element 3

Element 4

Element 2

Element 1

Element 3

Element 4

Element 2

Element 3

Element 4

Color by Component

Color by Property

Property Handling in HyperMesh


Abaqus *ELEMENT with section property

Organized into component (comp) collector

•

ELSET name is comp’s name

•

Elems

of different types can be in same comp

One *ELEMENT written to input file for each elem type

Material collector •

with card image •

and associated to prop collector

Prop collector’s card image

*ELEMENT, TYPE=[type], ELSET=cradle

*MATERIAL, NAME=steel

*SOLID SECTION, ELSET=cradle, MATERIAL=steel


Import options•

By HM Comment (default)•

Maintain model organization of previous export•

If no comments are found, follows ‘By Property’

option

•

By Property•

Creates a component from every ELSET with sectional property

•

Creates a property for each component and assigns to the component (Both have the same name)

•

By 1 Component•

All elements are moved to an ‘Auto1’

component•

Properties are assigned on element level

File import panel :

Example:

Property to ComponentProperty to Element

Assignment:

Importing input file in HyperMesh


Model Data Model Data –– Card EditorCard Editor

• View card image from Card Edit panel from tool bar

• Review Abaqus keywords and data lines from card images

• Define and edit parameters and data items

• Card image of an Abaqus material

• Card image Abaqus element


HyperMesh entity configuration and type

•

Two identifiers for elements and loads in HyperMesh•

Configuration: HM core feature •

Type: Defined by loaded template

•

Element configurations: rigid, spring, quad4, hex8•

quad4 (template) types: S4, S4R, S4R5…

•

Load configurations: constraints, force, pressure, temperature•

pressure (template) types: DLOAD, FILM, DFLUX, DECHARGE

•

Select Abaqus element types for HyperMesh element configurations from elem types panel in 1D, 2D, or 3D pages

•

Select Abaqus constraint and load types for HyperMesh load configurations from load types panel in Analysis page


HyperMesh entity configuration and type (2)

elem types panel•

Predefine element type to be used next•

Switch elements to a new type (e.g. S4 -> S4R) by using elems selector and update button

•

Only elements of the same configuration can be changed by this panel•

Otherwise use config edit panel•

review writes the element type on the screen•

Change color of configuration for displaying purposes

Element type

Configuration

Color of Configuration Element type

Configuration

Color of Configuration


HyperMesh entity configuration and type (3)

Load types panel•

Predefine load types to be used next•

Update loads•

Compare to element types panel

Load

type

Configuration


Graphical user interface for•

Handling of include file structures•

Review and Manipulation of includes•

Move entities into/between includes•

Import new data into includes•

Export include structures

Include Browser


•

Many FEA solvers allow the organization of a model into several include files

•

Include browser helps to handle these include files

•

This tool may be used to display model information and to change an include structure e.g. adding/deleting entities to (from) an include, adding new includes, exporting selected includes etc.

•

The Include View can be started by clicking Include View from the Model Browser

Include View within the Model Browser - Purpose


•

The functions of the tool can be activated after pressing the right button of the mouse

•

Only the highlighted functions are active (context sensitive)

•

Include browser offers following functionalities:

•

Display and mask includes•

Add/delete/rename and import includes•

Choose the ‘current’

include. All new entities will be organized in current include

•

Collapse and expand trees of model structure•

Export one/all includes•

Cards are editable directly by right mouse click

Include View - Functionality


Import a master file with includes•

Import models with import sub-panel of the files panel

•

Make sure, that the option preserve include files is active

Create new includes in the includes browser•

Right-mouse click on master model (or an include), choose Create > Include File and type in the name of the new include

•

Move entities to the new include by drag ‘n drop

Import an include•

Select the ‘Import Include …’ option of right mouse button menu

•

The files-panel opens to import the new include-

file

Include Browser – Generating Includes


•

After importing the include files, every include file is represented by an own folder

•

Entities which belong to an include, can be found in these folders organized by entity type

•

User can move entities to (from) includes with the organize - panel or simply by drag ‘n’ drop

•

Data, which does not have any references to an include file, is stored in the master model

•

Includes can be shown or hidden by display options, which can be found in the context menu of the includes

Include Browser – Include Handling


New Conversion Framework•

Controlled by configuration file•

Status of converted entities•

Direct access to card image•

Information about mapped cards•

Many new solver conversions supported

Nastran to/from Abaqus•

Converts:•

Elements•

Sectional Properties•

Materials•

Loads and Constraints•

Systems and Masses•

Subcases

to Steps

Conversion: Abaqus from/to Nastran

tria3,CTRIA3 tria3,S3tria3,CTRIAR tria3,S3Rquad4,CQUAD4 quad4,S4quad4,CQUADR quad4,S4Rquad4,CSHEAR quad4,M3D4tetra4,CTETRA tetra4,C3D4penta6,CPENTA penta6,C3D6hex8,CHEXA hex8,C3D8tria6,CTRIA6 tria6,STRI65quad8,CQUAD8 quad8,S8Rtetra10,CTETRA tetra10,C3D10penta15,CPENTA penta15,C3D15hex20,CHEXA hex20,C3D20mass,CONM2 mass,MASSmass,CELAS1 mass,SPRING1mass,CELAS2 mass,SPRING1rigid,RBE2 rigid,COUP_KINrigidlink,RBE2 rigidlink,COUP_KINrbe3,RBE3 rbe3,DCOUP3Dspring,CELAS1 spring,SPRING2spring,CELAS2 spring,SPRING2spring,CDAMP1 spring,DASHPOT2spring,CDAMP2 spring,DASHPOT2spring,CBUSH rod,CONN3D2bar2,CBEAM bar2,B31bar2,CBAR bar2,B31rod,CROD rod,T3D2rod,CONROD rod,T3D2gap,CGAP gap,GAPUNIweld,RBAR rigid,KINCOUP*END


3D Beam Visualization with Abaqus Models

Objective•

Provide Verification of Engineering Data Associated with 1D Elements by Visualizing 1D Elements as their “true”

3D Representation •

Engineering Data Accurately Visualized•

Cross-Section Dimensions•

Cross-Section Orientation•

Cross-Section Offset (limitation in Abaqus

User Profile)


Procedure for creating 1D elements which can be viewed in 3D•

Create BeamSections

using HyperBeam•

Create 1D properties•

Assign BeamSection•

Assign an offset•

Create 1D elements•

Assign property to either element component or directly on the element

3D Beam Visualization with Abaqus Models


3D Beam Visualization with Abaqus Models – CreationCreate BeamSections using HyperBeam (Menu Bar: Properties > HyperBeam)

•

Graphical Program for Creating Cross-Sections and Calculating Properties•

Several Abaqus

standard sections supported

•

If a different section type is needed, it can still be defined through the BEAMSECTION card image for the property

• RECT• CIRC

• I• L

• TRAPEZOID• BOX• PIPE


3D Beam Visualization with Abaqus Models – Creation

Create 1D Properties (Menu Bar: Properties > Create)

•

BeamSections

are Associated to

1D Properties•

Abaqus: *BEAMSECTION, *BEAMGENSECTION

•

In order to Visualize 3D Representation of 1D Element, 1D Property Assigned to 1D Element must have Associated BeamSection

BeamSection

Offset


3D Beam Visualization with Abaqus Models – Creation

Create 1D Elements (Menu Bar: Mesh > Create > 1D Elements > Bars)•

Define Orientation Vector –

specifies direction of n1 vector for local, right-handed axis system•

Vector –

not supported in Abaqus

User Profile•

Components –

can be used, although not fully supported in Abaqus

User Profile•

Defines direction cosines for n1 axis•

Can be used to visualize orientation•

Second step needed to update property card image with component values•

Node –

fully supported in Abaqus

User Profile•

Defines n1 going from node A to the selected direction node•

B31 card image has node A, node B, direction node•

Define node A and node B•

Designates the ends of the beam element

node A

node B

direction node


Chapter 3: Defining Abaqus Steps with the Step Manager



Defining Abaqus Steps with Step Manager

Topics Presented

•

Define model data with Step Manager

•

Define history data with Step Manager


Model Data – Step Manager

Use to create•

Initial conditions defined in the model data section of input file

Main window of Step Manager

Initial condition definition


History Data – Step Manager (1)Use to create

•

Abaqus

steps •

Boundary conditions and loads in steps•

Output requests (.odb, .fil, .dat)


History Data – Step Manager (2)Abaqus Steps


History Data – Step Manager (3)

Abaqus Steps



Order of steps in Step Manager is order they appear in INP file•

Reorder steps using up and down arrows



Display on and off load steps in Step Manager•

Loads in steps are displayed on and off

Export only certain steps to INP file


History Data – Loads and Constraints

Process driven by the Step Manager

Create *CLOAD-cards BCs > Create > Forces to enter Forces

panel

Create *BOUNDARY-cards BCs > Create > Constraints to enter Constraints panel

Both panels are accessible directly and by Step manager


Chapter 4: Pretension, Analytical Surfaces, and Contacts



Pretension, Analytical Surfaces, and Contacts

Topics Presented

•

Contact Manager

•

Bolt pre-tensioning

•

Analytical rigid surface definition

•

One-node elements and contact definition using the Contact Manager


ABAQUS Contact Manager - Overview

Create and review the following contacts•

Contact Pair•

General Contact (only explicit)•

Tie•

Pretension Section

Two Methods to create new contacts•

Method 1: create surfaces and interface during building contact pair•

Method 2: build the contact using surfaces and interfaces predefined in Surface or Surface interaction tab


ABAQUS Contact Manager ABAQUS Contact Manager –– Contact Pair Contact Pair (1)(1)

Method 1•

Create

a new

contact•

If

needed: create

new

surfaces•

Assign

surface(s) as master

or

slave•

Define

a new

surface

interaction

or

choose

an existing

one


ABAQUS Contact Manager ABAQUS Contact Manager –– Contact Pair Contact Pair (1)(1)

Method 2•

Create

and review

surfaces

from

Surfaces tab

first•

Define

a new

Interaction•

Finally

combine

surfaces

and interaction

to a *CONTACT PAIR


ABAQUS Contact Manager – *SURFACE (1)

Define *SURFACE from Contact Manager for these entities:

solid

shell

membrane

rigid

gasket

beam

pipe

truss


ABAQUS Contact Manager ABAQUS Contact Manager –– *SURFACE *SURFACE (2)(2)

Define surface by *ELEMENT id and face identifier*SURFACE, NAME = new_surface, TYPE = ELEMENT2204, SPOS2203, SPOS

•

Element face identifiers•

Solids -

S1, S2, S3, S4, S5, S6•

Shells and gaskets -

SPOS, SNEG Excluding the Element set option, use any option in the Define tab

•

Treat gaskets as regular solids. HM will write SPOS or SNEG to inp-file•

Adjust normals

(shells) and optional parameters



Define surface by *ELSET id and face identifier*ELSET, ELSET=MTubeContSet1, 2, 3 *SURFACE, NAME = Ma_Moving, TYPE = ELEMENTMTubeContSet, SNEG

•

Select ELSET and specify identifier. Use Element set option in Define tab•

HM writes ELSET name and identifier to INP file•

If None selected for Face, no identifier written to INP file. ABAQUS will use all faces for all elements in the ELSET.



No need to know relation of keywords to HM entities

*CONTACT PAIR *PRE-TENSION SECTION*TIE all are HM groups (interfaces panel)*SURFACE, TYPE = ELEMENT*SURFACE, TYPE = NODE

*SURFACE INTERACTION*FRICTION all are HM property collectors*SURFACE BEHAVIOR


ABAQUS Contact Manager – SURFACE INTERACTION

Definition of *SURFACE INTERACTION cards


Contact Manager – *PRETENSION SECTION

Modelling of pretension sections for 1D and 3D elements•

*PRETENSION SECTION, TYPE=SURFACE, NODE=n•

*PRETENSION SECTION, TYPE=ELEMENT, NODE=n

Definition of normal of pretension section

Definition via pre-tension

node

and surface/element

Definition of the

normal


ContactContact Manager Manager –– AnalyticalAnalytical Rigid SurfaceRigid Surface

Definition of *SURFACES, TYPE=SEGMENTS, CYLINDER and REVOLUTION

*SURFACES, TYPE=SEGMENTS, CYLINDER


Create, edit, review, delete *SURFACE from Surface tab

Contact Manager – Analytical Rigid Surface (2)


Cylinder: Creates a rigid surface going from -∞

to +∞. The Plane/axis is along the direction of sweep. In case of a user defined system this should be the Local z-axis.

Revolution: Creates a rigid surface that spins around an axis. The Plane/axis is the axis of spin. In case of a User defined system, this should be the Local z-axis.

Contact Manager – Analytical Rigid Surface (3)


Chapter 5: Systems in Abaqus



Systems in Abaqus

Topics Covered

•

*SYSTEM and *TRANSFORM

•

*ORIENTATION


Systems collector

Create one system per system collector

System Collectors do not require a card image

Systems are organized in systems collectors

Create systems collectors from panel or model browser


*SYSTEM and *TRANSFORM systems

Create systems from Systems panel

*SYSTEM - defines node coordinates in a local coordinate system•

Select the nodes and use set reference•

*SYSTEM followed by nodes defined will appear in the input file

*TRANSFORM – defines the directions for the degrees of freedom of nodes•

Select the nodes and use set displacement•

*TRANSFORM followed by *NSET will appear in the input file


*ORIENTATION system*ORIENTATION system

*ORIENTATION defines a local system for elements*ORIENTATION, NAME=, DEFINITION=, SYSTEM=

Xa Ya Za Xb Yb Zc

locdiralpha

Creation process:•

1 -

create systems collector with no card image•

2 -

create HM system from Systems panel•

3 -

card edit HM system (systs) and activate ORIENTATION option

Associate *ORIENTATION to section property:•

1 -

card edit property collector•

2 -

specify systems collector name in ORIENTATION field


Chapter 6: Model Setup in Abaqus/Explicit



Model Setup in Abaqus/Explicit

Topics Covered

•

Boundary conditions and general contact


•

General Contacts for Abaqus/Explicit can be specified as model data or history data.

•

Use Step Manager to specify General Contact.

Define General Contact for Abaqus/Explicit


Contact Definition in Abaqus/Explicit - Example

**** Surface Definition***CONTACT*CONTACT INCLUSIONS, ALL ELEMENT BASED*CONTACT PROPERTY ASSIGNMENT,,FRIC

*SURFACE INTERACTION, NAME=FRIC*FRICTION0.2,


Variable loading in Abaqus/Explicit

*AMPLITUDE is used for loading history in Abaqus/ExplicitCurve created in Curve Editor or XY plots

•

Both referenced from XYPlots

pull down menu

Associate *AMPLITUDE to a load in Step Manager


Chapter 7: Post Processing Abaqus Results in HyperView



Post Processing Abaqus Results in HyperView

Topics Covered

•

Post Processing Static Analysis Results •

Result Types in HyperView•

Use corner data option in HyperView•

Reader options in HyperView•

Available averaging methods in HyperView•

Comparing contour options in HyperView

•

Post Processing Complex Results •

Complex Result in HyperView


•

Results in ODB file are calculated:•

At Integration points•

At Element centroid•

At Node•

Shell elemental results in elemental or material system

•

Result Types in HyperView•

Scalar and Tensor results available•

With “IP”

suffix –

Results at Integration points•

Without “IP”

suffix –

Results dependent on output request•

(t) -

Indicates a tensor-type result, such as stress or strain tensors.•

(v) -

Indicates a vector-type result, such as displacement, velocity, and acceleration.

•

(s) -

Indicates a scalar-type result. The components and invariants are read directly from the ODB file.

•

(c) -

Indicates complex results.

Post Processing Static Analysis Results


•

Result Types in HyperView – Tensor vs. Scalar•

Scalar results are taken directly from .odb

file •

Generally in material or elemental coordinate system

•

Tensor results are translated into global system•

Using scalar results and transformation matrix in .odb

file•

Prefixed in HyperView with “Global”

•

Possible to have Abaqus

calculate element output in global system•

*ELEMENT OUTPUT

DIRECTIONS=NO

•

.odb file contains Integration Point results and another set of results•

*ELEMENT OUTPUT POSITION parameter•

POSITION=INTEGRATION POINTS•

HyperView extrapolates the results from the integration points to the nodes.•

POSITION=NODES•

Abaqus

places the results at the nodes.•

POSITION=CENTROIDAL•

Results are located at the center of the element. There is one value per element.



•

Use Corner Data Option in HyperView•

Not available for all result types•

When activated, HyperView displays color bands by interpolating available corner results within each element

•

Integration point results are not interpolated

•

Discontinuities across element boundaries can be seen•

What not activated, results are averaged as the base result of the element•

One result per element

•

Results shown depend on result type selected and if Use corner data is enabled:


Without "IP" suffix

For example: S-Stress components(s)

Display corner data on: Integration point results are extrapolated to the element corners. This is equivalent to POSITION=NODES in Abaqus.

Display corner data off: Integration point results are averaged as the base result of the element. This is equivalent to POSITION=CENTROIDAL in Abaqus.

With "IP" suffix

For example: Global S-Stress components IP (t)

Display corner data on: Integration point results are displayed at the nearest element corners.

Display corner data off: Integration point results are averaged as the base result of the element.


•

Reader Options in HyperView•

Load Model panel, Reader Options button:

•

Available reader options for ABAQIS ODB Reader:


Options for “Element results position”

All -

(default) reads both the extrapolated corner (POSITION=NODES) and the integration point (POSITION=INTEGRATION POINTS) results.

Auto -

reads the extrapolated corner results for Abaqus

Standard analysis and integration point results for Abaqus

Explicit analysis.

Extrapolate -

reads only the extrapolated corner results.

Integration Points -

reads only the integration point results.


•

Available averaging methods in HyperView


NoneNo averaging method is used. Color will be displayed in element-based results, a solid color for centroidal

results, or multiple color bands within an element.

SimpleTensor and vector components are extracted and the invariants are computed prior to averaging.

Advanced

Tensor or vector results are transformed into a consistent system and then each component is averaged separately to obtain an average tensor or vector. The invariants are calculated from this averaged tensor or vector.

DifferenceThe difference between the maximum and minimum corner results at

a node is contoured.

Use variation (%)The relative difference at a node from corresponding corner values with respect to the value range from all nodes in the selected components is shown.


Result type: Global S-

Stress components IP (t)

Use corner data: off

Averaging method: none





Use corner data: on

Averaging method: none





Use corner data: on

Averaging method: simple





Use corner data: on

Averaging method: advanced





Use corner data: on

Averaging method: simple

Variation: 75%



•

Complex results are animated in Modal Animation Mode,•

Result types that are complex have a suffix of (c) •

Complex Filter option in Contour Panel appears when in Modal Animation Mode

•

Complex Filter selections:•

mag*cos(ωt-phase)

The response with varying angle or ωt

(in degree)•

Mag

Magnitue

(r) of the complex result•

Phase

Phase

of the complex number•

Real

Real

part (x) of the complex number•

Imaginary

Imaginary

part (y) of the complex number

Post Processing Complex Results


•

Viewing Complex Results at certain angle•

Current angle field in Animation Controls panel,

•

Controlling the angular increment when animating complex results•

Angular Increment field in Animation Controls panel,

Post Processing Complex Results


Appendix: Results Visualization for Abaqus



Results Visualization for ABAQUS

Using the AbaqusODB UpGrade tool

In the animation mode:•

Loading input and ODB files for model data•

Naming convention for result types, components and invariants for results from ODB file

•

Understanding support of different POSITION results, i.e. POSITION=INTEGRATION POINTS, POSITION=NODES

•

Understanding Abaqus

systems in HyperView•

Creating and overlaying contour and vector plots

In the plot mode, creating XY plots of history data from ODB files


AbaqusODB UpGrade Tool

•

HyperView’s 11.0 animation and plot modes support version 6.8 ODB files

•

AbaqusODB UpGrade Tool converts older version ODB files to v6.8

•

Access the AbaqusODB UpGrade Tool from the Start Menu•

Start > All Programs > Altair HyperWorks

11.0 > Tools > AbaqusODB

Upgrade > Abaqus

ODB Upgrade


Loading Abaqus input and ODB files into HyperView

In the animation mode:

•

Load either input file or ODB file for model data

•

For the input file•

Components display is similar to HyperMesh•

Component names, and ids are maintained

•

In most cases, loading the input file for model data is recommended

•

Load version 6.8 ODB file for result data

In the plot mode:

•

Load version 6.8 ODB file to plot history data

•

Naming convention for history data is

[data type] (Time History)

Date post:	13-Apr-2015
Category:	Documents
Upload:	treyturner3340
View:	180 times
Download:	10 times

HW11 AbaqusInterface Final PPT

Documents