*SetForce() - asymmetric translational
Sets the values for an asymmetric translational action-only or action-reaction force pair.
Syntax
*SetForce(force_name, , TYPE_fx_l, TOKEN_fx_l,
TYPE_fy_l, TOKEN_fy_l
TYPE_fz_l, TOKEN_fz_l,
TYPE_fx_r, TOKEN_fx_r,
TYPE_fy_r, TOKEN_fy_r,
TYPE_fz_r, TOKEN_fz_r)
Token
If you select this TYPE, use this TOKEN
- LIN
- Enter a value for fx_l, fy_l, fz_l, fx_r, fy_r, and fz_r.
- CRV
- Use a Curve to represent the force behavior. See Comments.
- SPL3D
- Use a Spline3D to represent the force behavior. See Comments.
- EXPR
- Enter a solver expression that represents the force behavior.
Arguments
- force_name
- The variable name of an existing translational action-only or action-reaction force pair.
- fx_l, fy_l, fz_l
- Numbers, MDL expressions, or solver expressions that determine the values of the translational X, Y, and Z components of the left force.
- fx_r, fy_r, fz_r
- Numbers, MDL expressions, or solver expressions that determine the values of the translational X, Y, and Z components of the right force.
- 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 force.
Example
Example 1
In the following example, the rotational force pair uses linear values for all except the
TZ on the right side, which uses a solver expression. The left force TX uses a parametric
expression that refers to a
dataset.
*SetForce(frc_wc, , LIN, ds.real1.value * ds.real2.value,
LIN, 10.3,
LIN,ds.real3.value,
LIN,0.0,
LIN, 0.0,
EXPR,‘100*sin(2*PI*TIME)‘)
Example 2
The following example shows usage of setting forces with different types. TY of the
rotation force left uses a curve (with the Y rotational displacements of the force markers
as independent variable), and TY on the right side uses a spline3D (second independent
variable is angular velocity between force markers). TZ on the right uses a solver
expression.
*SetForce(frc_wc, , LIN, ds.real1.value * ds.real2.value,
CRV, crv_torq_y, AKIMA, `{frc_wc.l.AY}`,
LIN,ds.real3.value,
LIN,0.0,
SPL3D, spl_torq_y, AKIMA, `{frc_wc.r.AY}`,`WY({frc_wc.r.i.idstring},{frc_wc.r.j.idstring})`,
EXPR,‘100*sin(2*PI*TIME)‘)
Context
Comments
The second argument (used to specify symmetry) is left empty when specifying asymmetric properties for a bushing pair.
To specify non-linear properties for the force in any direction, a solver expression, 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.