The Altair Bushing Model reads a property file that contains all of the information required for a bushing at run-time. This property file is known as the Bushing Property file or General Bushing System property file and uses the extension .gbs.
The following table shows the structure of the .gbs file:
Structure of the GBS File |
|||||||||
|
The .gbs file uses the TeimOrbit format organized into the following blocks:
Block Type |
Description |
HEADER |
Mandatory block specifying the file type, version, and format information for use by file readers. |
UNITS |
Mandatory block that specifies the unit system for parameter values in the property file. This block enables file readers to convert the parameter values in the property file to those used in the simulation. |
GLOBAL |
Mandatory block specifying whether or not to couple the X-, Y-, and Z-direction force computations and the X-, Y-, and Z-direction moment computations. |
DIRECTIONS |
Mandatory block that specifies the force formulations active for each force and moment direction. |
PARAMETER |
Parameter blocks for the active force methods for each direction. For each force direction of interest the .gbs file contains six blocks. These are shown in brown in the figure below. In order to conserve space, the force blocks are shown in multiple columns, though in the file they are organized one below the other. Since six possible directions of interest exist, the .gbs file can contain up to 36 blocks of information containing the force data. The string, FX, FY, FZ, TX, TY, or TZ, is appended to the block name to identify the direction, for example: [CONSTANT_STIFFNESS_FZ]. Force models selected in the ACTIVITY table must have a corresponding parameter block in the .gbs file. Parameter blocks are available for the following force methods: |
FRICTION |
Friction blocks support the parameters for the LuGre friction model—a model that supports both static and dynamic friction. |
The following section provides a detailed definition for each block:
The header block contains metadata for use by file readers to identify the type, version and format of the file. This is a mandatory block. The keywords that are used in this block are:
The following is an example of a HEADER block:
$-----------------------------------------------------------------HEADER [HEADER] FILE_TYPE = 'gbs' FILE_VERSION = '1' FILE_FORMAT = 'ASCII'
|
The units block specifies the unit system used for the values in the property file. This is a mandatory block. The units must be defined for length, time, force, mass, and angle. The table below describes the valid choices for the Units block:
The following is an example of a Units block: $--------------------------------------------------------------- UNITS [UNITS] LENGTH = 'mm' ANGLE = 'degree' FORCE = 'newton' MASS = 'kg' TIME = 'second'
|
The Global block contains settings for coupling the X, Y, and Z direction force computations and the X, Y, Z direction moment computations. This block is mandatory.
The following is an example of a Global block: $-------------------------------------------------------------- GLOBAL [GLOBAL] COUPLING = 'spherical' |
The Directions block selects what force formulations the simulation model uses for each force and torque direction. This is a mandatory block. The block contains a table where each row is a force method and each column a force or torque direction. To select or turn on a force formulation for a given force direction, enter 1 in the corresponding row and column. To turn off a force method for a given force direction, enter 0 (zero).
Some of the formulations are mutually exclusive and some of the formulations can be added in parallel.
In the following example, the stiffness models are shown in blue and damping models in green.
$$---------------------------------------------------------- DIRECTIONS [DIRECTIONS] (ACTIVITY) { formulation FX FY FZ TX TY TZ } 'SPLINE_STIFFNESS' 1 0 0 0 0 1 'CONSTANT_STIFFNESS' 0 1 1 0 1 0 'CUBIC_STIFFNESS' 0 0 0 1 0 0 'CONSTANT_DAMPING' 0 0 1 1 1 0 'RUBBER_DAMPING' 1 0 0 0 0 1 'HYDROMOUNT_DAMPING' 0 1 0 0 0 0
The net force output for any direction is the sum of the forces due to the active force formulations in that direction.
|
Friction parameters for the LuGre model are defined in the Friction block as shown in the following table:
The following table describes the type and dimension for the various input parameters. Abbreviations are: [F] = force, [L] = length, [T] = time.
The example below shows the specification of a LuGre Friction block in the .gbs file: $--------------------------------------------------------------- [LUGRE_FRICTION] MU_STATIC = 0.0 MU_DYNAMIC = 0.0 ANALYSIS_MODES = 'STATICS_AND_DYNAMICS' EFFECT = 'SLIDING' USE_FORCE = 'YES' TRANSITION_VELOCITY = 0.1000 BRISTLE_STIFFNESS = 0.0100 BRISTLE_DAMPING = 0.31625 SLIP_DAMPING = 0.0008 TORQUE_FROM_PRELOAD = 526.882 BALL_RADIUS = 10.0
|