A Tire object represents six components of force and torque acting on a wheel body from the ground. Road Data File (*.rdf) and Tire Property File (*.tir) files must be specified to create the Tire. When a Tire is created, one wheel body and two force markers are created on the wheel body and ground. The parent body of the action marker is the wheel body and the parent body of the base marker is the ground. Force and torque are applied on the wheel body at the contact position and the reaction force and torque are zero. The directions of force and torque can be determined from the y-axis (spin axis) of the action marker and the normal direction to the road. Several tire types are supported for handling and riding simulation and can be classified as follows.
Figure 6.51: Tire classification
| Use | Type | Additional License | Additional Library |
| Handling | FIALA | N/A | N/A |
| UA | N/A | N/A | |
| MF-Tyre | Siemens | MF-Tyre/MF-Swift Library | |
| Riding | MF-Swift | Siemens | MF-Tyre/MF-Swift Library Salt License Library |
| FTire | Cosin | CTI Library |
The type of tire can be defined in Tire Property File (*.tir). Though the interfaces for MF-Tyre, MF-Swift and FTire are supported in Motion, their licenses and libraries are supported by their designers.
MF-Tyre is available free-of-charge. MF-Swift, which can consider Turn Slip, Rigid Ring, Enveloping, Temperature & Velocity, requires a Siemens license. All required library files for MF-Tyre/MF-Swift are included in the installation package, but additional an license needs be installed separately for MF-Swift.
FTire requires a Cosin license. All required library files for FTire are included when the Cosin program is installed.
To use these tires, you must contact each designer directly.