*SetForce() - asymmetric translational and rotational

Sets the values for an asymmetric translational and rotational 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_tx_l, TOKEN_tx_l, 
                                  TYPE_ty_l, TOKEN_ty_l, 
                                  TYPE_tz_l, TOKEN_tz_l, 
                                  TYPE_fx_r, TOKEN_fx_r, 
                                  TYPE_fy_r, TOKEN_fy_r, 
                                  TYPE_fz_r, TOKEN_fz_r, 
                                  TYPE_tx_r, TOKEN_tx_r, 
                                  TYPE_ty_r, TOKEN_ty_r, 
                                  TYPE_tz_r, TOKEN_tz_r)

Token

If you select this TYPE, use this TOKEN
LIN
Enter a value for fx_l, fy_l, fz_l, tx_l, ty_l, tz_l, fx_r, fy_r, fz_r, tx_r, ty_r, and tz_r.
Token: Value
CRV
Use a Curve to represent the force/torque behavior. See Comments.
Token: curve_name,

AKIMA|CUBIC|LINEAR|QUINTIC,

`indep_variable`

SPL3D
Use a Spline3D to represent the force/torque behavior. See Comments.
Token: spl3d_name,

AKIMA|CUBIC|LINEAR|QUINTIC

'indep_var1',

'indep_var2'

EXPR
Enter a solver expression that represents the force/torque behavior.
Token: `expression`

Arguments

force_name
The variable name of an existing translational and rotational action-only or action-reaction force pair.
Data type: varname
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.
Data type: real or string
tx_l, ty_l, tz_l
Numbers, MDL expressions, or solver expressions that determine the values of the rotational forces about the left X, Y, and Z axis.
Data type: real or string
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.
Data type: real or string
tx_r, ty_r, tz_r
Numbers, MDL expressions, or solver expressions that determine the values of the rotational forces about the right X, Y, and Z axis.
Data type: real or string
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

The following example demonstrates usage of different types and tokens used for translation and rotations part of the action reaction force pair. While left and right side translation Y force uses a curve, left side rotational force about X uses a spline3D. Left side translation Z and rotational Z use expressions.

*BodyPair(b_wheel, "Wheel body")
*PointPair(p_wc, "Wheel center")
*ActionOnlyForcePair(frc_asym, 
 "Assymetrical force", 
 TRANS_ROT, 
 b_wheel, 
 p_wc)
*SetForce(frc_asym, , LIN, 12, 
CRV, crv_frc, AKIMA , `{frc_asym.l.DY}`, 
EXPR, `100*sin(2*PI*TIME)`, 
SPL3D, spl3d_frc_ay, CUBIC, `{frc_asym.l.AX}`, 
LIN, 13, 
EXPR, `1000*sin(2*PI*TIME)`, 
LIN, 20 , 
CRV, crv_frc, , `{frc_asym.r.DY}`, 
LIN, 2000 , 
LIN, , 
LIN, , 
LIN)

Context

*BeginMdl()

*DefineAnalysis()

*DefineSystem()

*DefineAssembly()

*BeginContext()

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.