Ansys 51

Altair HyperMesh
Interfacing with ANSYS

Version 5.1
Contact Altair Engineering at:
Web site www.altair.com
FTP site Address: ftp.altair.com or ftp2.altair.com
Login: ftp
Password: <your e-mail address>
Location Telephone e-mail
North America 248.614.2425 hmsupport@altair.com
Germany 49.7031.6208.22 support@altair.de
India 91.80.658.8540 support@altair-eng.soft.net

91.80.658.8542
Italy 39.0832.315.573 support@altairtorino.it

39.800.905.595
Japan 81.3.5396.1341 aj-support@altairjp.co.jp
Scandinavia 46.46.286.2052 support@altair.se
United Kingdom 44.1327.810.700 support@uk.altair.com
2002 Altair Engineering, Inc. All rights reserved.
Trademark Acknowledgments:
HyperWorks, HyperMesh, OptiStruct, HyperForm, MotionView, HyperView, HyperGraph,

HyperOpt, HyperShape/Pro, StudyWizard, HyperView Player and Templex are registered
trademarks of Altair Engineering, Inc.
All other trademarks and registered trademarks are the property of their respective owners.
ANSYS Translation Overview
The HyperMesh ANSYS interface allows you to:
• Read an ANSYS ASCII database
• Create and edit an ANSYS ASCII database from within HyperMesh
• Preview and edit ANSYS cards after they are created
• Summarize ANSYS elements, loads, and properties
• Output an ANSYS ASCII database
• Convert an ANSYS binary results file into a HyperMesh binary results file that can be read into
HyperMesh for post-processing
• Assign macro commands to modify HyperMesh’s default ANSYS output
HyperMesh treats ANSYS as a card image code
HyperMesh supports ANSYS element types for STATIC, THERMAL, and MODAL analyses using
ANSYS versions 5.7 and below. In addition, ANSYS results files *.rst and *.rth are supported.
Warnings and error messages are written to a file called ansys.msg. Unrecognized lines are written
to a *.hmx file. These files are created in the directory from which HyperMesh is launched.
Importing Decks
Diagnostic messages are added to a file called ansys.msg, located in the directory from which
HyperMesh is launched. Errors or warnings are printed to this file.
The command.cmf file is also created and appended for each HyperMesh session. This file is
described in Tips and Techniques .
The *.hmx file contains the cards that are not recognized by the input translators.
NOTE The ansys.msg file is added during each read session. To conserve disk space, you
can delete these files as necessary.
Importing Multiple Decks

To import more than one deck into HyperMesh and then export a combined deck, or to create some
components in HyperMesh and then import a deck into HyperMesh to export a combined deck, you
must add the following commands to the last deck imported:
!HMOFFSET TYPE typeid
!HMOFFSET REAL realid
!HMOFFSET MAT matid
If a deck (a.ans) is imported into HyperMesh and you want to import another deck (b.ans), the above
three HMOFFSET commands should be added to the beginning of the b.ans deck before it is
imported. The typeid, realid and matid can be determined using Method #1 and/or Method #2
(described below). If the a.ans deck has NUMOFF commands in it, Method#1 can be used. If the
a.ans deck does not have NUMOFF commands, Method#2 should be used.
If components are created in HyperMesh and then a deck is imported into HyperMesh, the three
HMOFFSET commands should be added to the beginning of the deck before it is imported. The
typeid, realid and matid can be determined using the Method#2.
Altair Engineering Interfacing with ANSYS 1

Determining the typeid, realid and matid, used in HMOFFSET commands
Method #1
typeid = typeid of NUMOFFTYPE (NUMOFFTYPE, typeid)
realid = realid of NUMOFFREAL (NUMOFFREAL, realid)
matid = matid of NUMOFFREAL (NUMOFFREAL, matid)
Method #2
Do card edit for comps in HyperMesh. typeid is the maximum ET TYPE among all the comps.
Do card edit for comps and props. realid is the maximum R NSET value among all comps and props.
Do card edit for mats. Matid is the maximum MPDATA id or TBDATA id among all the mats.
To import data with the input translator:

1. Select the files panel.
2. Select the import subpanel.
3. Click EXTERNAL.
4. Click translator = and enter /ansys/ansys.exe, or click translator = again to browse the
directory structure to access the ansys.exe file.
5. Click filename = and enter the name of your ANSYS file, or click filename = again to browse the
directory structure for your file.
6. Click import.
Exporting Decks
The output translator outputs only the cards that the input translator recognizes. The CDWRITE
cards are output as regular format cards. The output translator writes only the numeric form of the
type in the ET card. For example, ET, 999, SHELL63 is written as ET, 999, 63.
The ansys.tpl template supports the following ANSYS element types:
1, 3, 4, 5, 8, 10, 12, 13, 14, 16, 18, 19, 20, 21, 22, 23, 24, 25, 28, 31, 32, 33, 34, 35, 42, 43, 44, 45,
46, 48, 49, 51, 52, 53, 54, 55, 57, 58, 60, 61, 63, 64, 66, 69, 70, 71, 72, 73, 75, 77, 78, 82, 83, 87,
90, 91, 92, 93, 95, 96, 97, 98, 99, 143, 151, 152, 169, 170, 171, 172, 173, 174, 181, 188, 189
The templates also support the ANSYS CP card (rigidlink) and the CERIG card (rigid element).
The templates write HyperMesh components (such as any unique combination of REAL, MAT, TYPE,
and SECNUM) as ANSYS components (CM card).
In order to maintain the HyperMesh component names and colors, the templates write out the
HyperMesh comments HMNAME and HMCOLOR for each HyperMesh component. The templates
write the loads in each HyperMesh load collector as ANSYS load steps.
Note For a new local coordinate system defined in HyperMesh and assigned an ID number
between 1 and 10, the templates shift the ID number by a factor of the maximum ID
number existing in the deck plus 10.
2 Interfacing with ANSYS Altair Engineering

Since ANSYS does not have a collectors format, it will not recognize collectors.
If you run a single load step analysis, it is recommended that you define all your loads using a single
load collector. If you have more than one load collector, use Organize to move all loads into one
load collector and delete the remaining load collectors.
If you have more than one load collector, ANSYS recognizes only those loads which are defined in
the last load collector. The other load collectors are written by ANSYS to ANSYS ASCII load step
files, which may be re-imported into ANSYS during the /SOLUTION phase.
To create an analysis deck via a template:

1. Select the files panel.
2. Select the export subpanel.
3. Click filename = and enter the name of the output file.
4. Click TEMPLATE.
A new input field, template =, is displayed if not already displayed.
5. Click template = and specify the file name of the template file (for 3-D problems,
../hm21/template/feoutput/ansys/ansys.3d).
6. Click all or displayed to output only some or all contents of the deck.
7. Click write.
Updating Element Types

The ANSYS macro allows you to change the ANSYS element type for elements in selected
components.
Note: The ansys.tpl template file must be loaded before using this macro.
To load the ANSYS macro:

1. On the permanent menu, click options.
2. Select menu config.
3. For macro file =, select or type ../scripts/ansys/ansys.mac.
4. Click retrieve.
5. Click return.
The ANSYS macro is displayed on the macro menu page.
To update ANSYS element types:

1. Click update elem types macro button.
2. Click comps.

3. Select the components that need to have the element types changed.
4. Click select.
5. Click return.
The element types panel is displayed in the macro menu area.

6. Select the element type.
The ANSYS element number is displayed in the elem type = text box.
or
Type a valid ANSYS element number in the elem type = text box.
7. Click update to update the element type for the elements in the selected components.
or
Click return to return to the ANSYS macro menu without updating the elements.
8. Repeat steps 1-7 to update the element type for each additional element.
To load HyperMesh macros:

1. On the permanent menu, click options.
2. Select menu config.
3. For macro file =, select or type hm.mac.
4. Click retrieve.
5. Click return.
Supported Cards
The HyperMesh input translator recognizes the ANSYS cards listed below. If HyperMesh finds an
unsupported field in a card, a message is displayed on the status bar. The messages are also
printed to the file ansys.msg. General slash commands, SOLUTION commands, POST1
commands, and POST26 commands are referred to as control cards. Unrecognized cards are
written to a *.hmx file.
ANTYPE
• Type, Status
/BATCH
• List
BF
• FLUE and HGEN labels are supported under the flux panel.

• TEMP (Structural temperatures) label is supported under the temperatures panel.
BFUNIF
• TEMP, FLUE, and HGEN labels are supported.
• You can create or edit this as a control card.
CE
CERIG, MASTE, SLAVE
• Ldof, Ldof2, Ldof3,Ldof4,Ldof5
/COM
CP, NSET
• Lab, NODE1, NODE2,... NODE9
CP, R5.0, LENGTH, NCP
• Dlab, NODE1, NODE2,... NODE7
CSYS, KCN
D, NODE
• Lab, VALUE, NEND, NINC

• NODE = ALL/P not supported
• Lab = ALL/UX/UY/UZ/ROTX/ROTY/ROTZ, TEMP supported
DOF
• You can create or edit this as a control card
EBLOCK
• N, SOLID
EBLOCK
• 19, SOLID (19i7)
EMORE
• Q, R, S, T, U, V, W, X
EN

• IEL, I, J, K, L, M, N, O, P
• I = P not supported
EN
• R5.1, Type, NumN, I1, I2, I3, I4, I5, I6, I7, I8
EN
• R5.5, ATTR, #nodes, mat, secnum, esys, ele#, solid, death, exclude
ET, ITYPE
• Ename
• Where the ET card supports the following element types (both alphanumeric and numeric formats
are recognized, for example SHELL43 or 43):
1, 3, 4, 5, 8, 10, 12, 13, 14, 16, 18, 19, 20, 21, 22, 24, 25, 31, 32, 33, 34, 35, 42, 43, 44, 45, 48, 49,
51, 52, 53, 54, 55, 57, 58, 60, 63, 64, 66, 69, 70, 71, 72, 73, 75, 77, 78, 82, 83, 87, 90, 92, 93, 95,
96, 97, 98, 99, 143, 152, 169, 170, 171, 172, 173, 174, 188, 189.
EXPASS
• Key
F, NODE
• Lab, VALUE, VALUE2

FINISH
IC, NODE
• Lab, VALUE, NEND, NINC

• Lab = ALL/UX/UY/UZ/ROTX/ROTY/ROTZ, TEMP supported
KEYOPT
• ITYPE, KNUM, VALUE
LOCAL
• KCN, KCS, XC, YC, ZC, THXY, THYZ, THZX, PAR1, PAR2
• Even if KCN>10, HyperMesh adds 10 to the current value

LOCAL
• R5.0, Type, NCSY, CSYTYP, VAL1, VAL2, VAL3

• Type = PRM not supported
MAT
• MAT
MODE
• MODE, ISYM
MODOPT
• Method, NMODE, FREQB, FREQE, PRMODE, Nrmkey

MP
• Lab, MAT, C0, C1, C2, C3, C4
MPDATA
• Lab, MAT, STLOC, C1, C2, C3, C4, C5, C6
MPDATA
• R5.0, LENGTH, Lab, MAT, STLOC, VAL1, VAL2, VAL3
MPTEMP
• STLOC, T1, T2, T3, T4, T5, T6
MPTEM
• R5.0, LENGTH, STLOC, TEMP1, TEMP2, TEMP3
• NODE, X, Y, Z, THXY, THYZ, THZX
• R5.1, Type, NODE, SOLID, VAL1, VAL2, VAL3
• R5.3, LOC, NODE, SOLID, NODLOC, VAL1, VAL2, VAL3

NBLOCK
• N, SOLID
POST1
/PREP
PRESOL
• NSET, R1, R2, R3, R4, R5, R6
• R5.0, NSET, Type, STLOC, VAL1, VAL2, VAL3
REAL
• NSET
RLBLOCK
• #sets, maxset, maxsize, 7

• (2i8, 6g16.9)
• (7g16.9)
RMODIF
• NSET, STLOC, V1, V2, V3, V4, V5, V6
RMORE
• R7, R8, R9, R10, R11, R12
RSYS
• KCN
SECDATA
• Geometrical data for the section types supported by SECTYPE.

SECNUM
SECOFFSET
• CENT, SHRC, ORIGIN, or USER.
SECTYPE
• SUBTYPE (RECT, QUAD, CSOLID, CTUBE, CHAN, I, 2, L, T, HATS, HREC, ASEC),

SECNAME.
SOLVE
SFE
• ELEM, LKEY, Lab, KVAL, VAL1, VAL2, VAL3, VAL4

• Lab = PRES and CONV supported
• Negative PRES values are supported
SFE
• ELEM, LKEY, Lab, Key, R5.0

• Lab = PRES CONV (both film coefficient and bulk temperature and HFLUX)
/SOLU
SOLU
TB
• TB_LAB, ID, NTEMP, NPTS, TBOPT, EOSOPT
TBDATA
• STLOC, C2(i)
TBTEMP
• TEMP, KMOD
/TITLE

TOTAL
TREF
TUNIF

NOTE HyperMesh creates one component collector for every unique combination of Type,
Real, Mat, and SECNUM. Property collectors are created for 1-D element types 1, 3, 4,
8, 10, 12, 14, 16, 18, 20, 21, 24, 31, 32, 33, 34, 44, 51, 52, 71, 188, and 189.
HyperMesh does not support surface loads on 1-D elements, except for SHELL51.
Material collectors are also created for each material ID encountered. The component in
HyperMesh is different from the component (CM) in ANSYS.
Card Previewer
The HyperMesh ANSYS interface includes the template, ansys.tpl. This template must be loaded
to display and edit ANSYS cards.
The ansys.tpl template supports the following ANSYS element types:
1, 3, 4, 5, 8, 10, 12, 13, 14, 16, 18, 19, 20, 21, 22, 23, 24, 25, 28, 31, 32, 33, 34, 35, 42, 43, 44, 45,
46, 48, 49, 51, 52, 53, 54, 55, 57, 58, 60, 61, 63, 64, 66, 69, 70, 71, 72, 73, 75, 77, 78, 82, 83, 87,
90, 91, 92, 93, 95, 96, 97, 98, 99, 143, 151, 152, 169, 170, 171, 172, 173, 174, 181, 188, 189
The templates also support the ANSYS CP card (rigidlink) and the CERIG card (rigid element).
The card image element names have been modified. The current names are the full ANSYS names.
For example, the name ETR42 has been modified to PLANE42. The elements are sorted by their
number.
The ESYS (Element Coordinate System) has been added to the element card previewer.
To display and edit ANSYS cards:

1. Select the global panel.
2. Select the template you want to use in the template file= field.
To preview an ANSYS card:

• Select the card panel on the permanent menu.

Results Translation
hmansys translates a binary ANSYS results file into a HyperMesh binary results file. The syntax to
run the translator is:
hmansys [options] <inputfile> <outputfile> <modelfile>
One or more of the following options can be used. Use the command hmansys –u to obtain these
options.
Flag Meaning
-d Displacements
-rf Reaction Forces
-rm Reaction Moments
-sx1 X Stress (T)
-sy1 Y Stress (T)
-sz1 Z Stress (T)
-sxy1 XY Stress (T)
-syz1 YZ Stress (T)
-sxz1 XZ Stress (T)
-sx2 X Stress (B)
-sy2 Y Stress (B)
-sz2 Z Stress (B)
-sxy2 XY Stress (B)
-syz2 YZ Stress (B)
-sxz2 XZ Stress (B)
-sx X Stress (max(T,B))
-sy Y Stress (max(T,B))
-sz Z Stress (max(T,B))
-sxy XY Stress (max(T,B))
-syz YZ Stress (max(T,B))
-sxz XZ Stress (max(T,B))
-ntemp Nodal Temperatures
-vonmises1 von Mises Stress (T)
-vonmises2 von Mises Stress (B)
-vonmises von Mises Stress (max(T,B))
-ps1t Principal Stress 1 (T)
-ps1b Principal Stress 1 (B)
-ps1 Principal Stress 1 (max(T,B))
-snx1 X Strain (T)
-sny1 Y Strain (T)
-snz1 Z Strain (T)
-snxy1 XY Strain (T)
-snyz1 YZ Strain (T)
-snxz1 XZ Strain (T)
-snx2 X Strain (B)
-sny2 Y Strain (B)
-snz2 Z Strain (B)
-snxy2 XY Strain (B)

-snyz2 YZ Strain (B)
-snxz2 XZ Strain (B)
-snx X Strain (max(T,B))
-sny Y Strain (max(T,B))
-snz Z Strain (max(T,B))
-snxy XY Strain (max(T,B))
-snyz YZ Strain (max(T,B))
-snxz XZ Strain (max(T,B))
-psn1t Principal Strain 1 (T)
-psn1b Principal Strain 1 (B)
-psn1 Principal Strain 1 (max(T,B))
-psnvp1 Principal Strain1(vec.mode)
-psvp1 Principal Stress1(vec.mode)
-snpx1 X Plastic Strain (T)
-snpy1 Y Plastic Strain (T)
-snpz1 Z Plastic Strain (T)
-snpxy1 XY Plastic Strain (T)
-snpyz1 YZ Plastic Strain (T)
-snpxz1 XZ Plastic Strain (T)
-snpx2 X Plastic Strain (B)
-snpy2 Y Plastic Strain (B)
-snpz2 Z Plastic Strain (B)
-snpxy2 XY Plastic Strain (B)
-snpyz2 YZ Plastic Strain (B)
-snpxz2 XZ Plastic Strain (B)
-snpx X Plastic Strain (max(T,B))
-snpy Y Plastic Strain (max(T,B))
-snpz Z Plastic Strain (max(T,B))
-snpxy XY Plastic Strain (max(T,B))
-snpyz YZ Plastic Strain (max(T,B))
-snpxz XZ Plastic Strain (max(T,B))
-psnp1t Principal Pl. Strain 1 (T)
-psnp1b Principal Pl. Strain 1 (B)
-psnp1 Prin. Pl. Strain 1 (max(T,B))
-sntx1 X Thermal Strain (T)
-snty1 Y Thermal Strain (T)
-sntz1 Z Thermal Strain (T)
-sntxy1 XY Thermal Strain (T)
-sntyz1 YZ Thermal Strain (T)
-sntxz1 XZ Thermal Strain (T)

-sntx2 X Thermal Strain (B)
-snty2 Y Thermal Strain (B)
-sntz2 Z Thermal Strain (B)
-sntxy2 XY Thermal Strain (B)
-sntyz2 YZ Thermal Strain (B)
-sntxz2 XZ Thermal Strain (B)
-sntx X Thermal Strain (max(T,B))
-snty Y Thermal Strain (max(T,B))
-sntz Z Thermal Strain (max(T,B))
-sntxy XY Thermal Strain (max(T,B))
-sntyz YZ Thermal Strain (max(T,B))
-sntxz XZ Thermal Strain (max(T,B))
-psnt1t Principal Th. Strain 1 (T)
-psnt1b Principal Th. Strain 1 (B)
-psnt1 Prin. Th. Strain 1 (max(T,B))
-swstrain Swelling strain
-epeq1 Av. Eq. Plastic Strain (T)
-epeq2 Av. Eq. Plastic Strain (B)
-epeq Av. Eq. Pl. Strain (max(T,B))
-altids Use alternate element ids. (default off)
-noconv Do not transform to global (default off)
-v53 Translate version5.3 rst file (default off)
-disk Translation is performed on disk (default off).
-size Number of entities (10000 default).
-file Scratch file name (default off).
-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.
If the size of the binary file is too large for hmansys to use, use the following option:
hmansys -disk -size 10000 -file /tmp/scratch.tmp
In addition, the following parameters are also available when the results translation is not performed
on the analysis machine and when the results file is binary. One of these parameters may need to be
specifed to indicate 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.

Summary Templates
HyperMesh contains the following summary templates:
../templates/hw5.0/summary/ansys/components Reviews components of the
current database containing
1-D, 2-D and 3-D elements
../templates/hw5.0/summary/ansys/elements.2d Reviews 2-D elements of the

current database
../templates/hw5.0/summary/ansys/elements.3d Reviews 3-D elements of the

current database
../templates/hw5.0/summary/ansys/loads Reviews the loads of the

current database
../templates/hw5.0/summary/ansys/ctr_of_gravity Calculates the model’s center

of gravity
../templates/hw5.0/summary/ansys/mom_of_inertia Determines area properties
NOTE To use the mom_of_inertia template, create a planar area with shell43/shell63 elements
(quads and trias) in the x-y plane.
To obtain a summary of the HyperMesh database:

1. Select the summary panel on the Post page.
2. Click template = and specifying the template.
3. Click summary.
Creating Cards
Select the ansys.tpl template before creating ANSYS cards. To load the corresponding template,
enter the template name in the template = field on the global panel.
* Control Cards (General Slash, SOLUTION, POST1, and POST26 cards)
To create a TITLE card:

1. Select cntl cards on the Post page.
2. Click TITLE and enter the title string.
3. Click return.
To create a node card:

1. Select the create nodes panel on the geom page.

2. Select the type in subpanel enter the coordinate values for the node.
3. Click create node.
4. Click return.
NOTE It is not possible to assign a system ID unless a coordinate system was previously
created.
To review a node card:

1. Select the card panel on the permanent menu.
2. Click nodes.
3. Click nodes and select a node by ID or pick the node from the model.
4. Click edit.
To delete nodes that are not associated with any elements:

1. Select the temp nodes panel on the geom page.
2. Click nodes and select the nodes.
3. Click clear.
To display a node ID:

1. Select the numbers panel on the Tool page.
2. Select nodes as the entity type to use.
3. Pick the nodes for which you want to display the IDs.
4. Click on.
To create a system card:

1. Ensure that at least three nodes are available to create a coordinate system.
2. Select the systems panel on the BCs page.
3. Select the create subpanel.
4. Click origin.
5. Pick the node that indicates the origin. (If the nodes are not visible, use the temp nodes panel to
add all nodes.)
6. Pick the node that indicates the x-direction.
7. Pick the node that indicates the x-y plane.
8. Select the coordinate system type you want to create: rectangular, spherical, or cylindrical.

9. Click create.
NOTE HyperMesh automatically assigns a system ID.
To assign a coordinate system to a set of nodes:

1. Ensure that the coordinate system is created.
2. Select the systems panel on the BCs page.
3. Select the assign subpanel.
4. Click nodes.
5. Pick the nodes that need to be assigned.
6. Click systems.
7. Pick the coordinate system.
8. Click set reference.
NOTE HyperMesh creates CSYS cards as necessary.
To delete a coordinate system:

1. Select the delete panel on the Tool page.
2. Click the switch and select systs for the type of entity to be deleted.
3. Pick the system.
4. Click delete.
To create an ET card and an R card for shell/solid elements:

1. Select the collectors panel.
3. Click the upper switch and select comps.
4. Click name = and enter a component name.
5. Click card image = and select the card image type.
6. Click create/edit.
7. Enter the relevant data for the ET and R cards.
8. Click return.
To create an ET card and an R card for 1-D elements:

(1, 3, 4, 8, 10, 12, 14, 16, 18, 20, 21, 31, 32, 33, 34, 51, 52, 71):

HyperMesh requires that 1-D elements belong to a component collector and a property collector. To
create a component collector, follow the steps on how to create an ET card and R card for shell/solid
elements . For 1-D elements, this procedure creates only the ET card. To create the R card, follow
the steps on how to create a property collector .
To create a property collector:

3. Click the upper switch and select props.
4. Enter a property name after name =.
6. Click material = and select a mat collector.
8. Enter the relevant data for the R card.
9. Click return.
To create a MAT card:

3. Click the upper switch and select mats.
4. Click name = and enter the name corresponding to the component collector for shell/solid
elements or pick the name corresponding to the property collector for 1-D elements.
7. Enter the relevant data for the MAT card.
8. Click return.
To create a shell/solid element card:

1. Click the header/status bar or use the global panel to determine if the element to be created
should belong to the active component.
2. Select the edit elements panel on the 2-D page.
4. Select the element type (quad, hex, tria etc.).
5. Pick the nodes in the appropriate sequences to create the element.

6. Click the elem types panel on the 1-D, 2-D or 3-D page. This updates the newly created element
to the appropriate ANSYS type
For example, to update the newly created tetra4, click tetra4. Select the appropriate ANSYS type
(SOLID45, SOLID69, SOLID70, or SOLID72). Select the elements to update and click update.
To reassign newly created elements to a previously created component

collector:
1. Select the organize panel.
2. Click the switch and select elems.
3. Select the element(s) you want to move to a different component.
4. Click destination = and select the appropriate component collector.
5. Click move.
To create a 1-D element (a 2-node or 3-node BEAM4):

1. Select the bars panel on the 1-D page.
2. Select the bar2 subpanel for both two-noded and three-noded beams.
The bar3 subpanel is for curved beam elements and is not supported for ANSYS.
3. Click property = and select a previously created property collector.
4. For a 2-noded BEAM4:
í Click the left-most switch and select components.
í Enter x = 1, y = 0, z = 0.
í Click the two nodes consecutively.

The element is displayed.
5. For a 3-noded BEAM4:
í Click the left-most switch and select node.
í Select z direction.
í Click the two nodes on the direction node panel.

The element is displayed.
This completes the creation of a two-node BEAM4 element. Assign the 1-D elements to the
appropriate component collector (follow the procedure for how to create a shell/solid element card). If
a third node is used to create a BEAM4 element, HyperMesh generates an appropriate third node
while writing. In addition to organizing the 1-D elements (1, 3, 4, 8, 10, 12, 14, 16, 18, 20, 21, 31, 32,
33, 34, 51,52, 71) into the appropriate component collectors, update the elements into the appropriate
property collectors.
To update the elements to the appropriate property collector:

1. Select the bars panel on the 1-D page.

2. Select the update subpanel.
3. Specify vector, components, or nodes.
4. Pick the set of bar elements.
5. Click property = and select the appropriate property collector.
6. Click update.
7. Select property.
8. Click update.
To create a rigidlink element (CP card):

1. Select the rigids panel on the 1-D page.
3. Click the switch and select multiple nodes.
4. Click node after independent: and select the node by ID or by picking it on the screen.
5. Pick the dependent nodes.
6. Select the dof (one option per element).
7. Click the rightmost create.
NOTE HyperMesh assigns an NSET ID to this rigidlink element. By default, this element is
assigned to the active component. You can create a new component and reassign the
elements to that collector.
To preview the newly created CP card:

1. Click card on the permanent menu panel.
2. Click the switch and select elems.
3. Pick one element.
4. Click config.
5. Select rigidlink.
6. Click edit.
HyperMesh displays the CP card in a separate panel.
To create a rigid element (CERIGID card):

1. Select the rigids panel on the 1-D page.

3. Click the switch and select single node.
4. Pick the master and slave nodes.
NOTE By default, this element is assigned to the active component. You can create a new
component and reassign the elements to that collector. Update the newly created
rigid element to the appropriate dof set.
To create a constraint card:

1. Select the constraints panel on the BCs page.
3. Pick the set of nodes.
4. Select the appropriate dof to constrain.
To create a force card:

1. Select the forces or pressures panel on the BCs page.
3. Pick the set of nodes.
4. Select the appropriate dof to constrain.
NOTE Unlike elements, the systems and forces do not have to be organized into collectors.
HyperMesh creates a system collector and a load collector and assigns the systems
and loads to those collectors. You can organize the loads into several collectors.
HyperMesh does not support surface loads on 1-D elements, with the exception of
SHELL51 type elements.
To create the CE card:

1. Select the equations panel on the BCs page.
3. Pick a dof, weight and constant.
4. Click the first node (dependent).
5. Click the remaining nodes (independent).
6. Click create.
The equation is displayed.
7. Click update and reassign the appropriate weights and dofs for each node.

Programming HyperMesh Templates
You can modify the HyperMesh output template, ansys.tpl, to add functions not included with the
templates.
The following table maps HyperMesh elements to the corresponding ANSYS elements.
Config Name Config Type ANSYS Element

Mass Element 1 1 MASS21
2 MASS71
13 TARGE169
Plot Element 2 3 CONTA171
Spring Element 21 1 COMBIN14
Bar Element 60 2 BEAM3

1 BEAM4
3 PIPE16
4 PIPE18
11 SURF19
9 BEAM23
6 BEAM24
7 BEAM44
SHELL51
10 BEAM54
5 PIPE60
SHELL61
12 SURF151
13 TARGE169
8 BEAM188
Rod Element 61 5 LINK1

1 LINK8
2 LINK10
4 PIPE20
6 LINK31
7 LINK32

8 LINK33
9 LINK34
10 FLUID66
Bar3 Element 63 13 TARGE169

2 CONTA172
1 BEAM189
Gap Element 70 2 CONTAC12

1 CONTAC52
Tria3 Element 103 3 PLANE13

6 PLANE25
4 PLANE42
2 SHELL43
8 CONTAC48
5 PLANE55
7 SHELL57
1 SHELL63
9 PLANE75
10 SHELL143
16 TARGE170
13 CONTA173
11 SHELL181
Quad4 Element 104 3 PLANE13

15 SURF22
6 PLANE25
12 SHELL28
4 PLANE42
2 SHELL43
8 CONTAC49
5 PLANE55
7 SHELL57
1 SHELL63
9 PLANE75

10 SHELL143
14 SURF152
16 TARGE170
13 CONTA173
11 SHELL181
Tria6 Element 106 7 PLANE35

9 PLANE53
2 PLANE77
8 PLANE78
1 PLANE82
3 PLANE83
6 SHELL91
4 SHELL93
5 SHELL99
16 TARGE170
10 CONTA174
Quad8 Element 108 15 SURF22

9 PLANE53
2 PLANE77
8 PLANE78
1 PLANE82
3 PLANE83
6 SHELL91
4 SHELL93
5 SHELL99
14 SURF152
16 TARGE170
10 CONTA174
Tetra4 Element 204 1 SOLID45

6 SOLID46
11 HYPER58
7 SOLID64
4 SOLID69

3 SOLID70
2 SOLID72
12 SOLID73
5 SOLID96
8 SOLID97
Penta6 Element 206 2 SOLID5

1 SOLID45
6 SOLID46
11 HYPER58
7 SOLID64
4 SOLID69
3 SOLID70
12 SOLID73
5 SOLID96
8 SOLID97
Hex8 Element 208 2 SOLID5

1 SOLID45
6 SOLID46
11 HYPER58
7 SOLID64
4 SOLID69
3 SOLID70
12 SOLID73
5 SOLID96
8 SOLID97
Tetra10 Element 210 5 SOLID87

2 SOLID90
3 SOLID92
1 SOLID95
4 SOLID98
Penta15 Element 215 2 SOLID90

1 SOLID95

Hex20 Element 220 2 SOLID90
1 SOLID95
Tips and Techniques

The operations performed in HyperMesh can also be saved as a compact HyperMesh binary file
using the files subpanel on the files panel.
To determine the mass of your finite element model, use the mass calc panel on the Tool page.
Select the ansys.tpl template file through the global panel. The mass calculation is supported for
the following element type numbers: 1, 3, 4, 5, 8, 10, 13, 16, 18, 19, 20, 21, 22, 23, 24, 25, 28, 31, 32,
33, 42, 43, 44, 45, 46, 51, 53, 54, 55, 57, 58, 60, 61, 63, 64, 66, 69, 70, 71, 72, 73, 75, 77, 78, 82, 83,
87, 90, 91, 92, 93, 95, 96, 97, 98, 99, 143, 152, 173, 174, 181
Each operation in HyperMesh results in an ASCII command that is added to a command.cmf file.
This file is useful if your computer shuts down while working in HyperMesh. You can restore your
previous work by reading this file with the command function, located on the command panel. You
can delete this file if it requires too much disk space.
The command.cmf file can also be used to store repetitive HyperMesh operations. If you deal with
the same set of geometrical and material properties, you can record the creation of these collectors
(steel plate, foam solids, aluminum rods, and so on) into series of command files and read them as
needed.
The ANSYS template is associated with the new composites panel. Using this panel for laminated
elements, such as SHELL99, enables the following:
• Element orientation by two methods:
í By system - assigns a system to the element (set ESYS for the element)
í By vector - projects a vector on the element plane. A coordinate system, in which the x-axis
í is parallel to the defined vector, is created and assigned to the element as ESYS.
í The by system axis and by angle options are not available for this template.
• Visualization of the element orientation
• Visualization of the ply direction on a layer-by-layer basis. Visualizes the angles defined in the R
card with respect to the element orienation.
Creating Target/Contact Element Pairs

The main objective of the HM-ANSYS contact wizard is to automate the procedure to create ANSYS
surface-to-surface Target/Contact element-pairs. The wizard allows you to create either 2-D
Target/Contact pairs or 3-D Target/Contact pairs. It supports both first order elements (TARGE169 &
CONTA171 for 2-D, TARGE170 & CONTA173 for 3-D) and second order elements (TARGE169 &
CONTA172 for 2-D, TARGE170 & CONTA174 for 3-D).
Additional objectives of the HM-ANSYS contact wizard are:

• Definition of the analysis options (KEYOPTs) for both the Target and Contact elements.
• Setting the values for a common property set (REAL constant set) for each pair.
• Creating new material for each pair or pointing the pair to an existing material.
• Reviewing the normal of the Target/Contact elements and flipping them if necessary.
The following means are used to achieve these objectives:
• A combination of HyperMesh technology and a TCL/TK window GUI.
• The Target/Contact body edges/faces are extracted automatically depending upon the model
type (2-D or 3-D analysis). For 2-D models, the target/contact elements are selected after
extracting the edges of the target/contact bodies (HyperMesh components). For 3-D models,
the target/contact elements are selected after extracting the faces of the target/contact bodies
(HyperMesh components).
• Appropriate target or contact components are created automatically with the selected target
or contact surface elements, respectively. The ANSYS Element Type (HyperMesh
component card image) is determined automatically depending upon the target or contact
body type.
• You may define both target and contact KEYOPTs by selecting them using toggles.
• A property collector (ANSYS REAL constant set) is created if the Target/Contact bodies are
2-D. Both the target and contact components point to this property collector.
• For 3-D Target/Contact bodies, the same real constant set (with same ID) is created at the
component level for both the target and contact components.
• You have the option of pointing the Target/Contact pair to a new material collector that is
created automatically, or you can point the pair to an existing material.
• You can review the normals of either the target element or the contact element, or both the
target element and contact element, while controlling the vector size. If the normals are not
pointing to each other, they can be flipped.
To use the contact wizard:

1. Be sure the following conditions are met:
í The loaded model contains 2-D ANSYS PLANE elements or 3-D ANSYS SOLID elements.
í The ANSYS template ansys.tpl is loaded in HyperMesh.
2. Consider the following restriction:
For each Target/Contact pair, either first order or second order elements might be selected as
CONTACT bodies, but not both of them.
Note: This restriction does not apply for TARGET bodies because TARGE169 (2-D) and
TARGE170 (3-D) are both first and second order element types.

3. Load the HM-ANSYS Contact Wizard.
í On the permanent menu, click options.
í Select menu config.
í For macro file =, select or type ../scripts/ansys/ansys.mac.
í Click retrieve.
í Click return.
The HM-ANSYS macros are displayed on the macro menu page.

4. Click the contact wizard macro button to launch the HM-ANSYS Contact Wizard.
5. Click on the Help button to access information regarding the current dialog.
See also
HM-ANSYS Contact Wizard 2-D Tutorial
HM-ANSYS Contact Wizard 3-D Tutorial

Ansys 51

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Ansys 51

Enviado por

Direitos autorais:

Formatos disponíveis

Altair HyperMesh

Interfacing with ANSYS

Web site www.altair.com

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

Password: <your e-mail address>

Location Telephone e-mail

North America 248.614.2425 hmsupport@altair.com

Germany 49.7031.6208.22 support@altair.de

India 91.80.658.8540 support@altair-eng.soft.net

Italy 39.0832.315.573 support@altairtorino.it

Japan 81.3.5396.1341 aj-support@altairjp.co.jp

Scandinavia 46.46.286.2052 support@altair.se

United Kingdom 44.1327.810.700 support@uk.altair.com

2002 Altair Engineering, Inc. All rights reserved.

HyperWorks, HyperMesh, OptiStruct, HyperForm, MotionView, HyperView, HyperGraph,

Importing Multiple Decks

Altair Engineering Interfacing with ANSYS 1

To import data with the input translator:

2. Select the import subpanel.

2 Interfacing with ANSYS Altair Engineering

To create an analysis deck via a template:

2. Select the export subpanel.

3. Click filename = and enter the name of the output file.

Updating Element Types

To load the ANSYS macro:

2. Select menu config.

3. For macro file =, select or type ../scripts/ansys/ansys.mac.

The ANSYS macro is displayed on the macro menu page.

To update ANSYS element types:

Altair Engineering Interfacing with ANSYS 3

The element types panel is displayed in the macro menu area.

To load HyperMesh macros:

2. Select menu config.

3. For macro file =, select or type hm.mac.

4 Interfacing with ANSYS Altair Engineering

CERIG, MASTE, SLAVE

• Ldof, Ldof2, Ldof3,Ldof4,Ldof5

• Lab, NODE1, NODE2,... NODE9

CP, R5.0, LENGTH, NCP

• Dlab, NODE1, NODE2,... NODE7

• Lab, VALUE, NEND, NINC

• You can create or edit this as a control card

• 19, SOLID (19i7)

Altair Engineering Interfacing with ANSYS 5

• Lab, VALUE, VALUE2

• You can create or edit this as a control card

• Lab, VALUE, NEND, NINC

• ITYPE, KNUM, VALUE

6 Interfacing with ANSYS Altair Engineering

• R5.0, Type, NCSY, CSYTYP, VAL1, VAL2, VAL3

• Method, NMODE, FREQB, FREQE, PRMODE, Nrmkey

• Lab, MAT, C0, C1, C2, C3, C4

• Lab, MAT, STLOC, C1, C2, C3, C4, C5, C6

• R5.0, LENGTH, Lab, MAT, STLOC, VAL1, VAL2, VAL3

• STLOC, T1, T2, T3, T4, T5, T6

• R5.0, LENGTH, STLOC, TEMP1, TEMP2, TEMP3

• NODE, X, Y, Z, THXY, THYZ, THZX

• R5.1, Type, NODE, SOLID, VAL1, VAL2, VAL3

• R5.3, LOC, NODE, SOLID, NODLOC, VAL1, VAL2, VAL3

Altair Engineering Interfacing with ANSYS 7

• You can create or edit this as a control card

• You can create or edit this as a control card