*SetForce() - translational and rotational
Sets the values for a translational and rotational action-only or action-reaction force.
Syntax
*SetForce(force_name, TYPE_fx, TOKEN_fx,
TYPE_fy, TOKEN_fy,
TYPE_fz, TOKEN_fz,
TYPE_tx, TOKEN_tx,
TYPE_ty, TOKEN_ty,
TYPE_tz, TOKEN_tz)
Token
- LIN
- Enter a value for fx, fy, fz, tx, ty, and tz.
- CRV
- Use a Curve to represent the force/torque behavior. See Comments.
- SPL3D
- Use a Spline3D to represent the force/torque behavior. See Comments.
- EXPR
- Enter a solver expression that represents the force/torque behavior.
Arguments
- force_name
- The variable name of an existing translational and rotational action-only or action-reaction force.
- fx, fy, fz
- Numbers, MDL expressions, or solver expressions that determine the values of the translational X, Y, and Z components of the force.
- tx, ty, tz
- Numbers, MDL expressions, or solver expressions that determine the values of the rotational force about the X, Y, and Z axis.
- 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/torque 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/torque 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/torque 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 force/torque.
Example
*BodyPair(b_wheel, "Wheel body")
*BodyPair(b_wheel, "Wheel body")
*PointPair(p_wc, "Wheel center")
*ActionOnlyForce(frc_wc,
"Applied force on left wheel center",
TRANS_ROT,
b_wheel.l,
p_wc.l)
*SetForce(frc_wc, LIN, ds1.real1.value*ds1.real2.value,
LIN, 10.3,
LIN, ds1.real3.value,
LIN, ds2.real1.value,
LIN, ds2.real2.value,
LIN, ds2.real3.value)
*SetForce( frc_trans_rot, LIN, 12,
CRV, crv_frc, AKIMA , `{frc_asym.l.DY}`,
EXPR, `100*sin(2*PI*TIME)`,
SPL3D, spl3d_frc_ax, CUBIC, `{frc_asym.l.AX}`,
LIN, 13,
EXPR, `1000*sin(2*PI*TIME)`)
Context
Comments
To specify non-linear properties for the force in any direction, a solver expression or curve data can be used to compare the force. When using a solver expression, Templex syntax is used and all variables are enclosed in braces {} and the rest is treated as literal. To use curve data, a curve, interpolation method, and a independent variable must be specified, for example,
CRV, curve_name, AKIMA, `{DX}`
where curve_name is the variable name of an existing curve, interpolation method can be set to AKIMA, CUBIC or LINEAR and the independent variable is specified in Templex syntax.