Browsers supply a great deal of view-related functionality in HyperMesh 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.
Connectors are geometric entities (not FE) used to create connections between components. Connectors are used to realize
FE idealizations of the physical connection. Just as you create an FE mesh on a surface, you create FE connections
by realizing a connector.
There are many advantages to the way connectors store information. Not only does this local storage allow you to edit
the connector definition, it also allows you to review connector details and the quality of the realization.
Most of the information stored in the connector entity can be exported to a master connectors file, which contains
connector entity information such as location, link entity, link entity state, link entity rules. The exported file
may also contain metadata information stored in the connector.
Create weld points at a predefined pitch distance so that the model build process can continue without the need to
wait for the published weld data from CAD.
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.
Create weld points at a predefined pitch distance so that the model build process can continue without the need to
wait for the published weld data from CAD.
Create weld points at a predefined pitch distance so that the model build process can
continue without the need to wait for the published weld data from CAD.
From the menu bar, click Connectors > Create > Autopitch.
The Autopitch dialog opens.
Using the Components selector, select the components to automatically add
connectors to.
All selected components receive connectors with the same qualities to help you
perform a blanket application of connectors-using the same pitch-to all
components that need them as a single operation. Be wary of simply selecting the
whole model, however, as this could result in undesirable actions, such as
adding welds to a cars tires.
To use shell meshes that enclose a volume (some small gaps are allowed) as
input, enable the Consider closed shell thin solids
checkbox.
For example, the outer skin of a solid part can be shell meshed and used as
input to create connectors. Standard mid-plane meshes are also still considered
when this option is used.
To create connectors in the middle of the found flanges, enable the
Create in middle checkbox.
By default, connectors are created on either one of the flanges. This applies
to both mid-plane and closed shell thin solid inputs, when appropriate.
Define settings.
In the Search distance field, enter the distance
to consider between components.
In the Spot pitch distance field, enter the
distance between each connector.
In the Spot pitch end offset field, enter the
distance from the end of an edge/flange to the connector.
In the Distance from free edge field, enter the
distance from the free edge to the connector.
In the Feature angle field, enter the angle used
to segregate the model into faces that are planar within its specified
value.
In the Max deviation from avg dist (%) field,
enter the average distance that can be calculated based on the
estimation that the distance between two flanges does not change too
much in the areas where connectors should be placed.
If the distance at the position where a connector is planned exceeds
the given deviating value, no connector will be created at that
position.
This segregation is used to identify where autopitch connectors are
placed. For example, faces found to have significant topological
complexity are not used to create autopitch connectors.
Note: By reducing its value, the complexity of some of these faces is
generally reduced. Of course, flat regions are unaffected by the
parameter.
Click create.
The created output is a series of connectors with the appropriate pitch distance and
other associated parameters. These connectors are in the unrealized state, thereby
allowing the connector to be realized to a configured state.
The output is organized in the current component collector. If there is no current
component collector, then a new collector called ^autopitch is created.