Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The eigenfrequencies for each iteration of the optimisation process are calculated by MSC Nastran. Therefore, MSC Nastran has to be installed on the same machine and a valid license is required.

The path to the

...

MSC Nastran executable

...

can be set manually in the application settings:

Please use nast20233(.exe) (or the matching executable for your installed nastran version) for frequency analysis.

...

The frequency constraint can directly set in the GD Scenario:

...

Frequency Constraint

The Frequency Constraint (in Hz) is the target for the first occurring eigenfrequency of the part. Per default the first 10 eigenfrequencies in a range up to 3 times the frequency constraint value are considered. Based on these eigenmodes the part is stiffened to push the the first eigenfrequency upwards.

As an optional input the range and the number of frequencies which are taken into account for the optimisation can be modified with the Advanced User Settings.

Post Processing

The calculated first eigenfrequency over the iterations can be observed with a chart in the Post Processing. The frequency Event does not create any visible plots for the Failure Criterion or Stress on the geometry. But the influence of the frequency Event can be observed with the optimization achievement index which shows where material will be added (>0) to increase the first eigenfrequency of the part.

Known Limitations

Symmetry
Info

Symmetry and a Frequency Event cannot be set up together. Some of the Eigenfrequency modes will be asymmetric.

Frequency Constraint
Info

If the Frequency Constraint is higher than the first calculated Eigenfrequency of the whole Design Space in the first Iteration, this can lead to the case that no material will be reduced. This can be resolved by reducing the Frequency Constraint or by entering the following command to the Advanced User Settings:

...

Info

RBE2 can be used as a connection type, but the RBE2 connection won’t be considered in a static load case. This can occur if a Point Mass is added in combination with acceleration. In this case, the static load of the point mass will be considered with a RBE3 connection.

pointMass.PointMassInertia_Point_Mass_1.type=RBE2

You might also be interested in this tutorial: