force create direct general_force
Allows you to create a general force. A GENERAL_FORCE defines a complete force element, consisting of three mutually orthogonal translational force components and three orthogonal torque components.
Format:
force create direct general_force |
|---|
general_force_name = | .model_1.GFORCE_1 |
Adams_id = | 1 |
i_marker_name = | .model_1.part_1.marker_1 |
j_floating_marker_name = | .model_1.part_2.marker_2 |
ref_marker_name = | .model_1.part11.marker_1 |
Description:
Parameter | Value Type | Description |
|---|
general_force_name | String | Specifies the name of the new general_force. You may use this name later to refer to this general_force. |
Adams_id | Integer | Specifies an integer used to identify this element in the Adams data file. |
Comments | String | Specifies comments for the object being created or modified. |
i_marker_name | String | Specifies the marker at which Adams applies the forces and/or torques. |
j_floating_marker_name | String | |
j_part_name | String | Specifies the part on which Adams View creates a floating marker. Adams subsequently applies the reaction forces and/or torques to this "floating" J marker. |
j_marker_id | Integer | Specifies the Adams ID for the floating marker which is automatically created on the J part by Adams View. |
ref_marker_name | String | Specifies a marker that acts as a coordinate reference for the definition of three orthogonal force and/or torque components. |
x_force_function | String | Specifies the x component of the translational force for this element. Adams applies this force parallel to the x axis of the reference marker specified in the REF_MARKER_NAME parameter. |
y_force_function | String | Specifies the y component of the translational force for this element. Adams applies this force parallel to the y axis of the reference marker specified in the REF_MARKER_NAME parameter. |
z_force_function | String | Specifies the z component of the translational force for this element. Adams applies this force parallel to the z axis of the reference marker specified in the REF_MARKER_NAME parameter. To enter a function expression, you enter a series of quoted strings. |
x_torque_function | String | Specifies the x component of the rotational torque for this element. |
y_torque_function | String | Specifies the y component of the rotational torque for the element. |
z_torque_function | String | Specifies the z component of the rotational torque for this element. |
user_function | String | Specifies up to 30 values for Adams to pass to a userwritten subroutine. See the Adams User's Manual for information on writing user-written subroutines. |
Routine | String | |
Extended Definition:
1. A GENERAL_FORCE defines a complete force element, consisting of three mutually orthogonal translational force components and three orthogonal torque components. The two resultant vectors formed by the three component forces and the three component torques determine the direction of the force and torque actions, respectively. The user defines these force and torque components along and about the "reference" marker axes. The reactions are equal and opposite to the action. The user may define the GENERAL_FORCE in Adams View through user-specified function expressions or by specifying up to 30 user-defined parameters that are passed to a user-written subroutine (a "GFOSUB") the user links with Adams.
2. The GENERAL_FORCE corresponds to the Adams GFORCE statement.
3. A GENERAL_FORCE creates a six component force element that applies the forces between two parts of the system. Here, force means three orthogonal translational components and three orthogonal rotational components. The element applies actions to the part to which the I marker belongs and corresponding reactions to the part to which a "floating_marker" belongs. This "floating marker" is automatically created by Adams View and is positioned to be coincident with the I marker. Subsequently, the GENERAL_FORCE internally establishes the position of the "floating_marker". As the system moves, Adams moves the "floating_marker"on its part to keep the "floating_marker" and I markers always superimposed. Thus, Adams applies the reaction force to the part containing the "floating_marker" marker at the instantaneous position of the I marker.
4. The magnitude of the force depends on expressions or subroutines that the user supplies. The value of the force is the resultant (i.e. the square root of the sum of the squares) of (up to) three mutually orthogonal force components together with the resultant (i.e. the square root of the sum of the squares) of (up to) three mutually orthogonal torque components.
5. The resultant vector formed by the three user-defined component forces along the reference marker axes defines the direction of the translational force action. The reaction is equal and opposite to the action. The resultant vector formed by the three component torques determines the direction of the rotational torque action. The user defines these torques about the reference marker axes. The reaction is equal and opposite to the action.
6. The general_force_name parameter specifies the name of the new general_force. You may use this name later to refer to this general_force. Adams View will not allow you to have two general_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. For more information, see
Using Extended Names. They may be of any length. 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 theentity 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.
7. Specifies an integer used to identify this element in the Adams data file. 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.
8. 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 the 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.
9. The user must ensure that the I marker is a fixed marker and on a different part than the part specified in the J_PART_NAME parameter. Because the I marker is a fixed marker, and the "floating" marker will move around on the j_part to remain coincident with the I marker, Adams always applies the force action at a fixed point on the part containing the I marker. The reaction force is applied to the j_part at a point coincident with the I marker. The "floating" marker is automatically created by Adams View on the part specified in the J_PART_NAME parameter.
10. Adams subsequently applies the reaction forces and/or torques to this "floating" J marker. The user must ensure that the j_part is a different part than the part containing the I marker. Adams will move the "floating" J marker around on the j_part to keep it superimposed on the I marker, meaning the point of application of the reaction force may move around on the j_part. Reaction forces are not calculated when the "floating" J marker is on the ground part.
11. Specifies the Adams ID for the floating marker which is automatically created on the J part by Adams View. This allows you to reference the floating marker in a request or function by the ID you specify, instead of letting Adams View generate one.
12. The x-force function specifies the x component of the translational force for this element. Adams applies this force parallel to the x axis of the reference marker specified in the REF_MARKER_NAME parameter. To enter a function expression, you enter a series of quoted strings. 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 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.
13. The y-force function specifies the y component of the translational force for this element. Adams applies this force parallel to the y axis of the reference marker specified in the REF_MARKER_NAME parameter. To enter a function expression, you enter a series of quoted strings. 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 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.
14. The z-force function specifies the z component of the translational force for this element. Adams applies this force parallel to the z axis of the reference marker specified in the REF_MARKER_NAME parameter. To enter a function expression you enter a series of quoted strings. 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 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.
15. The user_function parameter 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.