*SetForce() - rotational

Sets the values for a rotational action-only or action-reaction force (torque).

Syntax

*SetForce(force_name, TYPE_tx, TOKEN_tx, 
                               TYPE_ty, TOKEN_ty, 
                               TYPE_tz, TOKEN_tz)

Token

If you select this TYPE, use this TOKEN
LIN
Enter a value for tx, ty, and tz.
Token: Value
CRV
Use a Curve to represent the torque behavior. See Comments.
Token: curve_name,

AKIMA|CUBIC|LINEAR|QUINTIC,

`indep_variable`

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

AKIMA|CUBIC|LINEAR|QUINTIC

'indep_var1',

'indep_var2'

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

Arguments

force_name
The variable name of an existing rotational action-only or action-reaction force.
Data type: varname
tx, ty, tz
Numbers, MDL expressions, or solver expressions that determine the values of the rotational forces about the 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 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 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 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`
An expression for the torque.

Example

Example 1

In the following example, the rotational force pair uses linear values for all directions.
*Body(b_body,  “body")
*Point (p_frc, "Wheel center")
*ActionOnlyForce(frc_rot,
                 "Applied rotational force",
                 ROT,
                 b_body,
                 p_frc)
*SetForce(frc_rot, LIN, ds.real1.value * ds.real2.value, 
                   LIN, 10.3, 
                   LIN, ds.real3.value,
                   )

Example 2

The following example shows the usage of setting forces with different types. TX of the rotation force uses a curve (with the X rotational displacements of the force markers as independent variable), and TY uses a spline3D (second independent variable is angular velocity between force markers). TZ uses a solver expression.
*SetForce(frc_rot, CRV, crv_torq_y, AKIMA, `{frc_wc.l.AX}`, 
                   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

*BeginMdl()

*DefineAnalysis()

*DefineSystem()

*DefineAssembly()

*BeginContext()

Comments

To specify non-linear properties for the force (torque) 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.