HyperWorks Release Notes

MotionSolve 14.0.231 Release Notes

MotionSolve 14.0.231 Release Notes

 Previous topic Next topic Expand/collapse all hidden text  

MotionSolve 14.0.231 Release Notes

 Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

Highlights

MotionSolve is a state-of-the-art multi-body solver available in HyperWorks. It has a complete set of modeling elements and powerful numerical methods to support a full set of analysis methods. The accuracy, speed and robustness of MotionSolve have been validated through extensive testing with customer models and test data. MotionSolve also offers unmatched compatibility with ADAMS/Solver input.

In version 14.0.231, which is a service update to the 14.0.230 release, MotionSolve brings continuous improvements to the major functionalities.

 

hmtoggle_arrow1Updated H3D Libraries

With this service update, the H3D libraries within MotionSolve have been upgraded to version 14. The upgrade has been done primarily to be consistent with the version of H3D libraries that is used by OptiStruct.

What this means is that there is no change in the CMS flexible body generation or ESLM workflow in any way.

 
hmtoggle_arrow1Resolved Issues

Incorrect SENVAL evaluation

For the class of models that

1.Contain sensors and stop/halt simulations using <Sensor_Event> modeling elements
2.Contain multiple simulates within the simulation,

a bug that led to wrong evaluations of SENVAL has been fixed.

 

Fixes for specific scenarios that lead to MotionSolve crashing

Within this release, a number of crash scenarios have been addressed and the robustness of MotionSolve has been improved such that the crash issues are avoided. These specific usage scenarios are listed below:

1.Models that contain a Point to Deformable Curve (PTdCV) modeling entity defined on a linear flexible body. The crash occurs while writing the output files after the simulation, specifically when the linear flexible H3D file is not available.
2.Models that contain multiple simulates, the user define subroutine MESSAGE_SUB and are run on the Mac platform.
3.Models that make use of the CONTACTPOST modeling subroutine, specifically when an RM other than “0” is specified, or, if the get_contact_post utility function is called in the case when no contact occurs.

These have been fixed within the current release.

 

Stopping co-simulation in Activate is slow

With the previous release, if a user stopped a co-simulation between MotionSolve and Activate from within Activate, the co-simulation would not stop immediately.

This has been fixed within this release such that the co-simulation stops immediately when a stop is requested.