Hyperworks 9.0 User'S Guide Abaqus Solver Interface

HyperWorks 9.
0 User's Guide
Abaqus Solver Interface
Altair Engineering Contact Information
Web site www.altair.com
FTP site Address: ftp.altair.com or ftp2.altair.com or http://ftp.altair.com/ftp

Login: ftp
Password: <your e-mail address>
Location Telephone e-mail

North America 248.614.2425 hwsupport@altair.com
China 86.21.5393.0011 support@altair.com.cn
France 33.1.4133.0992 francesupport@altair.com
Germany 49.7031.6208.22 hwsupport@altair.de
India 91.80.6629.4500 support@india.altair.com
1.800.425.0234 (toll
free)
Italy 39.800.905.595 support@altairengineering.it
Japan 81.3.5396.2881 support@altairjp.co.jp
Korea 82.31.728.8600 support@altair.co.kr
Scandinavia 46.46.286.2052 support@altair.se
United Kingdom 44.1926.468.600 support@uk.altair.com
Brazil 55.11.3884.0414 br_support@altair.com
Australia 64.9.413.7981 anzsupport@altair.com
New Zealand 64.9.413.7981 anzsupport@altair.com
The following countries have distributors for Altair Engineering: Mexico, Romania, Russia, South Korea,
Singapore, Spain, Taiwan, and Turkey. See www.altair.com for complete contact information.
© 2008 Altair Engineering, Inc. All rights reserved. No part of this publication may be reproduced,
transmitted, transcribed, stored in a retrieval system, or translated to another language without the written
permission of Altair Engineering, Inc. To obtain this permission, write to the attention Altair Engineering legal
department at: 1820 E. Big Beaver, Troy, Michigan, USA, or call +1-248-614-2400.
Trademark and Registered Trademark Acknowledgments

® ® ©
Listed below are Altair HyperWorks applications. Copyright Altair Engineering Inc., All Rights Reserved
for:
® ®
HyperMesh 1990-2008; HyperCrash™ 2001-2008; OptiStruct 1996-2008; RADIOSS™ 1999-2008;
® ® ® ®
HyperView 1999-2008; HyperView Player 2001-2008; HyperStudy 1999-2008; HyperStudy DSS 2002-
2008; HyperGraph 1995-2008; HyperGraph 3D 2005-2008; MotionView 1993-2008; MotionSolve® 2002-
® ® ®
® ®
2008; HyperForm 1998-2008; HyperXtrude 1999-2008; FEModel™ 2004-2008; Process Manager™ 2003-
2008; HyperDieDynamics™ 2007-2008; Templex™ 1990-2008; Data Manager™ 2005-2008; MediaView™
1999-2008; Batch Mesher™ 2003-2008; TextView™ 1996-2008; Manufacturing Solutions™ 2005-2008.
All other trademarks and registered trademarks are the property of their respective owners.
HyperWorks 9.0 User's Guide - Abaqus Solver Interface
HyperMesh Interface
...........................................................................................................................................
with the Abaqus Solver 1
Changes in...............................................................................................................................................
Sectional Property Handling 3
Importing ............................................................................................................................................... 5
By HM Comment
............................................................................................................................................... 5
Support of Include Files
............................................................................................................................................... 5
Templates............................................................................................................................................... 9
Summary Templates
............................................................................................................................................... 9
HyperMesh Entities
............................................................................................................................................... 11
Control Cards
............................................................................................................................................... 11
Coordinate Systems
............................................................................................................................................... 11
Curves
............................................................................................................................................... 11
Elements
............................................................................................................................................... 11
Groups
............................................................................................................................................... 11
Load...............................................................................................................................................
Collectors 11
Loads
............................................................................................................................................... 11
Load...............................................................................................................................................
Steps 11
Materials
............................................................................................................................................... 11
Multi-point Constraints
............................................................................................................................................... 11
Nodes
............................................................................................................................................... 11
Output Blocks
............................................................................................................................................... 11
Properties
............................................................................................................................................... 11
Sets............................................................................................................................................... 11
Abaqus ...............................................................................................................................................
Utility Menu 101
Component Browser
............................................................................................................................................... 101
Contact Manager
............................................................................................................................................... 101
Dummy Import/Export
............................................................................................................................................... 101
Set...............................................................................................................................................
Browser 101
Solid Face Alignment
............................................................................................................................................... 101
Step Manager
............................................................................................................................................... 101
Results ...............................................................................................................................................
Translation 215
Translating Complex Results
............................................................................................................................................... 215
Translating Element Results for Different Positions
............................................................................................................................................... 215
Supported Result Types
............................................................................................................................................... 215
Include File Support
............................................................................................................................................... 215
Free Body Diagram
............................................................................................................................................... 215
Supported Keywords
............................................................................................................................................... 229
Altair Engineering HyperWorks 9.0 User's Guide - Abaqus Solver Interface i
Proprietary Information of Altair Engineering

Unsupported Data Blocks
............................................................................................................................................... 235
Abaqus ...............................................................................................................................................
to/from Nastran Mapping 237
HyperWorks Desktop
...........................................................................................................................................
Interface with the Abaqus Solver 245
HyperView Overview
............................................................................................................................................... 247
Model Data
............................................................................................................................................... 247
Result Data from ODB
............................................................................................................................................... 247
Parts and Instances in the ODB File
............................................................................................................................................... 247
MotionView
............................................................................................................................................... 269
Exporting MDL Model Files to Abaqus
............................................................................................................................................... 269
HyperGraph
............................................................................................................................................... 279
ODB History Results in the HyperView Plot Window
............................................................................................................................................... 279
ii HyperWorks 9.0 User's Guide - Abaqus Solver Interface Altair Engineering

HyperMesh Interface with the Abaqus Solver
This section describes the Abaqus input translator, the output template, summary templates, and the result
translator in HyperMesh.
· By selecting the Abaqus user profile, you can work with pre-defined panels that are more specific
to Abaqus usage. The User Profiles dialog is launched by default when HyperMesh is started the
first time.
These are some general comments about HyperMesh interface with Abaqus:
Import and · The Abaqus interface supports Abaqus version 6.7

Export
· The Abaqus input translator supports free and fixed formats, however, the export
template writes all cards in free format. An import option also exists to read all
input data as free format.
· HyperMesh places all elements into separate components, based on sectional

property. Each component is written out from HyperMesh as element set in the
Abaqus input deck.
· Although HyperMesh supports 160 characters in entity names, Abaqus output

files are truncated at 80 characters to match the Abaqus name support level.
· The loads and constraints are organized under load collectors in HyperMesh.
These load collectors need to be added to a load step for the *STEP card in
Abaqus history definition. If a **HMLOAD_SETS_EXPAND comment is found in
the input file, all loads and boundary conditions on sets are expanded to
individual nodes and elements.
· The output options are organized under output blocks in HyperMesh. These
output blocks also need to be added to load steps.
· When HyperMesh encounters an **HM_GENERATE_SET_EXPAND in the input

file, all sets with the GENERATE parameter are imported as regular sets. This is
useful for when node/element IDs are renumbered during import.
Syntax · HyperMesh supports some abbreviated key words and parameters.
· All Abaqus keywords and parameters supported in HyperMesh are case

insensitive.
· HyperMesh ignores spaces in keyword lines.
· HyperMesh supports quotation marks around component (ELSET with sectional

properties) names, which is especially useful for names that begin with a
number.
HyperMesh · Warnings and error messages are written to a file named abaqus.msg.
Operations Unrecognized lines are written to a *.hmx file. These files are created in the
Altair Engineering HyperWorks 9.0 User's Guide - Abaqus Solver Interface 1

same directory from where HyperMesh is launched.
· Step time calculations can differ between HyperMesh and Abaqus (Explicit
analyses), so you may find differences between reported values in the Abaqus
status (.sta) file and the time sub-panel of the check elems panel in
HyperMesh. The values reported by HyperMesh are close estimates of the step
time; refer to the Abaqus documentation to learn more about the factors that
Abaqus/Explicit uses to reach the final result.
2 HyperWorks 9.0 User's Guide - Abaqus Solver Interface Altair Engineering

Changes in Sectional Property Handling
Changes in Sectional Property Handling in HyperMesh Abaqus interface 9.0

This document explains the major changes in the handling of Abaqus sectional properties (e.g. SHELL
SECTION, SOLID SECTION) in the Abaqus interface.
Introduction
Starting in HyperMesh 9.0, sectional properties, such as SHELL SECTION, are defined by the card image
of a property collector. In previous versions sectional properties were defined within a component collector.
Elements still belong to a component collector. Their property assignment can now be made either by
assigning a property to a component or to individual elements.
In common cases, elements get their property from the card image of the property collector, which is
assigned to the component they belong to. Elements can be assigned individually to property collectors by
using the assign sub-panel of the property collectors panel. This is useful to get better performance for
models that have a huge amount of properties, such as composite models or models with many beam
elements. For both ways, properties of the model can be visualized by coloring with the by Prop option
from the toolbar or the Properties View option in the Model Browser.
Assigning an element directly to a property always takes precedence over the property the component
collector of this element is pointing to.
Export
On export *ELEMENT card will be written from every component. The sectional property will be written
from the property collector itself. In addition, HyperMesh automatically creates ELSETs of the elements,
which are individually assigned to a property. In the regular case, properties are assigned to a component,
the name after the ELSET parameter in the sectional property will be the component name. In the case of
individual element assignment, the property will point to the ELSET, automatically created by HyperMesh.
To ensure the maintenance of the model organization during an export and a following import of the model,
a comment is written before each sectional property. **HM_comp_by_property is written, if the property is
assigned to a component. This comment also contains the name of the property collector and its color.
**HM_set_by_property and the color of the property collector are written in front of the properties, which are
assigned individual to each element. In all cases component collector color is maintained by a comment in
front of the *ELEMENT card.
Import
Also new to HyperMesh 9.0 are the import options by HM Comment, by Property and by 1 Component.
For details please refer to the related help topic of this online manual.

Importing
The Import Options button opens a dialog with the following options available:
Generic material: Import a model in the generic material mode, in which all material sub-options,
parameters, and data lines are supported as simple text.
Free format: HyperMesh can read in mixed free- and fixed-format data. Select this option to force
HyperMesh to interpret all data as free format in the imported model.
Coupling as groups: Import *COUPLING cards as groups. This option maintains the constraint and
surface names but might be slow when many *COUPLING cards are in the model.
Expand loads on sets: All loads on sets are expanded to individual nodes/elements.

By HM Comment
When importing Abaqus files, you can use the By HM Comment option, understanding the following items:
· If available, HyperMesh will consider comments written during a previous model export from
Version 9.0.
· If neither **HM_comp_by_property nor **HM_set_by_property comments are present, HyperMesh

creates a component and a property collector for every element set (ELSET) that points to a
sectional property. Both collectors will have the name of the referenced element set.
· If a comment such as **HM_comp_by_property “<property name>” <color> is found before a

sectional property (e.g. *SHELL SECTION) is found, a component with the name of the referenced
element set will be created. At the same time, a property collector will be created, which defines
the sectional property of the component (property assignment on component level). Its name will
be taken from the HyperMesh comment.
· If an **HM_set_by_property comment is found, HyperMesh will create a property collector, which

defines the sectional property of the elements mentioned in the element set (property assignment
on element level). In addition, the elements will be placed into the component they were in before
exporting. If present, the prefix “HMprop_” will be stripped on import.

Support of Include Files
Many FEA solvers allow you to organize your input deck into separate files and provide a mechanism to
include all the files in a single input deck. This capability is commonly known as "include" capability.
HyperMesh allows you to import such models for Abaqus.
HyperMesh’s Include Browser allows you to create, review, edit, organize, and update the contents of a
model into various include files.
The following rules and considerations apply to the Abaqus include file support in HyperMesh:
· Include files must include complete information for each keyword. A keyword and its data lines
must be part of the same file.
· Include files must contain complete information for cards that contain multiple sub-keywords. For
example, all sub-keywords and their data lines in a *Material card must be part of the same include
file.
· Include files must contain complete information for *Step cards. All history keywords and their data
lines must be a part of the same file.
· The HyperMesh Abaqus interface is comprised of four types of include files: Model (start), Model
(middle), Model, and History. They define the sequence of the *Include keywords in the model.
Model (start) type of include files are written at the beginning of the deck, after the *Node block.
Model (middle) is written in the middle of the deck, after the *Material block. Model is written at
the end of the model definition, and History keywords are written after the model definition.
· Include file names are sorted according to their names in the browser. The sequence in the
exported model is primarily determined by the four types of includes files as described above.
Within each type the sequence is determined by the order in which they are created.
· The Abaqus syntax for the include file path is:
In Abaqus, file names can include a full or relative path name. Relative path names must be in
relation to the directory from which the job was started. If a path is not specified, it is assumed that
the file is located in the same directory from which the job was submitted.
From HyperMesh, it is, however, not always possible to predict the directory from which the job will
finally be submitted. Therefore a relative path must be defined. This relative path should be defined
with respect to the folder where the corresponding *Include keyword appears. If you run the job
from a different folder in subsequent runs, you must also update the path name.

Templates
The following templates can be used to generate Abaqus input decks:
Standard.2d Generates a deck for two-dimensional models containing planar or

axisymmetric elements for use with Abaqus Standard.
Standard.3d Generates a deck for three-dimensional models containing bar, shell, and
solid elements for use with Abaqus Standard.
Explicit Generates a deck for use with Abaqus Explicit.

Summary Templates
The following summary templates are available for Abaqus:
elements.2d Summarizes the number and type of 2-D elements in the current
HyperMesh database.
elements.3d Summarizes the number and type of 3-D elements in the current
HyperMesh database.
elements.exp Summarizes the number and type of elements in the current

HyperMesh model for an Abaqus Explicit analysis.
loads Summarizes the forces and moments applied to the current model.
ctr_of_gravity Calculates the center of gravity of the model.
components Summarizes the component information in the current HyperMesh

database.
mom_of_inertia Calculates the moment of inertia of each component of the model

as well as the moment of inertia of the entire model.

HyperMesh Entities
The following entities are supported by Abaqus:
Control Cards
Coordinate Systems
Curves
Elements
Groups
Load Collectors
Loads
Load Steps
Materials
Multi-Point Constraints
Nodes
Output Blocks
Properties
Sets

Control Cards
In HyperMesh, Control Cards define model information, which needs to be specified only once in the input
file. The following Abaqus keywords are supported as Control Cards:
Abaqus Card Supported Parameters
*CONSTRAINT NO CHECKS and NO CHANGES

CONTROLS
*DEPVAR
*HEADING
*PREPRINT CONTACT, ECHO, HISTORY, and MODEL
*RESTART READ, WRITE, STEP, INC, END STEP, FREQUENCY and

OVERLAY
To create a *RESTART card as model data
1. From the Setup drop down menu, select Create and select Control Cards.
2. Click the RESTART card you want to create.
3. Input the necessary information for the control card.
4. Click return.
To create a *RESTART card as history data
1. From the Setup drop down menu, select Create and select Load Steps.
2. Click name = and select a load step.
3. Click edit.
4. Check the Restart_Write option and input necessary information.
5. Click return.
6. Click return.

Coordinate Systems
The coordinate systems are defined from the systems panels in HyperMesh. A system in HyperMesh can
be exported as a *SYSTEM or *TRANSFORM card depending on the nodal assignment of the system. The
*ORIENTATION card is created from the card image of the system.
The following Abaqus (system) keywords are supported in HyperMesh:
Abaqus Card Supported Notes

Parameters
*ORIENTATION NAME, SYSTEM The *ORIENTATION card needs a name

in Abaqus. Since HyperMesh systems do
DEFINITION =
not have a name, the name of the system
COORDINATES
collector is used as the ORIENTATION
name by default. Therefore, each
ORIENTATION system should be placed
in its own system collector.
However, you can write a user-defined
name (up to 80 characters long) for each
ORIENTATION system by selecting the
User_defined_Long_name option in the
system card image.
*ORIENTATION
DEFINITION = NODES option with only
two nodes is converted to
DEFINITION=COORDINATES upon
import from an input file.
*ORIENTATION with SYSTEM = Z
RECTANGULAR is converted to
RECTANGULAR upon import from an
input file.
*SYSTEM On export, each *SYSTEM card is

followed by the nodes that are assigned to
the coordinate system as reference.
*TRANSFORM TYPE and NSET On export, each *TRANSFORM card

creates references to an automatically
generated *NSET card. This *NSET card
is followed by the list of the nodes that are
assigned to the coordinate system as
analysis.

To create a *SYSTEM card
1. Ensure that the local coordinate system is already created.

2. From the Analysis page, select systems.
3. Select the assign sub-panel.
4. Click nodes.
5. Pick the nodes that need to be defined in this coordinate system.
6. Click system.
7. Pick the coordinate system.
8. Click set reference.
9. Click return.
To create a *TRANSFORM card
1. Ensure that the local coordinate system is already created.

2. From the Analysis page, select systems.
3. Select the assign sub-panel.
4. Click nodes.
5. Pick the nodes that have dof directions defined using this coordinate system.
6. Click system.
7. Pick the coordinate system.
8. Click set analysis.
9. Click return.
To create an *ORIENTATION, DEFINITION=COORDINATES card
1. Ensure that a node-independent local coordinate system is already created.
2. Select the Card Edit icon .

3. Click the switch and select systs.
4. Click systs and select the system that you want to define as the *ORIENTATION.

5. Click edit.
6. Select the ORIENTATION option from the menu.
7. By default, the NAME for the *ORIENTATION card is taken from the name of the system collector.
However, you can select the User_defined_Long_name option to define a name (maximum 80
characters long).
8. Select the System_origin option to define the origin of a rectangular coordinate system in the dataline.
Note: The System_origin option is only supported in Abaqus 6.5 or later versions.
9. If necessary, select the locdir_alpha option to define an additional rotation.
10. Click return.
To create an *ORIENTATION, DEFINITION=NODES card
1. Ensure that a node-dependent local rectangular coordinate system is already created.

3. Click the switch and select systs.
4. Click systs and select the system that you want to define as the *ORIENTATION.
5. Click edit.
7. By default, the NAME for the *ORIENTATION card, is taken from the name of the system collector.
However, you can select the User_defined_Long_name option to define a name (maximum 80
characters long).
8. Select the System_origin option to define the origin node ID of the system in the dataline.
Note:
· The System_origin option is only supported in Abaqus 6.5 or later versions.
· The DEFINITION= parameter will become NODES only when System_origin is selected for a
node-dependent rectangular system. Otherwise, it remains COORDINATES.
9. If necessary, select the locdir_alpha option to define an additional rotation.
10. Click return.

Curves
The curves in HyperMesh are exported as *AMPLITUDE card in the Abaqus input file.
*AMPLITUDE NAME, DEFINITION = TABULAR, DEFINITION = SMOOTH

STEP/EQUALLY SPACED, TIME, VALUE, FIXED INTERVAL,
BEGIN

Elements
Standard.3d Template
Abaqus Card HyperMesh Supported Types

Configuration
*COUPLING Rigid COUP_KIN, COUP_DIS
*DISTRIBUTING Rigid DCOUP3D, MASS

COUPLING
*ELEMENT TYPE and ELSET
Mass/1 node MASS, ROTARYI, SPRING1, DASHPOT1,

CONN3D2
Rigid RB3D2
RBE3 DCOUP 3D, COUP_DIS
Spring SPRING2, SPRINGA, DASHPOT2,

DASHPOTA, JOINTC
Bar2 B31, B31H, B33, B33H, B31OS, B31OSH,

PIPE31, PIPE31H, GK3D2, GK3D2N, AC1D2,
ELBOW31, ELBOW31B, ELBOW31C
Bar3 B32, B32H, B32OS, B32OSH, AC1D3,

ELBOW32, PIPE32, PIPE32H
Rod T3D2, T3D2H, T3D2T, T3D2E, CONN3D2,

SFMAX1, MGAX1, SFMGAX1
Gap GAPUNI, GAPCYL, GAPSPHER
Tria3 S3, S3R, STRI3, M3D3, R3D3, DS3,

SFM3D3, SFMAX2, MGAX2, SFMGAX2,
SFMAX2
Quad4 S4, S4R, S4R5, M3D4, M3D4R, R3D4, DS4,

SFM3D4, SFM3D4R, GK3D4L, GK3D4LN,
F3D4
Tria6 STRI65, DS6, M3D6, SFM3D6
Quad8 S8R, S8R5, S8RT, DS8, M3D8, M3D8R,

SFM3D8, SFM3D8R
Tetra4 C3D4, C3D4H, DC3D4, C3D4E, DC3D4E,

AC3D4

Abaqus Card HyperMesh Supported Types
Configuration
Pyramid5 C3D8, C3D8I, C3D8H, C3D8T, C3D8HT,

C3D8IH, C3D8R, C3D8RH, C3D8E, C3D6,
C3D6H, C3D6E
Penta6 C3D6, C3D6H, DC3D6, C3D6E, DC3D6E,

GK3D6, GK3D6N, SC6R, COH3D6, AC3D6
Hex8 C3D8I, C3D8, C3D8T, C3D8H, C3D8HT,

C3D8IH, C3D8R, C3D8RH, C3D8E, DC3D8,
AC3D8, DC3D8E, DCC3D8, DCC3D8D,
GK3D8, GK3D8N, SC8R, COH3D8
Tetra10 C3D10, C3D10H, C3D10M, C3D10MH,

DC3D10, C3D10E, DC3D10E, AC3D10
Pyramid13 C3D20, C3D20H, C3D20R, C3D20RH,

C3D20E, C3D20RE, C3D20T, C3D20HT,
C3D20RT, C3D20RHT, C3D15, C3D15H,
C3D15E
Penta15 C3D15, C3D15H, DC3D15, C3D15E,

DC3D15E, AC3D15
Hex20 C3D20, C3D20H, C3D20R, C3D20RH,

DC3D20, AC3D20, C3D20E, C3D20RE,
C3D20T, C3D20HT, C3D20RT, C3D20RHT,
DC3D20E
*KINEMATIC Rigid KINCOUP

COUPLING
*MPC Rigid BEAM, LINK, PIN, TIE
*RELEASE Bar2/Bar3
Standard.2d Template
Abaqus Card HyperMesh Name Supported Parameters
*DISTRIBUTING Rigid DCOUP3D, MASS

COUPLING
Mass/1 node MASS, ROTARYI, SPRING1,

DASHPOT1, CONN2D2
R2D2, RAX2, RB2D2, BEAM, LINKI, PIN,

Rigid
TIE, KINCOUP, COUP_KIN, COUP_DIS
RBE3 DCOUP2D, COUP_DIS
SPRING2, SPRINGA, DASHPOT2,

Spring
DASHPOTA, JOINTC
SAX1, B21, B21H, B23, B23H, PIPE21,

Bar2
PIPE21H, F2D2, FAX2, AC1D2
B22, SAX2, AC1D3, B22H, PIPE22,

Bar3
PIPE22H
T2D2, T2D2H, T2D2T, T2D2E, GK2D2,

Rod GK2D2N, CONN2D2, SFMAX1, MGAX1,
SFMGAX1
Gap GAPUNI, GAPCYL, GAPSPHER
CPE3, CPS3, CPS3E, CPE3H, CPE3E,

CAX3, CAX3H, CAX3E, CGAX3,
Tria3 CGAX3H, DCAX3, DCAX3E, DC2D3,
DC2D3E, AC2D3, ACAX3
CPE4I, CPS4, CPS4I, CPS4R, CPS4T,

CPS4E, CPE4, CPE4H, CPE4IH, CPE4R,
CPE4RH, CPE4T, CPE4HT, CPE4E,
CAX4, CAX4H, CAX4I, CAX4IH, CAX4R,
CAX4RH, CGAX4, CGAX4H, CGAX4R,
Quad4 CGAX4RH, DCAX4, DCCAX4,
DCCAX4D, DCAX4E, CAX4T, CAX4HT,
ACAX4, CAX4E, DC2D4, DC2D4E,
AC2D4, CAXA4N, CAXA4HN, CAXA4RN,
CAXA4RHN, GKPS4, GKPE4, GKPS4N,
COH2D4, COHAX4
DCAX6, CPS6, CPS6M, CAX6, CAX6H,

CAX6M, CAX6MH, CGAX6, CGAX6H,
Tria6 CPE6, CPE6H, CPE6M, CPE6MH,
DC2D6, DCAX6E, DC2D6E, AC2D6,
ACAX6
CPS8, CAX8, CAX8H, CAX8HT, CAX8R,

CAX8RH, CAX8RHT, CAX8RT, CGAX8,
CGAX8H, CGAX8R, CGAX8RH, CPE8,
CPE8H, CPE8R, CPE8RH, CPS8R,
Quad8
DC2D8, AC2D8, CAXA8N, CAXA8HN,
CAXA8PN, CAXA8RN, CAXA8RHN,
CAXA8RPN, DCAX8, DCAX8E, DC2D8E,
AC2D8, ACAX8, CAX8T

*KINEMATIC Rigid KINCOUP

COUPLING
*RELEASE Bar2/Bar3
Explicit Template
Mass/1 node MASS, ROTARYI, CONN3D2, CONN2D2
Rigid R2D2, RAX2, BEAM, LINK, PIN, TIE,

COUP_KIN, COUP_DIS
RBE3 COUP_DIS
Spring SPRINGA, DASHPOTA
Bar2 B21, B31, SAX1, F2D2, FAX2
Bar3 B22, B32
Rod T2D2, T3D2, CONN3D2, CONN2D2
Tria3 CPS3, CPE3, CAX3, S3R, R3D3, M3D3,

S3RS, SFM3D3, F3D3, AC2D3, ACAX3
Quad4 CPS4R, CPE4R, CAX4R, S4R, R3D4,

M3D4R, S4RS, S4RSW, SFM3D4R,
COH2D4, COHAX4, F3D4
Tetra4 C3D4, AC3D4
Pyramid5 C3D8R, C3D6
Penta6 C3D6, SC6R, COH3D6, AC3D6
Hex8 C3D8R, SC8R, COH3D8, AC3D8R
Tetra10 C3D10M

*RELEASE Bar2/Bar3
To select an element type
1. Select the elem types panel on the 1D, 2D, or -D page.

2. Set the Abaqus type you want to use for each configuration of element.
These types are used for any new elements created.
3. Click return.
To change an existing element's type
1. Select the elem types panel from the 1D, 2D, or 3D page.
2. Set the Abaqus type you want to use for each configuration of element.
3. Click elems.
4. Indicate which elements you want to update by picking them from the graphics window, or click elems
and choose from the extended entity selection menu.
5. Click update.
6. Click return.
To check an existing element's type
1. Select the appropriate Abaqus template.

3. Click the leftmost switch and select elems from the pop-up menu.
4. Select the element for which you want to find the element type from the graphics window.
5. Click edit.
6. Verify the element type.

7. Click return.
To create a beam element
1. From the Mesh drop down menu, select Assign and select Element Types.
2. Select the bar2 or bar3 element type you want to create.
3. Click return.
4. In the Model Browser, right-click on the component that has the appropriate property assigned and
select Make Current.
5. Select the bars panel on the 1-D page.
6. If you want to select a direction node to specify the n1 vector orientation
- Click the leftmost switch, and from the pop-up menu, select node.
7. If the direction of the n1 axis of the bar is to be specified by typing in the components, you can edit the
*BEAM SECTION or *BEAM GENERAL SECTION card image that is attached to the current
component. In order to create beam elements, a pseudo-direction vector must still be chosen in the
bars panel for visualization purposes. To do this:
- Click the leftmost switch, and from the pop-up menu, select vectors.
- Click the rightmost switch, and from the pop-up menu, select x-axis.
Note: This orientation vector is not used when exporting the elements. Only the vector
components entered into the *BEAM SECTION or *BEAM GENERAL SECTION card
image are maintained.
8. To add a *RELEASE card to this element, click pins a = and pins b = and type in the HyperMesh dof
code for the Abaqus release combination code you want from the following table:
HyperMesh dof Code Abaqus Release Combination Code
4 T
5 M2
45 M2-T
6 M1
46 M1-T
56 M1-M2

456 ALLM
Note: For 2-D problems, only dof6 (M1) is active.

9. Click node A.
10. Select the first node in the element connectivity from the graphics area.
11. Click node B.
12. Select the second node in the element connectivity from the graphics area.
- If you selected components or vectors as the vector orientation method, HyperMesh creates the
bar2 element after both node A and node B have been selected.
- If you are creating a bar3 element, click node C and select the third node in the element
connectivity from the graphics area.
13. If you clicked node as the vector orientation method, pick the direction node on your model.
- HyperMesh creates the bar2 or bar3 element after the direction node has been selected.
14. To create more bars with the same properties, repeat steps 8-12.
To create a rod element
2. Select the rod element type you want to create.
3. Click return.
5. Select the rods panel on the 1D page.
8. To create more bars with the same properties, repeat steps 6 and 7.
9. Click return.
To create a MASS, ROTARY1, SPRING1, or DASHPOT1 element
2. Select the mass element type you want to create.

Note: SPRING1, ROTARY1, and DASHPOT1 elements are created from the masses panel and are
displayed as mass elements in the graphics window.
3. Click return.
5. Select the masses panel on the 1-D page.
6. Click nodes.
7. Indicate the nodes on which you want to place masses by picking them from the graphics window, or
click nodes and choose from the extended entity selection menu.
Note: The mass =, property =, and system fields are not shown in the Abaqus user profile. The
*MASS, *ROTARY INERTIA, *SPRING or *DASHPOT card image must be edited to input this
information.
8. Click create.
To create a SPRING2, SPRINGA, DASHPOT2, DASHPOTA, or JOINTC

element
2. Select the spring element type you want to create.
3. Click return.
5. Select the springs panel on the 1-D page.
- HyperMesh creates the spring element after both nodes have been selected.
Note: The dof, property =, and orient vector fields are not shown in the Abaqus user profile. The
*SPRING, *DASHPOT, or *JOINT card image must be edited to input this information.
To create a GAPUNI, GAPCYL, or GAPSPHER element
2. Select the gap element type you want to create.
3. Click return.

5. Select the gaps panel on the 1-D page.
6. Select the create sub-panel.
7. With the From Node button activated, select the first node in the element connectivity from the
graphics area.
8. With the to node button activated, select the second node in the element connectivity from the
graphics area.
- HyperMesh creates the gap element after both nodes have been selected.
Note: The property =, and orient vector fields are not shown in the Abaqus user profile.
To create a R2D2, RAX2, RB2D2, or RB3D2 rigid element
2. Select the rigid element type you want to create.
3. Click return.
5. Select the rigids panel on the 1D page.
7. With the independent node button activated, select the first node in the element connectivity from the
graphics area.
8. With the dependent node button activated, select the second node in the element connectivity from
the graphics area.
HyperMesh creates the rigid element after both nodes have been selected.
Note: The dof fields are not shown in the Abaqus user profile. The RIGID_BODY card image must be
edited to input other related information.
9. Click return.
To create a CONN3D2 or CONN2D2 connector element
3. Click the rod= button and select CONN3D2 or CONN2D2.

4. Click return.
6. With the top node button activated, select the first node in the element connectivity from the graphics
area.
7. With the bottom node button activated, select the second node in the element connectivity from the
graphics area.
HyperMesh creates the connector element after both nodes have been selected.
Note: The property= field is not shown in the Abaqus user profile.
If you use the BEHAVIOR parameter in *CONNECTOR SECTION that points to a *CONNECTOR
BEHAVIOR card, you should create a material with the CONNECTOR_BEHAVIOR card image. This
material name would have to be selected from the material = field for the component with
CONNECTORSECTION card image.
8. Click return.
To define a *COUPLING card
The *COUPLING card can be defined in three ways in HyperMesh:
· as rigid elements from the rigids panel
· as rbe3 elements from the rbe3 panel, in combination with *DISTRIBUTING card
· as groups from the interfaces panel.
Define a COUPLING card as a rigid element from the rigids panel:

2. Select the rigid element type as COUP_KIN or COUP_DIS for *KINEMATIC and *DISTRIBUTING
cards, respectively.
3. Click return.
5. Click the dependent toggle and select multiple nodes.
6. With the independent node button activated, select the reference node from the graphics area.
7. With the dependent nodes button activated, select the dependent nodes from the graphics area.
8. Select the degrees of freedom and click create.
HyperMesh creates the rigid element and shows it in graphical display.
9. From the Mesh drop down menu, select Card Edit and select Elements.
11. Select the rigid element created above from the graphics area and click edit.
12. Enter all relevant parameter values.

Note: The *COUPLING card created as rigid elements has automatically generated constrained name
and node based SURFACE. This surface contains all the dependent nodes defined for this rigid
element.
Define a *COUPLING-DISTRIBUTING card as an rbe3 from the rbe3 panel:

2. Select the rbe3 element type as COUP_DIS for *DISTRIBUTING cards.
3. Click return.
4. Select the rbe3 panel on the 1D page.
6. Click the independent node.
7. Select the reference node from the graphics area.
8. Click on the dependent nodes.
9. Select the dependent nodes from the graphics area.
11. Select the update sub-panel of the rbe3 panel to change the weighting factors.
12. Change sub options for weight factors:
· With the set individual option you can enter the desired value and click on the node you want to
update
· With the select to adjust option you can increase the value with the right mouse button or decrease
with the left mouse button. Alternatively, you can increase/decrease the value by holding the left
mouse button and move the mouse up/down.
13. Finish the change of the weighting factors by pressing the update and the return button.
14. To edit parameters of the card select card editor from the setup pull-down menu.
15. Click the toggle and select elems.
16. Select the rbe3 element created above from the graphics area and click edit.
Note: The *COUPLING card created as rbe3 elements has automatically generated constrained name
and node-based SURFACE. This surface contains all the dependent nodes defined for this rigid
element.
Define a COUPLING card as groups from the interface panel:

1. From the BCs drop down menu, select Create and select Interfaces.
2. Click name = and specify a name for the interface.

3. Click type = and select the COUPLING card image type.
4. Click create/edit.
5. Select Kinematic or Distributing from the options toggle to define *KINEMATIC or DISTRIBUTING
6. Enter all other relevant data items and parameter values
7. Click return.
Note: The *COUPLING card created from the interfaces panel does not have any graphical display in
HyperMesh.
To create a *KINEMATIC COUPLING card
2. For rigid =, select KINCOUP as the rigid element type.
3. Click return.
4. On the 1D page, select the rigids panel.
6. Click the dependent: toggle and select multiple nodes.
HyperMesh creates the KINEMATIC COUPLING rigid elements and shows it in graphical display.

11. Click the switch and select elems.
12. Click elems and select the rigid element you just created.
13. Click edit.
15. In the Orientation = field, enter any system collector from the list.
16. Click return.
17. Click return.

Pyramid Elements
HyperMesh supports two pyramid element configuration types: pyramid5 and pyramid13 (2nd order).
Although Abaqus does not support pyramid elements, some degenerated hexa and penta elements can be
used to support pyramid elements. The elements are: C3D8 (hexa8), C3D6 (penta6), C3D20 (hexa20),
and C3D15 (penta15).
There are several methods by which the hexa or penta elements can be degenerated to define a pyramid
element. HyperMesh only supports one such method for each type. If any other degeneration scheme is
found in an input file, the HyperMesh import reader does not recognize it as a pyramid element.
See the following topics for more details about node and face mapping:
Pyramid5 elements as hexa8 elements
Pyramid5 elements as penta6 elements
Pyramid13 elements as hexa20 elements
Pyramid13 elements as penta15 elements
pyramid5 from hexa8
Pyramid5 elements are degenerated to hexa8 elements for Abaqus output.

The node mapping between the two element types is listed below:
pyramid5 hexa8
Node 1 Node 1
Node 2 Node 2
Node 3 Node 3
Node 4 Node 4
Node 5 Node 5
Node 5 Node 6
Node 5 Node 7

Node 5 Node 8
The face mapping between the two element types is listed below:
pyramid5 hexa8
S1 S1
-- S2
S2 S3
S3 S4
S4 S5
S5 S6
pyramid13 from hexa20
Pyramid13 elements are degenerated to hexa20 elements for Abaqus output.

pyramid13 hexa20
Node 1 Node 1
Node 2 Node 2
Node 3 Node 3
Node 4 Node 4
Node 5 Node 5

Node 5 Node 6
Node 5 Node 7
Node 5 Node 8
Node 6 Node 9
Node 7 Node 10
Node 8 Node 11
Node 9 Node 12
Node 5 Node 13
Node 5 Node 14
Node 5 Node 15
Node 5 Node 16
Node 10 Node 17
Node 11 Node 18
Node 12 Node 19
Node 13 Node 20
pyramid13 hexa20
S1 S1
-- S2
S2 S3

S3 S4
S4 S5
S5 S6
pyramid5 from penta6
Pyramid5 elements are degenerated to penta6 elements for Abaqus output.

pyramid5 penta6
Node 4 Node 1
Node 3 Node 2
Node 5 Node 3
Node 1 Node 4
Node 2 Node 5
Node 5 Node 6
pyramid5 penta6
S4 S1
S2 S2
S1 S3

S3 S4
S5 S5
pyramid13 from penta15
Pyramid13 elements are degenerated to penta15 elements for Abaqus output.

pyramid13 penta15
Node 4 Node 1
Node 3 Node 2
Node 5 Node 3
Node 1 Node 4
Node 2 Node 5
Node 5 Node 6
Node 8 Node 7
Node 12 Node 8
Node 13 Node 9
Node 9 Node 10
Node 7 Node 11
Node 5 Node 12

Node 6 Node 13
Node 11 Node 14
Node 10 Node 15
pyramid13 penta15
S4 S1
S2 S2
S1 S3
S3 S4
S5 S5

Groups
The groups in HyperMesh are entities for various types of interfaces. It is recommended that all contact
interfaces, such as *CONTACT PAIR, *TIE, *PRE-TENSION SECTION, *SURFACE, *SURFACE
INTERACTION, as *CONTACT, be defined from the Contact Manager in the Abaqus user profile. It is
recommended that all history type interface controls, such as CONTACT INTERFERENCE, MODEL CHANGE
, CHANGE FRICTION, CONTACT CONTROLS, CONTROLS, and CLEARANCE, be defined from the
Step Manager in the Abaqus user profile.
The following Abaqus keywords are supported as groups in the interface panel in HyperMesh:

Parameters
*BLOCKAGE
*CHANGE FRICTION ELSET, The Standard template only.

INTERACTION,
AMPLITUDE, RESET It must be added to a load step (*STEP).
*CLEARANCE CPSET, MASTER, Must be added to a load step (*STEP) in

SLAVE, TABULAR, explicit template.
VALUE, INPUT, BOLT
*CONTACT OP Explicit template only.

(General Contact)
*CONTACT CLEARANCE NAME, ADJUST,

CLEARANCE,
SEARCH ABOVE,
SEARCH BELOW
*CONTACT CLEARANCE
ASSIGNMENT
*CONTACT CONTROLS APPROACH, Must be added to a load step (*STEP).

AUTOMATIC
TOLERANCES,
FRICTION ONSET,
MASTER, MAXCHP,
PERRMX, RESET,
SLAVE, SLIDE
DISTANCE,
UERRMX,
STABILIZE,
TANGENT
FRACTION,
LAGRANGE
MULTIPLIER, RESET

Parameters
*CONTACT CONTROLS TYPE = SCALE This card is a sub-option in the *CONTACT

ASSIGNMENT PENALTY, NODAL card image.
EROSION
*CONTACT DAMPING DEFINITION=DAMPI This card is a sub-option in the *SURFACE

NG COEFFICIENT INTERACTION card image.
*CONTACT EXCLUSIONS This card is a sub-option in the *CONTACT

card image.
*CONTACT TYPE = PURE This card is a sub-option in the * CONTACT

FORMULATION MASTER-SLAVE card image.
*CONTACT INCLUSIONS ALL ELEMENT This card is a sub-option in the *CONTACT

BASED, ALL card image.
EXTERIOR
*CONTACT AMPLITUDE, OP, The Standard template only.

INTERFERENCE SHRINK, TYPE=
{CONTACT PAIR, Must be added to a load step (*STEP).
ELEMENT}
*CONTACT PAIR INTERACTION,

ADJUST,
EXTENSION ZONE,
SMALL SLIDING,
SMOOTH, TIED,
HCRIT, TYPE, NO
THICKNESS
*CONTACT PROPERTY This card is a sub-option in the *CONTACT

ASSIGNMENT card image.
*COUPLING CONSTRAINT NAME, The *COUPLING is also supported as rigid

REF NODE, elements (COUP_KIN and COUP_DIS) in
SURFACE, HyperMesh.
INFLUENCE RADIUS,
ORIENTATION See Importing and Exporting *COUPLING
Cards.
*DIAGNOSTICS ADAPTIVE MESH = Explicit template only.

{STEP SUMMARY /
SUMMARY / DETAIL / Must be added to a load step (*STEP).
OFF}, CONTACT
INITIAL
OVERCLOSURE =
{DETAIL /
SUMMARY}, CUTOFF
RATIO,
DEFORMATION

Parameters
SPEED CHECK =
{SUMMARY / DETAIL
/ OFF}, DETECT
CROSSED
SURFACES = {ON /
OFF}, PLASTICITY =
{SUMMARY / DETAIL
/ OFF}, WARNING
RATIO, WARPED
SURFACE =
{SUMMARY / DETAIL
/ OFF}
*DISTRIBUTING WEIGHTING This card is a sub-option in the *COUPLING

METHOD = card image.
{UNIFORM, LINEAR,
QUADRATIC, CUBIC} It is also supported as COUP_DIS type rigid
elements in HyperMesh
*FASTENER (SPOT INTERACTION The *FASTENER PROPERTY card is defined

WELD) NAME, PROPERTY, from the property panel.
REFERENCE NODE
SET, ELSET,
ADJUST
ORIENTATION,
NUMBER OF
LAYERS,
ORIENTATION,
RADIUS OF
INFLUENCE,
SEARCH RADIUS,
WEIGHTING
METHOD,
UNSORTED
*FILTER NAME, TYPE= Explicit template only.

{BUTTERWORTH,
CHEBYS1,
CHEBYS2}
*FIXED MASS SCALING DT, ELSET, TYPE= Explicit template only.

{BELOW MIN,
UNIFORM, SET Must be added to a load step (*STEP).
EQUAL DT}, FACTOR
*FRICTION ANISOTROPIC, This card is a sub-option in the *SURFACE

EXPONENTIAL INTERACTION card image.
DECAY, TAUMAX,
DEPENDENCIES,
ROUGH, USER,
ELASTIC SLIP,

Parameters
LAGRANGE, SLIP
TOLERANCE,
DEPVAR,
PROPERTIES
*FRICTION ANISOTROPIC, This card is a sub-option in the *CHANGE

EXPONENTIAL FRICTION card image.
DECAY, TAUMAX,
DEPENDENCIES,
ROUGH, USER,
ELASTIC SLIP,
LAGRANGE, SLIP
TOLERANCE,
DEPVAR,
PROPERTIES
*INTEGRATED OUTPUT NAME, SURFACE,

SECTION REF NODE,
ORIENTATION,
PROJECT
ORIENTATION,
POSITION = { INPUT,
CENTER}, REF
NODE MOTION =
{INDEPENDENT,
AVERAGE
TRANSLATION,
AVERAGE}
*KINEMATIC This card is a sub-option in the *COUPLING

card image.
It is also supported as COUP_KIN type rigid
elements in HyperMesh.
*MODEL CHANGE ACTIVATE, ADD = The Standard template only.

{STRAIN FREE,
WITH STRAIN}, Must be added to a load step (*STEP).
REMOVE
*PRE-TENSION SECTION NODE, ELEMENT,

SURFACE
*SHELL TO SOLID CONSTRAINT NAME, The EDGE BASED surfaces can be created
COUPLING INFLUENCE from the Contact Manager.
DISTANCE,
POSITION
TOLERANCE
*SURFACE NAME, TRIM, TYPE= For analytical rigid surfaces (TYPE=

Parameters
{ELEMENT, NODE, SEGMENTS, CYLINDER, REVOLUTION),

SEGMENTS, corresponding *RIGID BODY card should also
CYLINDER, be created from the collector panel.
REVOLUTION},
CUTTING SURFACE
}, CROP, COMBINE =
{UNION,
INTERSECTION,
DIFFERENCE}
*SURFACE BEHAVIOR NO SEPARATION This card is a sub-option in the *SURFACE

INTERACTION card image.
PRESSURE-OVERCL
OSURE= {HARD,
EXPONENTIAL,
LINEAR, TABULAR},
AUGMENTED
LAGRANGE,
PENALTY
*SURFACE Explicit template only.

INTERACTION
This card is defined from the property panel in
case of standard3d and standard2d
templates.
*SURFACE PROPERTY PROPERTY = This card is a sub-option in the *CONTACT

ASSIGNMENT THICKNESS, card image.
FEATURE EDGE
CRITERIA,
PROPERTY =
OFFSET FRACTION
*TIE POSITION
TOLERANCE, TIED
NSET, ADJUST,
CYCLIC SYMMETRY,
NO ROTATION,
TYPE, NO
THICKNESS, CYCLIC
SYMMETRY,
CONSTRAIN RATIO
*VARIABLE MASS DT, ELSET, TYPE= Explicit template only.

SCALING {BELOW MIN,
Must be added to a load step (*STEP).
UNIFORM, SET
EQUAL DT,
ROLLING},
FREQUENCY,
NUMBER INTERVAL,
CROSS SECTION

Parameters
NODES, EXTRUDED
LENGTH, FEED
RATE
Note: Use the interfaces panel on the Analysis page to create a group entity in HyperMesh.
A User Comments block is supported for all groups. See information below on how to add
comments to any group card image. These comments are preserved during import and export
of the Abaqus input deck.
There have been significant changes in the support of Abaqus contact in HyperMesh. Please
refer to the Abaqus Analysis using HyperMesh tutorial for information on how to define
different types of contact.
The *SURFACE INTERACTION card is supported as group in the Abaqus Explicit template
only. This change allows the *SURFACE INTERACTION card to be used as a history data
along with *CONTACT PAIR cards. For standard3d and 2d templates, it is defined as
property.
The Analytical Rigid Surfaces are supported as a non-displayable entity in the
ANALYTICAL_RIGID_SURFACE card image.
To add an Analytical Rigid Surface to a RIGID BODY
1. From the Properties drop down menu, select Card Edit.

2. Click props and select the property created with the RIGID_BODY card image.
3. Click edit.
4. Check the Analytical_Surface option.
5. Click the Surface_Name field in the card image and select the group from the list that contains the
analytical rigid surface definition.
6. Click the Node_Id field and select a node as the reference node.
7. Click return.

To add comments to a group card image
1. From the BCs drop down menu, select Card Edit and select Groups.
2. Click groups and select a group.
3. Click edit.
4. Click the User Comments toggle and select the Show In Menu/Export option.
5. Enter an integer in the Num_Comments field to describe the number of lines you want for making
comments.
6. Enter text in the fields below the Entity_Comments heading in the card image.
7. Click return.
To define a *SURFACE card by selecting element faces
1. From the BCs drop down menu, select Assign and select Interface Entities.
2. Click name = and select the group with SURFACE_ELEMENT type.
3. Click the switch and select face.
4. Click solid elems and select the elements whose faces make up the surface.
5. Click nodes to the right of face of nodes and pick two corner nodes (or three nodes) of any of the
elements selected.
6. Click add to add these faces to the *SURFACE.
7. Click return.
To define a *SURFACE using sets or components
1. From the BCs drop down menu, select Assign and select Interface Entities.
2. Click name = and select the group with SURFACE_ELEMENT type.
3. Click the switch and select comps or sets from the pop-up window.
4. Click comps or sets and select a component or set from the list.
5. Click update.
6. Select the card image sub-panel.
7. Click edit.
8. Select the multiple_sets option in the card image if you are using multiple components or sets to

define the *SURFACE.
9. Click the selection box under Label and choose the appropriate face label for each component or set
from the pop-up menu.
Notice that HyperMesh does not display a *SURFACE that is defined using sets.
10. Click return to exit the panel.
Comments
Only one option (entities, comps, or sets) can be used to define a surface.
To add elements to the *PRE_TENSION SECTION with element option
2. Click groups and select the group with PRE_TENSION_SECTION type.
3. Click edit.
4. Click ptnid in the card image and select a node from the graphics window, or click ptnid again to enter
the ID of the node involved in the *PRE_TENSION_SECTION.
5. Click elemop in the card image and select an element from the graphics window, or click elemop
again to enter the ID of the element involved in the *PRE_TENSION_SECTION.
6. To enter a user-defined normal to the SECTION, click vcomps and enter the values in the card image.
7. Click return.
To edit or add options to *CONTACT_PAIR card
2. Click groups and select the group with CONTACT_PAIR type.
3. Click edit.
4. Click the Property field in the card image and select the property from the list that contains the
*SURFACE INTERACTION card for this contact pair. (For Explicit template, check the INTERACTION
option and click the Surface_Interaction field to select the group from the list.)
5. Click the Slave_Surface field in the card image and select the group from the list that contains the
slave surface definition for this contact pair.
6. Click the Master_Surface field in the card image and select the group from the list that contains the
master surface definition for this contact pair.

7. Select options that you want to include on the *CONTACT PAIR card and enter the appropriate values
in the card image.
8. Click return.
Note: For self-contact, only the Slave_Surface field needs to be selected.
To specify multiple surface pairs, select the MultipleDataLines option in the card image and type
the number of data lines in the field that appears when the option is selected.
To edit or add options to *PRE_TENSION SECTION with surface

option
2. Click groups and select the group with PRE_TENSION_SECTION type.
3. Click edit.
4. Select Surface Option from the option list in the card image.
5. Click the Surface field in the card image and select the group from the list that contains the surface
definition for this contact pair.
6. To enter a user-defined normal to the SECTION, click vcomps and enter the values in the card image.
7. Click return.
To define a *SURFACE INTERACTION card in Explicit template
3. Click type = and select the SURFACE_INTERACTION card image type.
5. Click SurfaceBehavior, ContactDamping or Friction options to define *SURFACE BEHAVIOR,
*CONTACT DAMPING, or *FRICTION cards, respectively.
6. Click DataLine to input the optional out-of-plane thickness of the surface or cross-sectional area for
every node in the node-based surface.
7. Click return.

To create an Analytical Rigid Surface
3. Click type = and select ANALYTICAL_RIGID_SURFACE.
5. Select the TYPE= toggle to select the surface type and fill in the necessary information
6. Click return.
To create a cutting surface
3. Click type = and select CUTTING_SURFACE.
5. Fill in the necessary data items.
6. Click return.
To create a combined or cropped surface
3. Click type = and select SURFACE_COMBINE_CROP.
5. Fill in the necessary data items
6. Click return.

To define a *CONTACT (General Contact) card in Explicit template
3. Click type = and select the General_CONTACT card image type.
5. Click the following:
· Contact_Inclusions to define *CONTACT INCLUSIONS
· Contact_Exclusions to define *CONTACT EXCLUSIONS
· Contact_Property_Assignment to define *CONTACT PROPERTY ASSIGNMENT
· Contact_Formulation to define *CONTACT FORMULATION
· Contact_Controls_Assignment to define *CONTACT CONTROLS ASSIGNMENT
· Surface_Property_Assignment_Thickness to define *SURFACE PROPERTY ASSIGNMENT

with PROPERTY= THICKNESSS
· Surface_Property_Assignment_Feature_Edge_Criteria to define *SURFACE PROPERTY

ASSIGNMENT with PROPERTY= FEATURE EDGE CRITERIA
7. Click return.
Note: The *CONTACT card can be defined as both model or history data in Abaqus. You can use the
load steps panel to add the *CONTACT to a specific *STEP.
Importing and Exporting *COUPLING cards
Importing *COUPLING cards

By default, HyperMesh reads all *COUPLING cards as rigid elements except when a *COUPLING card in
combination with a *DISTRIBUTING card refers to a *SURFACE with varying weight factors. In this case,
the card will be read in as rbe3 elements. In addition, you can choose to import all *COUPLING cards as
HyperMesh groups.
When *COUPLING is imported as rigid or rbe3 elements, the nodes from the corresponding *SURFACES
are used to define the rigid/rbe3 elements and weight factors. The *SURFACES themselves are ignored
during import. On export, HyperMesh auto-creates the *SURFACES from dependent nodes of the element.
As a result, the surface names will be changed. If the surfaces are referenced by other keywords for which
the names must be maintained, you should import the *COUPLING as groups.
To read the *COUPLING as groups, select the Coupling as Groups option from the Solver Options
dialog on the Import tab.
In addition to the Solver Options dialog, you can also insert comments in the input file to dictate the import
process. The relevant comments are:

· **HM_coupdis_RBE3 (to import *COUPLING-*DISTRIBUTING as rbe3)
· **HM_coupling_Group (to import *COUPLING as groups)
Note that these comments in the input file take precedence over any selection in the Solver Options
dialog.
Exporting *COUPLING cards

There are three different methods of export for *COUPLING cards that depend on the HyperMesh
configuration of the card:
· Rigid elements: No additional comments will be written by HyperMesh
· RBE3: An additional comment, HM_coupdis_RBE3, will be inserted before the *COUPLING card
· Group: An additional comment, HM_coupling_Group, will be inserted before the *COUPLING

card. Surface names are maintained.
To define a *FASTENER (SPOT WELD) card
1. From the BCs drop down menu, select Create and elect the Interfaces.
3. Click type = and select the FASTENER card image type.
5. Click Property_Name and select the property defined with FASTENER_PROPERTY card image.
6. Enter all other relevant data items and parameter values.
7. Click return.
To create a *DISTRIBUTING COUPLING card with corresponding

DCOUP3D/DCOUP2D element
1. From the Collectors drop down menu, select Create and select Component.
2. For name =, enter a component name.
3. Click the toggle next to property= and to set the property to blank.
4. Click color and select a color.
5. Click create
6. Click return.

7. On the 1D page, select the elem types panel.
8. For rbe3 =, select DCOUP3D or DCOUP2D as the element type.
9. Click return.
12. With the dependent node button activated, select the reference node from the graphics area.
13. With the independent nodes button activated, select the independent nodes from the graphics area.
14. Select the degrees of freedom.
15. For weight =, input the weight factor.
16. Click create.

Load Collectors
A load collector in HyperMesh is a repository for loads and constraints. Each load or constraint must
belong to a load collector. There are two card images called HISTORY and INITIAL_CONDITION. Loads
or constraints that are to be used as history data (under *STEP) should be collected into load collectors
with the "HISTORY" card image. These load collectors also need to be added to the corresponding load
steps (*STEP) from the load steps panel. In contrast, loads or constraints for model data should be
collected into load collectors with INITIAL_CONDITION card image. They will automatically be written out
in the model portion of the Abaqus input deck.
Note If a **HMLOAD_SETS_EXPAND comment is found in the input file, all loads and boundary
conditions on sets are expanded to individual nodes and elements.

Parameters
*CFILM AMPLITUDE, FILM Only in HISTORY card image

AMPLITUDE,
REGION TYPE =
{LAGRANGIAN/SLIDI
NG, EULEREIAN}, OP
*CONNECTOR LOAD AMPLITUDE, LOAD Only in HISTORY card image

CASE, OP
*CONNECTOR MOTION AMPLITUDE, LOAD In both HISTORY and INTIAL_CONDITION

CASE, OP card image
*DSLOAD AMPLITUDE, LOAD Only in HISTORY card image

CASE, CYLIC MODE,
OP
*INERTIA RELIEF FIXED, Only in HISTORY card image of Standard

ORIENTATION, template
REMOVE
*SFILM AMPLITUDE, FILM Only in HISTORY card image

AMPLITUD, OP
Note Prior to HyperMesh 6.0, all history type keywords including *STEP were created from the load
collector card image. In HyperMesh 6.0, these keywords are created and organized from the
load steps and output block panels.

To create a load collector for history data
1. From the Collectors drop down menu, select Create and select Load Collectors.
2. In the loadcol= field, enter a load collector name.
3. Click card image = and select HISTORY.
4. Click color and select a color from the menu.
5. Click create.
To create a load collector for model data
1. From the Collectors drop down menu, select Create and select Load Collectors.
2. In the loadcol= field, enter a load collector name.
3. Click card image = and select INTIAL_CONDITION.
4. Click color and select a color from the menu.
5. Click create.
To define a *CONNECTOR MOTION card
1. From the Collectors drop down menu, select Edit and select Load Collectors.
2. In the loadcol= field, select the load collector with the HISTORY or INTIAL_CONDITION card image.
3. Click update/edit.
4. Check the Connector_Motion check box.
5. Check the Connector_Motion_Element_Ids check box.
6. Input the number of data lines required in the Connector_Motion_data_lines entry box.
7. Click the yello element selector button for each line to pick the connector element from the HyperMesh
display (or write the element id directly in the id = entry box).
8. Input the available component of relative motion and magnitudes in corresponding entry boxes.
9. Click return.

To define a *CONNECTOR LOAD card
2. In the loadcol= field, select the load collector with the HISTORY card image.
4. Check the Connector_Load check box.
6. Input the number of data lines required in the Connector_Load_data_lines entry box.
7. Click the element selector button for each line to pick the connector element from the HyperMesh
8. Input available component of relative motion and magnitudes in corresponding entry boxes.
9. Click return.
To define a *CFILM, *DSLOAD, *SFILM, or *INERTIA RELIEF card
2. In the loadcol= field, select the loadcol with the HISTORY card image.
4. Check the CFilm, DSload, SFilm or Inertia_Relief check box.
5. Enter the relevant parameters and data items.
6. Click return.

Loads
In HyperMesh, each load or constraint must belong to a load collector. Loads or constraints in history data
(under *STEP) should be organized into load collectors with HISTORY card image. These load collectors
need to be added to a load step from the load steps panel. Loads or constraints in model data, however,
should be organized into load collectors with the INITIAL_CONDITION card image. These load collectors
do not need to be added to a load step. All Loads and Boundary conditions are recommended to be
defined from the Step Manager in the Abaqus user profile.
Note: If a **HMLOAD_SETS_EXPAND comment is found in the input file, all loads and boundary
conditions on sets are expanded to individual nodes and elements.
Abaqus Card HyperMesh Supported Parameters Notes

Configuration
Name
*BOUNDARY FLUX FIXED, USER, LOADCASE, Specifies flux

(electric potential, AMPLITUDE, REGION TYPE = boundary conditions
dof 9) {LAGRANGIAN,SLIDING, for piezoelectric
EULEREIAN}, OP analysis.
*BOUNDARY CONSTRAINT TYPE = {DISPLACEMENT, Creates structural

(structural) VELOCITY, boundary conditions.
ACCELERATION}FIXED, USER,
LOADCASE, AMPLITUDE,
REGION TYPE =
{LAGRANGIAN,SLIDING,
EULEREIAN}, OP. See To set the
OP parameter for a load step
*BOUNDARY TEMPERATURE FIXED, USER, LOADCASE, Specifies temperature

(temperature, dof AMPLITUDE, REGION TYPE = boundary conditions.
11) {LAGRANGIAN,SLIDING,
EULEREIAN}, OP
*CECHARGE FLUX OP Specifies concentrated

electric charges for
piezoelectric analysis.
*CECURRENT FLUX OP Specifies concentrated

current in electric
conduction.
*CFILM AMPLITUDE, FILM AMPLITUDE, Only in HISTORY load

REGION TYPE = collector card image
{LAGRANGIAN/SLIDING,
EULEREIAN}, OP
*CFLUX FLUX OP Creates flux loads.
*CLOAD FORCE AMPLITUDE , LOADCASE, Creates concentrated

CYCLIC MODE, FOLLOWER, forces.

Configuration
Name
REGION TYPE = {LAGRANGIAN,

SLIDING, EULEREIAN}, OP
*CLOAD MOMENT AMPLITUDE , LOADCASE, Creates concentrated

CYCLIC MODE, FOLLOWER, moments.
REGION TYPE = {LAGRANGIAN,
SLIDING, EULEREIAN},OP
*CONNECTOR OP, AMPLITUDE, LOAD CASE HISTORY card image

LOAD of the load collector
*CONNECTOR OP, AMPLITUDE, LOAD CASE HISTORY or

MOTION INITIAL_CONDITION
card image of the load
collector
*DECHARGE PRESSURE OP Distributes electric

charges for
*DECURRENT PRESSURE OP Distributes electric

charges for
*DFLUX PRESSURE OP Distributes fluxes for

heat transfer analysis.
*DLOAD PRESSURE AMPLITUDE , LOADCASE, Specifies distributed

CYCLIC MODE, REGION TYPE = loads.
{LAGRANGIAN, SLIDING,
EULEREIAN}, OP
*DSLOAD AMPLITUDE, LOAD CASE, CYLIC Only in HISTORY load

MODE, OP collector card image
*FILM PRESSURE AMPLITUDE, FILM AMPLITUDE, Defines film

REGION TYPE = coefficients.
{LAGRANGIAN/SLIDING,
EULEREIAN}, OP
*INERTIA RELIEF FIXED, ORIENTATION, REMOVE Only in HISTORY load

collector card image of
Standard template
*INITIAL PRESSURE Specifies initial

CONDITIONS pressures for
(TYPE = FLUID hydrostatic fluid filled
PRESSURE) cavities.

Configuration
Name
*INITIAL TEMPERATURE Specifies initial

CONDITIONS temperatures for heat
(TYPE= transfer analysis.
TEMPERATURE)
*INITIAL CONSTRAINT Specifies initial

CONDITIONS velocities for dynamic
(TYPE=VELOCITY) analysis.
*RADIATE PRESSURE Applies radiation

boundary conditions.
*SFILM AMPLITUDE, FILM AMPLITUD, Only in HISTORY load

OP collector card image
*TEMPERATURE TEMPERATURE AMPLITUDE, BSTEP, BINC, Specifies predefined

ESTEP, EINC, INPUT, FILE, temperature field.
MIDSIDE, OP
Note: Prior to HyperMesh 6.0, all history type keywords including *STEP were created from the load
To create a load card
1. Select the type of load to create on the Analysis page.

3. Enter the relevant data.
4. Click create.
5. Click return.
To select a load type
1. Select the load types panel on the Analysis page.

2. Set the Abaqus type you want to use for each load’s configuration.
These types are used for any new loads created.

3. Click return.
To check an existing load's type

3. Click the leftmost switch and select loads from the pop-up menu.
4. Click loads and select the load for which you want to find the load type.
5. Click edit.
6. Verify the load type.
7. Click return.
To change an existing load's type

2. Set the Abaqus type you want to use for each load’s configuration.
3. Click loads.
4. Indicate the loads you want to update by picking them from the graphics window, or click loads and
choose from the extended entity selection menu.
5. Click update.
6. Click return.
To define a *CONNECTOR MOTION card
2. In the loadcol= field, select the load collector with the HISTORY or INTIAL_CONDITION card image.
4. Check the Connector_Motion check box.

6. Input the number of data lines required in the Connector_Motion_data_lines entry box.
7. Click the yello element selector button for each line to pick the connector element from the HyperMesh
8. Input the available component of relative motion and magnitudes in corresponding entry boxes.
9. Click return.
To define a *CONNECTOR LOAD card
2. In the loadcol= field, select the load collector with the HISTORY card image.
4. Check the Connector_Load check box.
6. Input the number of data lines required in the Connector_Load_data_lines entry box.
7. Click the element selector button for each line to pick the connector element from the HyperMesh
8. Input available component of relative motion and magnitudes in corresponding entry boxes.
9. Click return.
To define a *CFILM, *DSLOAD, *SFILM, or *INERTIA RELIEF card
2. In the loadcol= field, select the loadcol with the HISTORY card image.
4. Check the CFilm, DSload, SFilm or Inertia_Relief check box.
6. Click return.

To define a *BOUNDARY, TYPE=VELOCITY or ACCELERATION card
1. Set the load collector that has the History card image loaded as the current collector by right-clicking
on it in the Model Browser and selecting Make Current.
2. Select the load types panel on the BCs page.
3. Click constraint = and select VELOCITY or ACCELERATION.
4. Click return.
5. Select constraints panel on the BCs page.
8. Click create.
9. Click return.
To define a *BOUNDARY, FIXED card
3. Click constraint = and select BOUNDARY.
4. Click return.
5. Select constraints panel on the Analysis page.
8. Click create.
9. Click return.
10. Click the Card Edit icon.

12. Click the switch and select loadcols.
13. Click loadcols and select the same load collector as selected in Step 1.
14. Click edit.
15. Select the FIXED option from the Type_Fixed_User toggle.
16. Click return.

To define a *TEMPERATURE card
3. Click temperature = and select TEMPERATURE.
4. Click return.
5. Select temperatures panel on the Analysis page.
8. Click create.
To define a *BOUNDARY for TEMPERATURE (dof 11) card
1. Set the load collector that has the HISTORY or INITIAL_CONDITION card image loaded as the current
collector by right-clicking on it in the Model Browser and selecting Make Current.
3. Click temperature = and select BOUNDARY.
4. Click return.
8. Click create.
To define a *INITIAL CONDITION, TYPE=TEMPERATURE card
1. Set the load collector that has the INITIAL_CONDITION card image loaded as the current collector by
right-clicking on it in the Model Browser and selecting Make Current.
3. Click temperature = and select TEMPERATURE.
4. Click return.

8. Click create.
9. Click return.
To define a *INITIAL CONDITION, TYPE=VELOCITY card
1. Set the load collector that has the INITIAL_CONDITION card image loaded as the current collector by
right-clicking on it in the Model Browser and selecting Make Current.
3. Click constraint = and select VELOCITY.
4. Click return.
5. Select constraints panel on the Analysis page.
8. Click create.
9. Click return.
To define a *BOUNDARY for ELECTRIC POTENTIAL (dof 9) card
1. Set the load collector that has the HISTORY or INTIAL_CONDITION card image loaded as the current
collector by right-clicking on it in the Model Browser and selecting Make Current.
3. Click flux = and select ELEC_POTEN.
4. Click return.
5. Select flux panel on the Analysis page.
8. Click create.

To create an *AMPLITUDE card
1. Select the xy plots panel on the Post page.

2. Create a curve using various sub-panels. In HyperMesh, you can import a curve from tabular data or
define a curve through a mathematical expression. For details, see the xy plots panel in the
HyperMesh documentation.
3. Click exit.
You can also use the Curve Editor to create, edit, review, and update *AMPLITUDE curves.

Load Steps
A load step in HyperMesh corresponds to a *STEP definition in Abaqus model history. Load collectors,
output blocks and groups within a load step are exported under the corresponding *STEP block in the
Abaqus input deck. It is recommended that all history (*STEP) data be defined from the Step Manager in
the Abaqus user profile.

Parameters
*BUCKLE EIGENSOLVER=SUB Defined in the load step card image

SPACE, LANCZOS
*BULK VISCOSITY Explicit template only. History data.
*DYNAMIC EXPLICIT, SCALE Defined in the load step card image.

FACTOR, ADIABATIC
(Explicit)
FIXED TIME
INCREMENTATION,
DIRECT USER
CONTROL,
ELEMENT BY
ELEMENT
IMPROVED DT
METHOD = YES or
NO
*DYNAMIC HAFTOL, DIRECT, Defined in the load step card image.

DIRECT=NO STOP,
(Standard) SUBSPACE,
ADIABATIC, ALPHA,
INITIAL, NOHAF
*FILE FORMAT ASCII, BINARY, Defined in the load step card image.
ZERO INCREMENT
*FREQUENCY PROPERTY Defined in the load step card image.

EVALUATION,
EIGENSOLVER =
{SUBSPACE,
LANCZOS, AMS},
NORMALIZATION =
{MASS,
DISPLACEMENT},
RESIDUAL MODES,
ACOUSTIC
COUPLING,
NUMBER INTERVAL,
BIAS, USER
BOUNDARIES

Parameters
*HEAT TRANSFER DELTMX, END = Defined in the load step card image.
PERIOD or SS,
STEADY STATE,
MXDEM
*LOAD CASE Defined in the load step card image.
*MODAL DYNAMIC CONTINUE = YES or Defined in the load step card image.
NO
*MONITOR DOF, NODE, Defined in the load step card image.

FREQUENCY
*PRINT CONTACT, MODEL Defined in the load step card image.

CHANGE,
FREQUENCY,
PLASTICITY,
RESIDUAL, SOLVE,
ALLKE, CRITICAL
ELEMENT, DMASS,
ETOTAL
*RESTART WRITE, Defined in the load step card image.

FREQUENCY,
OVERLAY, NUMBER
INTERVAL, TIME
MARKS
*STATIC ADIABATIC, FULLY Defined in the load step card image.

PLASTIC, RIKS,
STABILIZE, DIRECT,
DIRECT=NO STOP,
FACTOR, LONG
TERM
*STEADY STATE DIRECT, SUBSPACE Defined in the load step card image.
DYNAMICS PROJECTION = {ALL
FREQUENCIES,
CONSTANT,
EIGENFREQUENCY,
PROPERTY
CHANGE},
FREQUENCY SCALE,
INTERVAL, REAL
ONLY, DAMPING
CHANGE,
STIFFNESS CHANGE
*STEP INCREMENT, NAME, Parameters are defined in the load step card
NLGEOM, image.

Parameters
PERTURBATION,
UNSYMMETRIC
AMPLITUDE=STEP,
RAMP
EXTRAPOLATION=LI
NEAR, PARABOLIC,
NO
*VISCO CETOL, CREEP, Defined in the load step card image.

FACTOR, STABILIZE
Note: Prior to HyperMesh 6.0, all history type keywords including *STEP were created from the load
Only load collectors with the HISTORY card image should be added to a load step. Load
collectors with INITIAL_CONDITION card images need not be added to any load steps. They will
be ignored, if added.
To create a load step (*STEP card)
1. Select the load steps panel from the Analysis page.

2. Enter a load step name after name = .
3. Click the loadcols button and select the loadcols for this load step.
4. Click the outputblocks button and select the output requests for this load step
5. For Explicit template, click the groups button and select the groups (with CONTACT_PAIR and
SURFACE_INTERACTION types only) for this load step.
6. Click create.
7. Click return.
To add load collectors to a load step

2. Click the name = button and select a load step.

3. Click the loadcols button and select the loadcols for this load step.
4. Click update.
5. Click return.
To add output blocks to a load step

3. Click the outputblocks button and select the output blocks for this load step.
4. Click update.
5. Click return.
To add interfaces (groups) to a load step

3. Click groups and select the groups for this load step.
4. Click update.
5. Click return.
To add *CONTACT PAIR or *SURFACE INTERACTION cards to a load

step in Explicit template

3. Click the groups button and select the groups with CONTACT_PAIR and SURFACE_INTERACTION
types for this load step.
4. Click update.
5. Click return.

To edit a load step card image to define analysis types and other
history related keywords

3. Click edit
4. Define *STEP parameters, analysis types and other available history related keywords.
5. Click return.
6. Click return.
To review a load step

2. Click review.
3. Select a load step.
4. Click the loadcols, outputblocks or groups buttons. The entities for the load step will show as
checked.
5. Click return.
To set the OP parameter for a load step

3. Click edit.
4. Select the Load_OP_Options check box. It will show a list of check boxes for OP options for various
loads and constraints.
5. Select the corresponding OP option check boxes. Each option displays the corresponding keyword
with a selection button in the card previewer.
6. Click the OP = buttons for all selected load or constraint types and set the desired OP = value.
7. Click return.
8. Click return.

Note: OP = options selected for a load or constraint type are applied to all the loads of that type in the
load step. If no loads or constraints of that type are found in the load step, the corresponding
card with no data lines will be written.
For example, if the Boundary_OP check box is selected, the OP = value defined will be applied to
all the *BOUNDARY keywords in the load step. If no *BOUNDARY is found in the load step, a
*BOUNDARY card with OP = value and no data lines will be written.
To add multiple load cases to a load step

2. Click name = and select a load step.
3. Click loadcols and select all the loadcols for this load step including the ones under load cases.
4. Click update.
5. Click edit.
6. Select the LoadCase check box.
7. Enter the number of load cases in Number_of_Loadcase field. The card image will show all the
*LOAD CASE and *END LOAD CASE blocks.
8. Enter load case names in name = entry fields for each *LOAD CASE.
9. Select the maximum number of load collectors in a *LOAD CASE in the
Loadcase_maximum_data_lines field. Each *LOAD CASE card will show the same number of load
collectors selection buttons.
10. Select the desired load collectors in different load cases. All loads defined in these load collectors will
be exported within the corresponding *LOAD CASE and *END LOAD CASE block.
11. The load collectors selected under a *LOAD CASE must already be added in step 3. All others, if
selected, will be ignored.
Note: The load collectors selected under a *LOAD CASE must already be added (step 3 above) in the
load step. All others, if selected, will be ignored.

Materials
HyperMesh supports three material keywords - *MATERIAL, *GASKET MATERIAL, *CONNECTOR

BEHAVIOUR in the corresponding card images. They are: ABAQUS_MATERIAL, GASKET_MATERIAL and
CONNECTOR_BEHAVIOR, respectively.
Because Abaqus has a large selection of material types, many of which are not supported in HyperMesh,
HyperMesh includes a separate mode of material creation called "Generic Material". This model of created
is supported through the GENERIC_MATERIAL card image. In this mode, all material sub-options,
parameters, and data lines are supported as simple text. HyperMesh does not check the validity or syntax
of any data in this mode. You must manually check the validity of the data. This method is most helpful
when the material models are already defined and they are imported into HyperMesh for the purpose of
adding them to the corresponding sectional properties. No editing, updating, or review of the material data
is intended.
You can import a model in the generic material mode by using the Solver Options dialog in the Import
tab. You can also add an **HM_GENERIC_MATERIAL comment before a material card to have it imported
as a generic material.
Also see the Unsupported Data Blocks topic to learn more about how the HyperMesh Abaqus interface
handles unsupported data.

Parameters
*CONDUCTIVITY DEPENDENCIES, This card is a sub-option in the

TYPE=ISO, ABAQUS_MATERIAL card image.
ORTHO, ANISO
*CONNECTOR NAME,
BEHAVIOR INTEGRATION
*CONNECTOR This card is a sub-option in the

CONSTITUTIVE CONNECTOR_BEHAVIOR card image.
REFERENCE
*CONNECTOR INDEPENDENT This card is a sub-option in the

CONTACT FORCE COMPONENT, CONNECTOR_BEHAVIOR card image
DEPENDENCIES
*CONNECTOR COMPONENT, This card is a sub-option in the

DAMPING COUPLED, CONNECTOR_BEHAVIOR card image.
DEPENDENCIES,
NONLINEAR,
INDEPENDENT
COMPONENTS
*CONNECTOR COMPONENT, This card is a sub-option in the

ELASTICITY COUPLED, CONNECTOR_BEHAVIOR card image.
DEPENDENCIES,
NONLINEAR,
MOTION

Parameters
DEPENDENCIES
*CONNECTOR COMPONENT, Only in Explicit template

FAILURE RELEASE
This card is a sub-option in the
CONNECTOR_BEHAVIOR card image.
*CONNECTOR INTERACTION, This card is a sub-option in the

FRICTION COMPONENT, CONNECTOR_BEHAVIOR card image.
(Abaqus 6.4 version) INDEPENDENT
COMPONENT,
DEPENDENCIES,
STICK STIFFNESS
*CONNECTOR PREDEFINED, This card is a sub-option in the

FRICTION (Abaqus 6.5 COMPONENT, CONNECTOR_BEHAVIOR card image.
or later version) INDEPENDENT
COMPONENTS, This needs a *FRICTION card, which can
DEPENDENCIES, be created as a property using the
STICK STIFFNESS, FRICTION card image.
CONTACT FORCE
*CONNECTOR LOCK COMPONENT, This card is a sub-option in the

LOCK CONNECTOR_BEHAVIOR card image.
*CONNECTOR STOP COMPONENT This card is a sub-option in the

CONNECTOR_BEHAVIOR card image.
*CREEP DEPENDENCIES This card is a sub-option in both the

ABAQUS_MATERIAL and *GASKET
LAW=STRAIN, MATERIAL card images.
TIME, HYPERB,
USER Not in Explicit template.
*CRUSHABLE FOAM HARDENING = This card is a sub-option in the

{VOLUMETRIC, ABAQUS_MATERIAL card image.
ISOTROPIC},
DEPENDENCIES
*CRUSHABLE FOAM DEPENDENCIES This card is a sub-option in the

HARDENING ABAQUS_MATERIAL card image.
*DAMPING ALPHA, BETA, This card is a sub-option in the

COMPOSITE ABAQUS_MATERIAL card image.
*DENSITY DEPENDENCIES This card is a sub-option in the

ABAQUS_MATERIAL card image.
*DIELECTRIC TYPE=ISO, This card is a sub-option in the

Parameters
ORTHO, ANISO ABAQUS_MATERIAL card image.
*ELASTIC DEPENDENCIES, This card is a sub-option in the

MODULI, ABAQUS_MATERIAL card image.
TYPE=ISOTROPIC,
LAMINA,
ENGINEERING
CONSTANTS,
ORTHOTROPIC,
ANISOTROPIC
*EXPANSION ZERO, This card is a sub-option in both the

DEPENDENCIES, ABAQUS_MATERIAL and *GASKET
PORE FLUID, MATERIAL card images.
USER, TYPE=ISO,
ORTHO, ANISO,
SHORT FIBER
*FLUID BEHAVIOR NAME
*GASKET BEHAVIOR NAME Only in Standard template.
*GASKET CONTACT DEPENDENCIES This card is a sub-option in the

AREA *GASKET_MATERIAL card image.
*GASKET ELASTICITY DEPENDENCIES This card is a sub-option in the *GASKET

BEHAVIOR card image.
COMPONENT=ME
MBRANE,
TRANSVERSE
SHEAR
VARIABLE=STRES
S, FORCE
*GASKET ELASTICITY DEPENDENCIES This card is a sub-option in the

*GASKET_MATERIAL card image.
COMPONENT=ME
MBRANE,
TRANSVERSE
SHEAR
VARIABLE=STRES
S, FORCE
*GASKET THICKNESS DEPENDENCIES, This card is a sub-option in the

BEHAVIOR TENSILE *GASKET_MATERIAL card image.
STIFFNESS
FACTOR, SLOPE
DROP, YIELD
ONSET

Parameters
DIRECTION=LOADI
NG, UNLOADING
VARIABLE=STRES
S, FORCE
TYPE=ELASTIC-PL
ASTIC, DAMAGE
*HYPERELASTIC N, OGDEN, This card is a sub-option in the

POLYNOMIAL, ABAQUS_MATERIAL card image.
ARRUDA-BOYCE,
MOONEY-RIVLIN, Sub-options supported:
NEO HOOKE,
*UNIAXIAL TEST DATA
REDUCED
POLYNOMIAL, VAN *BIAXIAL TEST DATA
DER WAALS,
YEOH, MARLOW, *PLANAR TEST DATA
USER, TEST DATA
INPUT, BETA, *VOLUMETRIC TEST DATA
MODULI,
POISSON,
PROPERTIES
*MATERIAL NAME, SRATE

FACTOR, RTOL
*MULLINS EFFECT TEST DATA INPUT, This card is a sub-option in the

USER, BETA, M, R, ABAQUS_MATERIAL card image.
DEPENDENCIES,
PROPERTIES, Sub-options supported:
*UNIAXIAL TEST DATA
*BIAXIAL TEST DATA
*PLANAR TEST DATA
*HYPERFOAM N, TEST DATA This card is a sub-option in the

INPUT, POISSON, ABAQUS_MATERIAL card image.
MODULI
Sub-options supported:
*UNIAXIAL TEST DATA
*BIAXIAL TEST DATA
*SIMPLE SHEAR TEST DATA
*PLANAR TEST DATA
*VOLUMETRIC TEST DATA
*PIEZOELECTRIC TYPE=S, E This card is a sub-option in the

Parameters

Not in Explicit template.
*PLASTIC RATE, DATA TYPE

HARDENING=ISOT
ROPIC,
KINEMATIC,
COMBINED,
JOHNSON COOK
*RATE DEPENDENT TYPE= {POWER This card is a sub-option in the

LAW, JOHNSON ABAQUS_MATERIAL card image.
COOK, YIELD
RATIO},
DEPENDENCIES
*SHEAR FAILURE TYPE= {TABULAR, This card is a sub-option in the

JOHNSON COOK}, ABAQUS_MATERIAL card image in the
ELEMENT Explicit template.
DELETION = {YES,
NO},
DEPENDENCIES
*SPECIFIC HEAT DEPENDENCIES This card is a sub-option in the

*USER MATERIAL CONSTANTS, This card is a sub-option in the

TYPE= ABAQUS_MATERIAL card image.
{MECHANICAL,
THERMAL},
UNSYMM
*USER OUTPUT This card is a sub-option in both the

VARIABLES ABAQUS_MATERIAL and *GASKET
MATERIAL card images.
*VISCOELASTIC ERRTOL, NMAX This card is a sub-option in the

FREQUENCY=FOR Sub-options supported:
MULA, TABULAR
*SHEAR TEST DATA
TIME= CREEP
TEST DATA, *VOLUMETRIC TEST DATA
RELAXATION TEST
*COMBINED TEST DATA
DATA, PRONY
For the sub-options, the parameters
SHRINF and VOLINF are supported.

A User Comments block is supported for all materials. See the information below on how to add
comments to any material card image. These comments are preserved during import and export of the
Abaqus input deck.
To create a CONN3D2 or CONN2D2 connector element
3. Click the rod= button and select CONN3D2 or CONN2D2.
4. Click return.
6. With the top node button activated, select the first node in the element connectivity from the graphics
area.
7. With the bottom node button activated, select the second node in the element connectivity from the
graphics area.
HyperMesh creates the connector element after both nodes have been selected.
Note: The property= field is not shown in the Abaqus user profile.
If you use the BEHAVIOR parameter in *CONNECTOR SECTION that points to a *CONNECTOR
BEHAVIOR card, you should create a material with the CONNECTOR_BEHAVIOR card image. This
material name would have to be selected from the material = field for the component with
CONNECTORSECTION card image.
8. Click return.
To define a *CONNECTOR BEHAVIOR card
1. From the Materials drop down menu, select Create.

2. Click mat name = and enter the name for the material collector.
3. Click card image = and select CONNECTOR_BEHAVIOR.
5. Select the material connector behavior model you want to define.
6. Enter the appropriate values into the card image.
7. Click return.

To add comments to a material card image
1. From the Materials drop down menu, select Edit.

2. Click mats and select the material to edit.
3. Click Update/edit.
4. Click the switch next to User Comments heading.
5. Select the Show In Menu/Export option.
comments.
8. Click return.

Multi-point Constraints

Parameters or Types
*COUPLING CONSTRAINT NAME,

REF NODE,
SURFACE,
INFLUENCE RADIUS,
ORIENTATION
*DISTRIBUTING WEIGHTING
METHOD =
{UNIFORM, LINEAR,
QUADRATIC, CUBIC}
*DISTRIBUTING MASS See Elements.

COUPLING
*EQUATION Explicit node IDs are supported. Node sets

are not supported.
Equations are considered loads in HyperMesh
and therefore, they are collected in load
collectors. Upon export, they write to the bulk
data portion of the Abaqus deck.
*MPC BEAM, LINK, PIN, TIE See Elements.
*KINEMATIC
*KINEMATIC COUPLING ORIENTATION See Elements.
To define a *COUPLING card
The *COUPLING card can be defined in three ways in HyperMesh:
· as rigid elements from the rigids panel
· as rbe3 elements from the rbe3 panel, in combination with *DISTRIBUTING card
· as groups from the interfaces panel.
Define a COUPLING card as a rigid element from the rigids panel:

2. Select the rigid element type as COUP_KIN or COUP_DIS for *KINEMATIC and *DISTRIBUTING
3. Click return.
5. Click the dependent toggle and select multiple nodes.
9. From the Mesh drop down menu, select Card Edit and select Elements.
11. Select the rigid element created above from the graphics area and click edit.
Note: The *COUPLING card created as rigid elements has automatically generated constrained name
and node based SURFACE. This surface contains all the dependent nodes defined for this rigid
element.
Define a *COUPLING-DISTRIBUTING card as an rbe3 from the rbe3 panel:

2. Select the rbe3 element type as COUP_DIS for *DISTRIBUTING cards.
3. Click return.
6. Click the independent node.
7. Select the reference node from the graphics area.
8. Click on the dependent nodes.
11. Select the update sub-panel of the rbe3 panel to change the weighting factors.
12. Change sub options for weight factors:
· With the set individual option you can enter the desired value and click on the node you want to
update
· With the select to adjust option you can increase the value with the right mouse button or decrease

with the left mouse button. Alternatively, you can increase/decrease the value by holding the left
mouse button and move the mouse up/down.
13. Finish the change of the weighting factors by pressing the update and the return button.
14. To edit parameters of the card select card editor from the setup pull-down menu.
15. Click the toggle and select elems.
16. Select the rbe3 element created above from the graphics area and click edit.
Note: The *COUPLING card created as rbe3 elements has automatically generated constrained name
and node-based SURFACE. This surface contains all the dependent nodes defined for this rigid
element.
Define a COUPLING card as groups from the interface panel:

3. Click type = and select the COUPLING card image type.
5. Select Kinematic or Distributing from the options toggle to define *KINEMATIC or DISTRIBUTING
7. Click return.
Note: The *COUPLING card created from the interfaces panel does not have any graphical display in
HyperMesh.
To create an *MPC card
2. Select the rigid element type BEAM, LINK, PIN or TIE.
3. Click return.
4. From the Mesh drop down menu, select Create and select Rigids.
5. Click the independent node button.
7. Click the dependent toggle and select single node or multiple nodes.
9. Check the degrees of freedom and click create.

Note: If single node was selected in Step 7, HyperMesh creates the *MPC automatically.
HyperMesh creates the *MPC with corresponding type and displays them as rigid element.
To create *EQUATION cards
1. Select the equations panel on the Analysis page.

4. Click create.
5. Click return.
Note: To modify individual node dofs or weighting factors, you must use the update sub-panel on the
equations panel. See the equations panel for more information.
To create a *KINEMATIC COUPLING card
2. For rigid =, select KINCOUP as the rigid element type.
3. Click return.
4. On the 1D page, select the rigids panel.
6. Click the dependent: toggle and select multiple nodes.

11. Click the switch and select elems.
12. Click elems and select the rigid element you just created.
13. Click edit.
15. In the Orientation = field, enter any system collector from the list.

16. Click return.
17. Click return.

Nodes

Parameters
*NODE NSET and SYSTEM The SYSTEM parameter is created

automatically during export based upon the
type of reference coordinate system that is
assigned to the nodes.
The card image for a node is displayed in

global Cartesian coordinates in HyperMesh.

Output Blocks
An output block in HyperMesh is a repository for output requests. Output blocks are added to load steps
(*STEP) from the load steps panel. Output requests organized into the output blocks are written out within
the corresponding step definition in the Abaqus input deck. It is recommended that all output requests be
defined from the Step Manager in the Abaqus user profile.

Parameters
*CONTACT FILE NSET, FREQUENCY,

MASTER, SLAVE
*CONTACT OUTPUT NSET, MASTER,

SLAVE, VARIABLE =
{ALL, PRESELECT},
CPSET, GENERAL
CONTACT
*CONTACT PRINT NSET, FREQUENCY
*EL FILE ELSET,

FREQUENCY,
POSITION = {NODES,
AVERAGED AT
NODES,
CENTROIDAL,
INTEGRATION
POINTS},
DIRECTIONS, LAST
MODE, MODE,
REBAR
*EL PRINT ELSET, .

FREQUENCY,
POSITION = {NODES,
AVERAGED AT
NODES,
CENTROIDAL,
INTEGRATION
POINTS}, SUMMARY,
TOTALS, LAST
MODE, MODE
*ELEMENT OUTPUT ELSET, POSITION =

{NODES,
CENTROIDAL,
INTEGRATION
POINTS}, VARIABLE
= {ALL, PRESELECT}

Parameters
*ENERGY FILE ELSET, FREQUENCY
*ENERGY OUTPUT ELSET, VARIABLE =

{ALL, PRESELECT}
*ENERGY PRINT NSET, FREQUENCY,

MASTER, SLAVE,
SUMMARY, TOTAL
*INCREMENTATION VARIABLE = Explicit template only. History data. Only for

OUTPUT {ALL/PRESELECT} *OUTPUT, HISTORY.
*INTEGRATED OUTPUT SECTION, SURFACE, Only for *OUTPUT, HISTORY

VARIABLE = {ALL,
PRESELECT}
*MODAL OUTPUT VARIABLE = ALL Standard 2D and 3D templates only. History

data. Only for *OUTPUT, HISTORY.
*NODE FILE NSET, FREQUENCY,

GLOBAL, LAST
MODE, MODE
*NODE OUTPUT NSET, VARIABLE =

{ALL, PRESELECT}
*NODE PRINT NSET, FREQUENCY,

GLOBAL, LAST
MODE, MODE,
SUMMARY, TOTALS
*OUTPUT FIELD, HISTORY, .

OP, VARIABLE,
FREQUENCY, TIME
MARKS, TIME
INTERVAL, NUMBER
INTERVAL, MODE
LIST, FILTER
Note: Output blocks must be added to the corresponding load steps for them to be written out to the
Abaqus deck.
All types of output requests in an output block are defined from the card image. The edit
button in the panel displays the card image of the currently loaded output block. The entity
selector buttons available in the output block panel are not useful for Abaqus. They should
be ignored.

To edit an output block card image to define various output requests
1. From the Setup drop down menu, select Edit and select Output Block.
2. Click the name = button and select an output block.
3. Click edit.
4. Define from available keywords, parameters and key identifiers.
5. Click return.
6. Click return.

Properties
The following Abaqus keywords are supported as properties in HyperMesh:

Parameters
*BEAM GENERAL ELSET, DENSITY, Only one *BEAM GENERAL SECTION

SECTION DEPENDENCIES, card is output per component. Therefore,
POISSON, ZERO, the beam elements in each component
SECTION = BOX, must have the same cross-sectional
CIRC, PIPE, properties.
GENERAL, HEX,
Sub-options *BEAM ADDED INERTIA,
ELBOW,
*CENTROID, *SHEAR CENTER, *AXIAL,
NONLINEAR
*TRANSVERSE SHEAR STIFFNESS,
GENERAL, RECT,
and *THERMAL EXPANSION are
I-SECTION,
supported.
L-SECTION,
TRAPEZOID,
ARBITRARY,
ROTARY INERTIA
*BEAM SECTION ELSET, MATERIAL, Only one *BEAM SECTION card is output
POISSON, per component. Therefore, the beam
SECTION = BOX, elements in each component must have
CIRC, PIPE, HEX, the same cross-sectional properties.
I-SECTION,
Sub-options *BEAM ADDED INERTIA
L-SECTION,
and *TRANSVERSE SHEAR STIFFNESS
ELBOW, RECT,
are supported.
TRAPEZOID,
ARBITRARY,
ROTARY INERTIA,
TEMPERATURE
*COHESIVE SECTION ELSET, MATERIAL, Sub-option *TRANSVERSE SHEAR

CONTROLS, STIFFNESS is supported.
ORIENTATION,
RESPONSE=
{TRACTION
SEPARATION,
CONTINUUM,
GASKET},
STACK DIRECTION
= {1,2,3,
ORIENTATION},
THICKNESS=
{GEOMETRY,
SPECIFIED}
*CONNECTOR ELSET, BEHAVIOR, The following types are supported:

SECTION ELMINATION
Standard template:
ACCELEROMETER, ALIGN, AXIAL,

Parameters
BEAM, BUSHING, CARDAN,

CARTESIAN, CONSTANT VELOCITY,
CVJOINT, CYLINDRICAL, EULER,
FLEXION-TORSION,
FLOW-CONVERTER, HINGE, JOIN,
LINK, PLANAR, PROJECTION
CARTESIAN, PROJECTION
FLEXION-TORSION, RADIAL-THRUST,
RETRACTOR, REVOLUTE, ROTATION,
SLIDE-PLANE, SLIPRING, SLOT,
TRANSLATOR, UJOINT, UNIVERSAL,
WELD,
Explicit template:
All listed above, as well as
ROTATION-ACCELEROMETER
*CONTACT DAMPING DEFINITION=DAMP This card is a sub-option in the

ING COEFFICIENT *SURFACE INTERACTION card image.
*DASHPOT ELSET, Only one *DASHPOT card is output per

NONLINEAR, component. Therefore, the spring
ORIENTATION, elements in each component must have
DEPENDENCIES the same properties.
When the *DASHPOT card is written for
DASHPOT1 elements, both dof1 and dof2
are written, but Abaqus only reads dof1.
For DASHPOTA elements, choose the
DASHPOTA option in the *DASHPOT
card image.
*ELEMENT OFFSET,
PROPERTIES ORIENTATION,
THICKNESS
*FASTENER (SPOT NAME, MASS

WELD) PROPERTY
*FLUID PROPERTY ELSET, REF NODE, Sub-options *FLUID DENSITY, *FLUID

TYPE, AMBIENT EXPANSION, and *FLUID BULK
NAME MODULUS are supported.
*FRICTION ANISOTROPIC, This card is a sub-option in the

EXPONENTIAL *SURFACE INTERACTION card image.
DECAY, TAUMAX, It is also supported as a separate card
DEPENDENCIES, image to allow for it to be used as a
ROUGH, USER, sub-option of the *CONNECTOR
ELASTIC SLIP, FRICTION card (in *CONNECTOR
LAGRANGE, SLIP BEHAVIOR).
TOLERANCE,

Parameters
DEPVAR,
PROPERTIES
*GAP ELSE Only one *GAP card is output per

component. Therefore, the gap elements
in each component must have the same
properties.
*GASKET SECTION ELSET, MATERIAL, Only in Standard templates.

BEHAVIOR,
ORIENTATION,
STABILIZATION
STIFFNESS
*JOINT ELSET, Only one *JOINT card is output per

ORIENTATION component. Therefore, the spring
elements in each component must have
the same properties.
The *SPRING and *DASHPOT cards in
the *JOINT property behave the same
way as the individual cards mentioned
above. See the How do I section below
for more information.
*MASS ELSET, Only one *MASS card is output per

COMPOSITE, component. Therefore, the mass
ALPHA elements in each component must have
the same properties.
*MEMBRANE SECTION ELSET, MATERIAL, Sub-option *HOURGLASS STIFFNESS is

ORIENTATION, supported.
NODAL
THICKNESS,
POISSON,
CONTROLS
*NONSTRUCTURAL ELSET, UNIT = For Abaqus Explicit template only

MASS {TOTAL MASS,
MASS PER
VOLUME, MASS
PER AREA, MASS
PER LENGTH},
DISTRIBUTION =
{MASS
PROPORTIONAL,
VOLUME
PROPORTIONAL}

Parameters
*PHYSICAL ABSOLUTE ZERO,

CONSTANT STEFAN
BOLTZMANN,
UNIVERSAL GAS
CONSTANT
*RIGID BODY ELSET, REFNODE, For Analytical Rigid Surfaces, the

ANALYTICAL ANALYTICAL SURFACE parameter
SURFACE, should point to the corresponding
ISOTHERMAL, PIN ANALYTICAL_RIGID_SURFACE group
NSET, TIE NSET, from the card image of the *RIGID BODY
POSITION, card.
DENSITY, NODAL
THICKNESS,
OFFSET
*ROTARY INERTIA (no ELSET, ALPHA, Only one *ROTARY INERTIA card is
longer listed on panel) COMPOSITE, output per component. Therefore, the
ORIENTATION ROTARY1 elements in each component
must have the same properties.
*SECTION CONTROLS NAME, WEIGHT

FACTOR, SECOND
ORDER
ACCURACY,
DISTORTION
CONTROL,
LENGTH RATIO,
HOURGLASS =
{VISCOUS,
COMBINED,
ENHANCED,
RELAXED
STIFFNESS,
STIFFNESS},
KINEMATIC SPLIT
= {CENTROID,
AVERAGE STRAIN,
ORTHOGONAL},
ELEMENT
DELETION, INITIAL
GAP OPENING,
MAX
DEGRADATION,
VISCOSITY
*SHELL GENERAL ELSET, MATERIAL, Sub-options *HOURGLASS STIFFNESS

SECTION OFFSET, and *TRANSVERSE SHEAR STIFFNESS
ORIENTATION, are supported.
SECTION
INTEGRATION,
NODAL

Parameters
THICKNESS,
POISSON,
TEMPERATURE,
COMPOSITE,
CONTROLS,
STACK
DIRECTION,
POISSON
*SHELL SECTION ELSET, MATERIAL, Sub-options *HOURGLASS STIFFNESS

OFFSET, and *TRANSVERSE SHEAR STIFFNESS
ORIENTATION, are supported
SECTION
INTEGRATION,
NODAL
THICKNESS,
POISSON,
TEMPERATURE,
COMPOSITE,
CONTROLS,
STACK
DIRECTION,
POISSON
*SOLID SECTION ELSET, MATERIAL, Sub-option *HOURGLASS STIFFNESS is

ORIENTATION, supported.
STACK
DIRECTION,
COMPOSITE,
CONTROLS
*SPRING ELSET, Only one *SPRING card is output per

NONLINEAR, component. Therefore, the spring
ORIENTATION, elements in each component must have
DEPENDENCIES the same properties.
When the *SPRING card is written for
SPRING1 elements, both dof1 and dof2
are written, but Abaqus only reads dof1.
For SPRINGA elements, choose the
SPRINGA option in the *SPRING card
image.
*SURFACE BEHAVIOR NO SEPARATION This card is a sub-option in the

*SURFACE INTERACTION card image.
PRESSURE-OVER
CLOSURE= HARD,
EXPONENTIAL,
LINEAR,
TABULAR,
AUGMENTED
LAGRANGE,

Parameters
PENALTY
*SURFACE NAME For Abaqus Explicit template, this card is

INTERACTION defined as a group from the interface
panel.
*SURFACE SECTION ELSET, DENSITY
To define a *SURFACE INTERACTION card in standard3d and

standard2d templates
1. From the Properties drop down menu, select Create.

2. Enter a property name after prop name =.
3. Set the type= field to ALL.
4. Click card image = and select the SURFACE_INTERACTION card image type.
6. Click SurfaceBehavior, ContactDamping or Friction options to define *SURFACE BEHAVIOR,
*CONTACT DAMPING or *FRICTION cards respectively.
7. Click the DataLine option to input the optional out-of-plane thickness of the surface or cross-sectional
area for every node in the node-based surface.
8. Click return.
To define non-linear SPRING or DASHPOT properties
To define a non-linear SPRING or DASHPOT property, you must first create the SPRING elements, then
create the property with the SPRING or DASHPOT card image, and then assign a property to the
component collector to which the elements belong.
Create the elements:
1. In the Model Browser, right-click on Component and select Create.
2. Enter a name for the new component and if desired, select a color.
3. Click Create.
4. The element creation panel is displayed. Select the nodes for this component and click return.

Create the property:
5. Click the Property Collector icon.

6. In the prop name = field, enter a name for the property collector.
7. Click Type= and select Line Section.
8. Click Card Image= and select SPRING.
9. Click Create/edit.
10. Select the nonlinear option from the menu.
11. Select the SPRINGSTIFCARDS = or DASHPOTDATACARDS = field.
12. Enter the number of Force/Deflection or Force/Velocity lines required for the property definition.
13. Enter the Force/Deflection or Force/Velocity information in the table displayed in the card image.
14. Click return.
Assign the property to the component:
15. Click the Component Collector icon.

16. Select the Assign sub-panel.
17. Click the comps button and select the component.
18. Click the property= button and select the property to assign to this component.
19. Click return.
You can also assign the property to the component by clicking the Properties icon, graphically selecting
the elements, and clicking the property= button and selecting the property.
To define frequency dependent SPRING or DASHPOT properties
To define a non-linear SPRING or DASHPOT property, you must first create the SPRING elements, then
create the property with the SPRING or DASHPOT card image, and then assign a property to the
component collector to which the elements belong.

3. Click Create.

7. Click Type= and select Line Section.
8. Click Card Image= and select SPRING or DASHPOT.
10. Select the SPRINGSTIFCARDS = or DASHPOTDATACARDS = field.
11. Enter the number of Stiffness/Frequency or DashpotCoeff/Frequency lines required for the property
definition.
12. Enter the Stiffness/Frequency or DashpotCoeff/Frequency information in the table displayed in the
card image..
13. Click return.

18. Click return.
To add a TIE or PIN NSET to a *RIGID BODY


3. Click Create.

7. Click Type= and select RIGID SECTION.
8. Click Card Image= and select RIGIDS.
10. Check the Tie_Nset or Pin_Nset option.
11. Click the corresponding Node_Set field in the card image and select the node set from the list.
13. Click return.

18. Click return.
To add a deformable component or elset to a *RIGID BODY

3. Click Create.


7. Click Type= and select RIGID SECTION.
8. Click Card Image= and select RIGIDS.
10. Select Component or Set from the ELSET_Options toggle.
11. Click the corresponding Component_Name or Element_Set_Name field in the card image and select
the deformable component or elset from the list.
13. Click return.

18. Click return.
To define a *FASTENER (SPOT WELD) PROPERTY card
1. From the Properties drop down menu, select Create.

2. Enter a property name after prop name =.
3. Click card image = and select the FASTENER_PROPERTY card image type.

6. Click return.

Sets
Sets can be created of nodes, elements, components, and other sets.
*DISTRIBUTION LOCATION, NAME, TYPE
*ELSET ELSET, GENERATE
*EMBEDDED ELEMENT ABSOLUTE EXTERIOR TOLERANCE, EXTERIOR TOLERANCE,

HOST ELSET, ROUNDOFF TOLERANCE
*NODAL THICKNESS GENERATE
*NSET NSET, ELSET, GENERATE, UNSORTED
Sets can be specified directly from nodes and elements in the model or by a formula. Sets of sets and
components are also supported in HyperMesh Abaqus templates. To create sets that contain a
combination of sets and individual nodes or elements, select the add by IDs option in a formula-based set.
A User Comments block is supported for all sets. See the information below on how to add comments to
any set card image. These comments will be preserved during import and export of the Abaqus input deck.
When HyperMesh encounters an **HM_GENERATE_SET_EXPAND in the input file, all sets with the
GENERATE parameter are imported as regular sets. This is useful for when node/element IDs are
renumbered during import.
To create *NSET or *ELSET cards
1. From the Tools drop down menu, select Create and select Sets.
2. Enter a set collector name after name =.
Note: Abaqus set names cannot begin with a number.
3. Ensure that the card image field is blank.

4. Click the lower switch in the entity field and select nodes or elems.
5. Select nodes or elems from the graphics window or choose from the extended entity selection menu.
6. Click create.
7. Click return.

To create *NSET or *ELSET cards with the GENERATE option
2. Type a set collector name after name =.
3. Click the lower switch in the entity field and select nodes or elems, whichever corresponds to the
entity type in the set you are creating.
4. Select the nodes or elements, either graphically or by using the extended selection menu.
5. Click create. The *NSET or *ELSET card should be created before you add a formula expression.
6. Select the formula check box to enable the formula fields on the panel.
7. Click the switch above the center entity field and select add by range.
8. Type the value of the first node/element in the from field, the value of the last node/element in the to
field, and the value to increment by in the by field.
9. Click add. The expression appears in the first individual expression box.
10. Click return.
To reveiw a *NSET or *ELSET card
1. From the Tools drop down menu, select Edit and select Sets.
2. Click review.
3. Select the set you want to review.
HyperMesh highlights and selects the entities contained in the set that you selected.
4. Click return.
To update a *NSET or *ELSET card
1. From the Tools drop down menu, select Edit and select Sets.
2. Click review.
3. Select the set to update.
HyperMesh highlights and selects the entities contained in the set you selected.
4. Select or deselect nodes or elements to change the definition of the set.

5. Click update.
6. Click return.
To add comments to a set card image
1. From the Tools drop down menu, select Card Edit and select Sets.
2. Click sets and select the set you want to add comments to.
3. Click edit.
4. Click the drop down box below the User Comments heading in the menu.
5. Select Show In Menu/Export.
comments and click Enter.
8. Click return.
To create *ELSET of other existing ELSETs
2. Enter a set name after name =.
Note: Abaqus set names cannot begin with a number
3. Click the upper switch and select comps or sets.
4. Select the comps or sets from the graphics window or choose from the extended entity selection
menu.
5. Click create.
6. Click return.
7. Select the Card Edit icon.

8. Click the switch and select sets.
9. Click sets and select the set you just created.
10. Click edit.
11. Select the Elset option from the CompSet_type toggle.
12. Click return.

To create *NSET of other existing NSETs
Note: Abaqus set names cannot begin with a number
3. Click the upper switch and select sets.
4. Select sets from the extended set selection menu.
5. Click create.
6. Click return.
7. Select the Card Edit icon.

10. Click edit.
11. Select the Nset option from the SetSet_type toggle.
12. Click return.
To create *NSET from an existing ELSET
3. Click the upper switch and select comps or sets.
4. Select a comp or set from the graphics window or from the extended entity selection menu.
5. Click create.
6. Click return.
7. Select the Card Editor icon.


10. Click edit.
11. Select the Nset by Elset option from the SetSet_type toggle.
12. Click return.
To create a *DISTRIBUTION card for elements
3. Select the DISTRIBUTION card image in the card image field.

4. Click the lower switch in the entity field and select elems.
5. Pick elements from the graphics window or choose from the extended entity selection menu.
6. Click create.
7. Create a new property collector by clicking the Properties icon on the toolbar.
8. Enter a name for the new property collector, and select ELEMENT_PROPERTIES in the card image
field. Click create/edit.
9. Click the yellow Set1 button and select the set you created in steps 1-6 as the distribution set of
elements. This will define the property.
10. Click return to close the card image.
11. Click the Card Edit icon and set the switch to elems.
12. Click elems and select the element chosen in Step 5 above.
13. Click edit.
14. Select the Thickness check box. The THICKNESS field appears in the card image. Type a value for
the thickness and click return. (Repeat this step for each element in the set.)
To create a *DISTRIBUTION card for nodal clearance

3. Select the DISTRIBUTION card image in the card image field.
4. Click the lower switch in the entity field and select nodes.
5. Pick nodes from the graphics window or choose from the extended entity selection menu.
6. Click create.
7. Create a new property collector by clicking the Properties icon on the toolbar.
8. Enter a name for the new property collector, and select ELEMENT_PROPERTIES in the card image
field. Click create/edit.
9. Click the yellow Set1 button and select the set you created in steps 1-6
10. Click return to close the card image.
11. Click the Card Edit icon and set the switch to nodes.
12. Click nodes and select the nodes chosen in Step 5 above.
13. Click edit.
14. Select the Clearance check box.The CLEARANCE field appears in the card image. Type a value for
the clearance and click return. Repeat this step for each node in the set.
To create a *NODAL THICKNESS card
3. Select the NODAL THICKNESS card image in the card image field.
5. Pick nodes from the graphics window or choose from the extended entity selection menu.
6. Click create.
7. Click return.
8. Click the Card Edit icon and set the switch to nodes. Pick a node from the set of nodes you
selected in step 5 and click edit.
9. Select the Thickness check box. The THICKNESS field appears in the card image.
10. Type a value for the thickness and click return.
11. Repeat steps 8-10 for each node in the set.

To create a *NODAL THICKNESS card with the GENERATE option
3. Select the NODAL THICKNESS card image in the card image field.
5. Click create. The *NODAL THICKNESS card should be created before specifying the formula.
6. Select the formula check box to enable the formula fields on the panel.
7. Click the switch above the center entity field and select add by range.
8. Type the value of the first node in the from field, the value of the last node in the to field, and the value
by which the nodes should increment in the by field.
9. Click add. The expression appears in the first individual expression box. Repeat steps 7 and 8 to add
more formula expressions.
10. Click return.
To create an *EMBEDDED ELEMENT card
2. Type a set name in the name = field.
3. Select the embedded element card image in the card image field.
4. Click the lower switch in the entity field and select elems, comps, or sets.
5. Pick corresponding entities from the graphics window or choose from the extended entity selection
menu.
6. Click create.
7. Click the card edit button to card-edit the set to define various parameters.

Abaqus Utility Menu
The following macros are included on the Abaqus page of the Utility menu when you load the Abaqus
user profile.
Applies to templates: Description
Solid Face Alignment Standard3D

Explicit
Solid Face Alignment Determines the default stack or

thickness direction for Abaqus
composite solid, gasket and
continuum shell elements.
Review The Review button opens the

HyperMesh element selector panel
and allows you to pick solid elements.
Selected elements are highlighted.
When you click proceed, it highlights
the face1 of selected solids and
draws an arrow along the default
stack (or thickness) direction of
selected solids.
Reset The Reset button deletes the stack

(or thickness) direction arrows.
Conversion Standard2D
Standard3D
Abaqus to Nastran Opens the conversion tool to convert

Abaqus model files into a Nastran
format.
Nastran to Abaqus Opens the conversion tool to convert

Nastran model files into an Abaqus
format.
Dummy Explicit
Import The Import Dummy button allows

you to import an Abaqus dummy
model and the corresponding
positioning file.
Export The Export Dummy button allows

you to export an Abaqus dummy

model without the hierarchical system
references established in the import
process.
Cleanup Hierarchy Cleans up the hierarchical system

references that are established during
the import process. Use this macro if
you export without using the Export
macro.
Tools Standard2D
Standard3D
Explicit
Component Browser Activates the Abaqus Component

Browser, which allows you to
review/edit components with
associated properties and materials
in HyperMesh.
Step Manager Activates the Abaqus Step Manager,

which allows you to define Abaqus
history (*STEP) information in
HyperMesh.
Contact Manager Activates the Abaqus Contact

Manager, which allows you to create,
edit and review the following cards in
HyperMesh:
· *CONTACT PAIR
· *PRE-TENSION SECTION
· *TIE
· *CONTACT
· *SURFACE, TYPE = ELEMENT
· *SURFACE, TYPE = NODE
· *SURFACE, COMBINE
· *SURFACE, CROP
· *SURFACE, TYPE = CUTTING

SURFACE
· *SURFACE, TYPE = CYLINDER,

REVOLUTION, or SEGMENTS
· *SURFACE INTERACTION
· *FRICTION
· *SURFACE BEHAVIOR
· *CONTACT DAMPING

Component Browser
The Abaqus Component Browser is an interactive table representing Abaqus components with associated
properties and materials. It is accessed by loading the Abaqus user profile and clicking the Component
Browser button on the Abaqus Utility menu.
The essential features of the Abaqus Component Browser are:
· Abaqus components with various associated properties and materials are listed in separate
columns.
· You can select the column types from a set of available options.
· There are two modes of operation: review and editable. The review mode allows you to review
component information without changing any values. The editable mode allows you to change
values for the selected components.
· There are enhanced selection, review, display, and filter options for components.
· Components can be sorted according to any available column.
· The current configuration is saved automatically to a file at the end of a session and recalled on
reload. You can also save and load a configuration file.
· The table data can be exported in CSV and HTML format.
· Right click on the table to display menu options. All pull-down menu options are available using a
right click.
· Columns can be moved or swapped by pressing the left mouse button on a column title and
dragging it to the desired location.
· Columns can be resized by positioning the cursor along a column border, pressing the left or right
mouse button, and dragging the border to a new position.
· The shift or ctrl key combined with a left click can be used to select multiple rows.
Columns
The type of columns can be selected by clicking Table and selecting Configure and then selecting
Columns.... A dialog with the available column options is displayed. You can select the desired option
and the table will display only the selected columns. The available columns types are:
Title Description
Vis Visualization status. 1 = display on, 0 = display off
Name HyperMesh name of the component (maximum 32 characters)
Long Names Maintained for files from HyperMesh 7.0 and previous, when component
names could have only 32 characters (not recommended).
Id HyperMesh ID of the component

Color Component color
Style Component visualization style (hidden line, wireframe, etc.)
Property Name Name of the property collector assigned to the component
Property Card Image Property card image types to define the sectional properties
Material Abaqus materials (*Material, *Connector Behavior, or *Gasket Behavior)

associated with the component
Thickness Thickness of Shell/Membrane elements
Density Density of the material assigned to the property
Prop on Elems Yes: component contains elements that are individually assigned to
properties; No: No individual element assignment in this component
Elems Number of elements in the component
Nodes Number of nodes in the component
Components All or Displayed Mode

The Component Browser list components in two modes: All or Displayed. If All is selected from the
Components menu, the table lists all the components in the model. If Displayed is selected, only the
visible components are shown. Blank components are not shown in the Displayed mode even though
their display status is on.
Filter
The Component Browser table supports advanced filtering based on all available columns. The Filter...
menu option opens the Filter dialog as shown below.
You can write any valid string with a wildcard (*) in any of the available column types and click Apply to
filter the table. For example, if you want to show all components that start with letter ‘c’ and use material ‘
steel’, you can use the dialog as shown below. Note that the filter strings are case sensitive.
Show All turns off the filtering and displays all the components. Select Table and select Configure and
then select the Filter on top option to keep the Filter dialog posted after clicking Apply or Show All.
Otherwise, it closes.
Editable Mode

The editable mode in the Component Browser allows you to change values for all selected components at
the same time. From the Table option, click the Editable option to open the component browser in
editable mode. Cells with a white background can be manually edited. When you click on an editable cell,
it is selected with a cursor. Once a cell is selected, enter a value and press Enter.
If you want to assign the same value to multiple components at once, select the column type and value
from the Assign Values: pull-down menu and click Set. All the selected components will be updated with
the assigned values.
Note: Starting in HyperMesh 9.0, it is possible to assign property collectors directly to elements. The
component can point to a property, but an individual element within the component can point to
another. To unassign all elements within a component, you can choose Prop on Elems from
Assign Values and set it to No.

Contact Manager
The Abaqus Contact Manager allows you to create, edit and review the following cards in HyperMesh:
· *CONTACT PAIR
· *PRE-TENSION SECTION
· *TIE
· *CONTACT
· *SURFACE, TYPE = ELEMENT
· *SURFACE, TYPE = NODE
· *SURFACE, COMBINE
· *SURFACE, CROP
· *SURFACE, TYPE = CUTTING SURFACE
· *SURFACE, TYPE = CYLINDER,REVOLUTION or SEGMENTS
· *SURFACE INTERACTION
· *FRICTION
· *SURFACE BEHAVIOR
· *CONTACT DAMPING
The Abaqus Contact Manager is organized into three main tabs:

Interface
Surface
Surface Interaction
The following rules apply when you are using the Abaqus Contact Manager.
· When the Contact Manager window is minimized or it is behind the HyperMesh window, restore it
by clicking the Contact Manager button in the Abaqus Utility menu.
· To display the bubble help for a button, place the cursor over the button for a few moments.
· Double click on the interface, surface and surface interaction names in the table to open the
corresponding edit windows. Right click on the names to display pull-down menu options.
· Table columns can be resized by positioning the cursor along a column border, pressing the left or
right mouse button, and dragging the border to a new position.
· The shift and ctrl keys can be used with a left mouse click to select multiple items in a table.
· Press ctrl and the left or right arrow key to move the cursor within the active cell. Use the left, right,
up and down arrows to change the active cell.
· Right click on the Review button to clear the review selections.

· If you create, update or delete components, groups, properties, or entity sets from HyperMesh
panels while the Contact Manager is open, click the Sync button to update the Contact Manager
with the new changes.
· In the Friction and Surface Behavior tables, right click in the tables to display a pull-down menu
containing copy, cut and paste options. Comma delimited data can be copied, cut, or pasted in
these tables. Relevant hot keys, for example, ctrl-c, ctrl-x, and ctrl-v on PC, will also work.
· In some fields in the Contact Manager, you can access the Entity Browser, which is available via
the … button. The Entity Browser makes it more convenient to view and sort long lists of
components or other entities when selecting them for the field.
To load the Abaqus user profile
1. From the Preferences pull-down menu, select User Profiles....

2. Select Abaqus as the profile name on the User Profiles dialog.
4. Click OK.
To start the Abaqus Contact Manager
1. Load the Abaqus user profile.

2. Click Contact Manager in the Abaqus Utility menu.
Interface Tab
The interface tab contains a description of the *CONTACT PAIR, *PRE-TENSION SECTION, *CONTACT
(explicit only), and *TIE cards with corresponding surfaces and surface interactions. You can create, edit,
review, and delete interfaces from this tab. You can also edit, review, and delete surfaces and surface
interactions that are displayed on this tab.
The Interface table contains the following columns:
Name The contact interface names. These names are not exported to the
Abaqus input file. They are useful for identifying the various interfaces in
HyperMesh.

Interface Type The interface types. The currently supported types are contact pair,
pre-tension section, general contact, and tie.
Surface 1 The names of the slave surfaces in Abaqus Standard (or the first surface
in Abaqus Explicit).
Surface 2 The names of the master surfaces in Abaqus Standard (or the second
surface in Abaqus Explicit).
Surface Interaction The names of the surface interaction properties.
Surf1 display The display on/off check boxes and color change buttons for the surfaces
shown in the Surface 1 column. The color can be changed by clicking
the color button and selecting a color from the menu.
Surf2 display The display on/off check boxes and color change buttons for the surfaces
shown in the Surface 2 column. The color can be changed by clicking
the color button and selecting a color from the menu.
Note:
· The display on/off check boxes and color change buttons are disabled if the corresponding surface
is defined with sets and no displays are created for them.
· Double click on the interface, surface, and surface interaction names in the table to open the
corresponding edit windows. Right click on a name to display menu options.
· Right click on an interface, surface, and surface interaction name to display menu options. The
available options are:
- Edit
- Delete
- Review
- Review with underlying entity
- Reset review
- Review Options (Review by Highlighting, Review by Color Change, Transparency, and Grey
Color)
- Display All
- Display None
- Display Reverse
- Draw Rigid Surfaces
The Edit, Review, Delete, Display All, Display None and Display Reverse options work like the
corresponding buttons (described below). Review with underlying entity highlights the surface
along with the attached elements (or nodes). The Reset review button clears the review
selections.

· The shift or ctrl key and a left click can be used to select multiple items in a table.
The Interface tab contains the following buttons:
Auto Launches the Auto Contact dialog that allows you to quickly and easily create
interactions between several parts of your model.
New ... Opens the Create New Interface dialog in which you enter the name and type of
the new interface. The Same as: option allows you to create an interface by
copying from an existing interface. The Create... button in this dialog creates the
interface and opens the corresponding Contact Pair, Tie, General Contact, or
Pre-Tension Section dialog.
Edit ... Opens the corresponding dialog for editing the selected interface, surface, or
surface interaction.
Review Reviews the selected interface, surface, or surface interaction as follows:

· For surfaces, the selected surface is highlighted in white in the HyperMesh window.
The highlighting shows up through solid mesh in performance graphics. If the
surface is defined with sets (display option disabled), the underlying elements are
highlighted. A right-click on the Review button clears the review selections.
· For interface types, corresponding slave and master surfaces are
highlighted together in the HyperMesh window. The surfaces are
highlighted in the same fashion as mentioned above. A right-click on the
Review button clears the review selections.
· For surface interactions, the names of all interfaces using the selected
surface interaction in the table are highlighted. There is no graphical review
in the HyperMesh window for surface interaction.
Delete Deletes the selected interfaces, surfaces, or surface interactions. You can delete
single or multiple selections from the table.
Rename Rename the selected interface, surface, or surface interaction.
Sync Updates the Contact Manager with the current HyperMesh database. If you
manually create, update, or delete components, groups, properties, or entity sets
from HyperMesh panels while the Contact Manager is open, click the Sync button
to update the Contact Manager with the new changes.
Close Closes the Contact Manager.
Help Invokes the online help for Abaqus Contact Manager.

Contact Pair
The Contact Pair dialog allows you to define the *CONTACT PAIR card. Options vary according to the
active template. There are two tabs in this dialog.
Define
Parameter
The Contact Pair dialog contains the following buttons:
OK Updates the HyperMesh database with the changes and closes the Contact Pair
dialog.
Apply Updates the HyperMesh database with the changes without closing the Contact
Pair dialog.
Cancel Closes the Contact Pair dialog without updates.
Contact Pair: Define Tab

The Define tab allows you to select the slave surface, master surface, and surface interaction for the
*CONTACT PAIR card. You can also review the selected surfaces or create new ones.
The Define Tab contains the following options:
Auto-generated Select this option for HyperMesh to automatically generate *SURFACE

surface from cards from a selected component.
component
When this option is selected, the Surface: field becomes a Component:
field, and you can select a component from the adjacent drop-down list.
Click Slave>> or Master>> to add them to the table of included surfaces
as slave or master, respectively.

Surface The Surface: field contains a list of the existing surfaces. Select a slave
surface from the list or use the … button to open the entity browser to
select a surface.
Click the Slave>> button to add the surface as a slave to the table of
selected surfaces. Click the Master>> button to add the surface as a
master. Click Remove>> to remove any selected surface from the table.
You can add multiple sets of surfaces to the table.
Click the New button to create a new surface. Once you have specified
the surface properties, the surface appears in the drop-down list, where
you can select it and add it to the table. For a description of defining
surfaces, see Element Based Surface or Node Based Surface.
The Review button highlights the selected slave surface in white and
displays it through solid mesh in performance graphics in the HyperMesh
window. If the surface is defined with sets, the underlying elements are
highlighted. Right click on Review to clear the review selections.
Surface interaction The Surface Interaction: field contains a list of the existing surface
interaction properties. You can select a surface interaction from the list.
You can also use the … button to open the entity browser to select a
surface.
The New button opens the Create New Surface Interaction dialog for
creating a new surface interaction. When the new surface interaction has
been defined, the Contact Pair dialog reflects the newly-created surface
interaction as the interaction of the contact pair. For a description of
defining surface interactions, see Surface Interaction.
Note: The surface interaction is optional in explicit template. The
Define tab will show a Surface interaction check box if the explicit
template is loaded. This option should be checked first if a surface
interaction property is intended for the contact pair card.
Note that if you create multiple pairs of contacts, they will appear on the Interface tab in separate entries
using the same name.
Contact Pair: Parameter Tab

The Parameter tab allows you to define optional parameters for the contact pair card. Options vary
according to the template loaded.
The supported parameters are:
For Standard.3d/2d template Adjust, Extension Zone, Smooth, Hcrit, Tied, and Small
sliding. See the Abaqus Online Documentation for a
detailed description of these parameters

For Explicit template Mechanical constraint, CPSET, OP, Weight, and Small
sliding. See the Abaqus Online Documentation for a detailed
description of these parameters
Tie
The Tie dialog allows you to define the *TIE card. This dialog contains two tabs:
Define
Parameter
The Tie dialog contains the following buttons:
OK Updates the HyperMesh database with the changes and closes the Tie dialog.
Apply Updates the HyperMesh database with the changes without closing the Tie
dialog.
Cancel Closes the Tie dialog without updates.
Tie: Define Tab

The Define tab allows you to select slave surface and master surface for the *TIE card. You can also
review the selected surfaces or create new ones.

Auto-generated surface Select this option for HyperMesh to automatically generate

from component *SURFACE cards from a selected component.
When this option is selected, the Surface: field becomes a
Component: field, and you can select a component from the
adjacent drop-down list. Click Slave>> or Master>> to add them to
the table of included surfaces as slave or master, respectively.
Select slave surface Select this option for HyperMesh to automatically generate
*SURFACE cards from a selected component.
When this option is selected, the Surface: field becomes a
Component: field, and you can select a component from the
adjacent drop-down list. Click Slave>> or Master>> to add them to
the table of included surfaces as slave or master, respectively.
Select master surface The Surface: field contains a list of the existing surfaces. Select a
slave surface from the list or use the … button to open the entity
browser to select a surface.
Click the Slave>> button to add the surface as a slave to the table
of selected surfaces. Click the Master>> button to add the surface
as a master. Click Remove>> to remove any selected surface from
the table. You can add multiple sets of surfaces to the table.
Click the New button to create a new surface. Once you have
specified the surface properties, the surface appears in the
drop-down list, where you can select it and add it to the table. For a
description of defining surfaces, see Element Based Surface or
Node Based Surface.
The Review button highlights the selected slave surface in white
and displays it through solid mesh in performance graphics in the
HyperMesh window. If the surface is defined with sets, the
underlying elements are highlighted. Right click on Review to clear
the review selections.
Note that if you create multiple pairs of ties, they will appear on the Interface tab in separate entries using
the same name.

Tie: Parameter Tab
The Parameter tab allows you to define optional parameters for the *TIE card.
Explicit:
Standard2D/Standard3D:
The supported parameters are: Position tolerance, Tied nset, Cyclic symmetry (standard only),
Constraint ratio, No rotation, Adjust, No Thickness and Type. The Position tolerance and Tied nset
are optional mutually exclusive parameters. Select None if you do not want to select either of them. See
the Abaqus Online Documentation for detailed descriptions of these parameters.
Tied nset The Tied nset menu contains a list of existing node sets. You can select a
Selection node set from the list.
The Review Set button reviews the selected node set by highlighting it in the
HyperMesh window.
The Create/Edit Set button opens the entity sets panel in HyperMesh.
When you finish creating/editing the set, click return. The Tie window is
updated with the new set displayed in node set list.
Pre-Tension Section
The Pre-Tension Section dialog allows you to define the *PRE-TENSION SECTION card. This dialog
contains two tabs:
Define
Parameter
The Pre-Tension Section dialog contains the following buttons:
OK Updates the HyperMesh database with the changes and closes the Pre-tension

Section dialog.
Apply Updates the HyperMesh database with the changes without closing the
Pre-tension Section dialog.
Cancel Closes the Pre-tension Section dialog without updates.
Pre-Tension Section: Define Tab

The Define tab allows you to select the pre-tension node ID and element ID for beam or truss element or
the surface for the *PRE-TENSION SECTION card. You can also review the selected surface or create a
new one.
Pre-tension node Pick Node allows you to pick a node from HyperMesh graphics, or you
can enter a node number in the text box.
Review highlights the selected node in the HyperMesh window.
Element This option is valid for beam or truss elements only. It is mutually
exclusive to the Select surface option.
Pick Element allows you to select an element from HyperMesh
graphics, or you can enter an element number in the text box.
Review highlights the selected element in the HyperMesh window.
Select surface The Select surface menu contains a list of the existing surfaces. You
can select a surface from the list.
Review highlights the selected surface in white and displays it through
solid mesh in performance graphics in the HyperMesh window. If the
surface is defined with sets, the underlying elements are highlighted.
Create New opens the Create New Surface dialog for creating a new
surface. When the new surface has been defined, the Pre-Tension
Section dialog reflects the newly created surface. For a description of
defining surfaces, see Element Based Surface or Node Based Surface.
Note: Right click on Review to clear the review selections in HyperMesh graphics.

Pre-Tension Section: Parameter Tab
The Parameter tab allows you to define optional data lines for the *PRE-TENSION SECTION card.
Check Dataline to activate all three input boxes for the first, second, and third component of the normal.
See the Abaqus Online Documentation for a detailed description of these items.
Click the Define by vector button to define the values in the input boxes by a vector. To create a vector,
click the Create/Edit vector.. button.
General Contact
The General Contact option allows you to define the *CONTACT, *CONTACT INCLUSIONS, *CONTACT
EXCLUSIONS, *CONTACT PROPERTY ASSIGNMENT, *CONTACT FORMULATION, *CONTACT
CONTROLS ASSIGNMENT and *SURFACE PROPERTY ASSIGNMENT cards for Explicit template only.
The current version of Contact Manager does not have a Tcl/Tk dialog to define the General Contact.
Instead, it takes you to the corresponding card image panel as shown below.
Click the Edit... button in the Contact Manager to go into the card editor to define all relevant keywords,
parameters and data lines. When you are finished, click return and the Contact Manager window will once
again be displayed.
Auto Contact
The Auto Contact dialog helps you define the *CONTACT PAIR and *TIE keywords along with the
corresponding *SURFACE cards.
Auto Contact is functionality within the Abaqus user profile that allows you to quickly and easily create
interactions between several parts of your model. Based on a proximity distance, Auto Contact will search
the model and automatically define surfaces from identified components. The interactions and surfaces are
placed into a temporary Auto Contact Browser, where you can review the pairs and make adjustments as
needed.
Two types of interactions can be created by the auto contact functionality:

· *CONTACT PAIR: Definition of pairs of surfaces, which can contact or interact during an analysis.
When selecting this type of interaction, you must also specify the surface interaction properties.
· *TIE: Definition of constraints and interactions between pairs of surfaces. No surface interaction
definition is required.
The Auto Contact dialog contains the following buttons:
Find Searches the model for interacting components.
Cancel Closes the Contact Pair dialog without updates.
Remove Removes selected components from the table. You can use the CTRL and Shift
Selection icon key to select multiple items in the table.
Review Highlights the selected component in the graphic area. All other components are
Selection icon grayed out. You can use the CTRL and Shift key to select multiple items in the
table.
Right-click to return the model to normal display.
Help icon Opens the Auto Contact online help.
To Set Up an Auto Contact Run

1. Load the Abaqus user profile and select either the 2D or 3D template.
2. Click Contact Manager in the Abaqus Utility menu.
3. Click Auto. This opens the Auto Contact dialog.
4. Select the type of interface to create in the Type of Interface: field.
5. Click the yellow components button and select your components.
The components are automatically placed in the Component table in the Auto Contact dialog.
6. In the Proximity Distance: field, enter a value.
The proximity distance is the maximum distance between two selected components. When you create
the pair, any surfaces that are farther away than the value entered here will not be created as a contact
pair. The default value is zero.

7. In the Maximum reverse angle: field, enter a value.
If the angle between two normals of elements or element faces exceeds this value, the element will not
be added to the master or slave surface.
8. If creating a contact pair, select the type of interaction in the Interaction: field. You can use the
icon to open a browser to view the options more easily, or you can click New to create a new
interaction.
9. Click Find. The status bar activates and the Auto Contact Browser opens.
10. Use the Auto Contact Browser to make any necessary adjustments to the interfaces and surfaces.
When finished modifying, click Create.
The interfaces and surfaces marked as Accepted are created. The Contact Manager window reopens
with the new information listed.
Auto Contact Browser

The Auto Contact Browser provides options for viewing and modifying the contact pairs identified in the
Auto Contact process.
Naming Convention
During creation, a name is assigned to each interface and surface identified.
Interface:
Contact Pair example: CP:(comp name)_(comp_name)
Tie example: TIE:(comp name)_(comp_name)
Surface:
S:(comp name)
If more than one surface is selected, the naming convention uses S:(comp name):<index>
The Auto Contact Browser contains the following columns:
Name Lists the name of the interfaces, surfaces and surface interactions that were
assigned.
Underneath the interface name are the temporary surfaces included in that
interface. Red indicates a slave surface, and blue indicates a master surface.
Accept When the Accept box is checked, the Interface will be included in the creation
process.
Type Type of contact pair created.
Color Color assigned to the interaction and surfaces

Surface Opens the Auto Contact online help.
Interaction
The Auto Contact Browser contains the following icons:

Options icon This opens the Options dialog.
Enter a new feature angle or customize the transparency for a selected

entity. Click OK when finished.
Highlight
Highlights the elements stored in selected entities in the graphics
Elements icon
window. You can use the CTRL and Shift key to select multiple items in
the table.
Review Review of elements stored in the selected entities. Elements are

Elements icon highlighted by color, all other components are grayed out. You can use
the CTRL and Shift key to select multiple items in the table.
Review and Highlight are mutually exclusive. It is also possible to switch
both options off. This is helpful when working with big models.
Fit View to Automatically zooms in to the elements stored in the currently selected
Elements icon items.
Display All In combination with the Highlight Elements or the Review Elements
Elements icon option, current contents remain unchanged on the screen.
Display Highlights or reviews the elements referred by an interaction or surfaces

Components and shows the components they belong to. All other components will be
with Elements masked.
icon
Display Only Only elements are highlighted or reviewed. The rest of the component
Elements icon and other components will be masked.
Select Opens the Element selection panel so that individual elements can be
Elements added/removed manually. Click proceed when finished.
Manually icon
Add by Adds the elements adjacent to the surface to the selected surface.
Adjacent icon
Right-click to undo one time.
Add by Face Adds the adjacent face to the selected surface.

icon
Right-click to undo one time.

Recheck icon Opens the Auto Contact dialog to recheck the select interfaces.
Recheck will either add more contacts to the existing contacts for modify
the existing ones.
You can select interfaces from the browser, and the GUI will
automatically populate the components that the interaction was based on.
This helps modify an existing interface.
Modifying Auto Contact Entities

Right-clicking on an item in the Auto Contact Browser displays a context sensitive menu which offers
options for modifying the surfaces and contact pairs.
Rename Rename an existing entry.
Delete Delete items from the browser.
Swap Master - Allows you to switch the surfaces identified as master and slave. When
Slave selected, you will see the surfaces flip from the master/slave positions in the
browser.
Select multiple entities by using the CRTL and Shift keys when clicking on
entities.
Swap CP - Tie Allows you to change the type of interface created. Because a surface
interaction is required for Contact Pair but not for Tie, any surface interaction
identified earlier will be lost upon a swamp from CP to TIE. (If you switch back
from TIE to CP, the surface interaction will not be retained.)
Edit Faces Allows you to manually edit the faces of the surfaces. This opens the elements
selection panel where you can select and deselect the elements to include on
the face of the surface.
Add by Adds adjacent elements to the selected surface.

Adjacent
Add by Face Adds all elements to a selected surface, until the feature angle exceeds the
value (the feature angle can by set by clicking the Options icon).
Accept All/None Automatically accept or reject all items in the Auto Contact Browser.
Reverse Reverses the current selections in the Accept column.
Expand All/ Expands or collapses folders in the Auto Contact Browser.

Collapse

Surface Tab
The Surface tab contains a description of the *SURFACE cards with corresponding types. You can create,
edit, review, and delete surfaces from this tab.
The Surface table contains the following columns:
Name The name of surfaces in the HyperMesh database.
Type The types of surfaces. Currently supported types are ELEMENT, NODE, and
ANALYTICAL RIGID (SEGMENTS, CYLINDER or REVOLUTION).
Display The display on/off check boxes and color change buttons for the surface. The
color of a surface can be changed by clicking on the color buttons and selecting
a color from the menu.
Note:
· The display on/off check boxes and color change buttons are disabled if the corresponding surface
is defined with sets and a display is not created.
· Double click on a surface name in the table to open its corresponding editing dialogs.
· Right click on a surface name to display menu options. The available options are
- Edit
- Delete
- Review
- Review with underlying entity
- Reset review
- Review Options (Review by Highlighting, Review by Color Change, Transparency, and Grey
Color)
- Display All
- Display None
- Display Reverse
- Draw Rigid Surfaces
The Edit, Review, Delete, Display All, Display None and Display Reverse options work like the
corresponding buttons (described below). Review with underlying entity highlights the surface
along with the attached elements (or nodes). The Reset review button clears the review
selections.

The Surface tab contains the following buttons:
Auto Launches the Auto Contact dialog that allows you to quickly and easily create
interactions between several parts of your model.
New ... Opens the Create New Surface dialog, on which you enter the name and type
of the new surface. The Create… button in this dialog creates the surface and
opens the corresponding Element Based Surface, Node Based Surface, or
Analytical Rigid Surface dialog or takes you to the corresponding
HyperMesh card image.
Edit ... Opens the Element Based Surface, Node Based Surface, or Analytical
Rigid Surface dialog or takes you to the corresponding HyperMesh card
image for editing the selected surface.
Review Reviews the selected surface. Surfaces are highlighted in white and show up
through solid mesh in performance graphics the HyperMesh window. If the
surface is defined with sets (display option disabled), the underlying elements
are highlighted. Right-click the Review button to clear the review selections.
Delete Deletes selected surfaces. You can delete single or multiple selections from
the Surface table.
Rename Rename the selected surface.
manually create, update or delete components, groups, properties, or entity
sets from HyperMesh panels while the Contact Manager is open, click Sync to
update the Contact Manager with the new changes.
Display All Displays all surfaces in HyperMesh graphics.
Display None Hides all surfaces in HyperMesh graphics.
Display Reverse Displays all unchecked surfaces and hides all checked surfaces in HyperMesh
graphics.
Draw Rigid Shows analytical rigid surfaces in the HyperMesh graphics display.
Surfaces

Element Based Surface
The Element Based Surface dialog allows you to define and edit the *SURFACE, TYPE = ELEMENT
card. There are four tabs in this dialog:
Define
Adjust Normal
Delete Face
Optional Parameters
The Element Based Surface dialog contains the following buttons:
Surface Changes the color of the current surface in the HyperMesh display.
color
Review Reviews the current surface by highlighting in white and displaying it through solid
mesh in performance graphics in the HyperMesh window. If the surface is defined
with sets, the underlying elements are highlighted. Right click on the Review
button to clear the review selections.
Close Updates the HyperMesh database with the optional parameters specified and
closes the Element Based Surface window.
Element Based Surface: Define Tab

The Define tab allows you to define surfaces for solid, shell, membrane, rigid, gasket, beam, pipe, or truss
elements. You can also define the surface by specifying the face identifier for an element set. There are
six available surface definition options for various element types:
· 3D solid, gasket
· 3D shell, membrane, rigid
· 3D solid coated with shell

· 3D shell - edge based
· 2D solid, axisymmetric, gasket
· Beam, pipe, truss
· Element set
The layout of the Define tab changes, based on your selection (displayed in blue). Some options may be
disabled depending on the current template.
3D solid or gasket elements

The 3D solid or gasket elements option allows you to define the *SURFACE card by specifying face
identifiers for individual solid and gasket elements. In HyperMesh graphics, these faces are displayed by
special face elements.
In order to create surface, you need to select the underlying solid or gasket elements first.
The Elements buttons opens the HyperMesh element selector panel and allows you to pick the underlying
3-D solid or gasket elements from HyperMesh graphics. Selected elements are highlighted. The
corresponding Reset resets the selected elements.
After that, you can define the face identifiers for the selected solids in two ways: (a) by creating a solid skin
and manually picking the faces from the skin, (b) by picking nodes on a specific face and sweeping through
a break angle. Select Solid skin option for (a) and Nodes on face option for (b) from the Select faces
by: radio buttons.
(a) Solid skin option has the following buttons:
Faces Creates a temporary skin of the selected solids, opens the HyperMesh element
selector panel, and allows you to pick face elements from this skin. The selected
faces are highlighted. The corresponding Reset button resets the selected faces and
deletes the skin.
Note: by face on the element selector panel can be used to find all faces within a
feature angle of the selected face. The feature angle setting can be accessed
by clicking the Preferences pull-down menu and selecting Geometry Options.
The skin will initially have the same color as the current surface. You can change the
skin color using Solid skin color: button.
Add Adds the selected faces to the current surface and creates special face elements for
display. It also checks for duplicate faces and displays a message if any are found.
Note: The Delete Face tab contains tools to find and delete duplicate faces in the
current surface.

Reject Rejects the recently added faces.
(b) Nodes on face option has the following buttons:
Nodes Opens the HyperMesh node selector panel and allows you to pick nodes from
HyperMesh graphics. Three nodes (or two corner nodes) from the same solid element
must be picked to define a face of that solid. The selected nodes are highlighted. The
corresponding Reset button resets the selected nodes.
Note: Several three-node or two-corner-node sets can be selected at the same time
to define faces in different solids.
Add Finds all faces from the selected solids that fall within a specified break angle of the
face(s) defined by nodes. These faces are then added to the current surface and
creates special face elements for display. It also checks for duplicate faces and
displays a message if any are found.
current surface.
3-D shell, membrane, or rigid elements

The 3D shell, membrane, or rigid elements option allows you to define the *SURFACE card by specifying
face identifiers for individual shell, membrane, and rigid elements. In HyperMesh graphics, these faces are
displayed by special face elements. These face elements have their own normals to define the SPOS and
SNEG faces. The face with normals along the underlying element normals define the SPOS faces. In
contrast, the face with opposing normals define the SNEG face.
The 3D shell, membrane, or rigid elements option has the following buttons:
Elements Opens the HyperMesh element selector panel and allows you to pick the underlying
3-D shell, membrane, or rigid elements from HyperMesh graphics. The selected
elements are highlighted and their normals are displayed. The corresponding Reset
button resets the selected elements and hides the normals.

Add Adds the selected elements to the current surface and creates special face elements
for display. It also checks for duplicate faces and displays a message if any are
found. By default, SPOS faces are created. In order to create SNEG faces, activate
the Reverse check box and click Add.
current surface.
3-D solid coated with shell

In HyperMesh, surfaces on 3-D solid or gasket elements that are coated with shell, membrane, or rigid
elements are treated differently from surfaces on regular solids. The 3D solid coated with shell option
allows you to define the *SURFACE card by specifying face identifiers for these 3-D solid or gasket
elements. The faces are displayed by special contactsurface elements. Unlike, regular solids, there is
only one way to define the face identifiers for solids with shell coating: by picking nodes on a specific face
and sweeping through a break angle. Therefore, the Nodes on face option is always selected. This
option is valid for Standard.3D template or 3-D models in Explicit template only.
The 3D solid coated with shell option has the following buttons:
Elements Opens the HyperMesh element selector panel and allows you to pick the
underlying 3-D solid and gasket elements from HyperMesh graphics. The
selected elements are highlighted. The corresponding Reset button resets the
selected elements.
Opens the HyperMesh node selector panel and allows you to pick nodes from
HyperMesh graphics. Three nodes (or two corner nodes) from the same solid
Nodes element must be picked to define a face of that solid. The selected nodes are
highlighted. The corresponding Reset button resets the selected nodes.
Note: Several three-node or two-corner-node sets can be selected at the same
time to define faces in different elements.
Add Finds all faces from the selected 3-D solids that fall within a specified break
angle of the face(s) defined by nodes. These faces are then added to the current
surface and special contactsurface elements are created for display.
Note: You cannot add duplicate contactsurfaces for the same element in
HyperMesh. Therefore, the Add button does not check for duplicates and
there is no Reject button.

3-D shell - edge based
The 3D shell – edge based option allows you to define the *SURFACE card by specifying edge identifiers
for 3-D shell elements. The edges are displayed by special contactsurface elements. Face identifiers for
solids with shell coating are defined by picking nodes on a specific edge and sweeping through a break
angle. Therefore, the Nodes on edge option is always selected.
The 3D shell – edge based option has the following buttons:
3-D shell elements from HyperMesh graphics. The selected elements are
highlighted. The corresponding Reset button resets the selected elements.
Opens the HyperMesh node selector panel and allows you to pick nodes from
HyperMesh graphics. Two nodes from the same solid element must be picked to
Nodes define a edge of that shell. The selected nodes are highlighted. The corresponding
Reset button resets the selected nodes.
Note: Several two-node sets can be selected at the same time to define edges in
different elements.
Add Finds all edges from the selected 3-D shells that fall within a specified break angle
of the edge(s) defined by nodes. These edges are then added to the current surface
and special contactsurface elements are created for display.
Note: You cannot add duplicate contactsurfaces for the same element in
2-D solid, axisymmetric, or gasket elements

The 2D solid, axisymmetric, or gasket elements option is valid for Standard.2D template or 2-D models
in Explicit template only. It allows you to define the *SURFACE card by specifying edge identifiers for
individual 2-D solid, axisymmetric, and gasket elements. In HyperMesh graphics, these edges are
displayed by special contactsurface edge elements. Unlike, 3-D solids, there is only one way to define the
face identifiers for 2-D solids: by picking nodes on a specific edge and sweeping through a break angle.
Therefore, the Nodes on edge option is always selected.

The 2D solid, axisymmetric, or gasket elements option has the following buttons:
2-D solid, axisymmetric, and gasket elements from HyperMesh graphics. The
selected elements are highlighted. The corresponding Reset button resets the
selected elements.
Nodes Opens the HyperMesh node selector panel and allows you to pick nodes from
HyperMesh graphics. Two nodes from the same element must be picked to define
an edge of that element. The selected nodes are highlighted. The corresponding
Note: Several node pairs can be selected at the same time to define edges in
different element.
Add Finds all edges from the selected 2-D solids that fall within a specified break angle
of the edge(s) defined by nodes. These edges are then added to the current surface
and special contactsurface edge elements are created for display.
Note: You cannot add duplicate contactsurface edges for the same element in
Beam, pipe, or truss elements

The Beam, pipe, or truss elements option allows you to define the *SURFACE card for individual beam,
pipe and truss elements. In HyperMesh graphics, these faces are displayed by special contactsurface
elements. These contactsurface elements have their own normals to define the SPOS and SNEG faces.
The contactsurface with normals along the underlying element normals define the SPOS faces. In
contrast, the face with opposing normals defines the SNEG face.
Note: For 3-D beam, pipe and truss elements, the SPOS and SNEG faces do not have any meaning.
Therefore, these face identifiers will be ignored by the Standard.3d template.
The Beam, pipe, or truss elements option has the following buttons:
Elements Opens the HyperMesh element selector panel and allows you to pick the
underlying beam, pipe or truss elements from HyperMesh graphics. The selected
elements are highlighted. The corresponding Reset button resets the selected
elements.
Add Adds the selected elements to the current surface and creates special

contactsurface elements for display. By default, SPOS faces are created. In
order to create SNEG faces, activate the Reverse check box and click Add.
Note: You can not add duplicate contactsurfaces for the same element in
HyperMesh. The Add button does not check for duplicates and there is
no Reject button.
Element set
The Element set option allows you to define the *SURFACE card for element sets. HyperMesh allows only
one elset in a surface. It does not support a combination of elsets and individual elements in the same
*SURFACE data line.
The Element set: menu contains a list of the existing elsets. (You can also use the … button to open the
entity browser to select an elset.) There are two types of elsets in Hypermesh: Components and Entity
sets. The Abaqus elsets that are linked to sectional property cards (such as *SOLID SECTION, *SHELL
SECTION, etc.) become Components in HyperMesh. Others become Entity sets. To differentiate between
these two types, there is a divider line "- - - - -" in the elset lists that pops up if you click the Element set:
menu. The elsets listed below the divider line are Components.
The Element set option has the following buttons:
Review Set Reviews the selected elsets set by highlighting them in the HyperMesh
graphics. Right click on the Review button to clear the review selections.
Create/Edit Sets... Opens the entity sets panel in HyperMesh. When you finish creating/editing
the set, click return. The Element Based Surface tab is updated with the
new set appearing in the element set list.
Show Faces Creates a temporary skin of the selected elset, opens the HyperMesh element
selector panel, and allows you to pick face elements from this skin. When
you return from the element selector panel, the selected faces will display
color coded face identifier tags. In performance graphics, these tags are
sometimes blocked by the solid mesh. You may need to rotate the model a
little to view the tags.
Update Adds the selected elset into the current surface. By default, HyperMesh does
not create a display for surfaces defined with elsets. However, if you check
the Display option before clicking Update, it creates a special display using
contactsurface elements.
Note: The special display created with contactsurface elements does not
have links to the elset in the HyperMesh database. Therefore, if you

edit the elset later on, the display will not automatically reflect your
changes. In this case, check the Display option and click Update
again.
After selecting an element set, click the arrow keys to move the set into table on the right. Once an elset
has been added to the table, the face column becomes activated and you can manually define the
appropriate face identifier for the selected elset. Select None if you do not want to define a face identifier
for the set. In this case, Abaqus will create a surface with the free faces for the selected element set.
Element Based Surface: Adjust Normal Tab

The Adjust Normal tab allows you to display and reverse normal direction for surfaces defined on 3-D
shell, membrane, rigid and 2-D beam, pipe, and truss elements. For these elements, the normal directions
are used to define the SPOS or SNEG face identifiers. In HyperMesh, surfaces can be displayed in two
ways: by special face elements or by contactsurfaces. The surfaces defined on 3-D shell, membrane,
rigid elements are displayed by face elements while surfaces on 2-D beam, pipe, and truss elements are
displayed by contactsurfaces. The normal directions of the contactsurfaces are part of their display.
However, the normal directions of the faces have to be turned on for displaying. Use the Display normals
checkbox to display the normals of the faces. Use the Size: entry box to define the size of the normals
before selecting the Display normals checkbox.
Note: In HyperMesh, 3-D solid and gasket elements are also displayed by face elements. But, the
normal direction do not have any meaning for them.
There are two options for reversing normals: (a) Reverse all normals at a time, (b) Reverse normals by
individual faces or contactsurfaces.
(a) Reverse normals: All option has the following buttons:
Reverse Reverses normals of all faces for 3-D shell, membrane, rigid elements
and all contactsurfaces for 2-D beam, pipe, truss elements in the
current surface.
Note: The normals of the underlying elements are not reversed. It
reverses the normals of the faces or contactsurfaces only.
(b) Reverse normals: By element option has the following buttons:
Element faces Opens the HyperMesh element selector panel. For 3-D shell,
membrane, rigid elements, pick the faces (not the underlying
elements). However, for 2-D beam, pipe, truss elements, pick the
elements themselves as the contactsurfaces can not be picked from
HyperMesh graphics. The corresponding Reset button resets the
selected elements.
Reverse Reverses normals of the selected faces for 3-D shell, membrane, rigid

elements and contactsurfaces of the selected 2-D beam, pipe, truss
elements.
Note: The normals of the underlying elements are not reversed. It
reverses the normals of the faces or contactsurfaces only.
Element Based Surface: Delete Face Tab

In HyperMesh, surfaces can be displayed in two ways: by special face elements or by contactsurfaces.
The surfaces defined on 3-D solid, gasket, shell, membrane, rigid elements are displayed by face elements
while surfaces on 2-D solid, axisymmetric, gasket and all beam, pipe, truss elements are displayed by
contactsurfaces. The Delete Face tab allows you to delete faces or contactsurface from all elements
types. It contains tools to find and delete duplicate faces for 3-D solid, gasket, shell, membrane, or rigid
elements.
There are three options for deletion: (a) All, or (b) By element, and (c) Duplicate faces.
(a) All option has the following buttons:
Delete Deletes all the faces or contactsurfaces in the current surface.
(b) By element option has the following buttons:
Element Faces Opens the HyperMesh element selector panel. For 3-D solid,
gasket, shell, membrane, and rigid elements, pick the faces (not the
underlying elements). However, for 2-D solid, axisymmetric, gasket
or all beam, pipe, truss elements, pick the elements themselves as
the contactsurfaces can not be picked from HyperMesh graphics.
The corresponding Reset button resets the selected elements.
Delete Delete deletes the selected faces or contactsurfaces from the

selected 2-D solid, axisymmetric, gasket, beam, pipe, truss
elements.
(c) Duplicate faces option has the following buttons:
Find Duplicate Finds duplicate faces, if any exists, for the current surface and
Faces highlights them in the HyperMesh graphics. The HyperMesh status

bar shows the number of duplicates found. The corresponding Reset
button resets the selected elements.
Delete Deletes the highlighted duplicate faces found.

Note: Duplicate contactsurfaces cannot be added to the same
surface in HyperMesh. Therefore, Duplicate Faces is only
valid for 3-D solid, gasket, shell, membrane, and rigid
elements.
Element Based Surface: Optional Parameters Tab

The Optional Parameters tab allows you to define optional parameters for the *SURFACE card.
· Standard.3D/2D template: Trimming of open free surface
· Explicit template: Max ratio, Scale thickness, Region type for adoptive meshing, No offset and No
thickness
See the Abaqus Online Documentation for a detailed description of these parameters. Click on the Update
button to activate the Optional Parameters selection in the HyperMesh database.
Node Based Surface

The Node Based Surface dialog allows you to define and edit the *SURFACE, TYPE = NODE card.
There are three tabs in this window:
Define
Delete Surface Node
Optional Parameters
The Node Based Surface dialog contains the following buttons:

Surface color Changes the color of the current surface in HyperMesh display.
Review Reviews the current surface by highlighting it in white and displays it through solid
mesh in performance graphics in the HyperMesh window. If the surface is defined
with sets, the underlying nodes are highlighted. Right click on the Review button
to clear the review selections.
Close Updates the HyperMesh database with the optional parameters specified and
closes the Node Based Surface window.
Node Based Surface: Define Tab

The Define tab allows you to define surfaces with individual nodes. You can also define the surface by
specifying a node set. There are two available surface definition options:
· Individual nodes
· Node set
The layout of the Define tab changes based on your selections.
Individual nodes
The Individual nodes option allows you to define the *SURFACE, TYPE = NODE card by specifying
individual node IDs. In HyperMesh graphics, these nodes are displayed by special single node elements
with a SurfaceNodes tag.
The Individual nodes option has the following buttons:
Pick Nodes Opens the HyperMesh node selector panel and allows you to pick nodes from
HyperMesh graphics. The selected nodes will be highlighted. The corresponding
Add Adds the selected nodes to the current surface and creates special single node
SurfaceNodes elements for display. The Add button does not check for
duplicates and there is no Reject button.

Node set
This option allows you to define the *SURFACE, TYPE = NODE card for node sets. HyperMesh allows only
one node set in a surface. It does not support combination of node sets and individual nodes in the same
*SURFACE data line.
The Node set: menu contains a list of the existing node sets.
The Node set option has the following buttons:
Review Set Reviews the selected node sets by highlighting the nodes in HyperMesh
graphics. Right-click on the Review button to clear the review selections.
Create/Edit Set... Opens the entity sets panel in HyperMesh. When you finish
creating/editing the set, click return. The Node Based Surface dialog is
updated with the new set appearing in the node set list.
Area This check box allows you to define the optional cross-sectional area at
each nodes of the node set selected.
Note: In HyperMesh, the cross-sectional area data item is supported
only for surfaces defined by node sets.
Update Adds the selected node set into the current surface. HyperMesh does not
create a display for surfaces defined with node sets.
Node Based Surface: Delete Surface Node Tab

In HyperMesh, node bases surfaces are displayed by special single node SurfaceNode elements. The
Delete Surface Node tab allows you to delete the SurfaceNode elements.
There are two options for deletion: (a) All, (b) By node.
(a) All option has the following buttons:
Delete Deletes all SurfaceNodes elements from the current surface.

(b) By node option has the following buttons:
Surface nodes Opens the HyperMesh element selector panel for you to select
SurfaceNodes elements from HyperMesh graphics. The corresponding
Reset button resets the selected elements.
Delete Deletes the selected SurfaceNodes elements from the current surface
Node Based Surface: Optional Parameter Tab

The Optional Parameter tab allows you to define optional parameters for the *SURFACE card.
· Standard.3D/2D template: Trim
· Explicit template: Max ratio, Scale thickness, Region type, No offset and No thickness.
See the Abaqus Online Documentation for a detailed description of these parameters. Click on the Update
button to activate the optional parameter selection in the HyperMesh database.
Surface Combine or Crop

The Surface Combine or Crop option allows you to define the *SURFACE, COMBINE, or CROP. The
current version of Contact Manager does not have a Tcl/Tk dialog to define the surface combine or crop.
Review by highlighting or color change also does not work for these types of surfaces in HyperMesh.
Instead, it takes you to the corresponding card image panel for edit or review.
Click the edit button to go into the card editor to define all relevant keywords, parameters, and data lines.
When you are finished, click return and the Contact Manager window will once again be displayed.
Cutting Surface
The Cutting Surface option allows you to define the *SURFACE, TYPE = CUTTING SURFACE. The
current version of Contact Manager does not have a Tcl/Tk dialog to define the cutting surface. Review by
highlighting or color change also does not work for these types of surfaces in HyperMesh graphics.
Instead, it takes you to the corresponding card image panel for edit or review.
Click the edit button to go into the card editor to define all relevant keywords, parameters, and data lines.

When you are finished, click return and the Contact Manager window will once again be displayed.
Analytical Rigid Surface

The Analytical Rigid Surface option helps you define the *SURFACE, TYPE = CYLINDER,
REVOLUTION or SEGMENTS card. When you select this option and click Create… the Analytical Rigid
Surface dialog appears.
There are four tabs in this dialog:
Define
Adjust Normal
Rigid Body
Optional Parameters
Each tab of the Analytical Rigid Surface dialog contains the following buttons:
Surface color Changes the color of the current surface in the HyperMesh display.
Review Reviews the current surface by highlighting line segments and generated
revolute or swept surfaces in white. Right-click on the Review button to
clear the review selections.
Close Updates the HyperMesh database with the optional parameters that you
specified and closes the Analytical Rigid Surface window.
Analytical Rigid Surface: Define Tab

Specify the main characteristics of the surface on this tab. Depending on which Abaqus template you have
loaded (Standard3D, Standard2D, or Explicit), you can create surfaces defined by segments, cylinders, or
revolutions.
· The Standard3D template enables you to define rigid surfaces of type REVOLUTION and
CYLINDER.
· The Standard2D template enables you to define surfaces of type SEGMENTS.
· The Explicit template enables you to define all three types: REVOLUTION, CYLINDER, and

SEGMENTS.
You can define the line segments in three different ways – by picking nodes, by picking existing lines, or by
manually entering the coordinate values. The options on the Define tab vary according to the type selected.
Refer to the following topics for details:
SEGMENTS
CYLINDER
REVOLUTION
SEGMENTS Option
Analytical rigid surface of type SEGMENTS
Select the following options on the Define tab for planar rigid surfaces:
Plane definition
Plane/axis: Abaqus does not require the plane/axis definition for SEGMENTS type. In
HyperMesh, however, the XY plane must be used for a 2D model.
Therefore, the XY plane is selected by default. If the model is not in the
XY plane, you can choose to select a "User Defined" plane on which the
rigid surface should be defined.
If you choose to manually define the plane/axis, you must enter values
for three points (the origin, x axis, and y axis) that define the local
coordinate system.
You can also use the following buttons to automatically define the plane
in the Local System table:
· Pick System...: Click to select an existing system from the

model. Once you select a plane from the model and click
proceed, the values are populated in the table.
· Create/Edit System...: Click to create new coordinate systems

using the systems panel.
Line definition
No. of line segment In this field you specify the number of datalines needed to define the line
datalines segments. The actual number of line segments is one less than this
number.
Start by typing the number of datalines needed to define the line

segments and click the Set button. The corresponding number of rows
appears in the Line Type table below. In this table, specify the
coordinates of the ends of each line segment.
The first entry in the table is always the START node. This value
specifies the beginning point of the first segment. The subsequent
segments’ starting point is always the end point of the previous segment,
or the START node if the segment is the first in the definition.
For each line type, select a type from the Line Type column: LINE,
CIRCL, or PARAB. Each selection activates the appropriate number of
columns for the segment definition.
The segments can be circles, parabolas, or lines. Enter data in the
columns as described below:
· Lines are defined with the x and y coordinates of the end point in the two
active columns.
· For circles, specify the x and y coordinate of the end point in the
first two columns and then, define the x and y coordinate of the
center in the last two columns.
· For parabolas, specify the x and y coordinate of the mid point in

the first two columns and then, define the x and y coordinate of
the end point in the last two columns. You can also pick nodes or
lines from existing geometry using the following buttons:
Pick Nodes… Click to pick nodes from the HyperMesh model for
selected line segments. When you click proceed,
the coordinate values of the selected nodes will
appear in selected line segment cells. In addition,
temporary line segments (white color) will also be
drawn in HyperMesh graphics from the picked
nodes. Ensure that you select two nodes in the
correct order for circles and parabolas.
Pick Lines… Use this option to define line segments from existing
lines in HyperMesh. These lines must be single
curvature, connected and node1 of a line must be
same as node2 of the previous line.
Click to pick a line from the HyperMesh model.
When you click proceed, the coordinate values and
line types for the selected lines will appear in the
table.
Note In HyperMesh, the sequence of node1 and
node2 for lines can be visualized from the
line edit/extend line panel.
Click the Update button to update the HyperMesh database with your settings.

CYLINDER Option
Analytical rigid surface of type CYLINDER
Select the following options on the Define tab for cylindrical rigid surfaces:
Plane definition
Plane/axis: Choose User Defined if you want to create or select the system, or choose XY, YZ,
or XZ to define it in the respective plane.
If you choose to manually define the plane/axis, you must enter values for three
points (the origin, x axis, and generator axis) that define the local plane on which
the line segments will be defined.
You can also use the following buttons to define the plane:
Pick System... Click to select an existing system from the

model. Once you select a system from the
HyperMesh graphics and click proceed, the
values are populated in the table.
Create/Edit System... Click to create a new coordinate system

using the systems panel.
Line definition
No. of line In this field you specify the number of datalines needed to define the line segments.
segment The actual number of line segments is one less than this number.
datalines
Start by typing the number of segment datalines to define the surface and click the
Set button. The corresponding number of rows appears in the Line Type table
below. In this table, specify the coordinates of the ends of each line segment.
The first entry in the table is always the START node. This value specifies the
beginning point of the first segment. The subsequent segments’ starting point is
always the end point of the previous segment, or the START node if the segment is
the first in the definition.
For each line type, select a type from the Line Type column: LINE, CIRCL, or
PARAB. Each selection activates the appropriate number of columns for the
segment definition.
The segments can be circles, parabolas, or lines. Enter data in the columns as
described below:
· Lines are defined with the local x- and local y-coordinates of the end point
in the two active columns.
· For circles, specify the local-x and local-y coordinate of the end point in the
first two columns and then, define the local-x and local-y coordinate of the

center in the last two columns. .
· For parabolas, specify the local-x and local-y coordinate of the mid point in
the first two columns and then, define the local-x and local-y coordinate of
the end point in the last two columns.
Note The local x- and local y-coordinates must be relative to the plane
defined in the Plane/axis table.
You can also pick nodes or lines from existing geometry using the following
buttons:
selected line segments. When you click proceed, the
coordinate values of the selected nodes in terms of the
defined plane will appear in selected line segment cells.
In addition, temporary line segments (white color) will
also be drawn in HyperMesh graphics from the picked
nodes. Ensure that you select two nodes in the correct
order for circles and parabolas.
Pick Lines… Use this option to define line segments from existing
lines in HyperMesh. These lines must be single
curvature, connected and node1 of a line must be same
as the node2 of the previous line.
Click to pick a line from the HyperMesh model. When
you click proceed, the coordinate values relative to the
defined plane and line types for the selected lines will
appear in the table.
Note In HyperMesh, the sequence of node1 and
node2 for lines can be visualized from the
line edit/extend line panel.
Sweep Abaqus does not need the sweep distance. The CYLINDER type surfaces are
Distance swept to infinity in Abaqus. However, in HyperMesh, you must define a sweeping
distance to draw the three-dimensional surface. Select the Sweep distance check
box to specify a sweep distance and type a value in the adjacent box. Select the
Both directions check box to sweep in opposite directions along the generator
vector.
REVOLUTION Option

Analytical rigid surface of type REVOLUTION
Select the following options on the Define tab for rigid surfaces of revolution:
Plane definition
Plane/axis: Choose User Defined if you want to create or select the revolution axis, or choose X,
Y, or Z to define it in the respective axis.
If you choose to manually define the axis, you must enter values for two points (the
origin and the z axis). Abaqus does not need the x axis values because any plane
that passes through the z axis will define the same revolute surface. However,
HyperMesh requires the definition of the x (or radial) axis to define the plane on which
the line segments are drawn.
You can also use the following buttons to automatically define the axis of revolution
and x (radial) axis.
Note The coordinate values to define the x axis change if you pick a node (or line)
from HyperMesh as the START node.
Pick System... Click to select an existing system from the model. Once
you select a system from the HyperMesh graphics and
click proceed, the values are populated in the table.
Create/Edit System... Click to create a new coordinate system using the

systems panel.
Line definition
No. of In this field you specify the number of datalines needed to define the line segments.
segment The actual number of line segments is one less than this number.
datalines:
Start by typing the number of line segment datalines to define the surface and click
the Set button. The corresponding number of rows appears in the Line Type table
below. In this table, specify the coordinates of the ends of each line segment.
The first entry in the table is always the START node. This value specifies the
beginning point of the first segment. The subsequent segments’ starting point is
always the end point of the previous segment, or the START node if the segment is
the first in the definition.
For each line type, select a type from the Line Type column: LINE, CIRCL, or
PARAB. Each selection activates the appropriate number of columns for the segment
definition.
The segments can be circles, parabolas, or lines. Enter data in the columns as
described below:
· Lines are defined with the local-x (or r) and local-y (or z) coordinates of the
end point in the two active columns.
· For circles, specify the local-x (or r) and local-y (or z) coordinate of the end

point in the first two columns and then, define the local-x (or r) and local-y
(or z) coordinate of the center in the last two columns.
· For parabolas, specify the local-x (or r) and local-y (or z) coordinate of the
mid point in the first two columns and then, define the local-x and local-y (or z
) coordinate of the end point in the last two columns.
You can also pick nodes or lines from existing geometry using the following buttons:
selected line segments. When you click proceed, the
coordinate values of the selected nodes relative to the
defined plane will appear in selected line segment cells. In
addition, temporary line segments (white color) will also be
drawn in HyperMesh graphics from the picked nodes.
Ensure that you select two nodes in the correct order for
circles and parabolas.
Pick Lines… Click to pick a line from the HyperMesh model. When you
click proceed, the coordinate values in terms of the
defined plane and line types for the selected lines will
appear in the table.
Note In HyperMesh, the sequence of node1 and node2
for lines can be visualized from the line
edit/extend line panel.
Revolution Abaqus does not need the revolution angle. The REVOLUTION type surfaces are
angle: revolved around 360 degrees in Abaqus. However, in HyperMesh, you must define a
revolution angle to draw the three-dimensional surface. Select the Revolution angle
check box to specify the angle of revolution and type a value in the adjacent box.
Analytical Rigid Surface: Adjust Normal Tab

Select the following options on the Adjust Normal tab:
Display normals Select the Display normals check box to show the normals on the
HyperMesh display. Specify a length for the normals in the Size field. To
change the size, toggle the check box to update the display.
Reverse normals: Select one of the radio buttons to reverse the direction of the normals. You
can only choose to reverse the normals of all line segments in this type of
surface. Click the Reverse button to do this. When reversed, all coordinates
and sequence of all the line segments will be updated.

The analytical rigid surface should be oriented so that the outward normals
point toward any body of contact.
Analytical Rigid Surface: Rigid Body Tab

An analytical rigid surface must have a *RIGID BODY card with a reference node associated with it. When
you create a new rigid surface in the Contact Manager, an empty *RIGID BODY component is created
automatically. You can also associate the surface to an existing *RIGID BODY component or create a new
one from this tab.
This tab also includes several options related to preparing the model for visualization in HyperView.
HyperView currently does not support geometrical entities like analytical rigid surfaces. If you mesh
analytical rigid surfaces with rigid elements that point to the same *RIGID BODY card, these elements
would not participate in the analysis; they would move with the reference node as a rigid body. These rigid
elements would act like a "display body" in Abaqus, and would be imported in HyperView.
Select the following options on the Rigid Body tab:
Select a *Rigid Body: Use the drop-down list or the Entity Browser to select a rigid body. You
can also create a new rigid body in the HyperMesh model by clicking
the Create New… button.
Reference Node: Type the node ID used as a reference to define the rigid body motion.
Click Pick Node to pick a node from the model. Alternatively, type a
node value in the box and click Review to view the location of the node
in the model. (If you type a value that does not exist in the model,
nothing is highlighted.)
Line mesh density: Specify the density of the line mesh. Uniform uses the value you
specify as the mesh density for each line segment. Variable brings you
to the line mesh panel to create the mesh.
Select either Uniform or Variable and click Mesh to create the line
mesh.
Sweep distance/ The sweep field differs depending on whether the surface is of type
Sweep angle: CYLINDER or REVOLUTION.
If the surface is cylindrical, the field is Sweep distance. Type a value for
the distance of the sweep of the mesh. Select the Both direction check
box to extend the sweep in both directions for the specified distance.

When the Both direction check box is selected the number of layers
refers to the depth of segments in the sweep (number of layers of
elements).
If the surface is a revolution, the field is Sweep angle. Type a value for
the angle of the revolution. In the No. of layers field, type the value of
how many segments the rim of the revolution should be divided into.
Analytical Rigid Surface: Optional Parameters Tab
Select the following options on the Optional Parameters tab:
Trimming of open free surface Select to specify open free surface trimming. Then click the
adjacent button to select whether to trim.
Max ratio Select to adjust the thicknesses for surface facets in which
the thickness to minimum edge or diagonal length ratio
exceeds the specified value. Then type an adjustment value
in the adjacent box.
Scale thickness Select to scale all of the surface facets by a single factor.
Then type the scaling factor in the adjacent box.
Region type for adaptive meshing For surfaces defined on the boundary of an adaptive mesh
domain, select to create a boundary region for the surfaces.
Click the adjacent button to select the type of region.
No offset Select for the surface to ignore midplane offsets.
No thickness Select for the surface to ignore thicknesses. Do not select

this option if the surface will be double-sided or a
self-contact surface.
Fillet radius Select to define a radius of curvature to smooth

discontinuities between segments. Then type a length in the
adjacent box.

Surface Interaction Tab
The Surface Interaction tab contains a description of the *SURFACE INTERACTION cards. You can
create, edit, review, and delete surface interactions from this tab.
The Surface Interaction table contains the following column:
Name The name of the surface interaction cards in the HyperMesh database.
Note:
· Double click on a surface interaction name in the table to open the corresponding Surface
Interaction dialog. Right click on a name to display an option menu.
The Surface Interaction tab contains the following buttons:
Auto Launches the Auto Contact dialog that allows you to quickly and easily
create interactions between several parts of your model.
New... Opens the Create New Surface Interaction dialog in which you enter the
name of the new surface interaction. The Create.. button in this dialog
creates the surface interaction and opens the corresponding Surface
Interaction dialog.
Edit ... Opens the Surface Interaction dialog for editing the selected surface
interaction.
Review Not active on this tab.
Delete Deletes single or multiple surface interactions from the Surface Interaction
table.
Rename Rename the selected surface interaction.

manually create, update, or delete components, groups, properties, or entity
sets from HyperMesh panels while the Contact Manager is open, click Sync
button to update the Contact Manager with the new changes.
Surface Interaction
The Surface Interaction dialog allows you to define the *SURFACE INTERACTION card with
corresponding *FRICTION, *SURFACE BEHAVIOR, *CONTACT DAMPING cards. This dialog contains
the following tabs:
Define
Surface Behavior
Contact Damping
Friction
The Surface Interaction dialog contains the following buttons:
OK Updates the HyperMesh database with the changes and closes the Surface
Interaction window.
Apply Updates the HyperMesh database with the changes without closing the Surface
Interaction window.
Cancel Closes the Surface Interaction window without any update.
Surface Interaction: Define Tab

The Define tab allows you to select the surface interaction properties. The available options are: Surface
behavior, Contact damping, and Friction. Once you select an interaction property, its corresponding tab
will be activated. You can also define optional parameters (Pad thickness) and data lines (out-of-plane
thickness for 2-D model or cross-sectional area at every nodes for node based surface). See the Abaqus

Online Documentation for a detailed description of these parameters.
Surface Interaction: Surface Behavior Tab

The Surface Behavior tab allows you to create *SURFACE BEHAVIOR cards with optional parameters
and corresponding data lines. The supported optional parameters are: No separation,
Pressure-overclosure and Augmented lagrange. Options vary according to the active template.
Four types of pressure-overclosure are supported:
Hard There are no data lines needed for this option.
Exponential There are three input boxes to define the data line for this option. They are:
"Clearance at zero contact pressure", "Pressure at zero clearance" and
"maximum stiffness" (for explicit only).
Linear There is one input box to define the data line for this option. This is: "Slope of
the pressure-overclosure curve".
Tabular There is a table available for defining the data line values for this option. You
need to input the number of data lines required at the No of data lines entry
box. Clicking the corresponding Set button will update the table to have the
specified number of rows. For inputting values in the table, click on a cell to
make it active and write down the values from keyboard. The table works like a
regular spread sheet.
You can also read comma delimited data from a text file by clicking Read From
a File. This button opens a file browser window. Select the file and click Open
to export the comma delimited data. The row number is set to the number of
data lines found in the file.
Note:
· Right click in the table to display a pull-down menu containing copy, cut
and paste options. Comma delimited data can be copied/cut into or
pasted from the clipboard using these options. Hot keys, for example,
Ctrl-c, Ctrl-x and Ctrl-v on PC, can also be used.
· Left click in a cell to activate the cell. Click in an active cell to move the

insertion cursor to the character nearest the mouse.
· The shift and ctrl keys can be used with a left mouse click to select
multiple items in a table.
· Press ctrl and the left or right arrow key to move the cursor within the
active cell. Use the left, right, up and down arrows to change the active
cell.
· Press Backspace to delete the character before the insertion cursor in

the active cell. If multiple cells are selected, Backspace deletes all
selected cells.
· Press Delete to delete the character after the insertion cursor in the
active cell. If multiple cells are selected, Delete deletes all selected
cells.
· Table columns can be resized by positioning the cursor along a column

border, pressing the left or right mouse button, and dragging the border
to a new position.
Refer to the Abaqus Online Documentation for a detailed description of these parameters.
Surface Interaction: Contact Damping Tab

The Contact Damping tab allows you to create *CONTACT DAMPING cards with corresponding
parameters and data lines. The supported parameters are: Definition and Tangent fraction (explicit
only). The two definition types supported are: Damping coefficient and Critical damping fraction
(explicit only). The data item entry options change based on the current template. See the Abaqus Online
Documentation for a detailed description of these parameters.
Surface Interaction: Friction Tab

The Friction tab allows you to create *FRICTION cards with corresponding parameters and data lines.
The supported friction types (mutually exclusive parameters) are: Default (Coulomb), Elastic slip, Slip
tolerance, Lagrange multiplier, and Rough. Depending on the template loaded and friction type
selected, the window layout changes to show only the relevant options for defining other parameters and
data items. Other supported optional parameters are: Exponential decay, Test data, Anisotropic,
Taumax, and Dependencies. See the Abaqus documentation for detailed descriptions of these
parameters.
Note: The friction type User is not supported in the Contact Manager. However, it is supported in
HyperMesh in the *SURFACE INTERACTION card image.

For all friction types (except Rough), there are four options to define the friction coefficient:
Direct This is the default method for defining the friction coefficient. Selecting this
option means that the Exponential decay and Anisotropic parameters will
not be written in the input file.
The No of Dependencies check box and corresponding entry box should be
used to define the Dependencies parameter. There is a table available for
defining the corresponding data lines. The available data items are: Friction
coefficient, Slip rate, Contact pressure, Average temperature at the contact
point, and average field variable values.
The column numbers in the table will change based on the setting for No of
Dependencies. The row numbers can be defined at the No of data lines
entry box. Click Set to update the table to reflect the specified number of
rows.
To enter values in the table, click on a cell to make it active and write down
the values from keyboard. The table works like a regular spread sheet.
You can also read comma delimited data from a text file by clicking Read
From a File. This button opens a file browser. Select the file and click Open
to export the comma delimited data. The row number will be set to the
number of data lines found in the file.
Anisotropic This option allows you to define the data lines for the Anisotropic
parameter.
The No of Dependencies check box and corresponding entry box should be
used to define the Dependencies parameter.
There is a table available for defining the corresponding data lines. The
available data items are: Friction coefficient1 (first slip direction), Friction
coefficient2 (second slip direction), Slip rate, Contact pressure, Average
temperature at the contact point, and average field variable values.
The column numbers in the table will change based on the setting for No of
Dependencies. The row numbers can be defined at the No of data lines
entry box. Click Set to update the table to reflect the specified number of
rows.
To enter values in the table, click on a cell to make it active and write down
the values from keyboard. The table functions like a regular spread sheet.
You can also read comma delimited data from a text file by clicking Read
From a File. This button opens a file browser. Select the file and click Open
to export the comma delimited data. The row number will be set to the
number of data lines found in the file.

Exponential decay This option allows you to define the data lines for the Exponential decay
parameter. The available data items are: Static friction coefficient, Kinetic
friction coefficient, and decay coefficient.
Exponential This option allows you to define the data lines for the Exponential decay,
decay, test data test data parameter. The available data items are: Friction coefficient at
point 1 (first data line), Friction coefficient at point 2 (second data line), Slip
rate at point 2 (second data line) and Kinematic friction coefficient (optional
third data line).
Note:
Using the Direct and Anisotropic tables:
· Right click in the table to display a pull-down menu containing copy, cut and paste options.
Comma delimited data can be copied/cut into or pasted from the clipboard using these options.
Hot keys, for example, Ctrl-c, Ctrl-x and Ctrl-v on PC, can also be used.
· Left click in a cell to activate the cell. Click in an active cell to move the insertion cursor to the
character nearest the mouse.
· The shift and ctrl keys can be used with a left mouse click to select multiple items in a table.
up and down arrows to change the active cell
· Press Backspace to delete the character before the insertion cursor in the active cell. If multiple
cells are selected, Backspace deletes all selected cells.
· Press Delete to delete the character after the insertion cursor in the active cell. If multiple cells are
selected, Delete deletes all selected cells.

Dummy Import/Export
The Abaqus interface in HyperMesh supports Abaqus-Explicit dummy models with both coordinate based
and node dependent ORIENTATION systems. In order to position the dummy models from the
HyperMesh safety/dummy panel, the model must have a system hierarchy to define the parent-child
relationship. In addition, the min/max angle of rotation for each dof in a joint must be defined. This and
some other relevant information are defined in a separate file called the positioning (*.pos) file.
The Dummy Import button in the Abaqus Utility menu allows you to import an Abaqus dummy input file
and the corresponding positioning file at the same time. This tool creates assemblies from each dummy
part and establishes the required system hierarchy and min/max angles for each joint.
The Dummy Export button in the Abaqus Utility menu exports the dummy model without the hierarchical
system references established in the import process.
To remove the hierarchical system references manually, use the Cleanup Hierarchy macro.

Set Browser
HyperMesh includes a tool that automates the grouping and display of model components through the
HyperMesh entity set functionality.
The Set Browser is available from the Tools pull-down menu. Refer to the HyperMesh online help for
details about using the Set Browser.

Solid Face Alignment
The Solid Face Alignment utility uses the face1 to face2 direction to determine the default stack or
thickness direction for Abaqus composite solid, gasket and continuum shell elements. This tool allows
enables you to align the face1 of selected solid elements (hexa and penta) to match with a planar face. As
a result, the default stack (or thickness) directions for all selected elements become normal to a plane. In
addition, you can review the face1 and default stack (or thickness) direction of selected solids. The utility
has three buttons:
Align Faces The Align Faces button opens the HyperMesh element selector
panel and allows you to pick solid elements. Selected elements are
highlighted. When you click proceed, it creates a temporary skin of
the selected solids and allows you to pick face elements from this
skin. The selected faces are highlighted. When you click proceed,
the face1 of all selected solid elements will match with the selected
face element and a review of the stack (or thickness) direction will
be shown.
Review The Review button opens the HyperMesh element selector panel
and allows you to pick solid elements. Selected elements are
highlighted. When you click proceed, it highlights the face1 of
selected solids and draws an arrow along the default stack (or
thickness) direction of selected solids.
Reset The Reset button deletes the stack (or thickness) direction arrows.

Step Manager
The Abaqus Step Manager is a graphical interface that allows you to define Abaqus history keywords. The
Abaqus Step Manager is accessed by loading the Abaqus user profile and clicking the Step Manager
button on the Abaqus Utility menu. The process that allows you to create, edit, and review the following
keywords in HyperMesh begins in the Step tab:
*STEP
Analysis types:
*BUCKLE
*DYNAMIC
*FREQUENCY
*HEAT TRANSFER
*MODAL DYNAMIC
*STATIC
*STEADY STATE DYNAMICS
Loads:
*BOUNDARY
*CLOAD
*DLOAD
*DSLOAD
*FILM
*CFILM
*SFILM
*TEMPERATURE
*INERTIA RELIEF
*INITIAL CONDITIONS {TYPE=

TEMPERATURE, VELOCITY}
Output requests:
*OUTPUT
*NODE OUTPUT

*ELEMENT OUTPUT
*STEP OUTPUT
*ENERGY OUTPUT
*NODE FILE
*EL FILE
*STEP FILE
*ENERGY FILE
*NODE PRINT
*EL PRINT
*STEP PRINT
*ENERGY PRINT
Interface controls:
*MODEL CHANGE
*CONTACT INTERFERENCE
*CHANGE FRICTION
*CLEARANCE
*CONTACT CONTROLS
Others:
*MONITOR
*FILE FORMAT
*PRINT
*RESTART
Step Manager Dialog Environment
The following procedures are used to navigate through the Step Manager dialogs:
· When the Step Manager window is minimized or it is behind the HyperMesh window, restore it by
clicking the Step Manager button in the Abaqus Utility menu.

· Double click on a cell entry to open the corresponding editing window.
· The first row contains a list of all initial condition (or model) load collectors. Double click on an
Initial Condition name to open the corresponding dialog for defining initial condition loads.
· Right click on a table to display menu options. Examples of options are Display: all, Display:
none, Display: reverse, Text review, Review Load collectors, Reset review, Review Options,
Reorder, Export: all, and Export: none. The Text review and Review load collectors options
work like the Text and Review buttons, respectively (see Abaqus Step Manager: Load Step Dialog
). The Reset review option clears the highlighted selections.
· The shift or ctrl key combined with a left click can be used to select multiple items in a table.
· To display bubble help, place the cursor over a button for a few moments.
· Press ctrl and the left or right arrow key to move the cursor within the active cell. Use the left,
right, up, and down arrows to change the active cell.
· Right click on the Review button to clear the highlighted selections.
· If you create, update or delete steps, load collectors, output blocks, components, groups,
properties, or entity sets from HyperMesh panels while the Step Manager is open, click the Sync
button to update the Step Manager with the new changes.
· In some fields in the Step Manager, you can access the Entity Browser, which is available via the
… button. The Entity Browser makes it more convenient to view and sort long lists of components
or other entities when selecting them for the field.
Entity Browser
Use the Entity Browser to easily sort and select an entity for a field on a dialog. The Entity Browser is
available through the … button and lists the entities of the relevant type for the selection.
The entities are listed in a tree view. To select an entity, highlight it in the list and click OK. Use the buttons
on the dialog to sort the list to more easily view the choices when there are many entities in the list. The
buttons perform the following actions:
Filter Type text in the adjacent field and click Filter to show only the entities
with names that contain the text. You can use the wildcard character (*)
to specify that the text can appear anywhere within the entity name. To
clear the results and show all entities, right-click the Filter button.

Review Highlights the selected entity in the model in HyperMesh.
Sort Lists the entities in alphabetical order. Click again to reverse the order.
OK Selects an entity for the field on the dialog.
Cancel Closes the Entity Browser without making a selection.
Step Manager Tab Environment
· Editable cells have a white background, unless it is the active cell. You can input values using the
keyboard in editable cells. Non-editable cells have a gray background.
· Left click in an editable (white background) cell to activate it for input. Click in an active cell to
move the insertion cursor to the character nearest the mouse.
up, and down arrows to change the active cell.
· Press Backspace to delete the character before the insertion cursor in the active cell.
· Press Delete to delete the character after the insertion cursor in the active cell.
· In some fields, you can use the … button to open the Entity Browser to select the entity for that
field.
ABAQUS Step Manager Step Tab
The Abaqus Step Manager opens when you load the Abaqus user profile and click Step Manager on the
Abaqus Utility menu. The Step Manager window is organized into two tabs: Step and Load Case.
The Step tab contains the descriptions of existing load steps with the corresponding analysis types, load
collectors, output requests, and interface controls. You can create, edit, review, rename, reorder, and
delete load steps from this tab as well as set the export and display status of the load steps.
See Step Manager Dialog Environment for tips on navigating through the dialogs.
The Step tab table contains the following columns:

Export The export status of the load step. If the export status is on, the load step
is written to the input file when exported from HyperMesh. If the export
status is off, the STEP is not exported to the input file.
Name The name of the load step.
Analysis Type The analysis type of the load step.
Load Collector The list of load collectors in the load step.
Output Block The list of output blocks in the load step.
Interface The list of interface controls in the load step. Interface Controls defines
Controls the following Abaqus keywords: CONTACT PAIR, SURFACE INTERACTION,
CONTACT, CONTACT CONTROLS, CLEARANCE, CONTACT INTERFERENCE, MODEL
CHANGE, CHANGE FRICTION, and CONTROLS.
Display Turns the load step display on/off.
The Step tab contains the following buttons:
New... Opens the Create New Step dialog. Enter the name of the new load step in the
Name: text box and click Create to create the load step and open the
corresponding Load Step editing dialog. The Same as: option allows you to
create a new load step by copying from an existing load step.
Edit... Opens the load step editing dialog for the selected load step.
Review Reviews the selected load collectors. All loads in the load collectors are
highlighted in the HyperMesh graphics. The highlighted loads show through the
solid mesh in performance graphics. If a load is defined with set, the underlying
nodes or elements are highlighted. Right-click Review to clear the highlighted
selections.
Text Reviews the selected load step in a text window.
Renam Opens the HyperMesh rename panel for renaming load steps, load collectors,
e output blocks, or various interface controls. When you finish renaming, click
return to update the Step Manager with the new names.
Delete Deletes the selected load steps.
Sync Updates the Step Manager with the current HyperMesh database. If you
manually create, update, or delete load steps, load collectors, output blocks,
groups, or entity sets from HyperMesh panels while the Step Manager is open,
click Sync to update the Step Manager with the new changes.

Close Closes the Step Manager.
Moves the selected load steps up one row.
Moves the selected load steps down one row.
ABAQUS Step Manager: Load Step Dialog

The Load Step dialog allows you to define the *STEP-*END STEP block as well as the associated Abaqus
history keywords. To open this dialog, double-click on the load step name in the Name: column on the
Step tab or select the load step from the Name: column and click Edit.... Options vary according to the
active template. There are three vertical sections in this dialog.
left-most section Contains a tree structure with various Abaqus history options. Selecting an
option from the tree changes the dialog layout.
middle section Contains the corresponding collectors in a table and relevant buttons to
create, review, organize, reorder, rename, or delete these collectors. In
HyperMesh, all loads must be organized into load collectors and all output
requests must be under output blocks. When you select a load type,
output request type, or interface control from the tree, the load collector
table, output block table, or interfaces table is displayed in the middle
section.
right-most section Contains the various tabs and options to define, edit, review, or delete the
currently selected tree item. If the tree item needs to be organized in a
collector (such as a load or output request), a collector must be selected
from the middle section.
The Load Step dialog contains the following general buttons:
Review Reviews all load collectors in the current load step. All loads in the load collectors
are highlighted in the HyperMesh graphics. The highlighted loads show through
the solid mesh in performance graphics. If a load is defined with set, the
underlying nodes or elements are highlighted. Right-click on the Review button to
clear the highlighted selections.

Text... Reviews the current load step in a text window
Synchronize Updates the Step Manager with the current HyperMesh database. If you manually
create, update, or delete load steps, load collectors, output blocks, groups, or
entity sets from HyperMesh panels while the Step Manager is open, click
Synchronize to update the Step Manager with the new changes.
Close Closes the Load Step window and opens the Step Manager window.
The following options are available on the Load Step dialog tree:
Load Step
Title
Parameter
Analysis procedure
Load collector
· Boundary
· Concentrated loads
· CLOAD
· CFILM
· Distributed loads
· DLOAD
· FILM
· Surface loads
· DSLOAD
· SFILM
· Temperature
· Inertia Relief
· Interface controls
· Contact Pair
· Surface Interaction
· General Contact
· Contact Controls
· Clearance
· Contact Interference
· Model Change
· Change Friction

· Controls
· Output requests
· ODB file
· Result file (.fil)
· Data file (.dat)
· Monitor
· Print
· File Format
· File Output
· Restart write
· Unsupported cards
Load Step: Load Collector Table

In HyperMesh, each load or constraint must belong to a load collector. Therefore, when you select load
types from the tree, the load collector table appears in the middle section of the Load Step window.
The Load collector table contains a list of the load collectors with their corresponding display, color, and
history status. You can create, edit, review, rename, reorder, and delete load collectors from this table.
You can also organize (copy or move) loads into load collectors and edit the load labels here.
The Load collector table contains the following columns:
Status The history status of the load collector. If the status is on, the load collector
belongs to the current load step. This means, all loads in the load collector will be
written under the current *STEP block. If the status is off, no loads from the load
collector will be written under the current *STEP block.
Name The name of the load collector. The load collector names are for Hypermesh
internal use only. The Abaqus input file does not need them.
Display The display on/off check boxes and color change buttons for the load collector.
The color can be changed by clicking the color button and selecting a color from
the menu.
Click on a load collector name to set it as the current load collector in HyperMesh. All loads created from
this point are placed into the selected load collector.

The Load Type: status bar (below the load collector table) shows all the load types present in the selected
load collector. In addition, these load types are highlighted with bold font in the tree.
The Load collector table contains the following buttons:
New... Opens the Create Load Collector dialog in which you enter the name of the new
load collector. The Same as: option allows you to create a load collector by copying
attributes (except loads created from HyperMesh panels) from an existing load
collector. The Create button in this dialog creates the load collector and adds it to
the current load step.
Review Reviews the selected load collector. All loads in the load collector are highlighted in
the HyperMesh graphics. The highlighted loads show through the solid mesh in
performance graphics. If a load is defined with set, the underlying nodes or
elements are highlighted. Right click on the Review button to clear the highlighted
selections.
Organize... Opens the HyperMesh organize panel where you can copy/move loads into
different load collectors. When you have finished, click return to update the Step
Manager with the new organization.
Label... Opens the corresponding HyperMesh panel where you can turn on/off load labels
or update the label size.
Delete Opens the HyperMesh delete panel where you can delete load collectors. When
you are finished, click return to update the Load collector table.
Load Step: Title

The Title option in the tree allows you to define a one line title or sub-heading for the load step. This line
appears under the *STEP keyword in the input file. The title is also used in the ODB file to identify the step.
Check the Step Heading option to input the title and click Update to update the HyperMesh database.
Load Step: Parameter

The Parameter option in the tree allows you to define the parameters of the *STEP card.
Name, Amplitude, Extrapolation, Unsymmetric, Increment, Nlgeom, and Perturbation

See the Abaqus online documentation for a detailed description of these parameters. Click Update to
activate the parameters defined in the HyperMesh database.
Load Step: Analysis Procedure

The Analysis procedure option in the tree allows you to define the analysis type of the load step. The
following analysis types with the corresponding parameters and data lines are supported:
Analysis types: Parameter:
*STATIC ADIABATIC, FULLY PLASTIC, RIKS, STABALIZE, DIRECT,

DIRECT=NO STOP, FACTOR, LONG TERM
*FREQUENCY PROPERTY EVALUATION, EIGENSOLVER = {SUBSPACE,

LANCZOS, AMS}, NORMALIZATION = {MASS,
DISPLACEMENT}, RESIDUAL MODES, ACOUSTIC
COUPLING, NUMBER INTERVAL, BIAS, USER BOUNDARIES
*BUCKLE EIGENSOLVER = {SUBSPACE, LANCZOS}
*DYNAMIC HAFTOL, DIRECT, DIRECT=NO STOP, SUBSPACE,

(Standard) ADIABATIC, ALPHA, INITIAL, NOHAF
*DYNAMIC EXPLICIT, SCALE FACTOR, ADIABATIC

(Explicit)
FIXED TIME INCREMENTATION, DIRECT USER CONTROL,
ELEMENT BY ELEMENT
IMPROVED DT METHOD = YES or NO
*HEAT TRANSFER DELTMX, END = {PERIOD, SS}, STEADY STATE, MXDEM
*MODAL DYNAMIC CONTINUE = YES or NO
*STEADY STATE DYNAMICS DIRECT, SUBSPACE PROJECTION = {ALL FREQUENCIES,

CONSTANT, EIGENFREQUENCY, PROPERTY CHANGE},
FREQUENCY SCALE, INTERVAL, REAL ONLY, DAMPING
CHANGE, STIFFNESS CHANGE
There are two tabs for each analysis type: Parameter and Dataline. The layout of the tabs change, based
on the analysis types selected.

activate the optional parameter or data item selection in the HyperMesh database.
Load Step: Boundary

The Boundary dialog allows you to define and edit the *BOUNDARY card. To open this dialog, select
Boundary from the tree and a load collector from the Load collector table.
The Boundary dialog contains three tabs:
Define
Delete
Parameter
Load Step: Boundary: Define Tab

The Define tab allows you to define *BOUNDARY cards on individual nodes or geometry (surfaces, points,
lines). You can also define the boundary on node sets. There are five different types of boundary conditions
available:
Boundary types Abaqus keyword
Default (disp) *BOUNDARY
Velocity *BOUNDARY, TYPE = VELOCITY
Acceleration *BOUNDARY, TYPE =

ACCELERATION
Temperature *BOUNDARY on dof 11
Electric potential *BOUNDARY on dof 9

It is recommended that you use only one boundary type per load collector in HyperMesh. If you need to use
multiple boundary types in the same STEP, define each type in a separate load collector and add them to
the same load step.
You can define a *BOUNDARY card on nodes/geometry or on node sets. For Define Boundary on:, the
following options are available:
· Nodes or geometry
· Node sets
The layout of the Define tab changes, based on your selection.
Define Boundary on: Nodes or geometry

The Define Boundary on: Nodes or geometry option allows you to define various types of boundaries on
individual nodes or geometry. Boundaries created on nodes have a special graphical display in
HyperMesh. Loads created on geometric entities like surfaces, lines or points are automatically mapped to
FEA mesh on export. You can also map them using the Map Loads on Geometry button.
The Define tab for Define Boundary on: Nodes or geometry has the following buttons:
Define from Opens the HyperMesh constraints panel to create/update boundary conditions.
'Constraints'
panels To create a boundary on nodes, go to the create sub-panel, select the nodes
button, pick the desired nodes from HyperMesh graphics, check the constrained
degrees of freedoms, and click create.
To create a boundary on geometry, go to the create sub-panel, select surfs,
points, or lines using the switch, pick the desired geometry from the HyperMesh
graphics, check the constrained degrees of freedom, and click create.
Notes:
· Loads created on geometric entities are automatically mapped to FEA

mesh on export. You can also map them using the Map Loads on
Geometry button.
· An existing boundary can be updated from the update sub-panel.

· While you are in the constraints panel, press the h key to view
panel-specific help.
· When you are finished creating or updating boundary conditions, click

return to update Step Manager with the new loads.
Map Loads Opens the HyperMesh loads on geom panel to map loads on geometry to FEA
on Geometry mesh entities.
Click Map loads to map all geometric loads in the current load collector to FEA
entities.
Note:
· You can also pick other load collectors by clicking the loadcols button
and map loads in all of them together.
· While you are in the loads on geom panel, press the h key to view
· When you are finished, click return to update Step Manager with the new
loads.
Define Boundary on: Node sets

The Define Boundary on: Node sets option defines various types of boundaries on node sets. The node
set names are used in the *BOUNDARY data lines instead of the individual nodes. Unlike Abaqus surfaces
in HyperMesh, you can combine node sets with individual node IDs in the same *BOUNDARY card.
Note: HyperMesh does not graphically display loads created on sets. Therefore, when you review a
load collector in the Step Manager, only loads created on individual entities are highlighted. For
loads defined on sets, the underlying nodes or elements are highlighted.
This dialog contains a Node sets menu with a list of the existing node sets. It also has a table for data line
input containing the following columns:
Nset The name of the node sets. Node sets can only be added or deleted from this
column using the or buttons, respectively.
1st dof The first degree of freedom. You can input any integer or any of the following
types in this column:
XSYMM, YSYMM, ZSYMM, ENCASTRE, PINNED, XASYMM, YASYMM,
ZASYMM, NOWARP, NOOVAL, NODEFORM

Last dof The last degree of freedom.
Magnitude The magnitude.
Load Id The ID of the load collector
The Define tab for Define Boundary on: Node sets contains the following buttons:
Review Set Reviews the selected node sets by highlighting them in the HyperMesh
graphics. Right click the Review button to clear the review selections.
Create/Edit Set Opens the entity sets panel in HyperMesh. When you finish creating/editing
the set, click return. The Step Manager is updated with the new set
appearing in the node set list.
Add the selected node set from the pull down menu to the data line table on
the right.
Delete the selected node set from the data line table.
Review Reviews the selected node set in the data line table. Right click Review to
Update Updates the HyperMesh database with the data lines defined in the table. By
default, HyperMesh does not create a display for loads defined with sets.
Display/Review Opens the appropriate HyperMesh panel. Use the review button to expand the
from panel loads and constraints on the sets for visualization purposes.
For tips on entering information and navigating in the Define tab, see Step Manager Tab Environment.
Load Step: Boundary: Delete Tab

The Delete tab allows you to delete boundaries and other loads from Hypermesh. There are three deletion
options:
All loads in current collector The Delete button deletes all the loads from the current
load collector.
All 'Boundary' in current collector The Delete button deletes only *BOUNDARY loads from
the current load collector.

By selection The Pick Loads button opens the HyperMesh load
selector panel. Pick the loads you want to delete and
click proceed.
The corresponding Reset button resets the selected
loads.
The Delete button deletes the selected loads.
Load Step: Boundary: Parameter Tab

The Parameter tab allows you to define optional parameters for the *BOUNDARY card.
Amplitude, OP, Load Case, Fixed, and Region Type
activate the optional parameter selection in the HyperMesh database.
Load Step: CLOAD

In Abaqus, *CLOAD can have degrees of freedom (dof) 1 through 6. In HyperMesh, concentrated loads
with dofs 1 through 3 are called force and those with dofs 4 through 6 are called moments. The force
and moments are two separate entities that are defined from separate panels. Their graphical displays
are also different. As a result, Step Manager has two distinct tree options for *CLOAD: CLOAD-Force and
CLOAD-Moment.
The CLOAD-Force dialog allows you to define the *CLOAD card for dofs 1 through 3 and the
CLOAD-Moment for dofs 4 through 6. Open Concentrated loads in the tree, select CLOAD-Force or
CLOAD-Moment, and a load collector from the Load collector table to open the corresponding dialog in
the right most section of the Load Step window.
It is recommended that you do not use both CLOAD–Force and CLOAD-Moment in the same load
collector in HyperMesh. If you need to use both types of *CLOAD in the same STEP, define each type in a
separate load collector and add them to the same load step.
Each dialog contain three tabs:

Define
Delete
Parameter
Load Step: CLOAD: Define Tab

The Define tab allows you to define *CLOAD (force or moment) cards on individual nodes or geometry
(points). You can also define the *CLOAD on node sets.
You can define CLOAD-Force/Moment on nodes/geometry or on node sets. For Define
CLOAD-Force/Moment on:, the following options are available:
· Node sets
Define CLOAD-Force/Moment on: Nodes or geometry

The Define CLOAD-Force/Moment on: Nodes or geometry option allows you to define *CLOAD (force
or moment) on individual nodes or geometry. The concentrated loads created on nodes have special
graphical display in HyperMesh. Loads created on geometric entities such as surfaces, lines, or points are
automatically mapped to FEA mesh on export. They can also be mapped using the Map Loads on
Geometry button.
The Define tab for Define CLOAD-Force/Moment on: Nodes or geometry contains the following
buttons:
Define from 'Forces'/ Opens the HyperMesh forces or moments panel to create/update a
‘Moments’ Panel CLOAD.
To create a CLOAD on nodes, go to the create sub-panel, select nodes
using the switch, pick the desired nodes from HyperMesh graphics, select
the global/local system, select a vector, input a magnitude, and click
create..

To create a CLOAD on geometry, go to the create sub-panel, select
points using the switch, pick the desired geometry from HyperMesh
graphics, select the global/local system, select a vector, input a magnitude,
and click create.
Note:
· Loads created on geometric entities are automatically mapped to

FEA mesh on export. You can also map them using the Map
Loads on Geometry button.
· You can also update an existing force or moments from the

update sub-panel.
· While you are in the forces or moments panel, press the h key to
view panel-specific help.
· When you finish creating or updating CLOAD, click return to

update Step Manager with the new loads.
Map Loads on Opens the HyperMesh loads on geom panel to map loads on geometry to
geometry FEA mesh entities.
Click Map loads to map all geometric loads in the current load collector to
FEA entities.
Note:
· You can also pick other load collectors by clicking on the loadcols
button and map loads in all of them together.
· When you are finished, click return to update the Step Manager
with the new loads.
Define CLOAD-Force/Moment on: Node sets

The Define CLOAD-Force/Moment on: Node sets option defines CLOAD on node sets. The node set
names are used in the *CLOAD data lines instead of the individual nodes. Unlike Abaqus surfaces in
HyperMesh, you can combine node sets with individual node IDs in the same *CLOAD card.
Note: Loads created on sets are not graphically displayed in HyperMesh. Therefore, when you review a
load collector in Step Manager, only loads created on individual entities are highlighted. For loads
defined on sets, the underlying nodes or elements are highlighted.

This Define tab for Define CLOAD-Force/Moment on: Node sets includes a Node sets menu containing
a list of existing node sets. A data line input table also appears on the Define tab. The table contains the
following columns:
Nodeset
The name of the node sets. Node sets are added or removed using or
, respectively.
Comp_x The component in x direction. The x-direction indicates dof 1 for force and dof 4 for
moment.
Comp_y The component in y direction. The y-direction indicates dof 2 for force and dof 5 for
moment.
Comp_z The component in z direction. The x-direction indicates dof 3 for force and dof 6 for
moment.
Magnitude The magnitude. This column is non-editable. The magnitude is calculated based on
the Comp_x, Comp_y, and Comp_z defined for each node set when you click
Update.
Load Id The ID of the load collector.
The Define tab for Define CLOAD-Force/Moment on: Node sets contains the following buttons:
Review Set Reviews the selected node sets by highlighting them in the HyperMesh graphics.
Right click Review to clear the review selections.
Create/Edit Set.. Opens the entity sets panel in HyperMesh. When you finish creating/editing the
set, click return. Step Manager is updated with the new set appearing in the
node set list.
from panel loads and constraints on the sets for visualization purposes.
Add the selected node set from the drop-down menu to the data line table on the
right.
Delete the selected node set from the data line table.
Define by vector Opens the HyperMesh vector selector panel. Pick a vector and click proceed.
This vector is used to define the Comp_x, Comp_y, Comp_z, and Magnitude of
the CLOAD for the selected node set.
Create/Edit Opens the vectors panel in HyperMesh. When you finish creating/editing the

vector.. vector, click return.
Review Creates special review forces or moments in HyperMesh graphics for the
selected node set. These review forces or moments take into consideration the
*TRANSFORM cards that may be associated with nodes in the node set. Right
click Review to clear the special review loads and highlighting.
default, HyperMesh does not display loads defined with sets.
Load Step: CLOAD: Delete Tab

The Delete tab allows you to delete CLOAD and other loads from HyperMesh. There are three options for
deletion:
All loads in current collector The Delete button deletes all the loads from the current load
collector.
All 'CLOAD' in current collector The Delete button deletes only *CLOAD loads from the
current load collector.
By selection The Pick Loads button opens the HyperMesh load selector
panel. Pick the loads you want to delete and click proceed.
The corresponding Reset button resets the selected loads.
Load Step: CLOAD: Parameter Tab

The Parameter tab allows you to define optional parameters for the *CLOAD card.
Amplitude, OP, Load Case, Cyclic Mode, Follower, and Region Type

Load Step: CFILM
The CFILM dialog allows you to define the *CFILM card on node sets. To open the dialog in the Load
Step window, open Concentrated loads in the tree, select CFILM, and select a load collector from the
Load collector table.
The dialog contains three tabs:
Define
Delete
Parameter
Load Step: CFILM: Define Tab

The Define tab allows you to define a *CFILM card on node sets only. HyperMesh does not support
*CFILM on individual nodes.
The Define CFILM-Force/Moment on: Node sets option defines CFILM on node sets. The node set
names are used in the *CFILM data lines instead of the individual nodes. Unlike Abaqus surfaces in
HyperMesh, you can combine node sets with individual node IDs in the same *CFILM card.
Note: Loads created on sets are not graphically displayed in HyperMesh. Therefore, when you review a
load collector in the Step Manager, only loads created on individual entities are highlighted. For
This dialog has a node sets menu containing a list of the existing node sets. It also has a data line input
table with the following columns:
Nodeset
The name of the node sets. Node sets are added or removed using or
, respectively.

Area The area associated with the nodes.
Sink temp Reference sink temperature.
Film coef Reference film coefficient.
The Define CFILM on: Node sets option has the following buttons:
graphics. Right click Review to clear the review selections.
Create/Edit Set.. Opens the entity sets panel in HyperMesh. When you finish creating/editing
Adds the selected node set from the drop-down menu to the data line table on
the right.
Deletes the selected node set from the data line table.
Review Reviews the selected node set in the data line table. Right click Review to
Load Step: CFILM: Delete Tab

The Delete tab allows you to delete CFILM and other loads from HyperMesh. There are three deletion
options:
collector.
All 'CFILM' in current collector The Delete button deletes only *CFILM loads from the current
load collector.

Load Step: CFILM: Parameter Tab

The Parameter tab allows you to define optional parameters for the *CFILM card.
Amplitude, Film Amplitude, OP, and Region Type
Load Step: DLOAD

The DLOAD dialog allows you to define the *DLOAD cards on individual elements or geometry (surfaces).
You can also define the DLOAD on element sets. To open the dialog in the Load Step window, open
Distributed loads in the tree, select DLOAD, and select a load collector from the Load collector table.
Define
Delete
Parameter
Load Step: DLOAD: Define Tab

The Define tab allows you to define *DLOAD cards on individual elements or geometry (surfaces) as well
as on element sets. There are five different DLOAD types available: default (Pressure), centrifugal,
rotary acceleration, gravity, pressure in pipe/elbow, hydro pressure, and hydro pressure in
pipe/elbow.
Only default (Pressure) type DLOAD can be created on an individual element or geometry in HyperMesh.
The other types are available only for element sets.
It is recommended that you use only one type of DLOAD in a load collector in HyperMesh. If you need to

use multiple types of DLOAD in the same STEP, define each type in a separate load collector and add
them to the same load step.
You can define DLOAD on elements, geometry, or element sets. For Define DLOAD on:, the following
options are available:
· Elements or geometry
· Element sets
Define DLOAD on: Elements or geometry

The Define DLOAD on: Elements or geometry option allows you to define the default (pressure) type of
DLOAD on individual elements or geometric surfaces. Pressure loads created on elements have special
graphical display in HyperMesh. Loads created on geometric entities such as surfaces are automatically
mapped to FEA mesh on export. You can also map them using the Map Loads on Geometry button.
The Define tab for Define DLOAD on: Elements or geometry contains the following buttons:
Define from Opens the HyperMesh pressures panel to create/update DLOAD.

'pressures'
panels To create a pressure on elements, go to the create subpanel, select the elems
button, pick the desired elements from the HyperMesh graphics, select nodes
using the switch, pick two or three nodes from a face of a selected element,
input the magnitude, and click create.
To create a pressure on geometry, go to the create subpanel, select the surfs
option from the toggle, pick the desired geometry from the HyperMesh graphics,
input the magnitude, and click create.
Note:

Geometry button.
· You can also update an existing DLOAD from the update sub-panel.
· While you are in the pressure panel, press the h key to view
· When you finish creating or updating boundary conditions, click return

and Step Manager is updated with the new loads.

Map Loads on Opens the HyperMesh loads on geom panel to map loads on geometry to FEA
geometry mesh entities.
Click Map loads to map all geometric loads in the current load collector to FEA
entities.
Note:
· You can also pick other load collectors by clicking on the loadcols and
map loads in all of them together.
· When you finish, click return to update the Step Manager with the new
loads.
Define DLOAD on: Element sets

The Define DLOAD on: Element sets option allows you to define various DLOAD types on element sets.
The element set names are used in the *DLOAD data lines instead of the individual elements. Unlike
Abaqus surfaces in HyperMesh, you can combine element sets with individual element IDs in the same
*DLOAD card.
Note: There is no graphical display in HyperMesh for loads created on sets. Therefore, when you review
a load collector in the Step Manager, only loads created on individual entities are highlighted. For
This dialog contains a element sets menu with a list of the existing element sets. There are two types of
elsets in Hypermesh: Components and Entity sets. The Abaqus elsets that are linked to sectional property
cards (such as *SOLID SECTION, *SHELL SECTION, etc.) become Components in HyperMesh. Others
become Entity sets. To differentiate between these two types, there is a divider line "- - - - -" in the elset list
that pops up if you click the element sets menu. The elsets listed below the divider line are Components.
This dialog also contains a table for data line input. The table changes depending on the DLOAD type
selected.
The table contains the following columns:
For Default (Pressure) type:
Elset The name of the element sets. Element sets are added and deleted in this
column using or , respectively.

Label The labels of pressure load. The available labels are: P1, P2, P3, P4, P5, P6,
and P.
Magnitude The magnitude of the load.
For Centrifugal type:
Elset The name of the element sets. Element sets are added and deleted in this
Label The labels of centrifugal loads and Coriolis forces. The available labels are:
CENTRIF, CENT, and CORIO.
Coord1 Coordinate 1 of a point on the axis of rotation.
DirCos1 1-component of the direction cosine of the axis of rotation.
For Rotary acceleration type:
Elset The name of the element sets. Element sets are added and deleted in
this column using or , respectively.
Label The labels of the DLOAD type. The available labels are: ROTA.
Coord1 Coordinate 1 of a point on the axis of rotary acceleration.

DirCos1 1-component of the direction cosine of the axis of rotary acceleration.
For Gravity type:
Label The labels of the DLOAD type. The available labels are: GRAV.
Comp1 1-component of the gravity vector.
For pressure in pipe/elbow type:
Label The labels of the pressure in pipe/elbow elements. The available labels
are: PE, PI, PENU, and PINU.
Diameter The effective inner or outer diameter.
Condition The end loading condition: CLOSE (default) or OPEN.
For hydro pressure type:

Label The labels of the hydrostatic pressure. The available labels are: HP.
Zero press Z-coordinate of zero pressure level in three-dimensional or axisymmetric

cases; Y-coordinate of zero pressure level in two-dimensional cases.
Press point Z-coordinate of the point at which the pressure is defined in

three-dimensional or axisymmetric cases; Y-coordinate of the point at
which the pressure is defined in two-dimensional cases.
For hydro pressure in pipe/elbow type:
Label The labels of the hydrostatic pressure in pipe.elbow elements. The

available labels are: HPE, and HPI.

Press point Z-coordinate of the point at which the pressure is defined in

three-dimensional or axisymmetric cases; Y-coordinate of the point at
which the pressure is defined in two-dimensional cases.
Diameter The effective inner or outer diameter.
Condition The end loading condition: CLOSE (default) or OPEN.
The Define tab for Define DLOAD on: Element sets contains the following buttons:
Review Set Reviews the selected element sets by highlighting them in the HyperMesh

appearing in the element set list.
Display/Review Opens the appropriate HyperMesh panel. Use the review button to expand
from panel the loads and constraints on the sets for visualization purposes.
Add the selected element set from the pull down menu to the data line table
on the right.
Delete the selected element set from the data line table.
Show faces This option is only shown for Default (pressure) type. It is mainly used to
review the face identifiers of elements in the selected set. It creates a
temporary skin of the selected elset, opens the HyperMesh element selector
panel, and allows you to pick face elements from this skin. When you return
from the element selector panel, the selected faces display color-coded face
identifier tags. In performance graphics, these tags are sometimes blocked
by the solid mesh. You may need to rotate the model a little to view the tags.
Right click the Show faces button to clear the face review.
Define by vector This option is only shown for Gravity type. It opens the HyperMesh vector
selector panel. Pick a vector and click proceed. This vector is used to define
the Comp1, Comp2, Comp3, and Magnitude of the gravity load for the
selected elset.
Create/Edit This option is only shown for Gravity type. Opens the vectors panel in
vector.. HyperMesh. When you finish creating/editing the vector, click return.
Review For Default (pressure) type. Creates special review pressure loads in the
HyperMesh graphics for the selected set. For other types, it reviews the
selected element set. Right click the Review button to clear the special
review loads and highlighting.
Load Step: DLOAD: Delete Tab

The Delete tab allows you to delete DLOAD and other loads from Hypermesh. There are three deletion
options:

All loads in current collector The Delete button deletes all the loads from the current
load collector.
All 'Distributed loads' in current The Delete button deletes all distributed (*DLOAD,
collector *FILM) loads from the current load collector.
By selection The Pick Loads button opens the HyperMesh load

selector panel. Pick the loads you want to delete and
click proceed.
The corresponding Reset button resets the selected
loads.
Load Step: DLOAD: Parameter Tab

The Parameter tab allows you to define optional parameters for the *DLOAD card.
Amplitude, OP, Load Case, Cyclic Mode, and Region Type
See the Abaqus Online Documentation for a detailed description of these parameters. Click Update to
Load Step: FILM

The FILM dialog allows you to define the *FILM cards on individual elements or geometry (surfaces). You
can also define the FILM on element sets. To open this dialog in the Load Step window, select FILM from
the tree and a load collector from the Load collector table.
Define
Delete

Parameter
FILM Coefficient
There are two options for defining film coefficient on FILM created on individual elements or geometry:
panel. Pick the FILM loads to which you want to assign film
coefficient, and click proceed.
The Update button assigns the value specified in the Film
coefficient: text box to all selected FILM loads.
All FILMs in current collector The Update button assigns the value specified in the Film
coefficient: text box to all the FILM loads in the current load
collector.
Load Step: FILM: Define Tab

The Define tab allows you to define *FILM cards on individual elements or geometry (surfaces) as well as
on element sets.
For Define DLOAD on:, the following options are available:
· Elements or geometry
· Element sets
For options to assign FILM coefficient, see FILM coefficient.

Define FILM on: Elements or geometry
The Define FILM on: Elements or geometry option allows you to define FILM on individual elements or
geometric surfaces. FILM loads created on elements have special graphical display in HyperMesh. Loads
created on geometric entities like surfaces are automatically mapped to FEA mesh on export. You can
also map them using the Map Loads on Geometry button.
The Define tab for Define FILM on: Elements or geometry has the following buttons:
Define from Opens the HyperMesh pressures panel to create/update FILM. It only allows you
'pressures' to define the reference sink temperature. The film coefficient needs to be defined
panels separately.
To create a FILM on elements, go to the create sub-panel, select elems using the
switch, pick the desired elements from the HyperMesh graphics, click nodes, pick
two or three nodes from a face of a selected element, input the magnitude (sink
temperature), and click create.
To create a pressure on geometry, go to the create sub-panel, select surfs using
the switch, pick the desired geometry from the HyperMesh graphics, input the
magnitude (sink temperature), and click create.
Note:

Geometry button.
· You can also update an existing FILM from the update sub-panel.
· While you are in the pressure panel, press the h key to view
· When you are finished creating or updating boundary conditions, click

return and the Step Manager will be updated with the new loads.
Map Loads Opens the HyperMesh loads on geom panel to map loads on geometry to FEA
on geometry mesh entities.
Click the Map loads button to map all geometric loads in the current load collector
to FEA entities.
Note:
· You can also pick other load collectors by clicking the loadcols button and
map loads in all of them together.
· When you are done, click return and the Step Manager will be updated

with the new loads.
Define FILM on: Element sets

The Define FILM on: Element sets option allows you to define the FILM load on element sets. The
element set names are used in the *FILM data lines instead of the individual elements. Unlike Abaqus
surfaces in HyperMesh, you can combine element sets with individual element IDs in the same *FILM card.
This dialog contains an element sets menu containing a list of the existing element sets. There are two
types of elsets in Hypermesh: Components and Entity sets. The Abaqus elsets that are linked to sectional
property cards (such as *SOLID SECTION, *SHELL SECTION, etc.) become Components in HyperMesh.
Others become Entity sets. To differentiate between these two types, there is a divider line "- - - - -" in the
elset list that pops up if you click the element sets menu. The elsets listed below the divider line are
Components.
This dialog also contains a table for data line input, which contains the following columns:
Elset The name of the element sets. Element sets are added or deleted in this column
using or , respectively.
Label The labels of FILM load. The available labels are: F1, F2, F3, F4, F5, F6, FPOS,
and FNEG.
Sink Temp The reference sink temperature.
Film coeff The reference film coefficient.
The Define tab for Define FILM on: Element sets contains the following buttons:
Review Set Reviews the selected element sets by highlighting them in the HyperMesh

appearing in the element set list.
from Panel loads and constraints on the sets for visualization purposes.
Add the selected element set from the pull down menu to the data line table
on the right.
Delete the selected element set from the data line table.
Show faces Used mainly to review the face identifiers of elements in the selected set. It
creates a temporary skin of the selected elset, opens the HyperMesh element
selector panel, and allows you to pick face elements from this skin. When you
return from the element selector panel, the selected faces will display
color-coded face identifier tags. In performance graphics, these tags are
sometimes blocked by the solid mesh. You may need to rotate the model a
little to view the tags.
Right click Show faces to clear the face review.
Review Creates special review FILM loads in HyperMesh graphics for the selected
set. Right click Review to clear the special review loads and highlighting.
Load Step: FILM: Delete Tab

The Delete tab allows you to delete FILM and other loads from HyperMesh. There are three deletion
options:
collector.
All 'Distributed loads' in The Delete button deletes all distributed (*DLOAD, *FILM) loads
current collector from the current load collector.

Load Step: FILM: Parameter Tab
The Parameter tab allows you to define optional parameters for the *FILM card.
See the Abaqus Online Documentation for a detailed description of these parameters. Click Update to
Load Step: DSLOAD

The DSLOAD dialog allows you to define the *DSLOAD card on Abaqus surfaces (*SURFACE). To open
the dialog in the Load Step window, select DSLOAD from the tree and a load collector from the Load
collector table.
Define
Delete
Parameter
You can use Abaqus Contact Manager to create Abaqus surfaces.
Load Step: DSLOAD: Define Tab

The Define tab allows you to define *DSLOAD card on Abaqus surfaces (*SURFACE). There are two
types of DSLOAD available: default (Pressure) and hydro pressure.
It is recommended that you use only one type of DSLOAD per load collector in HyperMesh. If you need to
use multiple types of DSLOAD in the same STEP, define each type in a separate load collector and add

them to the same load step.
Note: There is no graphical display in HyperMesh for loads created on Abaqus SURFACEs. Therefore,
when you review a load collector in the Step Manager, only loads created on individual entities are
highlighted. For loads defined on SURFACE, the underlying SURFACE elements are highlighted.
This dialog also contains a table for data line input. The table changes depending on the DSLOAD type
selected.
The table columns for each DSLOAD type are listed below:
Default (Pressure) type:
Surface The name of the Abaqus surface. Surfaces are added and deleted in this
Label The labels of pressure load. The available labels are P, PNU, and VP.
hydro pressure type:
Surface The name of the Abaqus surface. Surfaces are added and deleted in this
Label The labels of the hydrostatic pressure. The available label is HP.

Press point Z-coordinate of the point at which the pressure is defined in three-dimensional
or axisymmetric cases; Y-coordinate of the point at which the pressure is
defined in two-dimensional cases.
The DSLOAD option has the following buttons:
Review Surface Reviews the selected surface by highlighting them in the HyperMesh graphics.
Right click on the Review button to clear the review selections.

Create/Edit Opens a message with information about surface definition in HyperMesh.
Surface..
Adds the selected surface from the pull down menu to the data line table on
the right.
Deletes the selected surface from the data line table.
Review Reviews the selected surface in the data line table. Right click on the Review
button to clear the highlighted selections.
Load Step: DSLOAD: Delete Tab

The Delete tab allows you to delete *DSLOAD and other loads from HyperMesh. There are three deletion
options:
All loads in current The Delete button deletes all the loads from the current load collector.
collector
All 'DSLOAD' in current The Delete button deletes only *DSLOAD loads from the current load
collector collector.
By selection The Pick Loads button opens the HyperMesh load selector panel. Pick
the loads you want to delete and click proceed.
Load Step: DSLOAD: Parameter Tab

The Parameter tab allows you to define optional parameters for the *DSLOAD card.

Amplitude, OP, Load Case, Cyclic Mode, and Region Type
Load Step: SFILM

The SFILM dialog allows you to define the *SFILM card on Abaqus surfaces (*SURFACE). To open the
dialog in the Load Step window, select SFILM from the tree and a load collector from the Load collector
table.
Define
Delete
Parameter
You can use Abaqus Contact Manager to create Abaqus surfaces.
Load Step: SFILM: Define Tab

The Define tab allows you to define *SFILM card on Abaqus surfaces (*SURFACE).
Note: There is no graphical display in HyperMesh for loads created on Abaqus SURFACEs. Therefore,
when you review a load collector in the Step Manager, only loads created on individual entities are
highlighted. For loads defined on SURFACE, the underlying SURFACE elements are highlighted.
This dialog contains a Surface menu containing a list of the existing Abaqus surfaces. It also has a table
for data line input. The table contains the following columns:

Surface The name of the surfaces. Surfaces are added and deleted in this column using
or , respectively.
Label The SFILM labels. The available labels are F and FNU.
Sink temp Reference sink temperature.
Film coef Reference film coefficient.
The SFIM option has the following buttons:
Review Surface Reviews the selected surface by highlighting them in the HyperMesh graphics.
Create/Edit Opens a message with information about surface definition in HyperMesh

Surface..
Adds the selected surface from the drop-down menu to the data line table on
the right.
Deletes the selected surface from the data line table.
Review Reviews the selected surface in the data line table. Right click on the Review
button to clear the highlighted selections.
Load Step: SFILM: Delete Tab

The Delete tab allows you to delete *SFILM and other loads from HyperMesh. There are three deletion
options:
All loads in current The Delete button deletes all the loads from the current load
All 'SFILM' in current The Delete button deletes only *SFILM loads from the current load
collector collector
By selection The Pick Loads button opens the HyperMesh load selector panel.
Pick the loads you want to delete and click proceed.

Load Step: SFILM: Parameter Tab

The Parameter tab allows you to define optional parameters for the *SFILM card.
Load Step: Temperature

The Temperature dialog allows you to define and edit the *TEMPERATURE card. To open the dialog in
the Load Step window, select Temperature from the tree and a load collector from the Load collector
table.
Define
Delete
Parameter
Load Step: Temperature: Define Tab

The Define tab allows you to define *TEMPERATURE cards on individual nodes or geometry (surfaces,
points, lines). You can also define the temperature on node sets
It is recommended that you do not use *TEMPERATURE and *BOUNDARY with dof 11 together in a load
collector in HyperMesh. If you need to use multiple types of temperature in the same STEP, define each
type in a separate load collector and add them to the same load step.
You can define *TEMPERATURE on nodes, geometry, or node sets. For Define Temperature on:, the
following options are available:

· Node sets
Define Temperature on: Nodes or geometry

The Define Temperature on: Nodes or geometry option allows you to define temperature on individual
nodes or geometry. Temperatures created on nodes have special graphical display in HyperMesh. Loads
created on geometric entities like surfaces, lines or points are automatically mapped to FEA mesh on
export. You can also map them using the Map Loads on Geometry button.
The Define tab for Define Temperature on: Nodes or geometry contains the following buttons:
Define from Opens the HyperMesh temperature panel to create/update temperature.

'temperatures'
panel To create a temperature on nodes, go to the create sub-panel, select nodes
using the switch, input a value, and click create.
To create a temperature on geometry, go to the create sub-panel, select
surfs, points, or lines using the switch, input a value, and click create.
Note:
· Loads created on geometric entities are automatically mapped to

FEA mesh on export. You can also map them using the Map Loads
on Geometry button.
· You can also update an existing temperature from the update

sub-panel.
· While you are in the temperature panel, press the h key to view
· When you are finished creating or updating temperature, click return

and the Step Manager will be updated with the new loads.
Map Loads on Opens the HyperMesh loads on geom panel to map loads on geometry to
geometry FEA mesh entities.
Click the Map loads button to map all geometric loads in the current load
collector to FEA entities.
Note:

· You can also pick other load collectors by clicking on the loadcols
button and map loads in all of them together.
· When you are finished, click return and the Step Manager will be
updated with the new loads.
Define Temperature on: Node sets

The Define Temperature on: Node sets option defines temperature on node sets. The node set names
are used in the *TEMPERATURE data lines instead of the individual nodes. Unlike Abaqus surfaces in
HyperMesh, you can combine node sets with individual node IDs in the same *TEMPERATURE card.
This dialog contains a node sets menu with a list of the existing node sets. It also contains a table for data
line input with the following columns:
Nset The name of the node sets. Node sets are added and deleted in this column
using or , respectively.
Temperature Reference temperature value.
Gradient1 Temperature gradient in the n2-direction for beams or temperature gradient

through the thickness for shells.
Gradient2 Temperature gradient in the n1-direction for beams.
The Define tab for Define Temperature on: Node sets has the following buttons:

Display/Review
from Panel
Adds the selected node set from the pull down menu to the data line table on
the right.
Deletes the selected node set from the data line table.
Review Reviews the selected node set in the data line table. Right click on the
Review button to clear the highlighted selections.
Load Step: Temperature: Delete Tab

The Delete tab allows you to delete boundaries and other loads from HyperMesh. There are three options
for deletion:
All loads in current The Delete button deletes all the loads from the current load
All 'Temperature' in The Delete button deletes only *TEMPERATURE loads from the
current collector current load collector.
By selection The Pick Loads button opens the HyperMesh load selector panel.
Pick the loads you want to delete and click proceed.

Load Step: Temperature: Parameter Tab
The Parameter tab allows you to define optional parameters for the *TEMPERATURE card.
Amplitude, OP, Bstep, Binc, Estep, Einc, Input, Result (File), and MidSide
Load Step: Inertia Relief

The Inertia relief dialog allows you to define and edit the *INERTIA RELIEF card. To open the dialog in
the Load Step window, select Inertia relief from the tree and a load collector from the Load collector
table.
The dialog contains two tabs:
Define
Parameter
Load Step: Inertia Relief: Define Tab

The Define tab allows you to define * INERTIA RELIEF cards.
Activate the Inertia relief check box to make the *INERTIA RELIEF load active for the current load
collector.
There are two data line options available:
Free direction Integer list of degrees of freedom identifying the free directions
Reference points Global X, Y, and Z-coordinates of the reference point.
Click Update to activate the data line selection in the HyperMesh database.

Load Step: Inertia Relief: Parameter Tab
The Parameter tab allows you to define optional parameters for the * INERTIA RELIEF card.
Orientation, Fixed, Remove, and None
Load Step: Interface Controls

The Interface Controls option defines the following Abaqus keywords: *CONTACT, *CONTACT CONTROLS,
*CLEARANCE, *CONTACT INTERFERENCE, *MODEL CHANGE, *CHANGE FRICTION, and CONTROLS.
It also allows you to add *CONTACT PAIR and *SURFACE INTERACTION cards created from the
Abaqus Contact Manager to a load step. When you select an interface controls option from the tree, the
corresponding table is displayed in the Load Step window.
The Interface controls: table contains a list of interface controls of the type selected in the tree. You can
create, edit, rename, reorder, and delete interface controls from this table.
The Interface controls table contains the following columns:
Status The history status of the interface control. If the status is on, the corresponding
interface control parameters and data lines will be exported in the current load step. If
the status is off, the interface control will not be exported under the current *STEP
block.
Name The name of the interface controls. Some of the interface controls names are for
HyperMesh internal use only. Abaqus input files do not require them.
Note:
· Right click on the table to display menu options. The available options are Rename and Reorder.
The Interface controls table contains the following buttons:
New Opens the Create dialog for the corresponding interface control. The name of the new
interface control is entered in this dialog. The Same as: option allows you to create an
interface control by copying attributes from an existing interface control of the same

type. The Create button creates an interface control and adds it to the current load
step.
Edit Opens the card image panel for the selected interface control. Click edit to open the
card editor and define all relevant keywords, parameters, and data lines. When you are
finished, click return twice and the Step Manager is updated.
Delete Opens the HyperMesh delete panel to delete interface controls. When you are
finished, click return and the Interface controls table will be updated.
Load Step: Output Request

In HyperMesh, Abaqus output requests are organized into HyperMesh collectors called output blocks. The
Output requests option in the tree allows you to define output options for ODB, result (.fil) and data (
.dat) file formats. When you select an output request file format from the tree, the output block table is
displayed in the Load Step window.
The Output block: table contains a list of the output blocks with corresponding history status. You can
create, edit, review, rename, reorder, and delete output blocks from this table.
The Ouput block: table contains the following columns:
Status The history status of the output block. If the status is on, the output block belongs to
the current load step. This means, all parameter and data line information in the
output block will be written under the current *STEP block. If the status is off, no
parameters or data lines from the output block will be written under the current
*STEP block.
Name The name of the output block. These names are for HyperMesh internal use only.
Note:
· Click on an output block name to set it as the current output block in HyperMesh. All changes and
additions to the parameters and data line will be for the selected output block.
· The Ouput type: status bar (below the output block table) shows all the output types present in the
selected output block.
· Right-click on the table to display menu options. The available options are Rename and Reorder.
The Output block table contains the following buttons:

New.. Opens the Create Output block dialog in which you enter the name of the new
output block. The Create button in this dialog creates the output block and adds it to
the current load step.
Review Reviews the selected output block in a text window. All parameters and data lines
associated with the selected output block are listed in the text window.
Delete Opens the HyperMesh delete panel to delete output blocks. When you are finished,
click return and the Output block table will be updated.
Load Step: Output request: ODB File

The ODB file dialog allows you to define and edit the output requests for the ODB file. Supported
keywords are: *OUTPUT, *NODE OUTPUT, *ELEMENT OUTPUT, *CONTACT OUTPUT, and *ENERGY
OUTPUT. To open the dialog in the Load Step window, select ODB file from the tree and an output block
from the Output block table.
The dialog contains five tabs:
Output
Node Output
Element Output
Contact Output
Energy Output
Load Step: Output request: ODB File: Output

The Output tab allows you to define *OUTPUT cards with associated parameters. Supported parameters
are:
Field, History, OP, Variable, Frequency, Time marks, Number interval, Time interval, and Mode list
activate the parameters defined in the HyperMesh database.

To enable the Node Output, Element Output, Contact Output, and Energy Output tabs used to define
the *NODE OUTPUT, *ELEMENT OUTPUT, *CONTACT OUTPUT and *ENERGY OUTPUT cards, you
must first activate the corresponding check boxes.
Load Step: Output request: ODB File: Node Output

The Node Output tab allows you to define *NODE OUTPUT for the selected Output block. Nset and
Variable parameters are supported. Activate/deactivate the check boxes in the tree on the Node Output
tab to add/remove identifier keys in the table. The data lines added in this manner have a gray background
indicating they cannot be manually edited. You may also add user-defined identifiers, by typing them
directly into the table. User-defined data lines appear with a white background, indicating they are editable.
Right click on the data line table to display menu options. The available options are Cut, Copy, Paste, Add
row, and Delete row.
The following buttons are available on the Node Output tab:
Create/Edit… Opens the entity sets panel in HyperMesh. When you finish creating/editing the
set, click return. The Step Manager is updated with the new set appearing in the
node set list.
Review Reviews the selected node sets by highlighting them in the HyperMesh graphics.
Update Updates the HyperMesh database with the data lines defined in the table and the
parameters.
Load Step: Output request: ODB File: Element Output

The Element Output tab allows you to define *ELEMENT OUTPUT for the selected Output block. The
following parameters are supported: Elset, Position, and Variable. Activate/deactivate the check boxes in
the tree on the Element Output tab to add/remove identifier keys in the table. Data lines added in this
manner have a gray background indicating they cannot be manually edited. You may also add
user-defined identifiers, by typing them directly into the table. The user-defined data lines appear with a
white background, indicating they are editable.
Right click on the data line table to display menu options. The available options are Cut, Copy, Paste,

Add row, and Delete row.
The Element Output tab has the following buttons:
element set list.
Review Reviews the selected element sets by highlighting them in the HyperMesh
parameters.
Load Step: Output request: ODB File: Contact Output

The Contact Output tab allows you to define *CONTACT OUTPUT for the selected Output block. The
following parameters are supported: Nlset, Master, Slave, General Contact, and Variable.
Activate/deactivate the check boxes in the tree on the Contact Output tab to add/remove identifier keys in
the table. The data lines added in this manner have a gray background, indicating they cannot be manually
edited. You may also add user-defined identifiers, by typing them directly into the table. The user-defined
data lines appear with a white background, indicating they are editable.
The Contact Output tab has the following buttons:
Create/Edit… Opens the entity sets panel in HyperMesh. When you finish creating/editing
the set, click return. The Step Manager is updated with the new set appearing
in the node set list.
Review Reviews the selected node sets, master surface, or slave surface by highlighting
them in the HyperMesh graphics. Right click on the Review button to clear the
review selections.

Update Updates the HyperMesh database with the data lines defined in the table and
the parameters.
Load Step: Output request: ODB File: Energy Output

The Energy Output tab allows you to define *ENERGY OUTPUT for the selected Output block. The
following parameters are supported: Elset and Variable. Activate/deactivate the check boxes in the tree on
the Energy Output tab to add/remove identifier keys in the table. The data lines added in this manner
have a gray background, indicating they cannot be manually edited. You may also add user-defined
identifiers by typing them directly into the table. The user-defined data lines appear with a white
background, indicating they are editable.
Right click on the Data line table to display menu options. The available options are Cut, Copy, Paste,
The Energy Output tab has the following buttons:
element set list.
parameters.
Load Step: Output request: Result File(.fil)

The Result file (.fil) dialog allows you to define and edit the output requests for the Result file. Supported
keywords are *NODE FILE, *ELEMENT FILE, *CONTACT FILE, and *ENERGY FILE. To open the dialog
in the Load Step window, select Result File (.fil) from the tree and an output block from the Output block
table.
Define
Node File

Element File
Contact File
Energy File
Load Step: Output request: Result File: Define

The Define tab allows you to enable the Node File, Element File, Contact File, and Energy File tabs,
which are used to define the *NODE FILE, *ELEMENT FILE, *CONTACT FILE, and *ENERGY FILE cards,
respectively.
Load Step: Output request: Result File: Node File

The Node File tab allows you to define *NODE FILE for the selected Output block. The following
parameters are supported: Nset, Frequency, Last mode, Global, and Mode. Activate/deactivate the check
boxes in the tree on the Node File tab to add/remove identifier keys in the table. The data lines added in
this manner have a gray background, indicating they cannot be manually edited. You may also add
user-defined identifiers by typing them directly into the table. User-defined data lines appear with a white
background, indicating they are editable.
The Node File tab contains the following buttons:
node set list.
parameters.

Load Step: Output request: Result File: Element File
The Element File tab allows you to define *ELEMENT FILE for the selected Output block. The following
parameters are supported: Elset, Directions, Mode, Frequency, Position, and Last Mode.
Activate/deactivate the check boxes in the tree on the Element File tab to add/remove identifier keys in the
table. The data lines added in this manner have a gray background, indicating they cannot be manually
edited. You may also add user-defined identifiers by typing them directly into the table. User-defined data
lines appear with a white background, indicating they are editable.
The Element File tab contains the following buttons:
element set list.
parameters.
Load Step: Output request: Result File: Contact File

The Contact File tab allows you to define *CONTACT FILE for the selected Output block. The following
parameters are supported: Nset, Master, Slave, and Frequency. Activate/deactivate the check boxes in
the tree on the Contact File tab to add/remove identifier keys in the table. The data lines added in this
manner have a gray background, indicating they cannot be manually edited. You may also add
user-defined identifiers, by typing them directly into the table. The user-defined data lines appear with a

The Contact File tab contains the following buttons:
Create/Edit… Opens the entity sets panel in HyperMesh. When you finish creating/editing
the set, click return. The Step Manager is updated with the new set appearing
in the node set list.
review selections.
Update Updates the HyperMesh database with the data lines defined in the table and
the parameters.
Load Step: Output request: Result File: Energy File

The Energy File tab allows you to define *ENERGY FILE for the selected Output block. The following
parameters are supported: Elset and Frequency.
The Energy File tab contains the following buttons:
element set list.
parameters.
Load Step: Output request: Data File(.dat)

The Data file (.dat) dialog allows you to define and edit the output requests for the data file. Supported
keywords are *NODE PRINT, *ELEMENT PRINT, *CONTACT PRINT, and *ENERGY PRINT. To open the
dialog in the Load Step window, select Data File (.dat) from the tree and an output block from the Output
block table.

Define
Node Print
Element Print
Contact Print
Energy Print
Load Step: Output request: Data File: Define

The Define tab allows you to enable the Node Print, Element Print, Contact Print, and Energy Print
tabs, which are used to define the *NODE PRINT, *ELEMENT PRINT, *CONTACT PRINT, and *ENERGY
PRINT cards.
Load Step: Output request: Data File: Node Print

The Node Print tab allows you to define *NODE PRINT for the selected Output block. The following
parameters are supported: Nset, Frequency, Mode, Global, Summary, Last mode, and Totals.
Activate/deactivate the check boxes in the tree on the Node Print tab to add/remove identifier keys in the
table. The data lines added in this manner have a gray background, indicating they cannot be manually
The following buttons are available on the Node Print tab:
node set list.

parameters.
Load Step: Output request: Data File: Element Print

The Element Print tab allows you to define *ELEMENT PRINT for the selected Output block. The following
parameters are supported: Elset, Position, Totals, Frequency, Last mode, Summary, and Mode.
Activate/deactivate the check boxes in the tree on the Element Print tab to add/remove identifier keys in
the table. The data lines added in this manner have a gray background indicating they can not be manually
The following buttons are available on the Element Print tab:
element set list.
parameters.
Load Step: Output request: Data File: Contact Print

The Contact Print tab allows you to define *CONTACT PRINT for the selected Output block. The following
parameters are supported: Nset, Master, Slave, Frequency, Totals, and Summary. Activate/deactivate the
check boxes in the tree on the Contact Print tab to add/remove identifier keys in the table. The data lines
added in this manner have a gray background, indicating they cannot be manually edited. You may also
add user-defined identifiers by typing them directly into the table. User-defined data lines appear with a
Right click on the data line table to display menu options. The available options are Cut, Copy, Paste, Add
row, and Delete row.

The following buttons are available on the Contact File tab:
node set list.
review selections.
parameters.
Load Step: Output request: Data File: Energy Print

The Energy Print tab allows you to define *ENERGY PRINT for the selected Output block. The following
parameters are supported: Elset and Frequency.
The following buttons are available on the Energy File tab:
element set list.
parameters.

Load Step: Monitor
The Monitor option in the tree allows you to define the *MONITOR card.
The supported attributes are: Node, DOF, and Frequency.
See the Abaqus online documentation for a detailed description of these attributes. Click Update to
activate the monitor attributes defined in the HyperMesh database.
The following buttons are available on the Monitor dialog:
Pick node Opens the node section panel in HyperMesh. When you finish picking a node
from the model, click return. The Step Manager is updated with the selected
node number appearing in the Node entry.
parameters.
Load Step: Print

The Print option in the tree allows you to define the *PRINT card.
The supported attributes are: Contact, Model change, Plasticity, Residual, Solve, Frequency, Allke, Critical
element, Dmass, and Etotal.
Load Step: File format

The File format option in the tree allows you to define the *FILE FORMAT card. This option is available
when a standard Abaqus template is loaded.

The supported attributes are: File format and Zero increment.
Load Step: File output

The File output option in the tree allows you to define the *FILE OUTPUT card. This option is available
when the Abaqus explicit template is loaded.
The supported attributes are: File output, Number interval, and Time marks.
Load Step: Restart write

The Restart write option in the tree allows you to define the *RESTART, WRITE card.
The supported attributes are: Overlay, Frequency, Number interval, and Time marks.
Load Step: Unsupported cards

The Unsupported cards option in the tree enables you to review and edit unsupported history data within
the Step Manager.
Select the check box to activate the text area. You can enter the unsupported cards by typing directly or
copying and pasting into the text area. Then click Update to include the cards.

ABAQUS Step Manager Load Case Tab
The Load Case tab contains the descriptions of all existing load cases with the corresponding load
collectors. You can create, edit, review, rename, reorder, and delete load cases from this tab as well as set
the display status of the load steps.
The Load Case tab contains the following buttons:
New... Opens the Create New Load Case dialog. Enter the name of the new load case in
the Name: text box and click Create to create the load step and open the
corresponding Load Case editing dialog.
Edit... Opens the Load Step Editing dialog for the selected load step.
Review Reviews the selected load collectors. All loads in the load collectors are highlighted
in the HyperMesh graphics. The highlighted loads show through the solid mesh in
performance graphics. If a load is defined with set, the underlying nodes or
elements are highlighted. Right click Review to clear the highlighted selections.
Text Reviews the selected load step in a text window.
Rename Opens the HyperMesh rename panel for renaming load steps, load collectors, output
blocks, or various interface controls. When you finish renaming, click return to
update the Step Manager with the new names.
Delete Deletes the selected load steps.
Sync Updates the Step Manager with the current HyperMesh database. If you manually
create, update, or delete load steps, load collectors, output blocks, groups, or entity
sets from HyperMesh panels while the Step Manager is open, click Sync to update
the Step Manager with the new changes.
Close Closes the Step Manager.
Moves the selected load cases up one row.
Moves the selected load cases down one row.


Results Translation
hmabaqus translates a binary or ASCII Abaqus (.fil) results file into a HyperMesh binary results file. The
syntax to run the translator is:
hmabaqus [options] <inputfile> <outputfile> <modelfile>
To run hmabaqus from Hypermesh:

1. On the Analysis page, select the solver panel.
2. Click the translator toggle and select hmabaqus.
3. For input file:, click browse... and select the .fil file.
4. Click Open.
5. For output file:, click browse... and write down the output file name.
6. Click Save.
7. Enter the options. To create an h3d file for a specific result, add –h3d after the options.
8. Click solve.
One or more of the following options can be used. Use the command hmabaqus-u to obtain a list of these
options.
Flag Meaning
-d Displacements
-rot Rotations
-v Velocities
-a Accelerations
-nflux NFLUX
-nflxrot nflux rotations
-von von Mises
-tr Tresca
-hydropr Hydrostatic Pressure
-tsi Third Stress Invariant
-pstrs Principal Stresses
-shstrs Shear Stresses
-sed Strain Energy Density

-temp Temperature
-sinktemp Sink Temperature
-filmcoef Film Coefficient
-ecursmag ECURS magnitude
-ncursmag NCURS magnitude
-recurmag RECUR magnitude
-ecdmag ECD magnitude
-ecd1 ECD1
-ecd2 ECD2
-ecd3 ECD3
-resflux Residual Flux
-conflux Concentrated flux
-intflux Internal Flux
-fluxs FLUXS
-nodetemp Nodal Temperatures
-ts Total Strains
-ls Logarithmic Strains
-ns Nominal Strains
-ps Plastic Strains
-es Elastic Strains
-cs Creep Strains
-ths Thermal Strains
-pstrn Principal Strains
-pnomsn Principal Nominal Strains
-plogsn Principal Logarithmic Strains
-pps Principal Plastic Strains
-pes Principal Elastic Strains
-pths Principal Thermal Strains

-stress Stresses
-rmsstrs RMS Stresses
-rmsstrn RMS Strains
-rf Reaction Forces
-rm Reaction Moments
-pl Point Loads
-thick Shell Thickness
-sinv Maximums (default off)
-s1 First Surface (default off)
-s2 Second Surface (default off)
-cr Contact Results
-epot Electrical Potential
-por Pore or Acoustic Pressure (default off)
-ps1v Principal Stress 1 (Vector)
-sh1v Shear Stress 1 (Vector)
-sh2v Shear Stress 2 (Vector)
-sv1 State Variable 1 (default off)
-svn State Variable n (default off)
-notrans Do not convert local displacements into global (default off)
-pc56 Read results for v5.6 on PC (default off)
-maxsim Max simulations (default 999) (default off)
-step For specific STEP results (default off)
-inc For specific ITERATION results (default off)
-freq For specific frequency of ITERATION results (default off)

-disk Translation is performed on disk
-size Number of entities (10000 default)
-file Scratch file name
-h3d Outputs file to an H3D file instead of to an hmresults file. The file
includes model and results information that was translated. The
model must contain geometry for it to be output to an H3D file.
(default off)
-noip Turns off all processing of element integration point values. If you ask
Abaqus to average values to element centroids, this option makes a
considerable difference in the amount of memory needed. If you also
specify a result type that is found on element integration points, and
the translator comes across such a result during processing, it reports
an error. (default off)
-sv1, State variables were being treated differently for some element
-sv2,..., groups from others. For some element types, they were always
-sv20
included, and, for others, they were processed only if specifically
listed, with the default listing all of them. Now, all are uniform. They
are translated only if you requests them to be translated. Also, the
translator used to allocate memory to process all 20 allowable state
variables whether you asked for any or not. Now, you can turn them
on individually, and use just the minimum memory necessary, or you
can turn on the first N of them using -nsdv. (default off)
-nsdv <number> Turns on the first <number> state variables (max of 20). If you list
both individual state variables and also the -nsdv option, the listed
ones are the only ones processed. You can get complete
compatibility with older versions by using "-nsdv 20". (default off)
Note: hmabaqus supports results for a range of increments and steps. It also supports results with a
specific frequency.
For example,
· "hmabaqus -inc 10 12 14 40 55" gives results for increments 10 12 14 40 55 for all steps.
· "hmabaqus -step 1 5 6 19" gives results for all increments in steps 1, 5, 6 and 19.
· "hmabaqus -step 1 5 6 19 -inc 10 15 26 31 55" gives results for increments 10, 15, 26, 31, 55
in steps 1, 5, 6 and 19.
· "hmabaqus -step 1 5 6 19 -freq 2" give results for 1st, 3rd, 5th, 7th, 9th .... last increments in
steps 1, 5, 6 and 19.
In addition, the following parameters are also available when the results translation is not performed on the
analysis platform and when the results file is binary. One of these parameters may need to be specified to
indicate the platform where the analysis result file was created.
Parameter Analysis File Created On
-cray Cray

-dec Dec 5000
-decalpha Dec Alpha
-hp Hewlett Packard.
-ibm IBM RS\6000
-pc PC
-sgi SGI
-sun Sun.

Translating Complex Results
Hmabaqus supports real and imaginary results for *STEADY STATE DYNAMICS analysis. If the results
are in the form of real and imaginary numbers, hmabaqus calculates the corresponding magnitude and
phase. If the magnitude and phases are available from the .fil file, hmabaqus calculates the corresponding
real and imaginary values.
All complex data type names will have (c) postfix. In addition, data types without the (c) will contain the
magnitude of the result.
HyperMesh always uses magnitude and phase values to contour plot the complex results.
Each result would be obtained using the following equation:
You can choose the value of when viewing the result by specifying the angle on the contour or
deformed panel on the Post page.
When you plot the contour for a complex data type and click on a node/element, both real/imaginary and
magnitude/phase pairs are shown.

Translating Element Results for Different Positions
There are four options for the POSITION parameter in the *EL FILE keyword in Abaqus. They are
CENTROIDAL, AVERAGED AT NODES, INTEGRATION POINTS (default), and NODES. However, in
HyperMesh there are only two ways results can be presented: (a) unique value at the center of each
element and (b) unique value at each node. Therefore, Hmabaqus must manipulate results from the .fil
file to some extent to fit the HyperMesh architecture as follows:
1. For POSITION = CENTROIDAL
Hmabaqus reads these values directly and assigns them to the center of each element. An assign
plot reflects exactly what is given in the .fil file. A contour plot contributes the same value to each
of the element's nodes and for each node, values coming in from all adjacent elements are averaged
to create the smooth contour image.
2. For POSITION = AVERAGED AT NODES
Hmabaqus reads these values directly and assigns them to each node. A contour plot shows the
exact values that were read from the .fil file at nodes. For boundaries between components with
material or thickness difference, there may be multiple values for a node in the .fil file. In this case,
HyperMesh considers the last value for each node. As a result, you may see a blending of color at
nodes along these boundaries. An assign plot averages the result coming from nodes of an element
and assigns them to the centroid of the element.
3. For POSITION = INTEGRATION POINTS
This is the default option in Abaqus. Hmabaqus averages the values from each integration point to the
centroid of an element. For example, for an element with four integration points, Hmabaqus reads the
values at each integration point, adds them, and then divides them by 4. This usually gives an answer
very close to POSITION = CENTROIDAL. An assign plot reflects these averaged values at elements.
A contour plot contributes the same value to each of the element's nodes and for each node, values
coming in from all adjacent elements are averaged to create the smooth contour image.
4. For POSITION = NODES
Hmabaqus does not currently support this option.

Supported Result Types
The following records in the Abaqus .fil results file are supported:
Abaqus/Standard Record Keys Abaqus/Standard Output Request

Identifier
1 Element Header <none>
2 Temperature TEMP
4 Distributed Flux FLUX5
5 Solution-dependent state variables SDV
10 Nodal Flux NFLUX
11 Stresses S
12 Stress Invariants SINV
14 Energy Densities ENER
21 Total Strain E
22 Plastic Strains PE
23 Creep Strains CE
25 Elastic Strains EE
27 Shell Thickness STH
33 Film Coefficients FILM
48 Transverse shear stresses TSHR
62 Magnitude and phase angle of stress PHS

components
63 RMS values of stress RS
65 Magnitude and phase angle of strain PHE

components
66 RMS values of strain RE
88 Thermal Strains THE

Identifier
89 Logarithmic Strains LE
90 Nominal Strains NE
101 Displacements U
102 Velocities V
103 Accelerations A
104 Reaction Forces RF
105 Electrical Potential EPOT
106 Point, Loads, Moments, Fluxes CF
108 Pore or Acoustic Pressure POR
111 Magnitude and phase angle of PU

displacement
138 Electrical Reaction Current RECUR
201 Nodal Temperatures NT
204 Residual Flux RFL
206 Concentrated Flux CFL
214 Internal Flux RFLE
401 Principal Stresses SP
403 Principal Strains EP
404 Principal Nominal Strains NEP
405 Principal Logarithmic Strains LEP
408 Principal Elastic Strains EEP
410 Principal Thermal Strains THEP
411 Principal Plastic Strains PEP
425 Electrical Current Density ECD
426 Distributed Electrical Current Density ECURS

Identifier
427 Nodal Current NCURS
1503 Output Request Definition <none>
1504 Node Header <none>
1511 Contact Tractions CSTRESS (CPRESS, CSHEAR)
1521 Contact Clearances CDISP (COPEN, CSLIP)
1900 Element Definitions <none>
1901 Nodal Definitions <none>
1902 Active Degrees of Freedom <none>
1921 Abaqus Version <none>
1980 Modal Results <none>
2000 Increment Start Record <none>
2001 Increment End Record <none>
Abaqus/Explicit Record Keys Abaqus/Explicit Output Request Identifier
1 Element Header <none>
2 Temperature TEMP
5 Solution-dependent state variables SDV
11 Stresses S
14 Energy Densities ENER
21 Infinitesimal Strains E
22 Plastic Strains PE
27 Shell Thickness STH
48 Transverse Shear Stresses TSHR
73 Equivalent Plastic Strain PEEQ

Identifier
75 Mises equivalent stress MISES
89 Logarithmic Strains LE
90 Nominal Strains NE
101 Displacements U
102 Velocities V
103 Accelerations A
104 Reaction Forces RF
201 Nodal Temperatures NT
204 Reaction Flux RFL
401 Principal Stresses SP
403 Principal Infinitesimal Strains EP
404 Principal Nominal Strains NEP
405 Principal Logarithmic Strains LEP
1900 Element Definitions <none>
1901 Nodal Definitions <none>
1902 Active Degrees of Freedom <none>
1921 Abaqus Version <none>
2000 Increment Start Record <none>
2001 Increment End Record <none>

Include File Support
Many FEA solvers allow you to organize your input deck into separate files and provide a mechanism to
include all the files in a single input deck. This capability is commonly known as "include" capability.
HyperMesh allows you to import such models for Abaqus.
HyperMesh’s include browser allows you to create, review, edit, organize, and update the contents of a
model into various include files.
The following rules and considerations apply to the Abaqus include file support in HyperMesh:
· Include files must include complete information for each keyword. A keyword and its data lines
must be part of the same file.
· Include files must contain complete information for cards that contain multiple sub-keywords. For
example, all sub-keywords and their data lines in a *Material card must be part of the same
include file.
· Include files must contain complete information for *Step cards. All history keywords and their
data lines must be a part of the same file.
· The HyperMesh Abaqus interface is comprised of four types of include files: Model (start), Model
(middle), Model, and History. They define the sequence of the *Include keywords in the
model. Model (start) type of include files are written at the beginning of the deck, after the *Node
block. Model (middle) is written in the middle of the deck, after the *Material block. Model is
written at the end of the model definition, and History keywords are written after the model
definition.
· Include file names are sorted according to their names in the browser. The sequence in the
exported model is primarily determined by the four types of includes files as described above.
Within each type the sequence is determined by the order in which they are created.
· The Abaqus syntax for the include file path is:

In Abaqus, file names can include a full or relative path name. Relative path names must be in
relation to the directory from which the job was started. If a path is not specified, it is assumed that
the file is located in the same directory from which the job was submitted.
From HyperMesh, it is, however, not always possible to predict the directory from which the job will
finally be submitted. Therefore a relative path must be defined. This relative path should be defined
with respect to the folder where the corresponding *Include keyword appears. If you run the job
from a different folder in subsequent runs, you must also update the path name.

Free Body Diagram
· Results are supported through the .odb output file.
· The installation of the HyperView Abaqus ODB API is required to support Abaqus FBD results in
HyperMesh.
· Grid Point Forces (GPF) results are requested with the following .odb file output requests:
*NODE OUTPUT
RF
CF
*ELEMENT OUTPUT
NFORC
· Displacement results are requested with the following .odb file output request:
*NODE OUTPUT
U
· It is recommended practice to output data for only the node/element set(s) of interest. This
procedure reduces the size of the solver results file and helps speed up the FBD extractions.
· Abaqus rigid elements, *Rigid bodies, *Coupling constraints, *MPC, *Fastener and *Equations do
not export forces and moments. If any of these are attached to the element set of interest, all
elements attached to them must be included in the element set to insure the GPF balance is
correct. If they are not included, an imbalance will occur. Refer to the Abaqus documentation to
determine these elements/bodies. Make sure to check the validity of all GPF results when any of
these are present in the model.
· The FBD Export Manager is currently not supported for Abaqus.

Supported Keywords
To create Abaqus cards in HyperMesh, load the Abaqus user profile and select the appropriate template (
Standard.2d, Standard.3d, or Explicit).
The supported Abaqus cards:
*AMPLITUDE
*BEAM ADDED INERTIA

*BEAM GENERAL SECTION
*BEAM SECTION
*BIAXIAL TEST DATA

*BLOCKAGE
*BOUNDARY
*BUCKLE
*BULK VISCOSITY
*CECHARGE
*CECURRENT
*CFILM
*CFLUX
*CHANGE FRICTION
*CLEARANCE
*CLOAD
*COHESIVE SECTION
*COMBINED TEST DATA

*CONDUCTIVITY
*CONNECTOR BEHAVIOR
*CONNECTOR CONSTITUTIVE REFERENCE
*CONNECTOR CONTACT FORCE
*CONNECTOR DAMPING
*CONNECTOR ELASTICITY
*CONNECTOR FAILURE
*CONNECTOR FRICTION
*CONNECTOR LOAD

*CONNECTOR LOCK
*CONNECTOR MOTION
*CONNECTOR SECTION
*CONNECTOR STOP
*CONSTRAINT CONTROLS
*CONTACT (General Contact)
*CONTACT CLEARANCE
*CONTACT CLEARANCE ASSIGNMENT
*CONTACT CONTROLS
*CONTACT CONTROLS ASSIGNMENT

*CONTACT DAMPING (Explicit template)
*CONTACT DAMPING (Standard templates)
*CONTACT EXCLUSIONS
*CONTACT FILE
*CONTACT FORMULATION
*CONTACT INCLUSIONS
*CONTACT INTERFERENCE
*CONTACT OUTPUT
*CONTACT PAIR
*CONTACT PRINT
*CONTACT PROPERTY ASSIGNMENT

*CONTROLS
*COUPLING
*CREEP
*CRUSHABLE FOAM
*CRUSHABLE FOAM HARDENING
*DAMPING
*DASHPOT
*DECHARGE
*DECURRENT
*DENSITY

*DEPVAR
*DFLUX
*DIAGNOSTICS
*DIELECTRIC
*DISTRIBUTING
*DISTRIBUTION
*DISTRIBUTING COUPLING
*DLOAD
*DSLOAD
*DYNAMIC
*DYNAMIC (Explicit)
*EL FILE
*EL PRINT
*ELASTIC
*ELEMENT
*ELEMENT OUTPUT
*ELEMENT PROPERTIES
*ELSET
*EMBEDDED ELEMENT
*ENERGY FILE
*ENERGY OUTPUT
*ENERGY PRINT
*EQUATION
*EXPANSION
*FASTENER (SPOT WELD)

*FASTENER PROPERTY
*FLUID BEHAVIOR
*FLUID BULK
*FLUID DENSITY
*FLUID EXPANSION
*FLUID PROPERTY

*FILE FORMAT
*FILM
*FILTER
*FIXED MASS SCALING
*FREQUENCY
*FRICTION (Explicit template)
*FRICTION (Standard templates)
*GAP
*GASKET BEHAVIOR
*GASKET CONTACT AREA

*GASKET ELASTICITY
*GASKET SECTION
*GASKET THICKNESS BEHAVIOR

*HEADING
*HEAT TRANSFER
*HYPERELASTIC
*HYPERFOAM
*INCREMENTATION OUTPUT
*INERTIA RELIEF
*INITIAL CONDITIONS (TYPE=TEMPERATURE)
*INITIAL CONDITIONS (TYPE=VELOCITY)

*INTEGRATED OUTPUT
*INTEGRATED OUTPUT SECTION

*JOINT
*KINEMATIC
*KINEMATIC COUPLING
*LOAD CASE
*MASS
*MATERIAL
*MEMBRANE SECTION
*MODAL DYNAMIC

*MODAL OUTPUT
*MODEL CHANGE
*MONITOR
*MPC
*MULLINS EFFECT
*NODAL THICKNESS
*NODE
*NODE FILE
*NODE OUTPUT
*NODE PRINT
*NONSTRUCTURAL MASS
*NSET
*ORIENTATION
*OUTPUT
*PHYSICAL CONSTANT
*PIEZOELECTRIC
*PLANAR TEST DATA

*PLASTIC
*PREPRINT
*PRE-TENSION SECTION
*PRINT
*RADIATE
*RATE DEPENDENT
*RELEASE
*RESTART
*RESTART
*RIGID BODY
*ROTARY INERTIA
*SECTION CONTROLS
*SFILM
*SHEAR FAILURE

*SHEAR TEST DATA
*SHELL GENERAL SECTION
*SHELL SECTION
*SHELL TO SOLID COUPLING
*SIMPLE SHEAR TEST DATA

*SOLID SECTION
*SPECIFIC HEAT
*SPRING
*STATIC
*STEP
*SURFACE
*SURFACE BEHAVIOR (Explicit template)
*SURFACE BEHAVIOR (Standard templates)

*SURFACE INTERACTION (Explicit template)
*SURFACE INTERACTION (Standard templates)
*SURFACE PROPERTY ASSIGNMENT (Explicit template)
*SURFACE SECTION
*SYSTEM
*TEMPERATURE
*TIE
*TRANSFORM
*TRANSVERSE SHEAR STIFFNESS
*UNIAXIAL TEST DATA

*USER MATERIAL
*USER OUTPUT VARIABLES

*VARIABLE MASS SCALING
*VISCO
*VISCOELASTIC
*VOLUMETRIC TEST DATA

Unsupported Data Blocks
The HyperMesh Abaqus interface can handle several types of unsupported cards.
· Unsupported materials
· Unsupported cards (model part)
· Unsupported step data (history part)
Unsupported material
Unsupported materials can be handled in two ways in HyperMesh.
· HyperMesh can automatically detect materials that contain certain cards that are currently
unsupported. Once detected, those cards are preserved as simple text within the material card. On
export, they will be written within the original material block and labeled with the comment
**HM_UNSUPPORTED_MATERIAL
· HyperMesh can declare entire materials as unsupported. To handle unsupported materials by this
method:
- Insert the comment **HM_GENERIC_MATERIAL before each *MATERIAL card that contains
unsupported keywords. Only materials with the comment will be imported as plain text.
or
- Select the Generic material check box on the options panel of the Utility menu. All material
cards will be set as unsupported.
If a supported material card has a parameter that is currently unsupported, the card will be imported but the
parameter will be ignored. You will receive a warning message during the import process.
Contents of unsupportd or generic materials can be reviewed or edited with the card editor in the Model
Browser.
Unsupported cards (model data)

In addition to the unsupported material card and the generic material there are three places where currently
unsupported keywords can be stored. All concerned cards placed before the first *NODE card will go to the
UNSUPPORTED_CARDS_START, those between *NODE and last *MATERIAL block are placed in
UNSUPPORTED_CARDS_MIDDLE card and all other unsupported cards of the model part can be found
in UNSUPPORTED_CARDS after import. Once unsupported cards are detected you will receive a warning
message during import.
The cards and their contents can be reviewed in the control cards area or in the Model Browser.
On export, HyperMesh inserts a comment before each type of unsupported card:
· **HM_UNSUPPORTED_CARDS_START
· **HM_UNSUPPORTED_CARDS_MIDDLE
· **HM_UNSUPPORTED_CARDS

The start of unsupported cards will be placed before the first node card, the middle part behind the last
*MATERIAL card and the last part will be placed directly before the Step definition.
However, there is one special case for unsupported model data cards. Abaqus provides several type
options for the *INITIAL CONDITIONS card. Currently, HyperMesh supports the VELOCITY,
TEMPERATURE, and FLUID PRESSURE types. For these cards, a load collector will be created on
import. However, in cases where the type parameter value is not one of these supported values, this card
will be handled as an unsupported card according to the rules described above.
Unsupported step data (history data)

If HyperMesh detects unknown keywords within a *STEP definition, they will be placed in the unsupported
cards section within the step. There is an unsupported card available in every *STEP. New unsupported
cards can also be added and exported by the Step Manager.

Abaqus to/from Nastran Mapping
The Nastran to/from Abaqus tool uses an open conversion scheme; you can specify different mappings in
the configuration file. Care has to be taken so that the element and property mappings are consistent. We
provided a valid mapping scheme in the ConfigurationFile.txt. This document explains the scope and
limitations of the mapping scheme.
Elements
HyperMesh elements have two basic attributes – configuration (or config) and type. The "config" defines
the basic geometrical shape of an element. For example, tria3 configuration is a 3 node triangular element
and hexa8 is an 8-node hexahedral element. The "type" in HyperMesh defines the solver specific element
type of a particular configuration. For example, the 4-node quadrilateral (quad4) element in Abaqus can be
any of the following types: S4, S4R, M3D4, R3D4 etc. The element types panel shows all supported
element configurations in HyperMesh and their types for a user profile.
For a specific configuration, you can map any supported Nastran element type to any supported Abaqus
element type, or vice versa. For example, for a Nastran to Abaqus direction, HyperMesh supports several
2-noded element configurations such as spring, rigid, bar2, rid, etc. Because all of them are 2-noded
elements, conversion across these configurations is also allowed for some element types. For example,
CBUSH is of "spring" configuration in the Nastran user profile and CONN3D2 is of ‘rod" configuration in
the Abaqus user profile. It is possible to map a CBUSH to CONN3D2 even though their configurations are
different. The element mapping scheme must be under the *ElemTypeConversion block in the
ConfigurationFile.txt file. You need to provide both configuration and type information to specify the
element mapping scheme as shown for the Nastran to Abaqus direction below:
HyperMesh configuration, HyperMesh configuration,

Nastran type Abaqus type
tria3, CTRIA3 tria3, S3

tria3, CTRIAR tria3, S3R
quad4, CQUAD4 quad4, S4
quad4, CQUADR quad4, S4R
quad4, CSHEAR quad4, M3D4
tetra4, CTETRA tetra4, C3D4
penta6, CPENTA penta6, C3D6
hex8, CHEXA hex8, C3D8
tria6, CTRIA6 tria6, STRI65
quad8, CQUAD8 quad8, S8R
tetra10, CTETRA tetra10, C3D10
penta15, CPENTA penta15, C3D15
hex20, CHEXA hex20, C3D20

mass, CONM2 mass, MASS

mass, CELAS1 mass, SPRING1
mass, CELAS2 mass, SPRING1
rigid, RBE2 rigid, COUP_KIN
rigidlink, RBE2 rigidlink, COUP_KIN
rbe3, RBE3 rbe3, DCOUP3D
spring, CELAS1 spring, SPRING2
spring, CELAS2 spring, SPRING2
spring, CDAMP1 spring, DASHPOT2
spring, CDAMP2 spring, DASHPOT2
spring, CBUSH rod, CONN3D2
bar2, CBEAM bar2, B31
bar2, CBAR bar2, B31
rod, CROD rod, T3D2
rod, CONROD rod, T3D2
gap, CGAP gap, GAPUNI
weld, RBAR rigid, KINCOUP
Notes:
· The CELAS1 or CELAS2 elements in Nastran have both spring stiffness and damping attributes. If
both spring and damping values are present and the mapping scheme is CELAS1 to SPRING1,
the conversion tool will automatically create an extra DASHPOT element.
· Similarly, the CONM2 elements in Nastran have both translational and rotational mass values. If
both translational and rotational values are present and the mapping scheme is CONM2 to MASS,
the conversion tool will automatically create an extra ROTARY1 element.
Sectional properties
The table below shows supported sectional property mapping between Nastran and Abaqus. Some of the
properties in one solver can be converted to two different Abaqus sections in the other solver. For a
Nastran to Abaqus conversion, for example, PSHELL can be converted to *SHELL SECTION or *SHELL
GENERAL SECTION. In the mapping scheme, you must select one of them. The property mapping
scheme must be under the *PropertyConversion block in the ConfigurationFile.txt file.
Abaqus beam section axes are defined at element level in Nastran. They are in the sectional property level

in Abaqus unless the beam axis is defined by a third node in element connectivity. This means that several
elements with different beam axis direction can point to the same PBEAM, PBEAML, PBAR or PBARL
property in Nastran. But in Abaqus, all elements under a *BEAM SECTION or *BEAM GENERAL
SECTION property have one beam axis orientation. If a third node is used to define the beam axis, even
Abaqus beams with a different axis can belong to a single *BEAM SECTION property. The conversion tool
allows you to select an extra (1 or 0) argument to define the beam axis conversion mechanism.
If the argument is 0 (or not defined), the conversion tool will take the beam axis direction of the first
element corresponding to a PBEAM, PBEAML, PBAR or PBARL property and map that to the
corresponding *BEAM SECTION or *BEAM GENERAL SECTION card. The beam axis vectors of other
elements with the same property will be ignored.
If the argument is 1, the conversion tool will create a third node for each element to define the equivalent
beam axis vector. As a result, the axis direction for each element will be maintained after the conversion.
Because this option updates each element, the conversion process might take a considerable amount of
time for models with a large number of beams.
A) Nastran to Abaqus
Nastran Abaqus Beam axis option
PSOLID *SOLID SECTION

PSHELL *SHELL SECTION or *SHELL GENERAL SECTION
PBEAM *BEAM GENERAL SECTION 1 or 0
PBEAML *BEAM SECTION 1 or 0
PBAR *BEAM GENERAL SECTION 1 or 0
PBARL *BEAM SECTION 1 or 0
PROD *SOLID SECTION

PBUSH *CONNECTOR SECTION
PELAS (*SPRING + *DASHPOT) or *CONNECTOR SECTION
PDAMP *DASHPOT or *CONNECTOR SECTION
CELAS2 (*SPRING + *DASHPOT) or *CONNECTOR SECTION
CDAMP2 *DASHPOT or *CONNECTOR SECTION
CONM2 (*MASS +*ROTARY INERTIA)
B) Abaqus to Nastran
Abaqus Nastran
*SOLID SECTION PROD or PSOLID

*SHELL SECTION PSHELL

Abaqus Nastran
*SHELL GENERAL SECTION PSHELL

*MEMBRANE SECTION PSHELL
*BEAM SECTION PBEAML or PBARL
*BEAM GENERAL SECTION PBEAM, PBAR, PBEAML or PBARL
*CONNECTOR SECTION PELAS or PBUSH
*MASS CONM2
*ROTARY INERTIA CONM2
*SPRING PELAS
*DASHPOT PELAS OR PDAMP
*GAP PGAP
Notes:
· CELAS2, CDAMP2 and CONM2 are elements in Nastran, but they are sectional properties in
Abaqus. Therefore, the mapping for them must also be defined under *PropertyConversion. The
conversion tool will create a separate component for each element in this case.
· The PELAS or CELAS2 in Nastran have both spring stiffness and damping attributes. If both spring
and damping values are present and they are mapped to *SPRING, the conversion tool will
automatically create an extra *DASHPOT component.
· Similarly, the CONM2 in Nastran has both translational and rotational mass values. If both
translational and rotational values are present and it is mapped to *MASS, the conversion tool will
automatically create an extra *ROTARY INERTIA component.
· The property conversion scheme and corresponding element conversion scheme must be
consistent. For example, if you define PBUSH to *CONNECTOR SECTION at the property
mapping scheme, the corresponding element CBUSH must map to CONN3D2 in the element
mapping scheme.
Materials
The table below shows supported material mapping between Nastran and Abaqus. The algorithm for
material conversion is provided by Abaqus, Inc. The same algorithm is used in the Abaqus Version 6.7
"FromNastran" converter. The material mapping scheme must be defined under *PropertyConversion
block in the ConfigurationFile.txt file.
A) Nastran to Abaqus

Nastran Abaqus
MAT1 *MATERIAL *ELASTIC, TYPE=ISO; *EXPANSION, TYPE=ISO;

and *DENSITY (G is used only for *BEAM GENERAL
SECTION)
MAT2 *MATERIAL When used alone in a PSHELL, MAT2 is translated to

*ELASTIC, TYPE=LAMINA or *ELASTIC,
TYPE=ANISOTROPIC
MAT8 *MATERIAL ELASTIC, TYPE=LAMINA; *EXPANSION,

TYPE=ORTHO; and *DENSITY
MAT9 *MATERIAL *ELASTIC, TYPE=ANISOTROPIC unless the data are

found to be orthotropic, in which case the data are
analyzed to create *ELASTIC, TYPE=ENGINEERING
CONSTANTS. Also *DENSITY; and *EXPANSION,
TYPE=ANISO or ORTHO.
B) Abaqus to Nastran
Abaqus Nastran
*MATERIAL MAT1 Density, Young's modulus, Poisson's ratio, thermal

expansion coefficient, reference temperature
*CONNECTOR PBUSH or
BEHAVIOR PELAS
Note: If a PBEAM or PBAR is mapped to a *BEAM GENERAL SECTION, the material properties
defined in the corresponding Nastran material are mapped to the *BEAM GENERAL SECTION
card. No *Material is created in this case.
Loads
HyperMesh loads have two basic attributes – configuration (or config) and type. The supported load
"config" in HyperMesh are: force, moment, constraint, pressure, temperature, flux, velocity, acceleration
and equation. The load "type" in HyperMesh defines the solver specific type of a particular configuration.
For example, pressure load in HyperMesh can be any of the following Abaqus types: DLOAD, FILM,
DFLUX etc. The load types panel shows all supported load configurations in HyperMesh and their types
for a user profile.
For a specific configuration, you can map any supported Nastran load type to any supported Abaqus load
type. The conversion tool does not support conversion across load configurations. The load mapping
scheme is valid for either direction and must be under the *BCsTypeConversion block in the
ConfigurationFile.txt file. You need to provide both configuration and type information to specify the

mapping scheme as shown below:

force, FORCE force, CLOAD
moment, MOMENT moment, CLOAD
const, SPC const, BOUNDARY
const, SPCD const, VELOCITY
const, SUPORT const, BOUNDARY
pressure, PLOAD pressure, DLOAD
pressure, PLOAD2 pressure, DLOAD
pressure, PLOAD4 pressure, DLOAD
temp, TEMP temp, TEMPERATURE
equation, MPC equation, *EQUATION
In addition to the above load types, the conversion tool also converts Nastran Dload (with corresponding
Rload1, Rload2, DAREA, TABLED1, TABLED2, TABLED3) to Abaqus *BOUNDARY or *CLOAD (with
corresponding *AMPLITUDE curve). No mapping scheme needs to be specified for this conversion; the
conversion is done automatically if present in the model.
Load steps and analysis type

The conversion tool maps between Nastran subcases and Abaqus steps. It does not convert the solution
type from/to any Abaqus analysis type. You must define it manually using the Abaqus Step Manager or the
Nastran Load Step Browser in HyperMesh.
Systems and mass

The conversion tool converts Nastran system types into the corresponding Abaqus system (*SYSTEM,
*TRANSFORM or *ORIENTATION). It also converts the NSM into *NONSTRUCTURAL MASS and
assigns them to the relevant properties. The mapping can be summarized as:

Nastran Abaqus
*NONSTRUCTURAL MASS
NSM
NSM1
NSML
NSML1
NSMADD
*NODE and *SYSTEM

GRID
*SYSTEM for nodes; *TRANSFORM if referred to on GRID;

CORD1R
*ORIENTATION for elements
CORD1C
CORD1S
CORD2R
CORD2C
CORD2S
WTMASS
If the WTMASS parameter is defined in the Nastran model, it is used to modify density, mass, and inertia
values during conversion.

HyperWorks Desktop Interface with the Abaqus Solver
This section discusses how the HyperWorks Desktop applications interface with the Abaqus solver.
HyperView
MotionView
HyperGraph

HyperView Overview
Functionality HyperView
Animation Window Plot Window
Reading Abaqus INP, FIL, and ODB Files
Reads model file directly INP, ODB N/A
Reads results file directly ODB (field) ODB (field and history)
Reads translated results

FIL (hmabaqus) FIL (hmabaqus)
FIL
(hgopt_abaqus.exe)
Supported field results (typically contoured) FIL, ODB ODB
Supported history results (typically plotted) N/A FIL, ODB
Abaqus version supported 6.7 6.7
Retains model's component names and IDs INP, H3D from HM N/A
Coordinate Systems
Can transform results to other system type Yes N/A

inside application
Abaqus Results for ODB
POSITION = INTEGRATION POINTS Yes Yes
POSITION = CENTROIDAL Yes Yes
POSITION = NODES Yes Yes
POSITION = AVERAGED AT NODES No No

Abaqus Results for FIL
POSITION = INTEGRATION POINTS Yes Yes
POSITION = CENTROIDAL Yes Yes
POSITION = NODES No No
POSITION = AVERAGED AT NODES Yes Yes
Abaqus Entities
Supports 1-D elements Model Yes Yes
Supports 1-D elements Results Yes Yes
Supports mass entities in model No Yes

Model Data
In the Animation client, either the Abaqus INP or ODB file can be loaded for model data.
INP Files as Model Data
When reading an INP file as model data, click the Reader Options... button to access different importing
options.
If selecting the By HM Comment option:
· HyperMesh will consider any available comments written during a previous model export from
Version 9.0.
· If no comments are found, HyperMesh creates a component for every element set (ELSET) that
points to a sectional property. The collector will have the name of the referenced element set.
· The model organization and colors are maintained when using this option.
When the model is read, the elements are organized into HyperView components based the Reader
Options selected. If By HM Comment is selected, elements are organized into HyperView components
based on section properties defined in the INP file. If the By 1 Comp option is selected, all elements are
organized into one component.
In most cases, Altair recommends using a corresponding INP file when one is available. HyperView 9.0
also reads node and element sets from the input file. These sets are available in the groups panel.
ODB Files as Model Data
When using an ODB file as model data the import options function is not available. On import, each ELSET
that has a sectional property assigned will become a component in HyperMesh. The name of each
component will be the name of the ELSET parameter the property is referring to. HyperView does not
currently read other sets from the ODB file.
In HyperView, an element must belong to only one component. Also, there is no data structure to support
Abaqus ELSET, where one element can belong to multiple components. The sectional property card of the
element set defines these components. However, the ODB file does not contain any sectional property
information. Therefore, there is no way to distinguish between a component and a regular ELSET from the
ODB file. To correct this, the Abaqus ODB reader sorts all the ELSETs according to their size (smaller to
larger) and creates components from them. Then, it loops through each ELSET and tries to add all
elements in that set to the corresponding component. If an element has already been added to a previous
component, it is ignored. At the end, if some components are left without any elements, they are deleted.
The consequence of this approach is that an element belongs to the smallest component in which it is
found, causing possible "holes" in components.
By Comments Option
HyperView will consider comments written during a previous model export from HyperMesh Version 9.0.
This will help you to retrieve the same component organization as created in a previous HyperMesh
session. Mainly you receive a component per each sectional property with an **HM_comp_by_property
comment in front of it.
If no comments are present, HyperView creates a component for every element set (ELSET) that points to
a sectional property.

Result Data from ODB
HyperView supports both field and history data from the Abaqus ODB file. The animation window shows
the field results, while the plot window shows both field and history results. To read the Abaqus ODB result
files, you need to install the Abaqus ODB API from Altair’s distribution CD.
The Abaqus ODB reader supports the following data type formats:
· SCALAR
· VECTOR
· TENSOR_3-D_FULL
· TENSOR_3-D_PLANAR
· TENSOR_2-D_PLANAR
TENSOR_3-D_FULL, TENSOR_3-D_PLANAR, and TENSOR_2-D_PLANAR are treated as TENSOR3-D
in HyperView.
The Abaqus ODB reader supports element results at the following positions:
· Integration points (default)
· Nodes
· Centroidal
HyperView also supports beam elements with section points. To determine the location of section point
IDs, refer to the Abaqus documentation for details.
The following diagrams represent the data locations for first-order elements in the ODB file and in
HyperView:
Key - ODB Key - HyperView
POSITION = Integration Element corner

points
POSITION = Nodes Element centroid
POSITION = Centroidal

Customizing the ODB Reader
The HyperView ODB reader can be customized by setting several environment variables. On PC platforms,
environment variables can be defined by following these steps:
1. Open System in the Control Panel.
2. On the Advanced tab, click Environment variables, and click the name of the user variable or system
variable you want to change, as follows. Select:
· New to add a new variable name and value.
· Edit to change a current variable name and value.
· Delete to remove a variable name and value.

On UNIX platforms, the environment variables can be defined with the following command:
setenv <variable name> <value>
Note HyperView must be restarted for the variables to take effect.
The supported variables are:
ALTAIR_ODB_ELEMDATATYPES
The ALTAIR_ODB_ELEMDATATYPES variable is for defining the element result locations (POSITION =
NODES/INTEGRATION POINTS).
It has four possible values:
ALL Reads both extrapolated corner (POSITION = NODES) and integration point (
POSITION = INTEGRATION POINTS) results. This is the default option.
AUTO Reads extrapolated corner (NODES

Supporting_Results_at_Position_CENTROIDAL) result for Abaqus Standard
analysis and integration point results for Abaqus Explicit analysis.
EXTRAPOLATE Reads extrapolated corner (POSITION = NODES) result only
INTPOINT Reads integration point (POSITION = INTEGRATION POINTS) results only
ALTAIR_ODB_DATACACHE
The ALTAIR_ODB_DATACACHE variable is a reader option now accessible through HyperViews "Reader
Options" dialog (Cache Data). When this option is enabled, the ODB reader will request HyperView to
cache the data. HyperView in most cases will fulfill that request. This leads to a better performance
if the same data get requested multiple times.
For example:
· the user plots "S- Global Stress - VonMises" then enables "Simple Averaging" (will use cached

data) and then contours "S-Global Stress-P1(Major)" (will use cached data)
ALTAIR_ODB_AUTOUPGRADE
The Abaqus ODB API can not read an older version ODB file without first upgrading it to the latest format.
The ALTAIR_ODB_AUTOUPGRADE variable specifies whether the file is to be upgraded automatically during
import.
FALSE No automatic upgrade. Manually upgrade the file using the Abaqus ODB Upgrade tool.
This is the default option.
TRUE HyperView will automatically upgrade the file during import. A temporary file will be
created and saved in the user folder. This file will, however, will be deleted
automatically when HyperView is closed
ALTAIR_ODB_DELAY_DESTRUCTION
HyperView does not release a file from memory unless a new file is loaded. This improves the performance
of multiple opening and closing operations on the same file. However, this might cause problems for a
partially-complete ODB file. When you try to re-load a partially-complete ODB file, it might not show the
new results. The ALTAIR_ODB_DELAY_DESTRUCTION variable controls this "closure delay" functionality.
TRUE The ODB reader will delay the file closure until a new file is loaded. Use this option
when you want to open and close the same file with same data multiple times.
FALSE The ODB reader will not delay the file closure. Instead, it will release memory as soon
as the file is closed. Use this option when you want to load the same file with new
data. This is the default option.
Contour Panel for Abaqus Results
The Contour panel in HyperView has contour options for FEA results. The following overview focuses on
Abaqus ODB files.
The following options on the Contour panel are applied to the model when you click Apply.
Result type The Result type section allows you to select the result type and the
corresponding component type that should be used to calculate contours.

Use the first drop-down menu under Result type to select one of the available
result types. The options change depending on the currently loaded result file.
Each result type is followed by a letter that indicates the category to which it
belongs. An "IP" suffix on the result type name indicates integration point
results; no "IP" suffix indicates extrapolated results to the element corner
nodes. Global element results are with respect to the global coordinate system
and are prefixed with "Global". For a full description of global results, see
Supported Tensor Results in Local Coordinate Systems .
(t) indicates a tensor-type result, such as stress or strain tensors. Refer
to the section Supported Tensor Results for additional information.
(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. Refer to the section Supported
Tensor Results for additional information.
(c) indicates complex results.
The second drop-down menu in the Result type section allows you to choose
the data component type. The list of available components is based on the
selected result type. For example:
Result type Component options
S-Stress Mises, Max Principal, Mid Principal, Min Principal, Tresca,

components (s) Press, Inv3, S11, S22, S33, S12, S13, or S23
S-Stress Mises, Max Principal, Mid Principal, Min Principal, Tresca,

components IP Press, Inv3, S11, S22, S33, S12, S13, or S23
(s)
S-Global-stress vonMises, P1 (major), P2 (mid), P3 (minor), Pressure,

components (t) MaxShear, Intensity, In-plane P1 (major), In-plane P2
(minor), XX, YY, ZZ, XY, YZ, or XZ
S-Global-stress vonMises, P1 (major), P2 (mid), P3 (minor), Pressure,

components IP MaxShear, Intensity, In-plane P1 (major), In-plane P2
(t) (minor), XX, YY, ZZ, XY, YZ, or XZ
Displacement (v) Mag, X, Y, or Z
UR-Rotational Mag, X, Y, or Z
displacement (v)
Entity with layers The Entity with layers option allows you to display a contour for a specified
element layer or section point along the thickness of the shell. The contour will
be applied to all layers defined in the model. If an element has no layer
definition, as in a mass or solid, the contour is also displayed regardless of
which layer is selected.
The options that control how layers will be displayed are:

Max Displays the maximum value among the layers for each
entity, i.e. maximum tensile stress or minimum
compressive stress.
Min Displays the minimum value among the layers for each
entity.
Extreme Displays the maximum absolute values among the layers

for each entity.
Section Point 1 Results on layer 1 of the shell elements.
(SNEG, bottom)
Section Point 5 Results on layer 5 of the shell elements.
(SPOS, top)
Note Section Point 1 (bottom) and Section Point 5

(top) are always defined by default. HyperView
supports all layers defined in the ODB file.
For example:
Element 1 Lower = -20, Upper = 10
Element 2 Lower = -5, Upper = 30
Lower layer:
Legend Max = -5, Min = -20
Upper layer:
Legend Max = 30, Min = 10
Min layer:
Legend Max = -5, Min = -20
Max layer:
Legend Max = 30, Min = 10
Extreme layer:
Legend Max = 30, Min = -20
Use corner data If corner data is available, the Use corner data option is enabled. If you
activate the option, HyperView displays color bands by interpolating available
corner results within each element. A discontinuity of the result distribution
across element boundaries can be seen.
The Abaqus ODB reader supports element results at
POSITION=INTEGRATION POINTS (default), NODES, and CENTROIDAL.
The ODB file does not support AVERAGED AT NODES. Abaqus ODB always
has results for integration points regardless of the position parameter setting in
the output request.
HyperView supports these results with respect to the Display corner data
option as follows:

Without "IP" suffix Display corner data on: integration point
results are extrapolated to the element corners.
For example: This is equivalent to POSITION=NODES in
S-Stress components (s) 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 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.
Refer to 1st Order Elements and 2nd Order Elements for schematics
describing this information. Also refer to Supported Results for 1D Elements
Selection Before creating a contour plot, you must pick one or more entities from the
model. You can do this by picking entities directly from the screen, using the
quick window selection, or clicking the Elements or Components input
collector and using the extended entity selection menu. If no selection is
made, the contour will be applied to displayed components or elements by
default. See Selecting Entities Using the Input Collector for more information
on selecting entities.
Resolved in The Resolved in drop-down menu allows you to select the result coordinate
system to be used to contour the results. The available options are dependent
on the current selection for Averaging method. You can select the analysis,
elemental, or global coordinate system as well as a user-defined system. The
System input collector is enabled when User System is selected.
The Abaqus part is written according to the guidelines described in Supported
Tensor Results.
Global System Transforms to the global system.

(proj: none) indicates that no projection rule is
selected for shells. When a projection rule is
selected (using the Projection Rule… button) it is
displayed, for example, (proj: y, x).
Elemental System Transforms results to the elemental coordinate

system. In HyperView, the elemental coordinate
system is defined by element connectivity, which
differs from the Abaqus elemental system, but is
similar to the Nastran elemental system.
Analysis System Transforms the results to systems associated with

each elements as they are defined in the result file.
Because every result in Abaqus has its own system
that can change with time, the results can not be
populated as a HyperView analysis system.
Therefore, the analysis system option is not
applicable to Abaqus results and is equivalent to the
global system.
User System Transforms the results to a user-defined coordinate

system.
This option is available when the results or model file
contains a user-defined coordinate system. Click the
System input collector to select a system by ID or
pick from the screen.
(proj: none) indicates that no projection rule is
selected for shells. When a projection rule is
selected (using the Projection Rule… button) it is
displayed, for example, (proj: y, x).
Projection Rule Abaqus uses X as the primary axis and Z as the secondary axis.
Averaging Method None No 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.
Simple Tensor and vector components are extracted and

the invariants are computed prior to averaging.
This option is equivalent to the Abaqus/Viewer
"compute scalars before averaging" option.
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.
This option is similar to the Abaqus/Viewer "compute
scalars after averaging" option.
Difference The difference between the maximum and minimum

corner results at a node.
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.
This option is equivalent to the "averaging threshold
(%)" option in Abaqus/Viewer, but the HyperView
denominator is different.

The following options are automatically applied to the model as you enter information.
Display options The display options change the appearance of the contour colors.
Discrete color Produces discrete color bands on contour plots

with distinct boundaries between contour levels.
This option uses a texture mapping capability in
your graphics card. If your graphics card does
not support texture mapping, the performance
may slow down.
Show feature lines Display feature lines for the displayed

components. You can set the desired feature
angle from the Tools menu, Options dialog,
Visualization tab.
Interpolate colors Interpolates the contour colors from the

undeformed shape (with a zero value) to the
result variable reported from the solver. If you
do not select Interpolate colors, the contour
colors remain the same for all frames. This is
only applied to modal and static animation.
Legend threshold Max Enter the value to be assigned to the highest

color in the contour plot. Activate the Max check
box to apply the value.
The new value is also changed in the Values
section of the Edit Legend dialog.
If a value entered for threshold Max is invalid, it
will not be applied and the panel will be updated
to reflect the actual state.
Min Enter the value to be assigned to the lowest

color in the contour plot. Activate the Min check
box to apply the value.
The new value is also changed in the Values
section of the Edit Legend dialog.
If a value entered for threshold Min is invalid, it
will not be applied and the panel will be updated
to reflect the actual state.
Multiplier Enter the multiplier for scaling all the result

values.
Edit Legend Opens the Edit Legend dialog where you can change the legend properties.
Result display The following options allow you to manage the result display.
control
Overlay result display Overlays contour, tensor, and vector results in

the same window. If all results are displayed
simultaneously, available memory may be
affected.
Clear Contour Clears the contour and returns the model to its
original state.
Query Results Opens the Query panel where you can view and export properties and other
information related to nodes, elements, components, and systems contained
in the active model.
Element Results
See the following topics for element results:
Tensor Results
Results at Position - Integration Points
2-D Solid, Axisymmetric, and Membrane Elements
3-D Solid Elements
3-D Shell Elements at Each Layer
2-D and Axisymmetric Gasket Elements
3-D Gasket Elements
1st-Order Elements
2nd-Order Elements
1D Elements
Results at Position - Nodes
Results at Position - Centroidal
Complex Results
Tensor Results
In general, HyperView supports tensor results in global, analysis, and elemental (Nastran-like) systems.
The analysis system means that the orientation or transform system is defined as model data in the
Abaqus analysis. By default in Abaqus, all shell and membrane element results are in local in-plane
systems. In addition, the material orientation for elements would change in a large deformation analysis.
Therefore, the Abaqus ODB file does not contain any information about the *ORIENTATION or
*TRANSFORM systems defined in the model. Instead, for every result in a local system, it contains the
direction cosines of the corresponding system.

Every tensor result in the ODB file can be in local material systems that can change with time. As a result,
HyperView creates two data types from each tensor result:
· scalar group with local results that are directly read from the ODB file
· tensor group with global results that are transformed from the local results.
These global data type names are prefixed with "-Global-". For example, there are two data types for
element stresses: S-Stress components (s) and S-Global-Stress components (t). The local scalar
group will get all components and valid invariants directly from the ODB file. The global tensor will have
transformed global components and a set of invariants calculated by HyperView. The components and
principal axes for a tensor data type can be viewed from the Tensor Plot panel.
HyperView system options include Global, Analysis, Elemental, and User-defined:
Global Nodal dof directions or element material directions are in the global
coordinate system.
Analysis The analysis system is the associated local dof directions (for nodes) or
local material directions (for elements) defined in the model. It is equivalent
to the Abaqus *TRANSFORM or *ORIENTATION systems. However in
large deformation analysis, these systems can rotate with time in Abaqus.
Because of this, the ODB file does not consider these systems as model
information. Instead, nodal results are always in the global system and
element results come with the direction cosines of the corresponding
systems at each increment. As a result, analysis systems HyperView are
not populated from the ODB file. in addition, the analysis system option is
not relevant for Abaqus results.
Elemental The elemental system is the default local system defined on the surface of
planar elements (shell, membrane, etc). Abaqus uses the projection of the
global axes onto the elements’ surface to define these in-plane systems. In
large deformation analysis, these default local systems can rotate with time.
As a result, the Elemental system option in HyperView does not represent
the Abaqus elemental system. Rather, it is similar to the Nastran elemental
system.
User-define Transforms vector results to a user-defined system. This option is available

d when *SYSTEM, *TRANSFORM, or *ORIENTATION systems are read into
HyperView from an INP file.
Results at Position - Integration Points

This is the default option in Abaqus. If the ODB file contains only integration point results, the ODB reader
in HyperView extrapolates the results to the element corner nodes in addition to the results for the
integration points. Therefore, you get results for both Position = NODES and Position = Integration
Points even if the ODB file only contains integration point results.
HyperView use the special suffix "IP" to distinguish integration point results from extrapolated element
corner results. The ODB file does not contain information about the exact location of the integration points.
Therefore, the nearest corner nodes are used to display the integration point results. The Display corner

data option on the Contour panel must be selected to plot contours at these corner nodes. If the Display
corner data option is off, all integration point results are averaged as the base result of the element and
one uniform value per element is used for the contour plot.
Note If the number of integration points is more than the number of nodes, only the integration points
near the nodes are mapped.
2-D Solid, Axisymmetric, and Membrane Elements
Element Type Total Number Result at Maps to Corner Base Result

of Integration Integration Point (local node)
Points Number
3-noded (TRIA3) 1 1 1 Average

1
2
1
3

2 2
3 3
4-noded (QUAD4) 4 1 1 Average

2 2
3 4
4 3

1 2
1 3
1 4

3 2
7 4
9 3

Points Number
2 2
3 4
4 3
3-D Solid Elements

Points Number
4-noded (TETRA4) 1 1 1 Average

1 2
1 4
1 3
6-noded (PENTA6) 2 1 1 Average

1 2
1 3
2 4
2
5
2
6
8-noded (HEX8) 8 1 1 Average

2 2
3 4
4 3
5 5
6 6
7 8
8 7

Points Number

1 2
1 3
1 4
2 5
2 6
2 7
2 8
10-noded (TETRA10) 9 1 1 Average

2 2
3 3
4 4
15 noded (PENTA15) 9 1 1 Average

2 2
3 3
7 4
8 5
9 6
20 noded (HEX20) 27 1 1 Average

3 2
7 4
9 3
19 5
21 6
25 8
27 7

2 2

Points Number
3 4
4 3
5 5
6 6
7 8
8 7
3-D Shell Elements at Each Layer

Points Number

1 2
1 3

2 2
3 3

2 2
3 3

2 2
3 4
4 3

Points Number
1 2
1 3
1 4

3 2
7 4
9 3

2 2
3 4
4 3
2-D and Axisymmetric Gasket Elements

Points Number
2-noded link (Rod) 1 1 1 Average

1 2

1 3
2 2
2 4

3-D Gasket Elements

Points Number
2-noded link (Rod) 1 1 1 Average

1 2

1 3
2 2
2 4
6-noded (PENTA6) 3 1 1 Average

1 4
2 2
2 5
3 3
3 6

1 5
2 2
2 6
3 4
3 8
4 3
4 7
1st-Order Elements
Key

Integration point results are Integration point results are at the
extrapolated to the element corners nearest element corners when Display
when Display corner data is corner data is selected. Results are not
selected. extrapolated.
Average of 1", 2", 3", and 4", when Average of 1’, 2’, 3’, and 4’ when
Display corner data is deselected. Display corner data is deselected.
2nd-Order Elements
Key
S_Stress Component (s)
Integration point results are extrapolated to element corners. Mid-node results are
ignored. For contours, results at mid-side nodes are linear interpolations of results at
element corners.
Average of 1, 2, 3, 4, 5, 6, 7, and 8 when Display corner data is off.
S_Stress Components_IP (s)
Integration point (IP) results are at the nearest element corners when Display corner
data is selected. Results are not extrapolated. Mid and center IP results are ignored.
For contours, results at mid-side nodes are linear interpolations of results at element
corners.
Average of 1’, 2’, 3’, 4’, 5’, 6’, 7’, 8’, and 9’ when Display corner data is deselected.
1D Elements

Points Number

2-noded line 1 1 1 Average
1 2
3 1 1
3 2
3-noded line 1 1 1 Average

1 2
2 1 1
2 2
3 1 1
3 2
Results at Position - Nodes
The data type names without the "IP" suffix contain the nodal tensor (ELEMENTAL_NODAL) results as the
corner result. The Abaqus ODB reader reads these values directly from the ODB file (or extrapolates them
from the integration point results) and assigns them to the corner of each element. In HyperView, the
Display corner data option on the Contour panel has to be selected to plot the contour with corner
results.
Results at Position - Centroidal
The data type names without the "IP" suffix contain the centroidal tensor results as the base result. The
Abaqus ODB reader reads these values directly from the ODB file and assigns them to the center of each
element. One uniform value per element is used for the contour plot. In this case, the Display corner data
option is enabled on the Contour panel. When the Display corner data option is selected, extrapolated
corner data of the integration points is displayed.
Note: Integration point results are always available in the ODB file.
Complex Results
For information on dealing with complex results, click here.

Parts and Instances in the ODB File
The ODB data structure is designed as parts and instances. Even if parts and instances are not defined
in the input file, Abaqus creates a part from the whole model and an instance of it in the ODB file. The
ODB reader in HyperView supports ODB files that have one or more parts and instances of the ODB file.
However, if an INP file is read in with an ODB results file as output, only single parts and instances are
supported.

MotionView
This section explains how MotionView interfaces with the Abaqus solver.

MotionView MDL models can be exported to an Abaqus .inp file.
Gravity, Units, and Solver Parameters

This section explains how MotionView works with gravity, units, and solver parameters for Abaqus.
Gravity
Gravity is an implicit data set, meaning that its definition is created automatically by MotionView. The
values for gravity can be accessed through the Forms panel while in the Misc system of a model. Default
values for gravity are set in the std_inc file that is part of the MotionView installation. A Templex
template is also included in std_inc. This template allows you to write the gravity to the Abaqus input file.
Units
Although MotionView is a "unitless" interface, it is often required that the units you are working with be
communicated to the solver input deck. Similarly, it may be necessary to ensure that the units are
consistent. Therefore, the definitions of mass, length, time, and force are automatically generated by
MotionView. To access this, go to the Forms panel and select Units under the Misc system. The default
values as well as the Templex template used for exporting units to Abaqus are generated from the
std_inc file.
Solver Parameters
Solver parameters vary considerably between different solvers and are stored in datasets. There are two
ways to generate solver parameter datasets:
· Data sets and their corresponding forms are created within the analysis task in the MDL library. If
you are creating your own MDL library, you need to verify that the solver parameter datasets are
defined in each analysis task.
· No library is used to construct a model. This includes interactive model construction and the
manual editing of .mdl files, or a combination of both. For this case, MotionView automatically
generates the system containing the solver parameters based on a definition within the std_inc
file.
MDL Statement Mapping

The mapping between MDL and the corresponding Abaqus entities are described below.
Note: All property data for these entities are set in corresponding *Set() statements.
MDL Statement Abaqus Entity
*ActionOnlyForce() CLOAD, AMPLITUDE (Time Function only)
*ActionReactionForce() CLOAD, AMPLITUDE (Time Function only)
*AtPointJoint() Joint (Connector Section)
*BallJoint() Joint (Connector Section)

*Beam() B31(Timoshenko beam)
*Body() Rigid Body
*Bush() Connector Behavior
*CoilSpring() Connector Behavior
*ControlSISO() None
*Coupler() None
*Curve() AMPLITUDE
*CVJoint() Joint + Constant Velocity (Connector Section)
*CylJoint() Slot + Revolute (Connector Section)
*FixedJoint() Weld (Connector Section)
*Graphic() None
*HookeJoint() Joint+Universal (Connector Section)
*InlineJoint() Slot (Connector Section)
*InplaneJoint() Slide-Plane (Connector Section)
*Marker() NODE + ORIENTATION
*Motion() Connector Motion (Time Function only)
*OrientJoint() Align (Connector Section)
*Output() Output, History
*ParallelAxisJoint() Revolute (Connector Section)
*PerpAxisJoint() Universal (Connector Section)
*PlanarJoint() Slide-Plane + Revolute (Connector Section)
*Polybeam() B31(Timoshenko Beam)
*RevJoint() Joint + Revolute (Connector Section)
*SetFlexbodyComplaince() Substructure Element

*SolverArray() None
*SolverDiffEquation() None
*SolverString() None
*SolverVariables() None
*TorsionSpring() Connector Behavior
*TransJoint() Slot + Align (Connector Section)
*UniversalJoint() Joint + Universal (Connector Section)
MDL CommandSet Mapping

CommandSet's do not apply to the Abaqus solver.
Templex Templates and solvermode

Templex templates can be used to export syntax directly to the solver input deck, including parametric
substitution if required. For the Abaqus solver, the location of statements within the solver input deck is
important. The four keywords listed below allow you to position the extra text. These keywords must be
the first line of the Templex template. The remaining text of the template is written according to the
position specified.
<@ABAQ/MODEL/HEAD> Designates text that is written at the top of the model data.
<@ABAQ/MODEL/TAIL> Indicates the end of the model data.
<@ABAQ/HISTO/HEAD> Indicates the top of the history data.
<@ABAQ/HISTO/TAIL> Indicates the end of the history data.

<@ABAQ/HISTO/STEP/HEAD> Indicates that data will be written at the start of the first step.
<@ABAQ/HISTO/STEP/TAIL> Indicates that data will be written at the end of the first step.
One MDL model can be used to export to more than one solver. In this case, create the instance of the
Templex template using the solvermode reserved keyword. This can be done in two ways:
For example, an MDL model containing:
if( solvermode == "Abaqus" )
*Template(.....1...)
else
*Template(.....2...)

endif
results in the entire template 1 being used when Abaqus is selected from the Solvers menu. When
another solver is selected, template 2 is used. When a template is used, it means that it is displayed in the
interface on the Templates panel and is acted upon when saving the solver input deck.
To use the keyword, put the required string in the first line of the template. For example, an MDL model
containing:
*DefineTemplate(........)
<@ABAQ/MODEL/HEAD>
text for abaqus
*EndDefine()
results in "text for abaqus" being exported to the input deck when you select Abaqus as the solver.
The same applies for the portion of template that is displayed in the user interface.
Template Types
· A Templex template can have several destinations as well as a unique default behavior.
· A USER template does not get exported into any solver file but can be useful for getting
parametrically based text into another file (by using the Templex Open and Close commands) or
for text targeted for the GUI only.
· A SOLVER_INPUT template results in the template text being exported to the .inp file for Abaqus.
The following templates do not apply to the Abaqus solver:

SOLVER_PARAM
GRAPHICS
ADAMS
ACF
CommandSets
CommandSets do not apply to the Abaqus solver.
Function Expressions
MotionView supports function expressions for many of its entities. These expressions can be a function of
time and state variables. You can create function expressions that are exported directly as part of a
corresponding solver entity.
The solver neutrality is somewhat limited because the solver needs to handle the syntax that MotionView
exports. For the Abaqus solver, supported expressions and curves must be a function of time.
Expressions that are a function of an axial distance between two points are also supported. MotionView
converts these to an XY curve before writing to the input deck.
Flexbodies/Substructures
Pre-processing
MotionView allows you to represent an MDL body as an Abaqus substructure. Before implementing the
flexbody into an MDL model, you have to create an Abaqus substructure for each component that you plan
on representing as a flexbody. (Please see Abaqus help for this process). In addition, you should export

an .h3d file of this same component from HyperMesh which will later be used for graphics within
MotionView pre-processing. The base name (basename.ext) of the .h3d file must match that of the
substructure files for each component.
To utilize an Abaqus substructure within MotionView, simply toggle a body to Flexbody in the Properties
tab. Identify the .inp and .sup file for the substructure and use the Nodes button to connect the flexbody
to the MDL model. You can choose to align the MDL point to the exact location of the Abaqus connection
node or you can enter a tolerance that will be exported to the final Abaqus input deck.
Post-processing
To obtain an animation of the entire model, overlay the animations based on the .odb files corresponding
to each sub-structure. Overlay one animation consisting of MODEL = .mdl and RESULTS = .mrf, where .
mrf comes from converting an Abaqus .fil file using ToolsèèCustom WizardsèèAbaqus Fil to
Altair Formats.
Note It is recommended that new bodies are not introduced through Templex templates as doing so
can break the mapping required for successful animation.
User Subroutines
User subroutines do not apply to Abaqus. Entities with a reference to user subroutines are not used when
exporting to the solver input deck.
Launching Solvers from MotionView

MotionView allows you to launch a process automatically after the solver input deck is exported. For
Abaqus, the installation contains default launch scripts located in
altair/utilities/mbd/launch_scripts. One or more of these launch scripts can be registered
through the preferences.mvw file and then selected from the Run panel by using the
*RegisterSolverScript() preference statement.
Post-Processing
Animation - Transient with Rigid Bodies Only
To animate the results of an Abaqus run that was performed on a model exported directly from
MotionView:
1. From the Load Model panel in the Animation window, select the MDL model for the Model field.
2. Select the converted .mrf file for the Result field.
The converted .mrf file can be obtained by running the translator fil2mrf from the ToolsèèCustom
Wizards menu. MotionView does not support the .odb format for rigid body animations at this time.
This method automatically captures all graphics that were set up in the pre-processed model. Animation
depends on mapping, which holds as long as no extra bodies were added in Templex templates, or edited
manually from the .inp file.
Plotting
To plot results from an Abaqus run, you can use the fil2mrf translator to create an Altair binary format (.
abf) file. This file can be loaded directly into the Plot window. The abf file contains the translational and
rotational displacements of all bodies. Any output requests for displacement, velocity and acceleration are
written out to the Abaqus ODB file. Output requests of other kinds are not supported.
Defining Stiffness and Damping Characteristics for Springs and Bushing

Elements
MotionView allows you to define stiffness and damping characteristics for coil and torsion springs and
bushing elements by:
· Constant
· Curve
· Expression
The Abaqus solver does not support expressions. If you use the Abaqus solver, you can only define
stiffness and damping characteristics by a constant or curve.
If you define stiffness and damping characteristics by a constant, your model will run correctly using the
ADAMS or Abaqus solver.
If you define stiffness and damping characteristics by curve, use the following conventions to obtain a
model that will run correctly using the ADAMS or Abaqus solver.
Spring Damper - Coil Spring- Stiffness

Verify that the independent variable does not contain a minus sign, "-", in the expression.
Set the characteristic curve with same trend as the curve below:
Spring Damper - Coil Spring - Damping

Verify that the independent variable does not contain a minus sign, "-", in the expression. By default,
MotionView writes the independent variable with a minus sign, `-{sd_.VR}`, instead of `{sd_.VR}`,
as required for a solver independent model.
Spring Damper - Torsion Spring - Stiffness

MotionView writes the independent variable with a minus sign, `-{sd_.AZ}`, instead of `{sd_.AZ}`,

Spring Damper - Torsion Spring - Damping
Verify that the independent variable does not contained a minus sign, -, in the expression. By default,
MotionView writes the independent variable with a minus sign, `-{sd_.WZ}`, instead of `{sd_.WZ}`, as
required for a solver independent model.
Bushing Elements - Translational Characteristics - Stiffness

MotionView writes the independent variable with a minus sign, `-{bsh_.DX}`, instead of `{bsh _.DX}`
, as required for a solver independent model.
This applies to the Y and Z direction as well.
Bushing Elements - Translational Characteristics - Damping

MotionView writes the independent variable with a minus sign, `-{bsh_.VX}`, instead of `{bsh_.VX}`,
Bushing Elements - Rotational Characteristics - Stiffness

MotionView writes the independent variable with a minus sign, `-{bsh_.AX}`, instead of `{bsh_.AX}`,

Bushing Elements - Rotational Characteristics - Damping

MotionView writes the independent variable with a minus sign, `-{bsh_.WX}`, instead of `{bsh_.WX}`,

HyperGraph
This section explains how HyperGraph interfaces with the Abaqus solver.

To plot the value against time for an Abaqus ODB result type

The Abaqus ODB reader in the HyperView and HyperGraph plot window reads both field and history results
from the Abaqus ODB file. The history result names are post-fixed with (Time History). Results without
this postfix are field data. Time history results have two components (or columns): Time and Value.
The Time component is the first column of the result. The value can be time steps, frequency, or mode
number, depending on the analysis types.
The Value component is the actual value for the result type.
Note Time data for different result types can be different. It is recommended to use both the Time and
Value from the same result type.
To plot the value against time for an Abaqus ODB result type
Note The Value component is the actual value for the result type.
1. Select the plot window, , from the window mode option menu.
2. Select the Build Plots icon, , from the toolbar.

3. Select the same result type and request for both the X and Y data.
4. Select Time as the X component.
5. Select Value as the Y component.
6. Click Apply.
Note Time data for different result types can be different. It is recommended to use both the Time and
Value from the same result type.

Hyperworks 9.0 User'S Guide Abaqus Solver Interface

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Hyperworks 9.0 User'S Guide Abaqus Solver Interface

Caricato da

Copyright:

Formati disponibili

HyperWorks 9.

Web site www.altair.com

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

Location Telephone e-mail

Trademark and Registered Trademark Acknowledgments

Altair Engineering HyperWorks 9.0 User's Guide - Abaqus Solver Interface i

Proprietary Information of Altair Engineering

ii HyperWorks 9.0 User's Guide - Abaqus Solver Interface Altair Engineering

Proprietary Information of Altair Engineering

Import and · The Abaqus interface supports Abaqus version 6.7

· HyperMesh places all elements into separate components, based on sectional

· Although HyperMesh supports 160 characters in entity names, Abaqus output

· When HyperMesh encounters an **HM_GENERATE_SET_EXPAND in the input

Syntax · HyperMesh supports some abbreviated key words and parameters.

· All Abaqus keywords and parameters supported in HyperMesh are case

· HyperMesh ignores spaces in keyword lines.

· HyperMesh supports quotation marks around component (ELSET with sectional

Altair Engineering HyperWorks 9.0 User's Guide - Abaqus Solver Interface 1

Proprietary Information of Altair Engineering

2 HyperWorks 9.0 User's Guide - Abaqus Solver Interface Altair Engineering

Proprietary Information of Altair Engineering

Changes in Sectional Property Handling in HyperMesh Abaqus interface 9.0

Altair Engineering HyperWorks 9.0 User's Guide - Abaqus Solver Interface 3

Proprietary Information of Altair Engineering

Altair Engineering HyperWorks 9.0 User's Guide - Abaqus Solver Interface 5

Proprietary Information of Altair Engineering

· If neither **HM_comp_by_property nor **HM_set_by_property comments are present, HyperMesh

· If a comment such as **HM_comp_by_property “<property name>” <color> is found before a

· If an **HM_set_by_property comment is found, HyperMesh will create a property collector, which

6 HyperWorks 9.0 User's Guide - Abaqus Solver Interface Altair Engineering

Proprietary Information of Altair Engineering

· The Abaqus syntax for the include file path is:

Altair Engineering HyperWorks 9.0 User's Guide - Abaqus Solver Interface 7

Proprietary Information of Altair Engineering

The following templates can be used to generate Abaqus input decks:

Standard.2d Generates a deck for two-dimensional models containing planar or

Explicit Generates a deck for use with Abaqus Explicit.

Altair Engineering HyperWorks 9.0 User's Guide - Abaqus Solver Interface 9

Proprietary Information of Altair Engineering

The following summary templates are available for Abaqus:

elements.exp Summarizes the number and type of elements in the current

ctr_of_gravity Calculates the center of gravity of the model.

components Summarizes the component information in the current HyperMesh

mom_of_inertia Calculates the moment of inertia of each component of the model

10 HyperWorks 9.0 User's Guide - Abaqus Solver Interface Altair Engineering

Proprietary Information of Altair Engineering

Altair Engineering HyperWorks 9.0 User's Guide - Abaqus Solver Interface 11

Proprietary Information of Altair Engineering

Abaqus Card Supported Parameters

*CONSTRAINT NO CHECKS and NO CHANGES

*PREPRINT CONTACT, ECHO, HISTORY, and MODEL

*RESTART READ, WRITE, STEP, INC, END STEP, FREQUENCY and

To create a *RESTART card as model data

To create a *RESTART card as history data

12 HyperWorks 9.0 User's Guide - Abaqus Solver Interface Altair Engineering

Proprietary Information of Altair Engineering

Abaqus Card Supported Notes

*ORIENTATION NAME, SYSTEM The *ORIENTATION card needs a name

*SYSTEM On export, each *SYSTEM card is

*TRANSFORM TYPE and NSET On export, each *TRANSFORM card

Altair Engineering HyperWorks 9.0 User's Guide - Abaqus Solver Interface 13

Proprietary Information of Altair Engineering

· If neither HM_comp_by_property nor HM_set_by_property comments are present, HyperMesh

ORIENTATION NAME, SYSTEM The ORIENTATION card needs a name

SYSTEM On export, each SYSTEM card is

TRANSFORM TYPE and NSET On export, each TRANSFORM card