Adams Basic Package > Adams View > View Command Language > force > force create direct single_component_force

force create direct single_component_force

Allows you to create a single component force object.
A single-component force applies force or a torque to two parts. You specify a marker on each part for force or torque application. You may define the magnitude of the force as a function of any combination of displacements, velocities, other applied forces, user-defined variables, and time. The force applied can be action-reaction forces or action-only forces.
For translational action-reaction forces, Adams applies the user-defined force along the line connecting the I and the J markers. The force exerted on I is directed from J towards I, while the force exerted on J is directed from I towards J.
For translational action-only forces, Adams applies the force on the I marker only. There is no reaction on the J marker. The force on the I marker is directed along the z axis of the J marker.
For rotational action-reaction forces, Adams applies the torque on the I marker about the z axes of the J marker. Furthermore, Adams assumes that the z axes of the I and the J markers are constrained to always be parallel for this type of single-component force.
For rotational action-only forces, Adams applies the torque only on the I marker. There is no reaction on the J marker. The torque on the I marker is directed along the z axis of the J marker.
You write a FUNCTION expression or a user-written subroutine (an SFOSUB) to define the constitutive equation for the force applied at the I marker. Adams evaluates the reaction forces at the J marker.

Format:

 
force create direct single_component_force
single_component_force_name=
new single component force
Adams_id=
geom_id
comments=
string
type_of_freedom=
translational/rotational
action_only=
on/off
function=
function
user_function=
Real
routine=
string
error=
real
i_part_name=
an existing body
j_part_name=
an existing body
location=
location
orientation=
orientation
along_axis_orientation=
location
in_plane_orientation=
location
relative_to=
existing model or part or marker
i_marker_name=
existing marker
j_marker_name=
existing marker

Example:

 
force create direct single_component_force &
single_component_force_name =
MY_FORCE &
function =
"PI+10" &
i_part_name =
PART_1 &
j_part_name =
PART_2 &
i_marker_name =
MARKER_1 &
j_marker_name =
MARKER_2

Description:

 
Parameter
Value Type
Description
single_component_force_name
New single_component force
Specifies the name of the new single_component_force. You may use this name later to refer to this single_component_force.
Adams_id
Geom_id
Specifies an integer used to identify this element in the Adams data file.
comments
String
Specifies comments for the object being created or modified.
type_of_freedom
Rotational/Translational
Specifies the type of force (rotation or translation) to be applied.ROTATIONAL designates a rotational force, i.e. a torque.TRANSLATIONAL designates a translational force.
action_only
On/Off
Specifies whether the force is action-only or action-reaction. For an action-reaction force, Adams applies a force between the I and J markers. For an action-only force, Adams applies a force on the I marker directed by the Z axis of the J marker, but does not apply a reaction force at the J marker.
function
Function
Specifies the function expression definition that is used to compute the value of this variable. To enter a function expression, you enter a series of quoted strings.
user_function
Real
Specifies up to 30 values for Adams to pass to a user-written subroutine. See the Adams User's Manual for information on writing user-written subroutines.
routine
String
 
error
Real
Currently not in use.
i_part_name
Existing body
Specifies the part, that is the first of the two parts that this force acts between. Adams View applies the force on one part at the I marker and the other at the J marker. These markers are automatically generated using this method of force creation.
j_part_name
Existing body
Specifies the part, that is the second of the two parts that this force acts between. Adams View applies the force on one part at the J marker and the other at the I marker. These markers are automatically generated using this method of force creation.
location
Location
Specifies the locations to be used to define the position of a force during its creation.
orientation
Orientation
Specifies the orientation of the J marker for the force being created using three rotation angles. The I marker is oriented based on the J marker orientation and the requirements of the particular force being created. These markers are created automatically.
along_axis_orientation
Location
Specifies the orientation of a coordinate system (e.g. marker or part) by directing one of the axes. Adams View will assign an arbitrary rotation about the axis.
in_plane_orientation
Location
Specifies the orientation of a coordinate system (e.g. marker or part) by directing one of the axes and locating one of the coordinate planes.
relative_to
AN EXISTING MODEL, PART OR MARKER
Specifies the coordinate system that location coordinates and orientation angles correspond to.
i_marker_name
Existing marker
Specifies a marker on the first of the two parts connected by this force element. Adams View connects this element to one part at the I marker and to the other at the J marker.
j_marker_name
Existing marker
Specifies a marker on the second of two parts connected by this force element. Adams View connects this element to one part at the I marker and to the other at the J marker.

Extended Definition:

1. The easiest way to enter a function expression in Adams View is to use the text editor in combination with the function builder. To invoke the text editor for entering a function expression, highlight the function field and then either pick the "EDIT" button at the top of the panel or type a ^t (control-t). The Adams View "function builder" is discussed below.
The syntactical correctness of a function expression can be investigated by using the "VERIFY" button at the upper right side of the text editor. If there is a syntax error, a message is printed and the cursor is put near the problem. Proper unit consistency is not checked during function expression verification.
The remainder of this explanation will cover the components of FUNCTION expressions as summarized in the following table:
 
Components
Examples
Numbers
FUNCTION = 1E2 + 3.4 + 6
Operators
FUNCTION = 3*6/2 + 3 - 2**2
System Constants
FUNCTION = PI + 20
System Variables
FUNCTION = AX(1040, 2010)
Arithmetic Ifs
FUNCTION = IF(DX(3, 5): -1, 0, 1)
Fortran-77 Functions
FUNCTION = ABS(NUM) - 6
Blanks
FUNCTION = 1 + 2
Continuation Commas
FUNCTION = 1 + 1 + 1 + 1 + 1 + 1 , + 1 + 1 + 1 + 1 + 1 + 1 + 1
Adams Functions
FUNCTION = POLY(0, 0, 6.28)
NUMBERS
FUNCTION expressions can include integers, real numbers, and exponents. In other words, any numbers that are legal in Adams are legal in a FUNCTION expression.
OPERATORS
In a FUNCTION expression, Adams allows any of the operators **, *, /, +, and -. Adams executes these operators according to the following precedence rules:
From greatest to the least, the operators have the following priorities. ** then * / then + -. In other words, Adams executes exponentiation (**) before all other operators and executes multiplication (*) and division (/) before addition (+) and subtraction (-).
When a statement has operators of the same priority, Adams executes them from left to right.
You can use parentheses to alter the precedence of operators. For example, in the equation,
FUNCTION = (1-TIME)*30/PI
Adams subtracts TIME from one before it performs multiplication and division.
SYSTEM CONSTANTS
You can include the following system constants in a FUNCTION expression:
PI Value of pi (to eighteen significant digits)
DTOR Value of pi/180 for converting degrees to radians
RTOD Value of 180/pi for converting radians to degrees
The following example of a FUNCTION with a system constant multiplies the system constant PI by the displacement of marker 10 with respect to marker 14:
FUNCTION = PI*DM(10,14)
BLANKS
A FUNCTION expression can contain any number of blank spaces. Five consecutive blank spaces in an expression do not terminate input of the expression (by indicating that what follows is a comment) as they do in an Adams statement. However, you should remember these two restrictions.
You cannot put a blank space in the middle of a number.
Adams does not accept a blank space between a function and its left bracket. (This is true for both, FORTRAN-77 functions and Adams functions.)
CONTINUATION COMMAS
You can use a comma to continue FUNCTION expressions. You can break the expression anywhere except in the middle of a number, in the middle of a name, or between a function and its left bracket. Put a continuation comma in column one of the following line before the rest of the expression. If you break the expression at a comma that is part of the expression, you must use both, the expression comma and the continuation comma. You may use more than one continuation comma to extend an expression over several lines.
FUNCTION BUILDER
The FUNCTIONS button at the right side of the Adams View text editor provides a means for constructing an Adams function string. These functions are briefly described below. Upon picking the FUNCTIONS button, you will be presented with the list of available functions in the "selection window". After you select the desired function, a panel will appear with fields representing the various parameters for the function. You will have full access to on-line help with this panel just like you have with regular panels. After you have completed the panel and selected the DONE button on the panel, the function string will be constructed and inserted at the current text cursor location in the text edit window.
SYSTEM VARIABLES
A FUNCTION expression may access the current value of a system variable and use the value in computations. These values are accessed through a collection of functions. The accessible system variables include the following: Time, Mode, Displacements (Translational and Rotational), Velocities (Translational and Rotational), Accelerations (Translational and Rotational), Forces (Translational and Rotational), and User-defined variables. Invoke the text edit window and pick the FUNCTIONS button to get a list of functions that can be accessed.
In general, you use a function character string (such as DM, VX, or FZ) and a list of values (e.g. i1, i2, and i3) to access a system variable in an expression. For example, the value i1 may be the name of the marker for which you want to measure a quantity (such as displacement, velocity, acceleration, or force), i2 is the name of the marker with respect to which you want to measure the quantity, and i3 is the name of the marker you want to use to resolve the components of the quantity. If you do not specify marker i3, Adams computes the result in the ground reference frame.
ARITHMETIC IFS
Arithmetic IFs allow you to conditionally define FUNCTION. The format for arithmetic IFs follows.
IF (expression 1: expression 2, expression 3, expression 4)
Adams evaluates expression 1. If expression 1 is less than zero, the arithmetic IF equals expression 2; if expression 1 equals zero, the arithmetic IF equals expression 3; and if expression 1 is greater than zero, the arithmetic IF equals expression 4.
A FUNCTION expression with an arithmetic IF and its four expressions is as given below:
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
If the radial velocity between markers 10 and 31 is less than or equal to zero, the value of the FUNCTION expression is zero; but if the radial velocity between markers 10 and 31 is greater than zero, the value of the FUNCTION expression is six hundred.
In some ways, you may treat IF as a variable. For example, you can place it anywhere in the expression. In addition, you can nest arithmetic IFs nine levels deep.
FORTRAN-77 FUNCTIONS
You can use the FORTRAN functions ABS, ATAN, ATAN2, COS, EXP, LOG, LOG10, MIN, MAX, SIN, SQRT, and TAN in your expression. For more information about these functions, see a FORTRAN reference manual. Invoke the text edit window and pick the FUNCTIONS button to get a list of functions that can be accessed.
Adams FUNCTIONS
In general, an Adams function evaluates a mathematical equation and returns a value to your FUNCTION expression. The following table lists all the Adams functions and their purposes. Invoke the text edit window and pick the FUNCTIONS button to make a list of functions that can be accessed.
 
Names
Purposes
AKISPL
Accesses the data in a SPLINE statement and uses the Akima cubic method to fit a cubic curve (a spline) to the data.
BISTOP
Evaluates a force restricting displacement of a part in two opposite directions
CHEBY
Evaluates a Chebyshev polynomial
CUBSPL
Accesses the data in a SPLINE statement and uses the traditional cubic method to fit a cubic curve (a spline) to the data.
FORCOS
Evaluates a Fourier cosine series
FORSIN
Evaluates a Fourier sine series
HAVSIN
Evaluates a haversine function
IMPACT
Evaluates a force restricting displacement of a part in one direction.
POLY
Evaluates a polynomial
SHF
Evaluates a simple harmonic function
STEP
Approximates a step function with a cubic polynomial
2. Adams View will not allow you to have two single_component_forces with the same name, so you must provide a unique name.
Normally, entity names are composed of alphabetic, numeric, or '_' (underscore) characters, and start with an alphabetic or '_' character. They may be of any length. For more information, see Using Extended Names.
By enclosing the name in double quotes, you may use other printable characters, or start the name with a numeral. If a name contains characters, or starts with a numeral, you must always quote the name when entering it.
Note that you can specify the parentage of an entity (e.g. what part "owns" a marker or a geometry element) when you CREATE it by changing the name. If you enter just the entity name, then the default parent will be assigned by Adams View. If you type in the full name, then you may override the default parent. In most cases, when creating an entity, Adams View will provide a default name. The default name that Adams View provides will specify the parentage that it has assumed. You may, of course, delete this name and use your own. The form of a full name is:
"...._NAME.GRAND_PARENT_NAME.PARENT_NAME.ENTITY_NAME"
The number of levels used varies from case to case and the parentage must exist before an entity can be assigned to it.
3. When you use the FILE Adams_DATA_SET WRITE command, Adams View writes an Adams data file for your model. Adams requires that each modeling element be identified by a unique integer identifier. If you use this parameter to specify a non-zero identifier, Adams View will use it in the corresponding statement in the Adams data file.
You may also enter zero as an identifier, either explicitly or by default. The next time you write an Adams file, Adams View will replace the zero with a unique, internally-generated identifier. Adams View will permanently store this identifier with the element just as if you had entered it yourself.
Normally, you would let all identifiers default to zero, and Adams View would generate the identifiers for you. You are never required to enter a non-zero identifier. You only need to specify it if, for some reason, you wish to control the Adams file output.
4. When an Adams Solver data file (.adm) is read into Adams View, all comments associated with a statement (from the end of the previous statement through the end of the current statement) are stored with the object. Comments in the data file can be associated with model. These comments must follow the title statement and be followed by the comment 'END OF MODEL COMMENTS'. This string must be uppercase.
When an Adams Solver data file is written, the comments for an object are written before the statement corresponding to the object.
5. The I and J markers will be automatically created at this location on the I_PART_NAME and J_PART_NAME respectively.
By default, you supply Cartesian (x, y, z) coordinates. You may use the 'defaults units coordinate_system_type =' command to change this convention. For example, selecting 'cylindrical' means you will subsequently be supplying r, theta, and z coordinates.
Adams View applies your location coordinates in the coordinate system you identify with the RELATIVE_TO parameter. The default for the RELATIVE_TO parameter is the default coordinate system. (See the RELATIVE_TO parameter for this command).
6. Adams View will orient the coordinate system by starting from the initial coordinate system and applying three successive rotations. Depending on the convention you have selected, the rotations may occur about space-fixed or body-fixed axes in any meaningful combination of the x, y, and z axes.
By default, you supply Euler (body313, or body-fixed z, x, z) angles. You may change this convention with the 'DEFAULTS UNITS ORIENTATION_TYPE=' command. For example, selecting SPACE123 means you will subsequently be supplying space-fixed x, y, and z angles.
Adams View applies your orientation angles starting from the coordinate system you identify with the RELATIVE_TO parameter. The default for the RELATIVE_TO parameter is the default coordinate system.
7. You may enter either one or two locations to direct the axis. If you enter one location, the axis will point toward the location. If you specify two locations, the axis will be parallel to, and pointing the same way as, the vector from the first location to the second.
Note that this does not completely dictate the orientation of the coordinate system. Adams View will position the coordinate system with an arbitrary rotation about the axis. If you must completely control the coordinate system orientation, use ORIENTATION or IN_PLANE_ORIENTATION.
By default, you direct the Z axis of the coordinate system. You may change this convention with the 'DEFAULTS ORIENT_AXIS_AND_PLANE AXIS_AND_PLANE_SETTING=' command. For example, selecting either X_AXIS_XY_PLANE or X_AXIS_XZ_PLANE means you will subsequently be directing the X axis. The plane-convention setting does not affect this parameter.
Adams View applies your location coordinates in the coordinate system you identify with the RELATIVE_TO parameter. The default for the RELATIVE_TO parameter is the default coordinate system.
8. If the “RELATIVE_TO” parameter is not specified, the default coordinate system is used. The default coordinate system is initially your model, i.e. the global coordinate system. You may change the default coordinate system using the 'defaults coordinate_system' command.