VFORCE
The VFORCE command redefines and/or lists the data for a VFORCE statement that defines a translational vector force element as specified using three orthogonal components.
Format
Arguments
FX=e | Respecifies the magnitude and sign of the x component of the VFORCE translational force. The direction of this component is parallel to the x-axis of the RM marker. |
FY=e | Respecifies the magnitude and sign of the y component of the VFORCE translational force. The direction of this component is parallel to the y-axis of the RM marker. |
FZ=e | Respecifies the magnitude and sign of the z component of the VFORCE translational force. The direction of this component is parallel to the z-axis of the RM marker. |
FXYZ=e3d | Respecifies the 3D vector expression for the VFORCE force relative to the RM marker. |
FUNCTION=USER(r1[,...,r30]) | Respecifies up to 30 user-defined constants for use in computing the force components in a user-defined subroutine VFOSUB (see the VFOSUB subroutine). |
I=id | Respecifies the marker at which Adams Solver (C++) applies the action force. You must ensure that the I marker is a fixed marker and on a different part than the JFLOAT marker. Because I is a fixed marker, Adams Solver (C++) always applies the force at a fixed point on the part. |
JFLOAT=id | Respecifies the marker at which Adams Solver (C++) applies the reaction force. You must ensure that the JFLOAT marker is a floating marker and on a different part than the I marker. Adams Solver (C++) moves the JFLOAT marker to keep it superimposed on the I marker, which means that the reaction force may move with respect to the part. Adams Solver (C++) does not calculate reaction forces when the JFLOAT marker is on the ground part. |
LIST | Lists the current values of the VFORCE arguments. |
RM=id | Respecifies the marker that determines the orientation of the force components. You must ensure that RM is a fixed marker. RM may be the same as I and may be on any part in your system. |
ROUTINE=libname::subname | Specifies an alternative library and name for the user subroutine VFOSUB. Learn more about the ROUTINE Argument. |
Extended Definition
The VFORCE statement lists or redefines a force element that consists of three mutually orthogonal translational force components. You can alter one or both points of force application, change the force reference marker, and change the force function expressions or the parameters passed to the VFOSUB user-written subroutine.
After a change to a VFORCE, Adams Solver (C++) reprocesses the model at the next SIMULATE command, as if it had just been read in from the dataset. During the reprocessing, Adams Solver (C++) checks the entire model for consistency, reinitializes user subroutines, and recomputes initial conditions.
While checking, Adams Solver (C++) verifies that the model is still valid with the new VFORCE. If, for example, the VFORCE function expression refers to an inactive element, Adams Solver (C++) issues an error.
Adams Solver (C++) also reinitializes all user subroutines to re-establish functional dependencies. For each element that refers to a user-written subroutine, Adams Solver (C++) calls the user-written subroutine with IFLAG set to true.
Prior to the actual simulation, Adams Solver (C++) computes initial conditions for the model. If this is the first simulation, Adams Solver (C++) begins with the positions and velocities specified in the dataset. If you ran a previous simulation, Adams Solver (C++) begins with the final displacements and velocities. Adams Solver (C++) then adjusts the initial conditions to ensure that they are consistent with the model constraints. If this is the first simulation, Adams Solver (C++) also maintains any user supplied joint initial-conditions and positions specified as EXACT.
Tip: | Depending on the nature of the desired force relationship, the RM marker may belong to the same part as the I marker, or the JFLOAT marker, or to a third, unrelated part. |
Caution: | The user-defined functions FX, FY, and FZ should be smooth, continuous, and single-valued. These conditions make the solution process very effective. |
Example
VFORCE/10,LIST &
,FX= -90.5*Dx(109,102,102) - 9.05*Vx(109,102,102,102)\ &
,FY= -90.5*Dy(109,102,102) - 9.05*Vy(109,102,102,102)\ &
,FZ=-750.8*Dz(109,102,102) - 75.08*Vz(109,102,102,102)
Example 2
VFORCE/10, LIST &
,FXYZ = -90.5*DXYZ(109,102,102) - 9.05*VXYZ(109,102,102) - [0, 0, 660.3*DZ(109,102,102), 66.03*VZ(109,102,102,102)]
See other Forces available.