*SetMotion() - asymmetric motion pair
Sets the properties of an asymmetric motion pair.
Syntax
*SetMotion(motion_name, , DISP|VEL|ACCL,
TYPE_left,
TOKEN_left,
TYPE_right,
TOKEN_right)
Arguments
- motion_name
- The variable name of an existing motion pair.
- DISP VEL ACCL
- This argument identifies whether a displacement, velocity, or acceleration is being specified.
- curve_name, AKIMA|CUBIC|LINEAR|QUINTIC, `indep_variable`
- When using curve data, a curve, an interpolation method, and an independent variable must be specified, where curve_name is the variable name of an existing curve that represents the force characteristic, the interpolation method can be set to AKIMA, CUBIC, LINEAR, or QUINTIC. The indep_variable is the solver expression representing the independent variable along which the force curve is characterized.
- spl3d name, AKIMA|CUBIC|LINEAR| QUINTIC, 'indep_var1', 'indep_var2'
- When using spline3d, a Spline3D entity, an interpolation method, and two independent variables must be specified, where spl3d_name is the variable name of an existing Spline3D entity that would represent the force v/s two independent variables. The interpolation method can be set to AKIMA, CUBIC, LINEAR, or QUINTIC. indep_var1 is the solver expression for the first independent variable. indep_var2 is the solver expression that represents the second independent variable.
- `expression`
- A solver expression for the motion.
Example
*RevJointPair(j_crank_pivot, "Crank pivot",
b_crank,
B_Ground,
p_crank_pivot,
p_crank_pivot_axis)
*MotionPair(crank_rot, "Crank rotation", j_crank_pivot)
*SetMotion(mtn1, RIGHT, VEL, ds.real1.value +
ds.real2.value, 30)
*SetMotion(crank_rot, , DISP,
`30xsin(2*P1*TIME)`,
`30xcos(2*P1*TIME)`)
*MotionPair( mtn_wc, "Wheel center motion", j_wc_trans)
*Curve( crv_wc_mtn, "Wheel center mtn")
*SetMotion(mtn_wc, , DISP, crv_wc_mtn.interp(AKIMA, `TIME`),
crv_wc_mtn.interp(AKIMA, `TIME`))
*SetMotion(mtn_wc, , DISP, `USER({ crv_wc_mtn.id, %d })`,
`USER({ crv_wc_mtn.id, %d })`)
Context
Comments
The second argument (used to specify symmetry) is left empty when specifying asymmetric properties for a motion pair.
Nonlinear properties can be specified only for asymmetric coil spring pairs.
To specify non-linear properties for the motion in any direction, a solver expression or curve data, or spline 3D data can be used. When using solver expressions, Templex syntax is used and all variables are enclosed in braces {} and the rest is treated as literal.
The QUINTIC interpolation method is supported for MotionSolve only.