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 + turnslip |
+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.