You can create a connector acceleration boundary condition to prescribe an acceleration for the available components of relative motion of connectors.
To create or edit a connector acceleration boundary condition:
Display the connector acceleration boundary condition editor using one of the following methods:
To create a new connector acceleration boundary condition, follow the procedure outlined in “Creating boundary conditions,” Section 16.8.2 (Category: Mechanical; Types for Selected Step: Connector acceleration).
To edit an existing connector acceleration boundary condition using menus or managers, see “Editing step-dependent objects,” Section 3.4.12. To edit the region to which the boundary condition is applied, see “Editing the region to which a prescribed condition is applied,” Section 16.8.4.
If a Distribution field appears in the editor, click the arrow to the right of the field, and select one of the following:
Select Uniform to define a uniform boundary condition.
Select User-defined to define the boundary condition in user subroutine DISP. See the following sections for more information:
If you are defining the boundary condition directly in the editor (and not in user subroutine DISP), perform the following steps:
Use the appropriate method to define the boundary condition. Only components common to all of the selected wires are available in the editor.
If no text fields appear next to each component of relative motion:
You can use the following techniques to define the boundary condition:
Toggle on a component of relative motion to fix the value at zero.
Toggle off a component of relative motion to leave the component of relative motion unconstrained.
If text fields appear next to each component of relative motion:
You can use the following techniques to define the boundary condition:
Toggle on a component of relative motion to constrain the component of relative motion. The text field becomes available in which you can specify a value for the component of relative motion. If you are creating the boundary condition in this step, a default value of zero appears in the text field. If you are modifying the boundary condition in this step, the value propagated from the previous step appears in the text field.
Toggle off a component of relative motion to leave the component of relative motion unconstrained. If you toggle off a component of relative motion after modifying the default or propagated value in the text field, the modified value is lost. If you toggle that component of relative motion back on, the default or propagated value reappears in the text field.
Click the arrow to the right of the Amplitude field, and select the amplitude of your choice from the list that appears. Alternatively, you can click Create to create a new amplitude. (See Chapter 38, “The Amplitude toolset,” for more information.)
Click OK to save your data and to exit the editor.
If you are defining the boundary condition in user subroutine DISP, perform the following steps:
If desired, use the following techniques to define the acceleration. Only components common to all of the selected wires are available in the editor.
Toggle on a component of relative motion to constrain the component of relative motion. If you are in the initial step, that component of relative motion is set to zero. If you are in any step other than the initial step, a text field becomes available in which you can specify a value for the component of relative motion.
Toggle off a component of relative motion to leave the component of relative motion unconstrained.
Click OK to save your data and to exit the editor.
Enter the Job module and display the job editor for the analysis job of interest. (For more information, see “Creating, editing, and manipulating jobs,” Section 18.5.)
In the job editor, click the General tab, and specify the file containing the user subroutine that defines the boundary condition. For more information, see “Specifying general job settings,” Section 18.6.6.
Note: You can specify only one user subroutine file in the job editor; if your analysis involves more than one user subroutine, you must combine the user subroutines into one file and then specify that file.
