MotionView User's Guide

FTire Integration with MotionView

FTire Integration with MotionView

Previous topic Next topic No expanding text in this topic  

FTire Integration with MotionView

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

Starting with MotionView 10.0-SA-110, you can create models directly within MotionView which are automatically set up to utilize tires.  This can be done by making the following Assembly Wizard selections from the Model menu:

assmbly_wzd_dialog

assmbly_wzd_dialog_pic2

(or Rear wheel drive or Four wheel drive)

assmbly_wzd_dialog_pic3

As long as FIALA/HTIRE is selected from the Tires drop-down menu, all other selections for the remainder of the Assembly Wizard will result in a full vehicle model enabled for tires.

After this point, when the Task Wizard is selected from the Analysis menu, only full vehicle tasks will be available to select.

NoteAll full vehicle analyses will utilize tires.

tsk_wzd_dialog

An example of a full vehicle model in MotionView is shown below:

model_exmple_pic

The resulting model will include an MDL system for the tires as shown in the browser image below (FIALA/HTIRE system):

model_browser_pic

The System panel will show all the necessary attachments for the HTIRE/FIALA tire system:

system_panel_exmple

The six key attachments are:

Wheel Center (Front & Rear):  This is a Point entity used to define the location of the center of the wheel.
Spindle Alignment Point (Front & Rear):  This is a Point entity used to define the spin axis of the wheel.
Wheel Body (Front & Rear):  This is a Body entity used as the body where the tire forces are applied.

Within this system is an MDL dataset called "Tire Data" which contains all the pertinent tire data, including references to the tire property file (.tir) and road property file (.rdf).

NoteEach tire can use its own tire or road property file.

dataset_prop_data_dialog

There is also a field for the unloaded radius, even though this same parameter is in the tire property file.  The unloaded radius is used here to calculate the rolling radius (rolling radius is set to 98% of the unloaded radius).  The rolling radius is used in turn to define the z location of the ground reference marker, thus defining the location of the road plane and ensuring that the road plane is slightly deforming the tire at the beginning of the simulation.  It is important for you to keep the value of the unloaded radius in this table consistent with (equal to) the value used in the tire property file.

Wheel body parameters are found in the body panel for the wheel body (which is located under the Bodies folder in the corresponding suspension system).

wheel_body_param_pic

bodies_panel_pic

 

See Also:

Coordinate Systems and Output Requests

Using Grasub (FTIRE only)