Beruflich Dokumente
Kultur Dokumente
Postprocessing
14.5 Release
ANSYS LS-DYNA
in Mechanical APDL
2012 ANSYS, Inc.
February 5, 2013
Release 14.5
Objectives
This lecture concerns Postprocessing. Both the POST1 and POST26 ANSYS
postprocessors are illustrated. Accessing LS-DYNA ASCII results file data
is also covered. Since the LS-PREPOST postprocessor from LSTC is
unsupported by ANSYS, Inc., it is only discussed in the workshop
accompanying this lecture.
Topics:
A. POST1 Overview
February 5, 2013
Release 14.5
A. POST1 Overview
POST1, the ANSYS General Postprocessor, behaves essentially the same for ANSYS
LS-DYNA as it does for implicit ANSYS. LS-DYNA writes results for the entire
model to the binary Jobname.RST file. The SET command reads the specified
results set into the database for subsequent postprocessing:
General Postproc > Read Results > Last Set
In contrast, the POST26 Time History Postprocessor is used to view a small subset
of the model (limited by the EDHIST command) much more often via the contents
of the binary Jobname.HIS file. The frequency at which data is written to this
history file is based on the EDHTIME command setting. The Time History
Postprocessor will be discussed in more detail, later.
February 5, 2013
Release 14.5
February 5, 2013
Release 14.5
To get results closer to the surface, more layers should be used through
the thickness of the shell. The NIP real constant determines how many
integration points exist through the shell thickness, but the EDINT
command determines which of these layers data is saved for.
2012 ANSYS, Inc.
February 5, 2013
Release 14.5
Another peculiarity is in how stress and strain data is saved. For a five
layer shell in which data is saved for each layer (NIP=5 and EDINT=5),
the stress data is available for all five layers, but LS-DYNA only writes
out strain data for the top and bottom layers. Therefore, LAYER=2
represents the second layer for stress, but the fifth layer (in this case)
for strain. Layers are counted from the bottom surface of the shell.
February 5, 2013
Release 14.5
RSYS, 0
RSYS, 0
PLNSOL,S,X
February 5, 2013
RSYS, 1
PLNSOL,S,Y
PLNSOL,S,Y
Release 14.5
Shell stresses can be rotated into another coordinate system using RSYS, except for
composite shells (KEYOPT(3) = 1). The data saved on some of the LS-DYNA ASCII
files (e.g., the elout file) can be presented in a different coordinate system than
discussed above.
Local coordinate systems defined with the EDLCS command must be redefined
with the LOCAL command in order to be interpreted by RSYS. Elements that do
not support RSYS should be unselected before issuing the RSYS command to avoid
POST1 error messages. Finally, the RSYS command is not applicable to POST26.
February 5, 2013
Release 14.5
Element failure based on equivalent plastic strain is the most common mechanism
for this feature. An example involving eroding contact is shown below. LS-PREPOST
can also be used to view element failure.
PUNCH
BLANK
DIE
2012 ANSYS, Inc.
February 5, 2013
Release 14.5
D. Animation in POST1
Use the ANDATA and ANMRES macros to animate results in POST1:
Utility Menu > PlotCtrls > Animate > Over Results
Note: The ANDATA.MAC macro is unusable for all but the most simple
models. Until this problem is corrected, you will need to use
interpolation (via ANTIME.MAC) to animate your models.
February 5, 2013
10
Release 14.5
E. POST26 Overview
POST26, the ANSYS Time History Postprocessor, tracks data over the
entire span of the analysis. Although the Jobname.RST file may be
processed, the Jobname.HIS file is most often used, since the latter
generally contains data saved at many more time steps, albeit for a
smaller subset of the model (specified by the EDHIST command):
TimeHist Postpro > Variable Viewer > File > Open > Explicit Dynamics
Results (*.his) > Jobname.his > Open > Jobname.db > Open
February 5, 2013
11
Release 14.5
The LAYERP26 command identifies the layer for which POST26 results data is
requested. As mentioned previously, the EDINT command determines how much
integration point data is saved to the disk.
February 5, 2013
12
Release 14.5
GLSTAT
- Global statistics data (Total model basis)
MATSUM
- Material energies summary (Part ID basis)
SPCFORC - Single point constraint reaction forces (Node basis)
RCFORC
- Resultant interface forces (Contact entity basis)
SLEOUT
- Sliding interface energies data (Contact entity basis)
RBDOUT
- Rigid Body Data (Part ID basis)
NODOUT
- Node Data (Node basis)
Most of these (e.g., MATSUM), can be read via the Variable Viewer:
February 5, 2013
13
Release 14.5
When reading most of these files, additional information is required. For example,
the SPCFORC file requires the specification of a node number for which the reaction
force data is desired.
February 5, 2013
14
Release 14.5
For the desired ASCII output data to be available, several things must
be done before the solution is initiated:
The output file needs to be requested ( EDOUT, SPCFORC )
The appropriate restraint, etc. needs to exist ( D, 1, ALL, 0.0 )
The entity must belong to a history file component ( EDHIST, NODE_1 )
February 5, 2013
15
Release 14.5
G. Postprocessing Workshop
This workshop consists of the following problem:
WS08. Bending a Pipe with a Rigid Punch
Please refer to your Workshop Supplement for instructions.
February 5, 2013
16
Release 14.5