Tire size does not appear as a special function on the Launch Elite 2.0 as do other coding variants such as auto start/stop, oil reset, etc. I spent several hours navigating through the menus and eventually found the page shown below after drilling down about 12 layers of menu (with numerous pop-up windows along the way that required "OK" acknowledgments). From the main screen, navigate down as follows:
Diagnostics
Mercedes
Manually Select
463 - G Class (MOPF18)
Basic Version
Gasoline Engine
Lefthand Steering
463-261 - G550
Control Units
Drive
PTCU Drivetrain
Variant Coding
Implicit_Variant Coding
Then scroll down to entries 010 and 011 on the screen shown below. I'm guessing these two coding variants might set the speed sensor calibration for various tire sizes.
Click on the 010 entry to reveal the list of alternate settings. (Both 010 Rear and 011 Front feature the same drop-down options.)
The drop-down arrow shows 60+ entries as follows:
(The Uxxxx represent tire circumferences in mm. Information in parentheses appear to be vehicle model related)
The entry option about halfway down "***U2210 (BR213 FS AT)/U2411 (BR463AMG OFFSET 2000)***" is the existing setting for my G550 with its OE 275/50R20 tires, whose calculated circumference is 2459. I understand neither the double entry (U2210 and U2411) nor why this is the existing entry when there are others that are better choices for the tire circumference at half-life (which I calculate should be about 2437 mm -- the third option from the bottom of the list). Not sure what "OFFSET 2000" means either. 2411 mm is the approximate circumference when the wear bars reveal. Maybe this coding sets other vehicle specific parameters such as the speed sensor gearing(?).
Is anyone able to shed some light on this?
My objective is to choose a setting appropriate for the 275/55R20 tires I have mounted, which are about 3% larger (2545 mm circumference new). The U2550 seems to be the closest option, although 2530 would account for some partial wear.
The next step is to drive some calibrated distance with the current setting and compare it with my odometer result -- then try another setting and see if the odometer result is accurate.
Tire size does not appear as a special function on the Launch Elite 2.0 as do other coding variants such as auto start/stop, oil reset, etc. I spent several hours navigating through the menus and eventually found the page shown below after drilling down about 12 layers of menu (with numerous pop-up windows along the way that required "OK" acknowledgments). From the main screen, navigate down as follows:
Diagnostics
Mercedes
Manually Select
463 - G Class (MOPF18)
Basic Version
Gasoline Engine
Lefthand Steering
463-261 - G550
Control Units
Drive
PTCU Drivetrain
Variant Coding
Implicit_Variant Coding
Then scroll down to entries 010 and 011 on the screen shown below. I'm guessing these two coding variants might set the speed sensor calibration for various tire sizes.
Click on the 010 entry to reveal the list of alternate settings. (Both 010 Rear and 011 Front feature the same drop-down options.)
The drop-down arrow shows 60+ entries as follows:
(The Uxxxx represent tire circumferences in mm. Information in parentheses appear to be vehicle model related)
The entry option about halfway down "***U2210 (BR213 FS AT)/U2411 (BR463AMG OFFSET 2000)***" is the existing setting for my G550 with its OE 275/50R20 tires, whose calculated circumference is 2459. I understand neither the double entry (U2210 and U2411) nor why this is the existing entry when there are others that are better choices for the tire circumference at half-life (which I calculate should be about 2437 mm -- the third option from the bottom of the list). Not sure what "OFFSET 2000" means either. 2411 mm is the approximate circumference when the wear bars reveal. Maybe this coding sets other vehicle specific parameters such as the speed sensor gearing(?).
Is anyone able to shed some light on this?
My objective is to choose a setting appropriate for the 275/55R20 tires I have mounted, which are about 3% larger (2545 mm circumference new). The U2550 seems to be the closest option, although 2530 would account for some partial wear.
The next step is to drive some calibrated distance with the current setting and compare it with my odometer result -- then try another setting and see if the odometer result is accurate.
Stay tuned.
Would be nice if there was a setting to allow larger than. 33” tires to keep cruise and such.
I took a 15 mile drive today, using a smartphone app "Speedometer-Pro" which uses GPS to accurately track speed, distance and time. On the first run with OE coding and 275/55R20 tires (about 3% over the 275/50R20 OE size), I recorded as distance of 15.4 miles on the instrument panel odometer versus 15.8 miles on the smartphone app. When the speedometer read 65 mph, the app indicated 67-68 mph. These results are consistent with the 3% larger tire circumference.
Using the Launch scanner, I changed both front and rear wheel circumference coding to "U2530 (X167 AMG Offset 2000)" from the OE coding "U2210(BR213 FS AT / U2411 (BR463AMG Offset 2000)". I drove the same route again, and I recorded the same distance and speed differentials. So this coding variant has no impact on tire size compensation.
I noticed no difference in behavior in driving the vehicle, such as gear shifting points. The purpose of these wheel circumference coding variants is unknown.
I took a 15 mile drive today, using a smartphone app "Speedometer-Pro" which uses GPS to accurately track speed, distance and time. On the first run with OE coding and 275/55R20 tires (about 3% over the 275/50R20 OE size), I recorded as distance of 15.4 miles on the instrument panel odometer versus 15.8 miles on the smartphone app. When the speedometer read 65 mph, the app indicated 67-68 mph. These results are consistent with the 3% larger tire circumference.
Using the Launch scanner, I changed both front and rear wheel circumference coding to "U2530 (X167 AMG Offset 2000)" from the OE coding "U2210(BR213 FS AT / U2411 (BR463AMG Offset 2000)". I drove the same route again, and I recorded the same distance and speed differentials. So this coding variant has no impact on tire size compensation.
I noticed no difference in behavior in driving the vehicle, such as gear shifting points. The purpose of these wheel circumference coding variants is unknown.
Still looking through this maze of menus.
Have you been able to find a solution for the speedometer difference, I have now - 3% since I have the 295/40R21 which is slightly smaller that the 275/50R20, and I'm planing to get bigger tires like 275/50R21 or 285/55/R20 which will be problematic for speed tickets 😬
Have you been able to find a solution for the speedometer difference, I have now - 3% since I have the 295/40R21 which is slightly smaller that the 275/50R20, and I'm planing to get bigger tires like 275/50R21 or 285/55/R20 which will be problematic for speed tickets 😬
No, I haven't had a chance to pursue this. There's got to be a tire size coding variant, but it might not be included within this Launch scanner's capability.
No, I haven't had a chance to pursue this. There's got to be a tire size coding variant, but it might not be included within this Launch scanner's capability.
Thank you for the confirmation.
Anyone can help to advise whether this is possible using STAR system?
