*SetForce() - translational

Sets the values for a translational action-only or action-reaction force.

Syntax

*SetForce(force_name, TYPE_fx, TOKEN_fx, 
                                TYPE_fy, TOKEN_fy, 
                                TYPE_fz, TOKEN_fz)

Token

If you select this TYPE, use this TOKEN
LIN
Enter a value for fx, fy, and fz.
Token: Value
CRV
Use a Curve to represent the force behavior. See Comments.
Token: curve_name,

AKIMA|CUBIC|LINEAR|QUINTIC,

`indep_variable`

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

AKIMA|CUBIC|LINEAR|QUINTIC

'indep_var1',

'indep_var2'

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

Arguments

force_name
The variable name of an existing translational action-only or action-reaction force.
Data type: varname
fx, fy, fz
Numbers, MDL expressions, or solver expressions that determine the values of the translational X, Y, and Z components of the force.
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 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

*BodyPair(b_wheel, "Wheel body")
*PointPair(p_wc, "Wheel center")
*ActionOnlyForce(frc_wc, 
 "Applied force at left wheel center", 
 TRANS
 b_wheel.l
 p_wc.l)
*SetForce(frc_wc, LIN, ds.real1.value * ds.real2.value, 
 LIN, 10.3, 
 LIN, ds.real3.value)
*SetForce(frc_wc, CRV, crv_frc_x, AKIMA, `{frc_wc.l.DX}`, , 
 LIN , , 
 SPL3D, spl_frc_z, AKIMA, `{frc_wc.r.DZ`, 
 `VZ({frc_wc.l.i.idstring}, {frc_wc.l.j.idstring}, 
 {frc_wc.l.j.idstring})`)

Context

*BeginMdl()

*DefineAnalysis()

*DefineSystem()

*DefineAssembly()

*BeginContext()

Comments

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.