Model Element |
|
Description |
|
GFORCE defines a general force and/or torque acting between two markers. It can be used to model a force, a torque, or both. The force and/or torque vectors are defined by their three components with respect to a third marker. The components may be defined using MotionSolve expressions or a user-defined subroutine. They may be a function of any system state and time. |
|
Declaration |
|
def GFORCE(id, LABEL="", I= 0, JFLOAT= 0, RM= 0, FX="", FY="", FZ="", TX="", TY="", TZ="",FUNCTION="", ROUTINE="", INTERPRETER="", SCRIPT=""): |
|
Attributes |
|
id |
Element identification number (integer>0). This number is unique among all the GFORCE elements. It uniquely identifies the modeling element. |
LABEL |
The name of the GFORCE element. |
I |
Specifies the ID of the marker at which the force/torque is applied. This is designated as the point of application of the force/torque. |
JFLOAT |
Specifies the ID of the floating marker at which an equal and opposite reaction force/torque is applied. |
RM |
Specifies the marker whose coordinate system is used as the basis for defining the components of the force/torque vector. |
FX |
Specifies the magnitude of x-components force vector as a constant value, or as a function expression that can be evaluated at run-time. |
FY |
Specifies the magnitude of y-components force vector as a constant value, or as a function expression that can be evaluated at run-time. |
FZ |
Specifies the magnitude of z-components force vector as a constant value, or as a function expression that can be evaluated at run-time. |
TX |
Specifies the magnitude of x-components torque vector as a constant value, or as a function expression that can be evaluated at run-time. |
TY |
Specifies the magnitude of y-components torque vector as a constant value, or as a function expression that can be evaluated at run-time |
TZ |
Specifies the magnitude of z-components torque vector as a constant value, or as a function expression that can be evaluated at run-time. |
FUNCTION |
The list of parameters that are passed from the data file to the user defined subroutine. The user defined subroutine VFOSUB is used when only forces are defined. VTOSUB is used when only torques are defined. GFOSUB is used when both forces and torques are defined. This attribute is common to all types of user subroutines and scripts. |
ROUTINE |
Specifies an alternative name for the user subroutine VFOSUB/VTOSUB/GFOSUB. |
INTERPRETER |
Specifies the interpreted language that the user script is written in. Valid choices are MATLAB or PYTHON. |
SCRIPT |
Specifies the path and name of the user written script that contains the routine. |
CommentsSee Force_Vector_TwoBody |
|
ExampleThe example below shows how a GFORCE may be defined.GFORCE(18, LABEL="My-Automotive-Bushing", I=1801, JFLOAT=1901, RM=1903, FX="CUBSPL(0,VX(1801,1903,1903,1903),1)",
GFORCE(18, LABEL="My-Automotive-Bushing", I=1801, JFLOAT=1901, RM=1903, FX="CUBSPL(0,VX(1801,1903,1903,1903),1)+CUBSPL(0,DX(1801,1903,1903,1903),4)", |
The following MDL Model statements:
*SetForce() - asymmetric force pair with user subroutine
*SetForce() - asymmetric line of action
*SetForce() - asymmetric rotational
*SetForce() - asymmetric single component rotation
*SetForce() - asymmetric translational
*SetForce() - asymmetric translational and rotational
*SetForce() - single component rotation
*SetForce() - single force with user subroutine
*SetForce() - symmetric line of action
*SetForce() - symmetric rotational
*SetForce() - symmetric single component rotation
*SetForce() - symmetric translational