41.1.2.1. Tire Property File
The .tir file and the .rdf file are needed to use the GTire. These files are used to the STI (Standard Tire Interface) format and the TNO Tire and COSIN FTire also use the format. So, the user should add the VENDER_TIRE_TYPE parameter to the .tir file of GTire for dividing the provider of the tire model and the model type. This parameter must exist in the [MODEL] category of the .tir file.
Tire Model |
VENDER_TIRE_TYPE |
TNO MF (license provide from FB) |
TNO-MF |
TNO SWIFT (license provide from TNO) |
TNO-SWIFT |
COSIN FTire |
COSIN-FTIRE |
RecurDyn UAtire |
RD-UA |
User Tire (using General Tire Interface) |
RD-USER |
41.1.2.1.1. UATire Property File
The existing UATire of RecurDyn does not need the tire property file. But the GTire needs the tire property file and the property file of the UATire for the GTire entity is as follows.
Sample Files: <Install Dir>\Toolkits\GTire\RECURDYN_UA\tire_files\
Parameter definition
UNLOADED_RADIUS: Tire unloaded radius (R1)
WIDTH: Tire width for creating the geometry
RIM_RADIUS: Rim radius for creating the geometry.
RADIAL_STIFFNESS: Radial stiffness (\(K\))
RADIAL_DAMPING_RATIO: Radial damping ratio (\(C\))
LONGITUDINAL_STIFFNESS: Longitudinal stiffness (\({{K}_{s}}\)) by the slip ratio
LATERAL_STIFFNESS: Lateral stiffness (\({{K}_{\alpha }}\)) by the slip angle
CAMBER_STIFFNESS: Lateral stiffness (\({{K}_{\gamma }}\)) by the camber angle
ROLLING_RESISTANCE: Rolling resistance moment coefficient (\({{C}_{r}}\))
FRICTION_MAX: Maximum friction coefficient (\({{\mu }_{s}}\))
FRICTION_MIN: Minimum friction coefficient (\({{\mu }_{d}}\))
For more expressions of the UATire, refer to UATire Model.
41.1.2.1.2. USER Tire Property File
The GTire for the user tire needs the tire property file, as follows.
To use the User Tire of GTire, VENDER_TIRE_TYPE and USUB_DLL must be set. USUB_DLL must be set with relative path from RecurDyn model. Also, to create the Tire body, DIMENSION block must be set as below tire property file. Additional user parameters can be added repeatedly.
[HEDER] FILE_TYPE = ‘tir’ $—————————————————————-units [UNITS] LENGTH = ‘mm’ FORCE = ‘newton’ ANGLE = ‘radians’ MASS = ‘kg’ TIME = ‘second’ $—————————————————————-model [MODEL] VENDER_TIRE_TYPE = ‘RD-USER’ USUB_DLL = ‘.GTIRE_USUBGTIRE_USUB.dll’ $———————————————————–dimensions [DIMENSION] $-Tire Dimension 205-60-R14 UNLOADED_RADIUS = 300.8 WIDTH = 205.0 RIM_RADIUS = 177.8 $————————————————————-parameter [PARAMETER] USER_DEFINE_PARAM1 = 100.0 USER_DEFINE_PARAM2 = 200.0 USER_DEFINE_PARAM3 = 300.0 |
41.1.2.1.3. MFTire Property File
The property file of the MFTire is same to the property file of the existing MFTire. The user should add the VENDER_TIRE_TYPE parameter and if the user uses the TNO Tire, the user can set various options by the USE_MODE parameter as follows. The next lines are only used by RecurDyn, Adams and ignored by other MBS codes.
Option Number |
Option Description |
0 |
Fz only, no Magic Formula evaluation |
1 |
Fx,My only |
2 |
Fy,Mx,Mz only |
3 |
Fx,Fy,Mx,My,Mz uncombined force/moment calculation |
4 |
Fx,Fy,Mx,My,Mz combined force/moment calculation |
5 |
Fx,Fy,Mx,My,Mz combined force/moment calculation + turn slip |
+0 |
steady state behavior |
+10 |
including relaxation behavior |
+20 |
including relaxation behavior (nonlinear) |
+30 |
including rigid ring dynamics |
+100 |
smooth road contact |
+200 |
smooth road contact (circular cross section, motorcycles) |
+300 |
moving road (default for RecurDyn GRoad) |
+400 |
road contact for 2D roads (using travelled distance) |
+500 |
road contact for 3D roads |
Example
USE_MODE = 334 implies
combined slip
rigid ring dynamics
moving road
Users want to use 2D road than USE_MODE set to 14 or 4 as below.
USE_MODE = 14
In case of the tire model provided by TNO, the value of VENDER_TIRE_TYPE should be TNO-MF or TNO-SWIFT. If the user uses SWIFT, the user should type VENDER_TIRE_TYPE to TNO-SWIFT and the user must use the independent license provided by TNO. If the user uses MFTire, the user should type VENDER_TIRE_TYPE to TNO-MF and the user does not need to use the independent license provided by TNO. But, in case of MFTire, the user cannot perform an analysis by the Rigid Ring Dynamic (USE_MODE = x3x) setting.
Sample Files: <Install Dir>\Toolkits\GTire\TNO_MF_SWIFT\tire_files\
For more information of the MFTire or the SWIFT Tire, refer to MFTire Model.
[HEADER] FILE_TYPE =’tir’ $—————————————————————-units [UNITS] LENGTH =’meter’ FORCE =’newton’ ANGLE =’radians’ MASS =’kg’ TIME =’second’ $—————————————————————-model [MODEL] VENDER_TIRE_TYPE = ‘TNO-MF’ LONGVL = 16.7 $Nominal speed VXLOW = 1 $Lower boundary of slip calculation ROAD_INCREMENT = 0.01 $Increment in road sampling ROAD_DIRECTION = 1 $Direction of travelled distance USE_MODE = 314 $———————————————————–dimensions [DIMENSION] UNLOADED_RADIUS = 0.3135 $Free tyre radius WIDTH = 0.205 $Nominal section width of the tyre RIM_RADIUS = 0.1905 $Nominal rim radius RIM_WIDTH = 0.152 $Rim width ASPECT_RATIO = 0.6 $Nominal aspect ratio $————————————————-operating conditions [OPERATING_CONDITIONS] INFLPRES = 220000 $Tyre inflation pressure NOMPRES = 220000 $Nominal tyre inflation pressure |
41.1.2.1.4. FTire Property File
The property file of FTire by COSIN is same to the property file of the existing MFTire. When creating the property file in the COSIN, the animation flag must be turned off. The user should add the VENDER_TIRE_TYPE parameter as follows. RecurDyn recommend setting Maximum Time Step smaller than 1.0e-3.
Sample Files: <Install Dir>\Toolkits\GTire\COSIN_FTIRE\tire_files\
$——————————————————————–MDI_HEADER [MDI_HEADER]
(COMMENTS) {comment_string}
$————————————————————————-SHAPE [SHAPE] $these data are not used by FTire, but only by the calling solver {radial width}
$————————————————————————-UNITS [UNITS]
$———————————————————————DOE_PARAM [DOE_PARAM] $use up to 20 factors p1, p2, p3,.. to modify parameters in [FTIRE_DATA] $these values might be overwritten, depending on environment
$etc. $———————————————————————DIMENSION [DIMENSION] $these data are not used by FTire, but only by the calling solver
$———————————————————————-VERTICAL [VERTICAL] $these data are not used by FTire, but only by the calling solver
$————————————————————————-MODEL [MODEL]
$———————————————————-OPERATING_CONDITIONS [OPERATING_CONDITIONS]
$————————————————————————–DATA [FTIRE_DATA] $……………………………………………….basic data and geometry
$…………………………….static and modal data for 1st infl. pressure
|