HyperWorksEngineering Solutions is a modeling and visualization environment for NVH, Crash, CFD, Drop Test and Aerospace using best-in-class solver
technology.
NVH analysis is a special form of physical analysis where the understanding of motion, energy and force transfer are the
primary means of root cause identification and problem solving.
Set parent modules with CMS SE representation in H3D format to be used for analysis in lieu of child module representations
when rolled up, or use the child representations when rolled down.
To manage any of the modules shown in the Assembly Browser, right-click on a module and select Edit Representations. This opens the Edit Module tab, and the Representation sub-tab is shown.
Create panel sets by selecting nodes/elements and/or existing node sets in the model file, that will automatically be
used in setting up Panel Participation diagnostic output in NVH analysis.
In a real-life application, necessary preparation work needs to be done to get the module representation files to a state
that is ready for assembly. Use the Prepare Module tool to accomplish this goal.
Edit and test NVH templates used for creating lumped parameter (LP) models, multiple instances of one model transformed
to a new geometric location, or loadcases.
An Analysis is a collection of module, connection and loadcase selections that completely specifies the assembly definition
for a particular simulation event.
Package all project data (Assembly .xml files, Representation files, LP Templates, Loadcase files, Job files and CSV templates) for transfer to others or for
archival.
The Crash application offers a tailored environment in HyperWorks that efficiently steers the Crash CAE specialist in CAE model building, starting from CAD geometry and finishing with
a runnable solver deck in Radioss, LS-DYNA and PAM-CRASH 2G.
HyperWorks offers high quality tools for CFD applications enabling the engineer to perform modeling, optimization and post-processing
tasks efficiently.
The Drop Test Manager is an automated solution that allows you to either simulate a single drop test or a choice of
multiple iterations with the aim of finding the sensitivity of process variables like initial orientation and drop
height in a typical drop test by controlling the run parameters and conditions with ease.
Many essential utility tools using HyperWorks-Tcl have been developed over the years to support Aerospace customers. A few tools have been collected and upgraded to
be compatible with this release.
Browsers supply a great deal of view-related functionality in Engineering Solutions by listing the parts of a model in a tabular and/or tree-based format, and providing controls inside the table
that allow you to alter the display of model parts.
Perform automatic checks on CAD models, and identify potential issues with geometry that may slow down the meshing
process using the Verification and Comparison tools.
Once the connections have been created, use the Connector Browser
to review the connections.
Reviewing Connections
The Connector Browser is divided into two browser panes. The top pane
is the Module Pane, where connected modules are listed. You can view connections attaching
to modules using typical browser functions, such as Show/Hide/Isolate. The lower pane is the
Connector Pane, where individual connections are listed.
The following connection views are available from the Connector Pane.
Connectivity View
Columns in this view focus on connectivity related details. Of particular
importance are the following columns:
PointA/PointB
These two columns show the two tagpoints on two modules that are being
connected for each connection. The same order (PointA first and PointB
second) is used when generating connection FE entities during connector
realization. PointA/PointB may be shown with two incomplete status
indications (in square brackets): [N/A] indicates that the tagpoint exists
in the assembly database, but is not available in the HyperMesh session (not imported.) [Undefined] indicates
that the tagpoint does not exist in the current assembly database, which
means the tagpoint is either deleted or the sub .xml file it travels with is not imported
in the session.
Owning Module
This column indicates which module owns the particular connection. The
owning module is always the module on the PointA side of the connection. The
connection definition and properties always travel with or organized under
their owning modules when sub .xml files are written.
Distance
This column shows the distance between PointA and PointB. It can be used
as a metric for checking the validity of the connection. Connections
spanning large distances are potentially connected by mistake. Some NVH
engineers prefer to keep all connections at zero length due to fear that
non-zero length springs may introduce unintended dynamic motion, which is a
valid concern if celas type spring elements are used during connector
realization. When cbush type spring and rbe2 type rigid elements are used,
this is the case for all current NVH Director supported realization types,
correct dynamic motion is ensured by element formulation and there is no
longer a need to maintain zero connection length.
Switch Nodes
This column shows if there is a need to switch the order by which PointA
and PointB are used in generating rbe2 rigid elements during connector
realization. This need is driven solely by dependency considerations of the
connected points, since a point that is already dependent cannot be made the
dependent point again in the connection element definition. Four possible
states of this column are possible.
No
If PointA is independent, regardless of the dependency of
PointB.
Yes
If PointA is dependent, but PointB is independent, in which case
PointB will be made the independent point in realizations involving
rbe2.
Unresolvable
This happens when both PointA and PointB are already dependent, in
which case a realization involving rbe2 is not possible and the
connection will fail to realize.
Unknown
If PointA’s dependency status is unknown or if PointA is dependent
and PointB’s dependency status is unknown.
Forced ID
Force ID's for connectors gives you an option to define the numbering
pattern to a connector, so that the connection elements created by
realization of those connectors fall in the defined numbering pattern.
Property View
Columns in this view focus on connection property types defined, local
coordinate systems used and property set that is active.
Location View
Columns in this view focus on the location definition.