└── README.md /README.md: -------------------------------------------------------------------------------- 1 | # Mu - Telemetry Exporter for iRacing 2 | 3 | ###### Version 1.9.5.0 4 | ###### Last update: 6/29/2022 5 | 6 | 7 | Overview 8 | ------------------------------------------------------------------------------ 9 | Mu is a telemetry exporter that converts iRacing telemetry files (.ibt) into 10 | to files that can be read by MoTeC's i2 software for analysis. i2 and i2 Pro 11 | are available for free on MoTeC's website. MoTeC has no affiliation with 12 | iRacing. Please do not ask them for support. 13 | 14 | Mu has the following features: 15 | - Can export to MoTeC and CSV formats 16 | - Can export Metric or Imperial units 17 | - Automatically turns on telemetry capture in iRacing 18 | - Saves a copy of the setup used to generate the telemetry 19 | 20 | 21 | Usage 22 | ------------------------------------------------------------------------------ 23 | Mu can be run with iRacing or on its own. Mu will monitor the Import 24 | Directory and export any telemetry automatically. Exported telemetry can then 25 | be analyzed by the software of your choice. 26 | 27 | When Mu is run in conjunction with iRacing, Mu can automatically turn on 28 | Telemetry Capture and save the setup that was used to generate the telemetry. 29 | 30 | Mu has a user interface (UI) that will appear when launched. Additionally, it 31 | will continue to run in the background if the UI is closed. Mu is accessible 32 | from the Windows system tray, and right-clicking will display a dialogue with 33 | options for exiting the program, displaying the UI, and other functions. 34 | 35 | 36 | GPS 37 | ------------------------------------------------------------------------------ 38 | GPS in iRacing allows for an alternative way to determine the position of the 39 | car on the track, the generation of laps, and the generation of the trackmap. 40 | 41 | Due to precision of the MoTeC data, GPS data needs to be combined from 42 | multiple channels (actual race teams need to do this as well). GPS Telemetry 43 | data is exported in 3 channels (Degrees, Minutes, Seconds), and must be 44 | combined by MoTeC Maths into the channels GPS Latitude and GPS Longitude. The 45 | Math formula you should use is as follows: 46 | 47 | ``` 48 | GPS Latitude - Quantity: Angle Display Unit: degree Decimal: 8 49 | Result Unit: Degree 50 | Expression: 'Latitude Degrees' + 'Latitude Minutes' / 60.0 51 | + 'Latitude Minute - fraction' / 3600 52 | 53 | GPS Longitude - Quantity: Angle Display Unit: degree Decimal: 8 54 | Result Unit: Degree 55 | Expression: 'Longitude Degrees' + 'Longitude Minutes' / 60.0 56 | + 'Longitude Minute - fraction' / 3600.0 57 | ``` 58 | 59 | 60 | Additional Configuration - vehicleinfo.cfg 61 | ------------------------------------------------------------------------------ 62 | Mu supports loading of car information from an configuration file. To 63 | define the configuration file, create a text file with the name 64 | 'vehicleinfo.cfg' in either the same directory as the Mu executable, the 65 | import directory, or the export directory. The file must be in YAML format. 66 | 67 | Units can be given in the following quantities. Usage of quantities not 68 | explicitly labeled below will result in incorrect data in MoTeC: 69 | 70 | - Volume 71 | cc 72 | l 73 | ml 74 | USfloz 75 | USgal 76 | 77 | - Length & Distance 78 | cm 79 | ft 80 | in 81 | km 82 | m 83 | mil 84 | mile 85 | mm 86 | 87 | - Mass 88 | cin 89 | g 90 | kg 91 | lb 92 | mg 93 | oz 94 | 95 | 96 | ### Vehicle Information 97 | 98 | Additional vehicle information can be exported into MoTeC that can be used in 99 | Maths or just general information. An example of a vehicle entry is as follows 100 | 101 | ``` 102 | Vehicles: 103 | - name: formulamazda 104 | Attributes: 105 | Vehicle Weight: 650 kg 106 | Fuel Tank Capacity: 72 l 107 | ``` 108 | 109 | Additional vehicles and attributes can be added. See the sample below for a 110 | complete example of how to add more vehicles and attributes. Only the values 111 | for the vehicle used in generating the telemetry will be included in the export. 112 | 113 | 114 | ### Constants 115 | 116 | Constants are similar to vehicle information except that the values are exported 117 | for all telemetry. 118 | 119 | ``` 120 | Constants: 121 | Minimum Laps: 2 122 | Acceleration of Gravity: 9.8 m/s^2 123 | ``` 124 | 125 | 126 | ### Filtering Channels 127 | 128 | Channels can be filtered by adding a ChannelFilter entry and listing the name 129 | of each channel to be filtered. Note that if you filter a channel needed by 130 | Motec, you could end up with missing / erronous telemetry. 131 | 132 | ``` 133 | ChannelFilter: 134 | - ChannelName1 135 | - ChannelName2 136 | ``` 137 | 138 | 139 | ### Sample vehicleinfo.cfg 140 | 141 | Below is a sample configuration used by Mu. The following can be cut-n-pasted 142 | to vehicleinfo.cfg 143 | 144 | ``` 145 | --- 146 | Vehicles: 147 | - name: formulamazda 148 | Attributes: 149 | Vehicle Weight: 650 kg 150 | Fuel Tank Capacity: 72 l 151 | Vehicle Track: 1485 mm 152 | Vehicle Wheelbase: 2522 mm 153 | 154 | - name: rt2000 155 | Attributes: 156 | Vehicle Weight: 664 kg 157 | Fuel Tank Capacity: 19684 ml 158 | Vehicle Track: 1562 mm 159 | Vehicle Wheelbase: 2459 mm 160 | 161 | - name: rileydp 162 | Attributes: 163 | Vehicle Weight: 2275 lb 164 | Fuel Tank Capacity: 20 USgal 165 | Vehicle Track: 78 in 166 | Vehicle Wheelbase: 110 in 167 | Maximum Speed: 200 mph 168 | 169 | Constants: 170 | Minimum Laps: 2 171 | Acceleration of Gravity: 9.8 m/s^2 172 | 173 | ChannelFilter: 174 | - RPM 175 | - Gear 176 | ``` 177 | 178 | 179 | Acknowledgements 180 | ------------------------------------------------------------------------------ 181 | - iRacing.com Motorsport Simulations for creating the best PC racing 182 | simulation. 183 | 184 | - MoTeC for their excellent telemetry analysis program i2 Pro. 185 | --------------------------------------------------------------------------------