Home
Full Vehicle NVH
Access the Assemble, Analyze, NVH Tools, NVH Post, and Physics AI ribbons.
Assembly
Learn how to create, open, import and save models.
Assembly Browser
The Assembly Browser is an object-oriented modeling environment where the fundamental entity is the module entity.

Welcome
What's New
View new features for HyperMesh NVH 2024.1.
Get Started
Learn the basics and discover the workspace.
Tutorials
Discover NVH functionality with interactive tutorials.
Full Vehicle NVH
Access the Assemble, Analyze, NVH Tools, NVH Post, and Physics AI ribbons.
- Assembly
  Learn how to create, open, import and save models.
  - Assembly Browser
    The Assembly Browser is an object-oriented modeling environment where the fundamental entity is the module entity.
  - Module Symmetry
    Allows symmetric creation of LP Modules, Connections and dynamic LCS.
  - Module Reparenting
    Module Reparenting allows you to change the assembly hierarchy by cutting or pasting the modules.
  - Module Roll-Up/Roll-Down
    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.
  - Module Subsystem
    Select and define a set of modules as the subsystem used for analysis.
  - Edit Module
    To manage any of the modules shown in the Assembly Browser, right-click a module and select Edit Representations. This opens the Edit Module tab, and the Representation sub-tab is shown.
  - Batch Create Assembly
    Create a complete vehicle assembly using external .csv files for assembly, tagpoints, connections, isolator, network diagram, symmetry and analysis.
  - Batch Create Module
    Use Batch Create Module to create assembly hierarchy and assign ID ranges to the modules from external .csv files.
  - Tagpoint Mapping Tool
    Use the Tagpoint Mapping Tool for automated mapping/creation of tagpoints and connections between data from different sources.
  - Connection Creation
    Connections can be created using the Create Connection-Interactive and Create Connection-Automatic tools.
  - Connection Browser
    Once the connections have been created, use the Connector Browser to review the connections.
  - Connection Manager
    Connections can be managed by right-clicking a connector in the Connector Browser and selecting Edit Connection.
  - Connection Mapping Tool
    Use the Connection Mapping tool for connection, property and hardpoint mapping.
  - Import Optimized Data
    Use the Optimization tool to automate mapping and update NVH connection parameters and modal parameters with optimized values from OptiStruct generated deterministic optimization output.
  - Connection Realization
    Use the Connection Realization tool for realization of selected connections based on the specified Tolerance, Property state and State rule.
  - LCS Manager
    Manage local coordinate systems (LCS) created in the Assembly framework.
  - Network View
    The network view is a block diagram view emphasizing inter-connectivity of the assembly.
- Analysis
  Set up the simulation model, materials, domains and boundaries.
- NVH Tools
- Prepare Module
  Create, organize and manage the CAE parts.
- Post-Processing and Diagnostics
  Define radiation conditions and create emissivity models.
High Frequency NVH
High frequency NVH is an implementation of Statistical Energy Analysis (SEA), and is used to predict and analyze the vibration and acoustic response of complex dynamic systems.
Squeak and Rattle
Create and evaluate evaluation lines and optimize interfaces to eliminate squeak and rattle issues.

View All Altair HyperWorks Help

Assembly Browser

The Assembly Browser is an object-oriented modeling environment where the fundamental entity is the module entity.

A module is a HyperMesh entity used to represent subsystems of an assembly. It can have multiple representations and related metadata such as ID ranges, tagpoints and states. Modules can be created from the Assembly Browser by right-clicking and selecting Create Module. The Edit Module is used to manage the various aspects of the module definition, which can be accessed from the Assembly Browser by right-clicking and selecting Edit Representations. A module-based assembly definition can be saved in an .xml file.

To open a previously created assembly, you need to import an .xml file. This should be an assembly database file that you exported from the NVH Director.

The Assembly Browser includes the following views:

Base View

This view displays every entity within the hierarchy, the display status and the Analysis status.

Figure 1.

File View

The File View display shows the Export status and the associated .xml file path for each module.

Figure 2.

This view also includes the Preserve/Merge option.

Preserve: Saves an assembly .xml file along with a set of nested subassembly files (similar to include files).
Merge: Saves the assembly file with all subassembly files merged into it.

Subassembly files can be specified by clicking the ‘-‘ icon in the XML file path column. Navigate to the desired folder and specify a file name. Export of subassembly files can be controlled by checking/unchecking of the checkbox in the Export column.

Note: The Save XML option is enabled only in the File View to ensure that you are aware that the subassembly files are over-written.

ID View

The ID View shows the summary of ID ranges assigned to modules with representation in the assembly hierarchy. It also shows the assignment and conflict status in terms of Intra-Module and Inter-Module flags. Intra-Module = Yes means IDs of all entities in the module are within assigned range, or else Intra-Module = No. Inter-Module = Yes means there are no ID conflicts across modules, or else Inter-Module = No.

Figure 3.

Property View

The Property View shows the mass and damping of modules with representation in the assembly hierarchy. Mass is also shown for the root module and parent modules.

Figure 4.

Configuration View

The Configuration View shows the list of all of the modules and a list of configurations with modules specific to that configuration.

Figure 5.