HyperWorks Release Notes

MotionSolve 14.0.230 Release Notes

MotionSolve 14.0.230 Release Notes

 Previous topic Next topic Expand/collapse all hidden text  

MotionSolve 14.0.230 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 multibody 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.230, which is a service update to the 14.0 release, MotionSolve brings continuous improvements to the major functionalities.

 

hmtoggle_arrow1New Python Interface for MotionSolve

This release introduces a new Python interface for MotionSolve. Through this interface, MotionSolve is now available in Python as a library. All of its functionality can be accessed through a well-defined set of Python functions, protocols and tools just like any other Python library. Using this interface, you can:

1.Import the MotionSolve library into your Python script, allowing you to:
a.Define inputs to MotionSolve as Python commands. These can be collected into a separate Python script, function or class and be re-used, encapsulated or inherited.
b.Extend the core capabilities of MotionSolve in the Python programming environment, thus allowing you to develop composite modeling entities, calculate custom results and perform on-the-fly post processing, while also making use of the rich set of functionalities available in Python and its application libraries.
2.Create application specific objects that know about the physics of their behavior. Communication with MotionSolve can now be in terms of these higher-level objects as opposed to parts and markers.
3.Parameterize the MotionSolve model that is sent to the solver for simulation
4.Create human readable and compact MotionSolve models
5.Directly cross reference objects in your model without having to manage and keep a track of IDs

This new interface now blurs the distinction between model, commands and user subroutines, since they are all contained within one file and there is no clear demarcation between them. This allows for greater flexibility in building the model.

The new Python interface is fully supported for all modeling and command entities within MotionSolve with the exception of NLFE components. Also supported are all the access functions and subroutines provided by MotionSolve.

A complete set of documentation, including an updated reference manual, user’s guide and tutorials is also being provided as part of this release. Please refer to these for more details on syntax and usage.

Note: The XML modeling language is still fully functional and you may continue to use XML as your choice of modeling language for creating MotionSolve models.

 
hmtoggle_arrow1Faster Advanced Altair Driver in MotionAuto

For vehicle models following a path using the feedforward steering controller in the Advanced Altair Driver overall CPU time is reduced up to 30%. The reduction was realized by optimizing evaluation of the internal bicycle model used by the feedforward steering controller to predict the vehicles path.

 
hmtoggle_arrow1Resolved Issues

UserGraphics do not work with Altair Advanced Driver:

In the previous release, the tire graphics were missing while post processing the results from the animation H3D. This issue was found to be due to a missing mgf file. This has been fixed with this release.

Memory issues while using event sensors:

Within the previous release, a memory management bug in the code was identified and fixed as part of this release. With the new fix, the usage of event sensors is more robust than before.

Behavior of implicit DIFFs different between XML and Lexicon models:

With the previous release, an implicit differential equation (DIFF) produced different results when run from an XML deck as compared to an equivalent Lexicon based input model. This was identified as a bug and has been fixed with this release.

Point mass body fails assembly analysis:

With the previous release, point mass body falling freely under gravity fails to run an assembly analysis successfully. This issue has been fixed with the current release.