Body: Flexible

Model Element

Description

Body_Flexible defines a flexible body object in MotionSolve. MotionSolve supports two kinds of flexible bodies:

•

Linear flexible body: This is a representation of the flexible component obtained by carrying out a Component Mode Synthesis (CMS) analysis. This entity has mass and inertia properties just like a rigid body. In addition, it has flexibility properties that allow it to deform under loads. The deformation is defined using a set of spatial mode shapes and time dependent modal coordinates. Such a body is linearly flexible meaning that it cannot handle non-linear or “large” deformations.

•

Non-linear Finite Element (NLFE) body: This is a fully non-linear finite element representation of the flexible component and does not require a pre-analysis to create. This entity, like the CMS flexible body, has mass and inertia properties. Owing to its fully non-linear formulation, this body is capable of handling “small” as well as “large” deformation.

A Body_Flexible may be connected to the rest of the system using any combination of constraints, motions, or applied forces. It does not support contact natively.

Linear Flexible Body:

The CMS flexible body operates in 3-D space where it can simultaneously undergo large overall motion and small deformations. Two types of CMS methods are supported: Craig-Bampton and Craig-Chang.

All the CMS data is encapsulated in a Reference_FlexData element. Every Body_Flexible element refers to a Reference_FlexData element that contains:

•	General information about the number of modes selected, rigid body properties, number of interface nodes, and so on.

•	Mode data block, which contains the frequency, eigenvalue, and damping for each mode.

•	Node data block, which contains:

o	Coordinates of the interface nodes chosen.

o	Mode shape corresponding to each of the interface nodes selected.

o	Inertia data block, which contains the inertia invariants required for the definition of the flexible body.

Every Body_Flexible element also refers to a Local Part Reference Frame (LPRF). This is the global coordinate system used for the finite element model and also serves as the coordinate system for the information in the Reference_FlexData element.

Reference_FlexData contains default damping properties associated with the flexible body. These may be overridden in the flexible body definition in two ways:

•	Modal damping as a function expression, or

•	DMPSUB user defined subroutine.

A finite element mesh and an optional scale factor may be provided while defining a Body_Flexible. This information is used to generate an H3D animation file. The H3D file containing the mesh data and the animation scale is not directly used in the simulation.

NLFE Body:

The NLFE body, like the CMS flexible body, also operates in 3-D space where it can simultaneously undergo large overall motion and large deformations. The NLFE body can be created and modified completely within MotionView. The NLFE body is represented as a Body_Flexible in the MotionSolve deck. Since this body is similar to a finite element component, the flexibility data is determined by specifying the geometric and material properties of the component in MotionView. This information is written to an XML file upon solver export, which is used by MotionSolve while solving the model and also while post-processing the results. Typically the contents of this XML file are statements that:

•	Define the grid locations and their gradients

•	Define the elements and their types

•	Define the properties of the flexible component

•	Define any other connector elements

The formulation of the NLFE body is based on the “Absolute Nodal Coordinate Formulation” in which the coordinates are always defined with respect to the global frame. Thus this body does not refer to a Local Part Reference Frame (LPRF), unlike the CMS flexible body.

You may specify Rayleigh damping for your flexible component. This damping is numerical in nature and care should be taken while using this parameter. Too large a value may lead to solution instabilities.

The connectivity and geometric properties defined for the NLFE body in MotionView determine the mesh for visualization of the NLFE body in the post processor. The animation H3D can be used to visualize stresses, strains and displacements just like the CMS flexible body.

Format – CMS Flexible Body

<Body_Flexible

id = "integer"

label = "string"

lprf_id = "integer"

mass = "real"

inertia_xx = "real"

inertia_yy = "real"

inertia_zz = "real"

inertia_xy = "real"

inertia_yz = "real"

inertia_xz = "real"

cm_x = "real"

cm_y = "real"

cm_z = "real"

h3d_file = "string"

flexdata_id = "integer"

animation_scale = "real"

is_user_damp = "{ TRUE | FALSE }"

{

cdamp_expr = "string"

usrsub_dll_name = "string"

usrsub_param_string = "USER([par_1, ..., par_n])"

usrsub_fnc_name = "string"

script_name = "string"

interpreter = "PYTHON"

usrsub_param_string = "USER([par_1, ..., par_n])"

usrsub_fnc_name = "string"

}

[[

rigidfied = "{ TRUE | FALSE}"

geostiff = "{ TRUE | FALSE}"

v_ic_x = "real"

v_ic_y = "real"

v_ic_z = "real"

w_ic_x = "real"

w_ic_y = "real"

w_ic_z = "real"

v_ic_x_flag = "{ TRUE | FALSE}"

v_ic_y_flag = "{ TRUE | FALSE}"

v_ic_z_flag = "{ TRUE | FALSE}"

w_ic_x_flag = "{ TRUE | FALSE}"

w_ic_y_flag = "{ TRUE | FALSE}"

w_ic_z_flag = "{ TRUE | FALSE}"

vm_id = "integer"

wm_id = "integer"

]]

Format – NLFE Body

<Body_Flexible

id = "integer"

label = "string"

ref_marker_id = "integer"

ancf_file = "string"

rayleigh_damping = "real"

num_i_marker = "integer"

[[

v_ic_x = "real"

v_ic_y = "real"

v_ic_z = "real"

v_ic_x_flag = "real"

v_ic_y_flag = "real"

v_ic_z_flag = "real"

w_ic_x = "real"

w_ic_y = "real"

w_ic_z = "real"

w_ic_x_flag = "real"

w_ic_y_flag = "real"

w_ic_z_flag = "real"

]]

< ! -- The area below lists IDs of markers attached to the NLFE body -- >

ID1 ID2 ... IDn

</Body_Flexible>

Attributes

Element identification number (integer>0).

This is a number that is unique among all Body_Flexible elements.

label

The name of the Body_Flexible element.

lprf_id

(CMS only) Specifies the ID of a Reference_Marker that defines the finite element global coordinate system in the MBS model.

ref_marker_id

(NLFE only) Specifies the ID of a Reference_Marker. The components of the relative displacement, relative velocity and forces are resolved in the coordinate system specified by ref_marker_id.

This is set to the ground reference frame.

mass

(CMS only) Specifies the mass of the Body_Flexible object. For the CMS flexible body, the mass is computed using information available in the CMS H3D file that represents the flexible component.

inertia_xx

inertia_yy

inertia_zz

inertia_xy

inertia_yz

inertia_xz

(CMS only) Defines the moments of inertia and the products of inertia of the CMS flexible body about the origin of the lprf_id marker and about its x-, y- and z-axes, respectively.

The attributes inertia_xx, inertia_yy, inertia_zz, inertia_xy, inertia_yz, and inertia_xz are typically calculated using information that is available in the CMS flexibly body representation.

When specified, inertia_xx, inertia_yy, and inertia_zz need to be strictly positive.

cm_x, cm_y, cm_z

(CMS only) Center marker x, y and z.

h3d_file

(CMS only) Specifies the name of the file that contains all the nodes in the finite element mesh. This file is needed only for creating an animation file. The solver does not use it for analysis.

ancf_file

(NLFE only) Specifies the complete or relative path and name of the XML that contains geometric and material property data for the NLFE body

flexdata_id

(CMS only) Specifies the ID of the Reference_FlexData object that contains the CMS representation for the flexible body.

animation_scale

(CMS only) Specifies the scale factor for animating the mode shapes. This information is used only for creating the animation file. The solver does not require this for analysis.

is_user_damp

(CMS only) A Boolean value that specifies how the damping coefficient for each mode is specified. A value of "TRUE" indicates that the damping is specified using either an expression or a user defined subroutine.

A value of "FALSE" causes MotionSolve to ignore the damping expression or user defined subroutine data provided in the Body_Flexible element and instead, use the damping values specified in the Reference_FlexData element.

cdamp_expr

(CMS only) A state dependent expression that defines the damping coefficient for each mode. Any valid run-time MotionSolve expression can be provided as input. MotionSolve uses this parameter only when is_user_damp = "TRUE".

usrsub_dll_name

(CMS only) Specifies the path and name of the DLL or shared library containing the user subroutine. MotionSolve uses this information to load the subroutine specified by usrsub_fnc_name in the user library at run time. Use this keyword only when is_user_damp = "TRUE".

usrsub_param_string

(CMS only) The list of parameters that are passed from the data file to the user defined subroutine. Use this keyword only when type = USERSUB is selected. This attribute is common to all types of user subroutines/scripts.

usrsub_fnc_name

(CMS only) Specifies an alternative name for the user subroutine DMPSUB.

script_name

(CMS only) Specifies the path and name of the user written script that contains the routine specified by usrsub_fnc_name.

interpreter

(CMS only) Specifies the interpreted language that the user script is written in. Valid choices are MATLAB or PYTHON.

rayleigh_damping

(NLFE only) Specifies the value of a Rayleigh damping coefficient for the NLFE body. See Comment 1 for more details.

num_i_marker

(NLFE only) Specifies the number of markers that are attached to this NLFE body. These markers can be thought of as interface markers where the NLFE body can connect with the rest of the multi-body system.

num_i_marker > 0

See Comment 1 for more details on this constraint

rigidified

(CMS only) A Boolean flag that allows you to convert the flexible body to a rigid body. This flag is optional. The default value for this flag is rigidfied = “FALSE”.

See Comment 4 for a discussion on this attribute.

geostiff

(CMS only) A Boolean flag that allows you to model the geometric stiffening effect in your CMS flexible body. The default for geostiff is FALSE.

Note: The geometric stiffening data must be available in the H3D for MotionSolve to be able to use it. Please see the tutorial on Geometric Stiffening for more information on generating a CMS flexible body with geometric stiffening data. See Comment 5 for more information.

v_ic_x

v_ic_y

v_ic_z

These attributes specify the initial translational velocity of the flexible body along the X, Y and Z axes respectively.

For CMS flexible bodies, you may define the local part reference frame (LPRF) velocities with respect to any coordinate system. The marker representing this coordinate system is defined by vm_id.

For NLFE bodies, the velocities are applied along the global X, Y and Z directions respectively.

v_ic_x, v_ic_y and v_ic_z are optional. They are assumed to be zero when not specified. MotionSolve may change these values to ensure that the initial velocities satisfy the system constraints.

w_ic_x

w_ic_y

w_ic_z

These attributes specify the initial angular velocity of the flexible body about the X, Y and Z axes respectively.

For CMS flexible bodies, you may define the local part reference frame (LPRF) velocities with respect to any coordinate system. The marker representing this coordinate system is defined by wm_id.

For NLFE bodies, the velocities are applied about the global X, Y and Z axes, respectively.

w_ic_x, w_ic_y and w_ic_z are optional. They are assumed to be zero when not specified. MotionSolve may change these values to ensure that the initial velocities satisfy the system constraints.

v_ic_x_flag

v_ic_y_flag

v_ic_z_flag

Boolean flags that indicate whether the X, Y or Z velocity is known exactly or is just an initial guess.

"TRUE" means this initial condition is applied exactly unless it is in conflict with a Motion input.

"FALSE" means this initial condition is applied as an initial guess. It may be changed by MotionSolve to ensure that all constraints are satisfied.

w_ic_x_flag

w_ic_y_flag

w_ic_z_flag

Boolean flags that indicate whether the angular velocities about the X, Y or Z axis is known exactly or is just an initial guess.

"TRUE" means this initial condition is applied exactly unless it is in conflict with a Motion input.

"FALSE" means this initial condition is applied as an initial guess. It may be changed by MotionSolve to ensure that all constraints are satisfied.

vm_id

(CMS only) Specifies the ID of a marker with respect to which the translation initial velocities are applied. If not specified, the velocities are applied with respect to the global frame

wm_id

(CMS only) Specifies the ID of a marker with respect to which the rotational initial velocities are applied. If not specified, the velocities are applied with respect to the global frame

ID1 ID2 … IDn

(NLFE only) A list of the IDs of the markers that are used to connect the NLFE body to the rest of the multi-body system

Comments

1.	MotionSolve supports two kinds of flexible bodies – CMS and NLFE flexible bodies. The following table lists key comparisons between the two:

	CMS flexible body	NLFE flexible body
Creating flexible bodies	User meshing is required to represent the component	No user meshing required for creating LD Body sub-systems through MotionView
	An additional CMS analysis is required to generate a modal representation of the flexible component	No analysis required to create an LD body. The LD Body can be created and modified directly in MotionView
	Line, shell and solid elements are supported	Only line elements are supported
	Connect to joints, forces etc. by defining interface nodes in CMS analysis	All nodes can be used as interface nodes – no special handling is required.
Modeling flexibility in components	Only accurate up to a linear deformation range, i.e. for small deformations; Must capture enough modal information to represent physical deformation accurately	Fully non-linear formulation allows accurate solution for small and large deformations without any reduction analysis
Modeling geometric non-linearity in flexible components	Cannot handle large deformations in general	The BEAM and CABLE element allow you to model large deformations in your flexible components
Modeling material non-linearity in flexible components	Does not support non-linear material models	You can model your flexible components with hyper elastic as well as linear elastic materials
Recover stresses and strains	Yes	Yes. MotionSolve writes out a 3D representation of the Beam and Cable elements to enable stress, strain and displacement visualizations in HyperView

CMS Flexible Bodies:

CMS flexible bodies are created by performing a component mode synthesis on an FE model using Altair’s FE Solver OptiStruct. Both Craig-Bampton and Craig_Chang methodologies are supported. The CMS data is stored in a Reference_FlexData element and is referred to by the attribute flexdata_id. OptiStruct can accept finite element data from the following sources.

HyperMesh

Patran

NASTRAN

ABAQUS

CMS represents the deformation characteristics of a flexible body. It must not contain the rigid body modes. These are automatically filtered out. If you see modes with eigenvalues close to zero in a Reference_FlexData element, be suspicious of the quality of the CMS data.

Modal damping for a CMS flexible body can be specified in two ways:

o	By setting is_user_damp to FALSE and defining damping in the Reference_FlexData element.

o	By setting is_user_damp to TRUE and defining damping in the Body_Flexible element with either the user defined subroutine DMPSUB or an expression.

Note the damping may only be a function of time, FXFREQ and FXMODE. It may not be a function of the system states. Thus, the access functions SYSFNC() and SYSARY() may not be invoked from a DMPSUB.

For the case when is_user_damp is set to FALSE, the default damping for the flexible body is as follows:

o	1% for modes under 100 Hz.

o	10% for modes from 100 to 1000 Hz.

o	Critical damping for modes over 1000 Hz.

The stresses, strains and displacements are written to the animation H3D file and can be visualized in HyperView. MotionSolve uses the mesh information from the H3D file specified by the attribute h3d_file to do this. The h3d_file is only used for animation purposes. It is not used by the solver, if you leave it blank, or the flex H3D file is not found in the specified location, the analysis will not be affected. But, the flexible body will not be shown in the animation. In some cases, the animation H3D file may be too large. In those cases, if stress and deformation results are not of interest, the h3d_file attribute may be omitted.

NLFE Bodies:

NLFE bodies are created within MotionView either individually or through sub-systems. The NLFE body is defined by its geometric and material properties. MotionSolve currently supports LINE elements (i.e. elements that connect two points in space). Two kind of elements are supported – CABLE and BEAM elements. The table below lists key differences between the two:

Element

Description

CABLE

The CABLE element does not resist shear or torsion forces. This implies that the cross section of this element does not change.

This element can be used to model cables, wires etc.

BEAM

The BEAM element resists all forms of deformation which implies that the cross section can also deform with load. This can be visualized in HyperView while using this element.

Multiple cross sections are supported for the BEAM element:

o	Circular (solid and hollow)

o	Rectangular or Box (solid and hollow)

Channel

Cross

Hat

o	H, I, L, T and Z sections

This element can be used to model beams, springs, belts, rubber components etc.

An XML file is created for each NLFE body in your system upon exporting the model to MotionSolve. This XML is referred by the Body_Flexible element in your model using the attribute ancf_file. This file typically contains the following information about your NLFE body:

o	Geometrical information like grid positions, connectivity information etc.

o	Material information for the NLFE body

o	Unit information for the model

Due to the full non-linear formulation of the NLFE body, it can be used to model large deformations. Also, you can choose non-linear material models for use with the BEAM element thus allowing you to model hyper-elastic components like rubber. Some of the typical situations in which using NLFE bodies may be advantageous are:

o	Large deformations are expected in your flexible part that can be modeled using BEAM or CABLE elements

o	An unusually big displacement is observed when using CMS flexible part

o	The stress for your CMS flexible part approaches the yield point of the material

o	Hyper-elastic materials like rubber need to be modeled in your system

o	There is a need to visualize stresses in components created using poly-beams

Conversely, The NLFE body in MotionSolve is not designed to replace an FE structural analysis. Increasing the number of NLFE elements in your multi-body system will result in a deterioration of solver performance and it is generally not recommended to replace an FE analysis with an equivalent multi-body analysis using NLFE bodies.

Damping for an NLFE body can be applied by specifying a non-zero value for the attribute rayleigh_damping. Rayleigh damping tries to mimic physical damping. Depending on the model, large values of this parameter can lead to an unstable solution. It is recommended to start with a small value and increase it till the desired system response is achieved.

The NLFE body can be connected to the rest of the multi-body system through most force and constraint elements. Each point on the NLFE body can be thought of as an interface node. Note: It is required to have at least one marker attached to the NLFE body (num_i_marker > 0). This is due to the way in which NLFE bodies are implemented in MotionSolve.

The stresses, strains and displacements are written to the animation H3D file and can be visualized in HyperView. MotionSolve generates the mesh information from the NLFE body’s geometric information. In some cases, the animation H3D file may be too large. In those cases, you can try to reduce the number of segments for post-processing in the NLFE body panel in MotionView.

MotionSolve provides you with non-linear hyper-elastic material models to simulate elastomers (for example rubber) and other materials that can undergo large, reversible elastic deformations. On removal of the load, these materials return to their original shape. Such materials typically have the following characteristics:

o	They can undergo large deformations and thus have large strain

o	The relationship between the stress and strain is highly non-linear often containing multiple inflection points

Shown below is a stress-strain relationship for a uniaxial test of a rod modeled using BEAM elements and using different hyper-elastic material models:

body_flexible_2

Figure 1: Engineering stress vs Engineering strain for hyper-elastic material models

Three non-linear hyper-elastic material models are available to use:

o	Neo-Hookean compressible: This is the simplest form of a hyper-elastic material model and is based on a strain energy density function. The material Shear Modulus, Poisson’s ratio and element density are specified as inputs for this model.

Mooney-Rivlin: The MR material model is a development of the Neo-Hookean model and is available in a two-parameter form in MotionSolve. Such a model is useful when the material stress-strain curve has a single curvature i.e. no inflection points. The material’s Poisson ratio and density, in addition to two material constants are specified as inputs for this model. The two material constants are typically obtained from curve fitting of test data obtained from axial or biaxial compression or tension tests.

o	Yeoh: The Yeoh model within MotionSolve is available as a three parameter model that has been shown to satisfactorily model various modes of deformation based on data from a uniaxial tensile test [1].

3.	MotionSolve does not use Euler Angles to represent large rotations. Consequently, it does not suffer from the "Euler Singularity" problem, where the angles defining the 3-D rotation are non-unique.

4.	The Boolean attribute “rigidified” is used to specify whether the flexible body should be modeled as such or as a rigid body. This can also be done using the <Body_Flexible> command element (see example 4 below) or by using the MotionSolve specific utility sub-routine c_modset.

Note: A rigidified flex-body is computationally more efficient than a pure flexible body, but less efficient than a pure rigid body, due to implementation differences. As a result, in some cases where the solver takes many iterations to achieve a static equilibrium, it may be a good practice to do the following:

1.	Convert all flex-bodies to rigidified flex bodies.

2.	Run a static simulation.

3.	Convert all rigidified flex bodies back to pure flex bodies.

4.	Run a static simulation again.

The above steps may reduce the total number of solver steps required to achieve static equilibrium. However, since static convergence is model dependent, the above may not help in some cases.

Geometric or stress stiffening is a non-linear geometric effect most commonly seen in thin, slender structures (flexible control arms, rotor blades, turbine blades, etc.) subjected to a tension load. In such a case, the frequency of the fundamental modes increases as the tension is increased. This effect can also be seen in a flexible beam undergoing large rigid body rotation, for example a rotor blade. Due to increasing rotation speed, the tensile (centrifugal) force acting on the blade increases, which increases the frequency of the beam’s fundamental modes, thereby resulting in an increased bending stiffness of the beam.

To include this coupling effect for your CMS flexible body, you need to generate the additional stiffening data (represented as <GeoStiff> in MotionSolve) at the time of generating the CMS flexible body.

Example 1

The image below shows the boom in a back-hoe loader:

Figure 2: Using a CMS flexible body to model the boom in a back-hoe loader

Because of the large hydraulic forces acting on the arm, the flexibility of the arm plays a significant role in determining the overall behavior of the system and the forces at the pivot points.

The definition of the flexible boom is shown below. Note that is_user_damping is set to FALSE and hence, damping is defined in the Reference_FlexData element.

The flexible body refers to Reference_FlexData 11. This defines the CMS representation of the flexible body.

•	The flexible body has 5 attachment points or interface nodes.

•	31 modes are used to represent the deformation shapes.

•	The original finite element mesh has 36,382 nodes.

•	The mass of the body is 343.79447 Kg.

•	The inertia at zero deformation is:

•	Ixx = 71.424 kgm2, Iyy = 204.970 kgm2, Izz = 270.996 kgm2

•	Ixy = -108.571 kgm2, Iyz = -0.0007927 kgm2, Izx = -0.0013968 kgm2

•	All modes above 1000 radians/second are critically damped (mode numbers 25 – 37).

The Reference_FlexData card is shown below.

<Reference_Flexdata

id = "11"

num_nodes = "36382"

num_sel_modes = "31"

num_sel_nodes = "5" >

7 1.6383385E+02 1.0596634E+06 1.0000000E-01

8 2.1524734E+02 1.8290949E+06 1.0000000E-01

9 2.3918134E+02 2.2584748E+06 1.0000000E-01

...

34 2.6830053E+03 2.8418668E+08 1.0000000E+00

35 2.7798731E+03 3.0507780E+08 1.0000000E+00

36 3.5534390E+03 4.9849222E+08 1.0000000E+00

37 4.4473195E+03 7.8083150E+08 1.0000000E+00

</ModeData>

320900 -4.1635098E+00 -3.7339999E-01 -1.3000000E-01

320905 -3.7123201E+00 1.6183400E-01 1.0700000E-10

320906 -4.2820601E+00 1.4321400E-01 -2.5000000E-02

320917 -5.7897798E+00 -1.0092300E+00 -1.6000000E-01

320919 -6.1077402E+00 -1.1671100E+00 -1.3000000E-01

-2.7620662E-03 -1.5999271E-02 -1.3520377E-02 -1.2305416E-01 2.1246834E-02 -1.8486151E-06

2.3995511E-07 -2.7162932E-06 -8.7264590E-02 -3.7223276E-02 1.3226432E-01 -1.4547608E-05

-2.7368159E-03 -3.5339149E-03 -1.4723917E-03 -1.4127485E-01 1.0950999E-01 1.5551852E-05

...

1.5056358E-02 9.0596480E-03 6.5006730E-05 -2.5446518E-04 1.5557368E-03 1.5840490E-01

-4.4426341E-02 1.0682830E-01 5.2728883E-05 2.6002291E-03 -1.4042209E-03 -4.8935637E+00

1.8613113E-02 -4.1820321E-02 6.9122898E-06 -7.9896546E-04 -5.2661070E-04 -5.9843439E-01

</NodeData>

8.7288856E-01 -4.8791962E-01 -4.4323963E-06 4.8791962E-01 8.7288856E-01 -4.7179542E-06

6.1709705E-06 1.9555952E-06 1.0000000E+00 -4.8517495E+00 -5.0135241E-01 -2.1201009E-06

2.6295942E+02 8.0369704E+00 2.6993996E+00 1.5783882E+02 -9.4482949E+02 -4.9331539E-03

-9.4482949E+02 8.2977114E+03 -1.1581632E-03 -4.9331539E-03 -1.1581632E-03 8.4501514E+03

</InertiaData>

</Reference_Flexdata>

Example 2

In the following example, damping is specified using a MotionSolve expression. Note that is_user_damp is set to TRUE.

<Body_Flexible

id = "30102"

lprf_id = "63330102"

h3d_file = "../../flex_h3d/beam.h3d"

is_user_damp = "TRUE"

cdamp_expr = "IF (FXFREQ-100:0.01,0.1,IF (FXFREQ-1000:0.1,1.,1))"

flexdata_id = "30102"

animation_scale = "1."

Example 3

In the following example, damping is specified using a user defined subroutine (DMPSUB). Note that is_user_damp is set to TRUE.

<Body_Flexible

id = "30102"

lprf_id = "633301012"

h3d_file = "../../flex_h3d/beam.h3d"

is_user_damp = "TRUE"

usrsub_param_string = "USER (0.01,100,0.1,1000,1)"

usrsub_dll_name = "NULL"

usrsub_fnc_name = "DMPSUB"

flexdata_id = "30102"

animation_scale = "1."

Example 4

The following lines show an example for converting a flexible body (0-3 seconds) to a rigid body (3-6 seconds) and then back to flexible body (6-10 seconds).

<Simulate

analysis_type = "Transient"

end_time = "3.0"

print_interval = "0.01"

<Body_Flexible

id = "30102"

rigidified = "TRUE"

<Simulate

analysis_type = "Transient"

end_time = "6.0"

print_interval = "0.01"

<Body_Flexible

id = "30102"

rigidified = "FALSE"

<Simulate

analysis_type = "Transient"

end_time = "10.0"

print_interval = "0.01"

Example 5

The following example shows how an NLFE body can be used to model a stabilizer bar used in the front suspension of an automobile.

body_flexible_3

Figure 3: NLFE body used to create a stabilizer bar flexible part

The NLFE body is represented in MotionSolve by the Body_Flexible statement:

<Body_Flexible

id = "30601"

label = "Stabilizer Bar"

ref_marker_id = "30101010"

ancf_file = "stabar_NLFE_30601.xml"

rayleigh_damping = "0.5"

num_i_marker = "4">

30601011 30601191 30601091 30601111

</Body_Flexible>

Markers 30601011, 30601191, 30601091 and 30601111 are used to attach the NLFE system to the rest of the vehicle. Marker 30101010 is a ground reference marker located at the origin.

The NLFE body is defined in the file “stabar_NLFE_30601.xml” as follows:

...

...

</ANCFModel>

As can be seen from the file above, the stabilizer bar is defined by BEAM elements of a circular cross section. The NLFE body refers to a linear elastic material.

References

[1] Mac Donald Brian J. Practical Stress Analysis with Finite Elements. Dublin: Glasnevin Publishing, 2007. Print.

Model Element
Description
FLEX_BODY defines a flexible body object in MotionSolve. For more details on the implementation of the flexible body and usage, please see Body_Flexible.
Declaration
def FLEX_BODY(id, LABEL="", QG=[], REULER=[], VX=0.0, VY=0.0, VZ=0.0, WX=0.0, WY=0.0, WZ=0.0, VM=0, WM=0, MTX_FILE="", H3D_FILE="", MASS=0.0, IP=[], CM=[], RIGIDIFIED=False, CRATIO="", ROUTINE="", INTERPRETER="", SCRIPT=""):
Attributes
id	Element identification number (integer>0). This number is unique among all of the FLEX_BODY elements.
LABEL	The name of the FLEX_BODY element.
QG	Specifies the coordinates of the local FLEX_BODY reference marker that defines the finite element global coordinate with respect to the MBS model global coordinate system.
REULER	Specifies the Euler angles of the local FLEX_BODY reference marker with respect to the global axes system.
VX	Specifies the initial translational velocity of the FLEX_BODY along the VM x-axis.
VY	Specifies the initial translational velocity of the FLEX_BODY along the VM y-axis.
VZ	Specifies the initial translational velocity of the FLEX_BODY along the VM z-axis.
WX	Specifies the initial rotational velocity of the FLEX_BODY about the WM x-axis.
WY	Specifies the initial rotational velocity of the FLEX_BODY about the WM y-axis.
WZ	Specifies the initial rotational velocity of the FLEX_BODY about the WM z-axis.
VM	Specifies the ID of the Marker whose axes' system would be used to define the initial translational velocities of the FLEX_BODY (VX,VY,VZ). When not specified, it defaults to Global axes system.
WM	Specifies the ID of the Marker whose axes' system would be used to define the initial rotational velocities of the FLEX_BODY (WX,WY,WZ). When not specified, it defaults to CM axes system.
MTX_FILE	Specifies the name of the MTX file that contains the CMS representation for the flexible body. The MASS, CM, and IP properties are obtained from the MTX file.
H3D_FILE	Specifies the name of the H3D file that contains all the nodes in the finite element mesh. This file is needed only for creating an animation file. The solver does not use it for analysis.
MASS	Specifies the mass of the FLEX_BODY object. When specified, mass must be a positive number. The attribute MASS is optional. MotionSolve obtains the MASS value from the MTX file. However, if this parameter is specified, MotionSolve will use the specified value.
IP	Specifies the mass moments of inertia and the products of inertia of the FLEX_BODY about the x,y,z axes, in the order of Ixx,Iyy,Izz,Ixy,Ixz,Iyz. These attributes are to be specified in the following order: inertia_xx, inertia_yy, inertia_zz, inertia_xy, inertia_yz and inertia_zx. These attributes are optional. MotionSolve obtains the IP values from the MTX file. However, if these parameters are specified, MotionSolve will use the specified values. When specified: Inertia_xx > 0 Inertia_yy > 0 Inertia_zz > 0
CM	Specifies the coordinates of the center-of-mass of the FLEX_BODY. This attribute is optional. MotionSolve obtains the CM values from the MTX file. However, if this parameter is specified, MotionSolve will use the specified values.
RIGIDIFIED	A Boolean that allows you to convert the flexible body to a rigid body. Specify either TRUE or FALSE. This flag is optional. The default is FALSE.
CRATIO	Defines a state-dependent expression that defines the damping coefficient for each mode. Any valid run-time MotionSolve expression can be provided as input. The list of parameters that are passed from the data file to the user defined subroutine. This attribute is common to all types of user subroutines and scripts.
ROUTINE	Specifies an alternative name for the user subroutine DMPSUB.
INTERPRETER	Specifies the interpreted language that the user script is written in. Valid choices are MATLAB or PYTHON.
SCRIPT	Specifies the path and name of the user written script that contains the routine.
Comments See Body_Flexible
Example The first example below demonstrates the one possible specification of the FLEX_BODY. FLEX_BODY(11, LABEL="FLEXIBLE_BODY element name", QG=[0,5,0], MTX_FILE="11", H3D_FILE="c:/work/boom.h3d", CRATIO=0.0) The second example below demonstrates the specification of the FLEX_BODY where damping is specified using expression FLEX_BODY(30102, QG=[10,12,0], MTX_FILE="30102", H3D_FILE=" ../../flex_h3d/beam.h3d", CRATIO="IF(FXFREQ-100:0.01,0.1,IF(FXFREQ-1000:0.1,1.,1.))") The third example demonstrates the specification of the FLEX_BODY where damping is specified using user defined subroutine (DMPSUB) FLEX_BODY(30102, QG=[10,12,0], MTX_FILE="30102", H3D_FILE=" ../../flex_h3d/beam.h3d", CRATIO="USER(0.01,100,0.1,1000,1") The fourth example below demonstrates how to rigidify a FLEX_BODY FLEX_BODY(30102, QG=[10,12,0], MTX_FILE="30102", H3D_FILE=" ../../flex_h3d/beam.h3d", RIGIDIFIED=True, CRATIO="IF(FXFREQ-100:0.01,0.1,IF(FXFREQ-1000:0.1,1.,1.))")

Body: Flexible

Body: Flexible

Body: Flexible

Model Element

Description

Linear Flexible Body:

NLFE Body:

Format – CMS Flexible Body

Format – NLFE Body

Attributes

Comments

CMS flexible body

NLFE flexible body

Example 1

Example 2

Example 3

Example 5

References

Model Element

Description

Declaration

Attributes

ROUTINE

Comments

Example