hm90 intro day1 folien

8/4/2019 HM90 Intro Day1 Folien

1/22

12/18/2008

1

Copyright 2008 Altair Engineering, Inc. All rights reserved.Altair Proprietary and Confidential Information

HyperMesh Introduction: Starting HyperMesh

On PC:

Start > Programs > Altair HyperWorks > Altair HyperMesh

Shortcut icons

Go to \hm\bin\

Right-click hmopengl.exe > create shortcut

New shortcut can be renamed, drag and dropped, etc.

Windows 2000, XP, Vista etc. can create shortcuts from the Start menuicons

On UNIX:

At the prompt, type /scripts/hm

Can set up an alias


HyperMesh Introduction: Starting Directory

By default, HyperMesh uses the start directory for files

Reads configuration files (hm.mac, hmmenu.set, etc.)

Writes history (command.cmf)

Open/save HyperMesh model, FE data, and geometry data files

Start directory determined by: On PC, specified by the programs icon

Right click the icon

Go to Properties

Go to the Shortcuttab

A path is specified for Start In:

On UNIX:

Start directory is the directory where you typed the command to runHyperMesh

If configuration files are not found in the start directory, HyperMesh willthen look in the users home directory


2/22

12/18/2008

2


Panels: General Layout

Panels often have sub-panels

Accessed by radio buttons on the left side of the panel

Panels generally work from left to right

Example: Project / to planesub-panel

1) What to do:

Pick a sub-panelfor the functionto be used

2) What to do it to:

Select entities thatwill be affected

3) How to do it:

Give parametersthat define howthe function willbe executed

4) Do the action:

Execute thefunction


Panels: General Layout

Some sub-panels are organized in columns

Each column is a different method

Work from top to bottom in the relevant column

Example: surface edit : trim with surfs/planesub-panel

1) What to do:

Pick a sub-panelfor the functionto be used

3) What to doit to:

Select entitiesthat will beaffected

4) How to do it:

Give parametersthat define howthe function willbe executed

5) Do theaction:

Execute thefunction

2) Method touse:

Work in theappropriatecolumn


3/22

12/18/2008

3


Model Organization: HyperMesh Entity Types

Geometry

Points

Lines

Surfaces

Solids

Connectors (used for welding)

FE Model

Nodes

Temp Nodes (marks a node with a small circle) Elements

Points

LinesSurfaces

Nodes Elements

Temp Nodes

Solids



FE Loading

Loads (constraints, forces, pressures, etc.)

Equations (mathematical link between nodes)

Contacts

Group (defines contact between entities)

Contact Surfs (defines a list of entities that can beused as master or slave in a group)

Constraints

Forces

Pressures

ContactSurface


4/22

12/18/2008

4



Multibodies

Ellipsoids (defines a shape for rigid bodies)

Mbplanes (defines a shape for rigid bodies)

Mbjoints (defines the connection of 2 rigid bodies)

Safety

Sensors (defines a trigger to start an event)

Control Volumes (defines airbags)



Coordinate Entities

Systems (coordinate axes)

Vectors

Reference Entities

Sets (a simple list of a particular type ofentity)

Blocks (a list of entities contained within abox shape)

1D Element Cross Sections

Beam Sections (cross sectionalproperties for a property collector)

Systems

Beam Section

Vectors


5/22

12/18/2008

5



Plotting

Curves (X-Y data)

Plots (a display of curves with axes)

Output Requests

Loadsteps (combinations of load collectors)

Output Blocks (request output from ananalysis for certain entities)

Labels Titles (label for a displayed item)

Tags (assigns a name to an entity) TTTT aaaa gggg ssss

TTTT iiii tttt llll eeee ssss

Plot with a Curve



Morphing

Handles controls model shape during morphing

Domains divides a model into regions (for domain based morphing)

Morph volume A cube shaped volume that morphs all entities that arelocated inside the shape (for volume based morphing)

Morph constraints Control the motion of nodes during morphing

Symmetries forces regions to be morphed symmetrically

Shapes model state during morphing saved for retrieval at a later point

Symmetries

Handles

DomainsMorph Volume


6/22

12/18/2008

6



Optimization

Designvars Variables that are changed during optimization (ex: thickness)

Optiresponses Values being measured (ex: von Mises stress)

Objectives Responses to maximize/minimize (ex: minimize weight)

Dobjrefs Objective reference response for minmax/maxmin optimization (ex:minimize maximum von Mises stress)

Opticonstraints Limitations (ex: von Mises stress < Yield stress)

Optidscreens Filters constraints to reduce computation time

Dvprels Relationships between design variables and properties

Desvarlinks Relationships between design variables

Dequations A calculated value to be measured Optitableentrs Table of constants

Opticontrols Parameters to control the optimization algorithms

DDVals Sets a discreet range of values to be used in a Designvar


Model Organization: Collectors

The HyperMesh model is organized using collectors

There are many types of collectors

Most entities in HyperMesh must be placed in a collector

Each collector type holds a specific type of entity

Collector Types Can contain entity types:

Component Elements, Points, Lines, Surfaces, Connectors

Multibody Ellipsoids, Mbjoints, Mbplanes, Sensors

Assembly Components, Multibodies, Assemblies

Load Collector Loads, Equations

Material none (materials and properties dont contain other entities but are

still treated as collectors)Property

System Collector Systems

Vector Collector Vectors

Beam Section Collector Beam Sections


7/22

12/18/2008

7



An entity can usually only belong to 1 collector of a given type

Ex: an element can only be in 1 component collector

Can create many collectors of the same type

All entities in a collector are the same color

Organization can be however the user desires

1 component per part Multiple components per part

Component 1

Component 2

Component 3

Component 1 Component 2

Component 3

Component 4



Model browser

View collectors and assemblies in a hierarchicaltree format

Create, delete, and rename collectors

Edit collector attributes

Organize collectors into assemblies

Drag and drop

Right-Click on

Collector for

advanced

options


8/22

12/18/2008

8



New entities are created in the current collector

Creating a new collector automatically sets the current collector to that newcollector

Model Browser or can be used to change the current collector.

Include Browsercan be used to change the current include.

Organizepanel can be used to move entities into a different collector

Bold Current Collector

Bold Current Include


Model Organization: Tools

Panels

Collectors Create new collectors

Model Browser Set the current collector for various entity types

Organize Move entities into a different collector than the one they are currentlycontained in

Rename Change the name of an existing collector

Reorder

Collectors appear in a certain order when presented in a list to pick from

Reorderallows the order the collectors appear in to be changed

Delete Delete entities or collectors


9/22

12/18/2008

9


Display Control: Viewing: Toolbar

Pan

Center (C)

Rotate Left

Rotate Right

Rotate Up

Rotate Down

Rotate Clockwise

Rotate Counter Clockwise

Dynamic Rotate (A)

Dynamic Spin (R)

Manually rotate by grabbing a point and dragging

Rotate relative to the mouse cursor and screen center

Pan the model

Select and click on the screen to re-center model ingraphics window

Incremental rotations in respective directions


Automeshing: What is it?

The automeshpanel creates shell mesh on existing surfaces

Allows rapid generation of mesh

Most parts from CAD software come in as surfaces

Automeshing allows all surfaces of a part to be meshed at the same time

Mesh on properly connected geometry assures proper connectivity of mesh


10/22

12/18/2008

10


Automeshing: What is topology?

Topology is how surfaces connect to adjacent surfaces of a part

Surface connectivity is controlled by the associated surface edges

If a surface edge is associated with more than 1 surface, those surfaces areconsidered to be connected (equivalenced)

Surface edges are categorized, named, and colored according to the number ofassociated surfaces:

Free edge (red) Associated with only 1

surface Surfaces with a free edge

between them are NOT

equivalenced at that edge

Shared edge (green) Associated with 2 surfaces

Surfaces are equivalenced

Suppressed edge (blue) Surfaces are treated as though

combined into 1 surface

T-junction edge (yellow) Associated with 3 or more

surfaces Example: surfaces forming a

T-connection

Surfaces are equivalenced


Automeshing: How topology affects the mesh

Surface edges control how mesh created on adjacent surfaces interact:

Free edge between2 surfaces

Nodes are placed alongedge for meshing

Mesh is discontinuous;nodes along the free edgeare not equivalenced(Nodes only separated forillustration)

5

5

5

2

2 3

3

Shared edge between2 surfaces

Mesh has properconnectivity; nodes alongthe edge are equivalenced


Free edges (red) Shared edges (green)

5

5

5

2

2 3

3

5


11/22

12/18/2008

11


Automeshing: How topology affects the mesh

Surface edges control how mesh created on adjacent surfaces interact:

Suppressed edgebetween 2 surfaces

Edge is ignored; nodesare not placed alongthe edge

Area is treated just like 1surface; there is no lineof nodes along the edge

Non-manifold edgebetween 3 surfaces

Mesh has properconnectivity; nodes alongthe edge are equivalenced


5

5

55

5

5

5

5

4

43

3

33

Suppressed edges (blue) T-junction edges (yellow)


Automeshing: Process and Strategy

Use geometry cleanup tools to address surface connectivity

Automesh the surfaces

Set the approximate element size you want

Use typeand algorithmto set the overall mesh style

Alter individual densities to find better mesh patterns

Change some biasing on problem surfaces (this can change mesh pattern aswell)

Use HyperMeshs mesh editing tools to fix the 10-20% elements that havepoor quality or bad mesh pattern

Dont delete a mesh that is 90% good. Keep it and fix the 10% that is bad

Experience is key: EXPERIMENT!

Goal: get the mesh to be approximately 80-90% good quality


12/22

12/18/2008

12


Batch Meshing: Introduction

Performs geometry cleanup and automeshing in a batch mode

Can dramatically improve productivity since there is minimal user interaction(especially for large assemblies)

Uses criteriaand parameterfiles to determine how the parts should bemeshed

Can mesh multiple files in the same run


Batch Meshing: Process & Required Input

1. Create / specify Configurations

Combination of element criteria andgeometric parameters

Element criteria are elementquality requirements

Geometric parameters areother requirements (elementtype, removal of pinholes,removal of fillets, etc.)

Criteria and parameters can beedited with the Criteria andParameters Files Editor


13/22

12/18/2008

13



2. Register and specify User Procedures(optional)

Custom TCL scripts (macros) created by the user

Performs additional operations on models during the batch run

Pre Runand Post Runoptions can specify procedures performed before or afterthe run

Can specify when the procedure should be performed during the run

Pre-geometry load as soon as batch mesher is invoked

Pre-batch mesh just before loaded geometry is meshed

Post-batch mesh after meshing is finished

3. Set up the Batch Meshjob

Specify a directory where geometry files are located

Select geometry files from the directory Select a configuration to use for the mesh type for each file

Specify any user procedures to be performed on each part

Specify a directory where the meshed files will be located

Run the batch mesh job



4. Monitor the Run Statusof the job

Use the Run Statustab to keep track of all your submitted jobs

Use Load Meshto open a selected file in a new HyperMesh session to view theresulting mesh


14/22

12/18/2008

14


Analysis Setup: What is it?

Definition of all information for an analysis besides the mesh

Specification of solver to be used

Creation materials, properties, etc.

Assignment of a solver specific format to HyperMesh entities

Creation boundary conditions (constraints, loads, contacts, etc.)

Definition of other required information (solution requests, general runparameters, etc.)


Analysis Setup: HyperMesh Capabilities

HM is asolver neutral pre-processor

Works with many different solvers

Can convert between supported solvers

Capable of assembly from input files of different solvers

Can be customized to support other solver codes

Can set up many types of analysis

Structural (Stress, NVH, Durability, Non-Linear Structural)

Radioss (Linear), Abaqus, Nastran, Ansys, Marc, nSOFT

Manufacturing (Flow / Mold-Filling, Extrusion)

Moldflow, CMold, HyperExtrude

Safety (Impact / Crash, Occupant Safety)

Dyna, Pamcrash, Radioss, Madymo

Optimization (Topology, Topography, Shape, Size / Gauge)

OptiStruct, Nastran


15/22

12/18/2008

15


Solver Formats: Interacting with Solvers

HyperMesh interacts with many solvers

Each solver has its own unique formats, terminology, etc.

Example: compare nodes and elements in Abaqus and OptiStruct / Nastran

3 nodes

2 quad elements

Format / structure is obviously different

*NODE

1, 0.0 , 1.0 , 0.0

2, 0.0 , 0.0 , 0.0

3, 1.0 , 0.0 , 0.0

*ELEMENT,TYPE=S4,ELSET=part_1

1, 1, 2, 3, 4

2, 3, 4, 5, 6

GRID 1 0.0 1.0 0.0

GRID 2 0.0 0.0 0.0

GRID 3 1.0 0.0 0.0

CQUAD4 1 1 1 2 3 4

CQUAD4 2 1 3 4 5 6

Radios (Linear) Abaqus


Solver Formats: HyperMesh Templates

HyperMesh can interact with different solvers by using templates

The selected template tells HyperMesh what solver the model is for

The template also tells HyperMesh how entities are formatted for that solver

Each entity may have several available formats for that solver

Each format has fields that make up its definition These fields may need to have values entered by the user

Example: a component for Radioss (Linear) can be a PSHELL or PSOLIDformat

PSHELL: holds shell elements, ID = 1, material = 1, thickness 5.0

PSOLID: holds solid elements, ID = 2, material = 1

PSHELL 1 15.0 1 1 0.0

PSOLID 2 1 0


16/22

12/18/2008

16


Solver Formats: Solver Formats for Collectors

Collectors format is specified by loading a card image

HyperMeshCollectorType:

Example solver keywords available as element types:

Radioss (Linear) LS-Dyna Abaqus

ComponentPSHELL, PSHEAR,PSOLID, PCOMP

*PART *SHELL SECTION,*SOLID SECTION,

*RIGID BODY, etc.

Property

PBAR, PBEAM,

PGAP, PELAS, etc.

*SECTION_SHELL,

*SECTION_SOLID,*SECTION_BEAM, etc.

*SURFACE

INTERACTION,*FRICTION, etc.

Material

MAT1, MAT2, MAT4,

MAT8, MAT9, MAT10

*MATL1, *MATL2,

*MATL3, etc.

*MATERIAL, *GASKET

BEHAVIOR, etc.


Solver Formats: Solver Formats for Elements

Elements format is specified by setting an element type

HyperMeshElementConfiguration:



Bar

CBEAM, CBAR,CBEND

*ELEMENT_BEAM *ELEMENT, TYPE= B31,B31H, B33, B33H, etc.

Quad4

CQUAD, CQUADR,

CSHEAR

*ELEMENT_SHELL *ELEMENT, TYPE= S4,

S4R5, M3D4, M3D4R,

R3D4, DS4, etc.

Tetra4

CTETRA *ELEMENT_SOLID *ELEMENT, TYPE=

C3D4, C3D4H, DC3D4,

C3D4E, DC3D4E


17/22

12/18/2008

17


Solver Formats: Solver Formats for Loads

Loads format is specified by setting a load type

HyperMeshLoadConfiguration:



Constraint

SPC, SPCD, ASET,

ASET1, SUPPORT,

QSET1, etc.

*BOUNDARY_SPC_NODE,

*BOUNDARY_

PRESCRIBED_MOTION_

NODE

*BOUNDARY,

*BOUNDARY, TYPE=

ACCELERATION,VELOCITY, etc.

Force FORCE *LOAD_NODE_POINT *CLOAD

Pressure

PLOAD, PLOAD2,PLOAD4, QBDY1

*LOAD_SHELL_ELEMENT,*LOAD_SEGMENT

*DLOAD, *DFLUX,*FILM, *DECHARGE


Solver Formats: Tools

Preferences>User Profiles

Loads the appropriate template for that solver

Template can also be set manually

Filespull down > Load> template file

g on the keyboard (Global Panel)

Sets the files> import> fesub-panel to theappropriate file type

Loads a macro menu with tools specific toworking with that solver

Customizes the HyperMesh menu

Removes panels that are not used with that solver

Removes controls inside a panel that are not used with that solver

Renames some panels & controls in panels to match solver terminology


18/22

12/18/2008

18



Collectorspull-down and collectorspanels

Create

Assign a card image to the collector being created

Edit the card image fields if desired

Assign a material to the collector being created

Update

Assign a material to an existing collector

Assign and/or edit a card image of an existing collector

Elem types> load typespanels

Set a current element / load type for an element / load configuration

Any new elements / loads of that configuration created will have that element/ load type

Change the element / load type of existing elements / loads



Collectors>Card Editor toolbar >

View / edit the card image of any entity in the model

Includes entities that are not collectors (nodes, elements, loads, etc.)

Model Browser

Right click a collector and select edit card View / edit the card image of the selected collector

Preferences>graphics

template labels type

Activate the graphic displayed names of entities in solver (template)terminology rather than HyperMesh (solver neutral) terminology

Helps keep track of what is in the model


19/22

12/18/2008

19



Solver Browser

Displays solver-based cards in a tree format

Uses organization & structure of the representedsolver

Performs basic actions involving cards

Create new cards

Delete existing cards

Edit attributes of existing cards

Solver Browser can be found in the Viewpull-downmenu



Summarypanel

Displays a text window with various types of information about the model

Helps to review the model and make sure all information has been enteredproperly

Summary Type Included Information

Components Component Name, ID, Material Name, Thickness, Mass,#Elements

Center of Gravity Component Name, ID, Mass, X, Y, Z

Elements Type of Elements, Element Configurations

Error Checks Load Collector, Load Steps, Components

Loads Load Collector, ID, FX, FY, FZ, Magnitude

Moment of Inertia Moment of Inertia


20/22

12/18/2008

20


Solver Formats: Process

1. Create the entities needed for your model

Keep in mind what is needed for the solver and analysis being used

Entities need to be properly organized in collectors

All entities in a collector share the same attributes

2. Load the proper card image or type where needed

Generally use the Setup/collectors, elem type, or load type panel

Elements and loads will always have a type

Sometimes collectors may not need a card image


Solver Formats: Process

3. Enter values in the card images as required

Use or Collectors>Card Editorpanels to check card imagesof all collectors

Some card images require other entities to be selected as a reference

Example: Dyna requires a components card image to point to a propertycollector for thickness information, etc.

Understand the details of how HyperMesh interacts with your solver

Refer to the External Interfacing portion of online help for details

Altair has training classes for interfacing with some solvers

Contact Altair support for additional questions

The goal in formatting for analysis is:

All entities have the proper formats (card image / type)

Card images of all entities have necessary information entered


21/22

12/18/2008

21


Boundary Conditions: Supported Entity Types

FE Loading

Loads (constraint, force, pressure,moment, temperature, flux, velocity,acceleration)

Equations (mathematical linkbetween nodes)

Contacts

Group (defines contact betweenentities)

Contact Surfs (defines a list ofentities that can be used as master orslave in a group)

Reference Entities Sets (a simple list of a particular type

of entity)

Blocks (a list of entities containedwithin a box shape)

ConstraintsForces

Pressures

ContactSurface


Boundary Conditions: Supported Entity Types

Coordinate Entities

Systems (coordinate axes)

Vectors

Plotting

Curves (X-Y data)

Plots (a display of curves with axes)

Output Requests

Loadsteps (combinations of loadcollectors)

Output Blocks (request output from ananalysis for certain entities)

Control cards (job-level, global parametersfor the analysis)

Vectors

Systems

Plot with a Curve


22/22

12/18/2008


Boundary Conditions: Tools

Analysis page

Analysis page is devoted to setting up analyses

User profile macro menus

User profiles add macro menu pages with tools specific to that solver

Abaqus Step Manager, Contact Manager, Component Browser

Ansys Contact Wizard, Component Manager, etc.

LS-Dyna Name Mapping, Constrained Rigid Body, Content Table, etc. Nastran Subcase Manager, Part Info, 1D Property Table, etc.

Radioss Bulk / OptiStruct Subcase Manager, Component Table, etc.

Radioss Block D01 Tool, Sections, Component List, Material table, etc.

etc.


Boundary Conditions: Loads on Geometry

Loads can be created on geometry as well as FE entities

Set the entity selector to a geometry entity

Create the load

Create the mesh

Create load ongeometry

Create themesh

Map the load tothe mesh

Use the load on geompanel to mapthe loads from the geometry to the

elements

hm90 intro day1 folien

Documents