HyperWorks Release Notes

ADAMS Compatibility

ADAMS Compatibility

 Previous topic Next topic Expand/collapse all hidden text  

ADAMS Compatibility

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

The definitions of the functions FX, FY, FZ, TX, TY and TZ have been made consistent with what is used in ADAMS. The table below lists the changes, using the FX function as an example:

Function

Arguments

Behavior

FX (I, J, K)

I, J and K markers

Computes the X component of all the forces acting between marker I and J resolved in the coordinate system of marker K

FX (I, J)

I and J markers

Computes the X component of all the forces acting between marker I and J resolved in the ground coordinate system

FX (I)

I marker

Computes the X component of all the resultant forces at marker I. To calculate the X component of action-only forces at the I marker, specify frc_expr_action_only = “TRUE” in the <ResOutput> command element in the XML input file

 
hmtoggle_arrow1GRAPHIC Statement Compatibility

MotionSolve now supports the adm statement GRAPHICS/… for displaying force vectors in the animation H3D. A sample statement is

GRAPHICS/10215001, FORCE, ETYPE=ALL, EM=10215001

The following ETYPE are now supported:      

ETYPE

ALL, BEAM, BUSH, FIELD, GFORCE, JOINT, JPRIM, NFORCE, SFORCE, SPDP, VFORCE, VTORQUE

 
hmtoggle_arrow1Correct Conversion of Output Steps to XML for Multiple Analyses

Previously, a model that had multiple SAVE/RELOAD statements and analyses with different output steps was not translated correctly to MotionSolve. An example of such a scenario is shown below:

ms_14_07

This has been resolved within this release.