Table 1 - Mapping between ADAMS and MotionSolve Modeling Elements

Blue - Supported in ADAMS, but not supported in MotionSolve.

Orange - Supported in ADAMS, but not applicable in MotionSolve.

Green - Not supported in ADAMS, but supported in MotionSolve.

ADAMS	MotionSolve
2d PART	Subsystem_Planar
ACCGRAV	Force_Gravity
ARRAY	Reference_Array
BEAM	Force_Beam
BUSHING	Force_Bushing
CONTACT	Force_Contact
COUPLER	Constraint_Coupler
CURVE	Reference_ParamCurve
CVCV	Constraint_CVCV
DEBUG	Debug_Output
DIFF	Control_Diff
END	Not Applicable
EQUILIBRIUM	Param_Static
FEMDATA	Not Applicable
FIELD	Force_Field
FLEX_BODY	Body_Flexible,Reference_FlexData
FRICTION	Force_JointFriction
GCON	Constraint_Mate
GEAR	Constraint_Gear
GFORCE	Force_Vector_{OneBody, TwoBody}
GRAPHICS	Post_Graphics (GRAPHICS of type FORCE are not supported). See Comment below.
GSE	Control_StateEqn (type:Usersub)
IC	IC
INTEGRATOR	Param_Transient
JOINT	Constraint_Joint
JPRIM	Constraint_Jprim
KINEMATICS	Not Applicable
LIST/NOLIST	Not Applicable
LSE	Control_StateEqn (type:Linear)
MARKER	Reference_Marker
MATRIX	Reference_Matrix
MFORCE	Force_FlexModal
MOTION	Motion_{Joint, Marker}
MREQUEST	Not Applicable
NFORCE	Force_MultiPoint
Not Supported	Constraint_PTdCV
Not Supported	Constraint_PTdSF
Not Supported	Constraint_PTSF
Not Supported	Constraint_CVSF
Not Supported	Constraint_SFSF
Not Supported	Force_PTdSF
Not Supported	Reference_DeformCurve
Not Supported	Reference_DeformSurface
OUTPUT	Not Applicable
PART	Body_Rigid
PINPUT	Control_PlantInput
POINT_MASS	Body_Point
POUTPUT	Control_PlantOutput
PREFERENCES	Not Applicable
PTCV	Constraint_PTCV
REQUEST	Post_Request
RESULTS	Not Applicable
SENSOR	Sensor_{Event, Evaluate}
SFORCE	Force_Scalar _{OneBody, TwoBody}
SPLINE	Reference_Spline
SPRINGDAMPER	Force_SpringDamper
STRING	Reference_String
SURFACE	Reference_ParamSurface
TFSISO	Control_SISO
UCON	Constraint_UserConstr
UNITS	Param_Unit
VARIABLE	Reference_Variable
VFORCE	Force_Vector_{OneBody, TwoBody}
VTORQUE	Force_Vector_{OneBody, TwoBody}

Comment

GRAPHICS of type FORCE are not supported directly by the MotionSolve translator. However, you may still create force vector graphics in your model by creating an output of type “FORCE” on a body in MotionView. Alternatively, you may add a modeling element <Post_Request> of type “MARKER_FORCE” to generate the force vectors in HyperView.

2.	When GRAPHICS is defined for use in contact scenarios, the MotionSolve translator does not support GRAPHICS of type EXTERNAL when the file format is .obj or .shl. For this scenario, you will need to:

•	Import the ADM model in MotionView

•	Convert the .obj/.shl graphics to H3D via the CAD import

•	Run the model from MotionView or export the model as XML