nTop Platform 2.31 is here! This release features a new block called Rotational Velocity Load (beta) that gives you the ability to apply rotational velocity to a part as a finite element force. As with every release, nTopology’s dedicated support team is ready to answer your questions. Please visit support.ntopology.com to gain access to helpful tutorials and support articles.

• Rotational Velocity Load (Beta)

• Usage Improvements

• Bug Fixes

Rotational Velocity Load (Beta)

• We’ve introduced a new block called Rotational Velocity Load (beta) which gives you the ability to calculate and apply an acceleration load (centrifugal force) caused by a constant rotational velocity. Below is an outline of this new block.
• Name: Rotational Velocity Load (beta)
• Location: Beta > Simulation
• Description: Calculate and apply a load that accounts for the structural effects of a region rotating at a constant rate.
• Input 01: Region
  • Type: FE Region
  • Description: Element group in which the rotational velocity load will be applied.
• Input 02: Axis
  • Type: Axis
  • Description: The axis of rotation.
• Input 03: Rate
  • Type: Scalar
  • Description: The rotational velocity rate.
• Output: FE Force
• Converts To: Boundary Condition

Usage Improvements

• The Lattice Body from Quad Mesh (beta) block will be replaced by a new block called Cell Map from Quad Mesh (beta). This block was introduced in 2.30, however, the Lattice Body from Quad Mesh block was not yet replaced. In order to create a Lattice Body from a quad mesh, please use the Periodic Lattice Body block in conjunction with the new Cell Map from Quad Mesh block and a unit cell. Backward compatibility will be applied to files utilizing the Lattice Body from Quad Mesh block.
• We’ve updated our HUD sliders to provide a smoother drag.

Bug Fixes

• We’ve resolved an issue where the Min eigenvalue and Max eigenvalue inputs in the Buckling Analysis block were accepting any units. Eigenvalues are unitless.
• In the homogenization HUD, the displacement factor used to reset to 1 every time the user switched to the “Directional” properties. We updated the HUD to keep the existing value if that value is between 0.01 and 1.0. Otherwise, the value will be clamped between 0.01 and 1.0.