MotionSolve 14.0 Release Notes

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, MotionSolve had the following major highlights:

•	Revamped 3D rigid body contact solution that improves robustness, accuracy and performance

•	Non-linear finite element bodies are introduced in MotionSolve

•	Geometric stiffening support is added for linear flexible bodies

•	A new Python Lexicon is available for model building

•	Several enhancements to Linear Analysis

In this version of 14.0.220, which is a service update to the 14.0 release, MotionSolve brings continuous improvements to the major functions.

MotionSolve 14.0 introduced the “NLFE Body” as an experimental feature, which allows you to model non-linearly flexible beams and cables in your multibody system. The NLFE Body is based on the Absolute Nodal Coordinate Formulation (ANCF). Nonlinearity can occur for two main reasons: (A) Geometric nonlinearity and (B) Material non-linearity. The NLFE body supports both. MotionView also introduced NLFE subsystems to model stabilizer bar, helical spring and belt pulley systems.

MotionSolve version 14.0.120/220 announces the formal release of the NLFE capability in MotionSolve

•	In MotionSolve 14.0.210, you could specify the maximum allowable von Mises strain for your NLFE component in the model.

If the maximum von Mises strain in any element of the NLFE component exceeded this value during the simulation, MotionSolve would issue a warning message. This message has been improved – the Body_Flexible ID for which the violation occurs is now included within the message for easy identification and debugging.

The following is an example of this updated warning message:

WARNING: Maximum vonMises strain exceeded maximum strain (YS) specified for NLFE element BEAM12 (id=20000000) on Body_Flexible (id=30105) at time=1.003E+00

Maximum strain Computed : 1.027E-03

Maximum strain Specified: 1.000E-03

Future warning for yield strain violation suppressed.

•	Several fixes have been made to enhance the robustness of displacement and stress calculations for BEAM elements subjected to different kinds of loading (axial, bending and torsion) during static, quasi-static and transient analyses.

•

By default, MotionView now defines a global method of attaching a marker to an NLFE body for defining joints, forces, bushes etc. This means that each marker that is attached to the NLFE body is accompanied by a CONN0 element with the conn attribute set to “TTTTTT”. To modify or disable this, you may define an environment variable HW_NLFE_CONN_TYPE with the required CONN0 string. You may specify up to six characters that determine how the additional 6 degrees of freedom at the NLFE attachment grid are to be constrained. For example:

-	HW_NLFE_CONN_TYPE = TTTTTT implies that the marker is fully clamped to the grid. The grid cannot be subjected to any axial or shear strain. This is the default value.

-	HW_NLFE_CONN_TYPE = FFFTTT implies that the marker is partially clamped to the grid. The grid can only undergo axial deformations but no shear deformation.

-	HW_NLFE_CONN_TYPE = TTTFFF implies that the marker is partially clamped to the grid. The grid can only undergo shear deformations but no axial deformation.

-	HW_NLFE_CONN_TYPE = FFFFFF implies that the marker is not clamped to the grid. All deformations are allowed on the grid.

-	For more details, please see the documentation on CONN0 in the solver reference manual.

•

You may now use the attribute “nf” within CABLE elements to modify the bending resistance of your cable component to suit your modeling needs. The ability to modify this attribute lets you model cables that are composed of multiple fibers or wires, wound together to form a compound cable component. For more details, please refer to the documentation of PCABLE in the reference manual.

With this release, MotionSolve introduces a co-simulation interface with solidThinking Activate. Activate is a modern block diagram environment to design and improve multi-disciplinary systems. Activate not only supports co-simulation with MotionSolve, but also supports the Functional Mockup Interface (FMI), both for model exchange and co-simulation.

This interface lets you simulate complex systems that include a Multi-body system with one or more control subsystems.

The Altair Advanced Driver is enhanced to support steering the vehicle from steering gear (e.g. rack-pinion or recirculating ball) without the need for a steering wheel and column. The vehicle parameters input to the driver now include markers on the left and right front wheels to enable the driver to determine the overall steering ratio.

The version of CDTire shipped with MotionSolve is updated to 4.2.3 from 4.1. CDTire version 4.2.3 includes:

CDTire/Realtime (CDT30/HPS)

The CDTire/Realtime model includes these new features:

•	LDE (large deformation element): This extension has been added from CDTire/Legacy model 30. It implements tire ground out behavior.

•	PIN_FLAG/PREF: This extension has been added from CDTire/Legacy model 30. It implements inflation pressure dependent rigid body frequencies FTX, FTY and FRY.

•	CRY_RED_FLAG/_DEF/_RES: This extension has been added from CDTire/Legacy model 30. It implements deflection dependent reduction of CRY for large deformations.

•	PNEUMATIC_SCALE_TRAIL: This parameter scales the pneumatic trail to yield more accurate self-aligning torque. Default setting yields backward compatibility.

•	For more information, please refer to the CDTireUser Manual.

CDTire/3D (CDT50)

The CDTire/3D model has these new features:

•	TREAD_HEIGHT: The tread sensor height can now also be specified for each individual tread sensor ring. This allows modelling of rotationally symmetric tread gaps.

•	PIN_FLAG/PREF: This extension for SW_MODE=40 has been added from CDTire/Legacy model 40. It implements inflation pressure dependent rigid body frequencies FTX, FTY and FRY.

•	CRY_RED_FLAG/_DEF/_RES: This extension for SW_MODE=40has been added from CDTire/Legacy model 40. It implements deflection dependent reduction of CRY for large deformations.

•	For more information, please refer to the CDTireUser Manual.

CDTire/MF++

CDTire version 4.2 introduces a new Magic Formula sub model called CDTire/MF+. The MF++ model estimates the contact patch shape, location and pressure distribution for coupling with CDTire/Thermal. To select CDTire/MF++ in ADAMS via GFORCE or ADAMS/Tire (CDT_MODEL_TYPE), set the model number to 10.

Note: CDTire v4.2.3 discontinues support for tire model 20 (CDT20). In addition, road surface model 1000 (RSM1000) is no longer supported for use with tire model 30 (CDT30).

With this release, additional support for modeling entities has been added to the Python Lexicon.

•	The INTEGRATOR statement now supports the following parameters:

MINIT

-	VEL_TOL_FACTOR

DAE_INDEX

-	DAE_CONSTR_TOL

-	DAE_VEL_CTRL

-	DAE_EVAL_EXPIRY

•	The H3DOUTPUT statement now supports the LINEAR_ANIM attribute

•	The LINEAR statement is now supported in the lexicon

With this release, MotionSolve adds the following data access functions:

•	CONTACTPOST

•	GET_NCONTACTS

•	GET_CONTACTPOST

These allow you to query the model during the simulation and write out contact information in a format desired by you. This comes in handy when trying to export loads from contact to a finite element or fatigue solver. Using these newly added functions, you may write out a file to disk in a format desired by your downstream CAE tool.

Translation of MFORCE from ADM to XML

This release includes a fix to correctly translate the MFORCE/Force keyword from an ADM deck to the XML deck.

Memory Leaks in Python Access Functions

With the previous release, there were memory leaks while using the Python based data/model access functions. This meant that the memory usage of MotionSolve was much higher than it should have been.

This has been corrected with this release for the following access functions:

py_gtcmat	py_sysary	py_relpar
py_str2dblary	py_str2intary	py_modinf
py_get_post_states	py_getidlist	py_get_full_matrix_data
py_get_sparse_matrix_data	py_gtaray	py_gtunts
py_slsqp

MSDAEMON Crash in IPC Co-Simulation Mode

Previously, the msdaemon module (required to run an IPC based co-simulation) would crash at the end of a co-simulation with Activate and Simulink or when the co-simulation was paused and started. This issue has been fixed with this release.

Contact Force Magnitude is Calculated Incorrectly

With the previous release, for some models, the contact force magnitude reported by using the expression CONTACT(..) was incorrect. This has been fixed with the current release.

CONN0 on Cable NLFE Elements Leads to Solver Failure

In the previous release (14.0.210), any marker attached to an NLFE component would be accompanied by a CONN0 element in the ANCF XML file which ensured that the marker was rigidly attached to the node of the NLFE component. However, for a CABLE element, this CONN0 may lead to a failure in the simulation. This issue has been identified and fixed with this release.

Mode Function Fix

The MODE function has been fixed to return the correct number based on the analysis type in MotionSolve:

MODE	Description
1	Kinematics
3	Initial Conditions
4	Dynamics
5	Statics
6	Quasi-statics
7	Linear analysis

MotionSolve 14.0.220 Release Notes

MotionSolve 14.0.220 Release Notes

MotionSolve 14.0.220 Release Notes

Highlights

Translation of MFORCE from ADM to XML

Memory Leaks in Python Access Functions

MSDAEMON Crash in IPC Co-Simulation Mode

Contact Force Magnitude is Calculated Incorrectly

CONN0 on Cable NLFE Elements Leads to Solver Failure

Mode Function Fix