Welcome to the 2GNT Forum! Interested In Advertising with 2GNT?
Home | Site Background| Info&Specs| Mods & Tech Info | CAPS | Part Reviews | Donate | 2GNT Stickers |
Search Printer-friendly copy Email this topic to a friend 0 Users in Chat
Top 2GNT Technical Handling/Suspension topic #32916
View in linear mode

Subject: "RE: possible tire problem." Previous topic | Next topic
RoninEclipse2GJul-21-10 03:37 PM
Donating 2GNT member
2745 posts,
Click to send email to this author Click to send private message to this author Click to view this author's profile Click to add this author to your buddy list
#32918, "RE: possible tire problem."
In response to In response to 1




          

Originally posted by Babbz413
Your tire size is not the problem.

Correct. Accoring to the miatanet tire size calculator you should be about 3mph slower when the speedo reads 60.

I have heard of guys taking the needle off and going down the road holding a steady pace using GPS to measure the speed then sticking the needle back on at the correct speed. That might fix it. Otherwise you probably have an issue with the gauge cluster or the speedo sensor.

Erik P.
Official 2GNT thread Hijacker
Some say that he's driven over more Covenant than he's shot, and that his grenades aren't where you'd expect them to be...
All we know is, He's not The Stig... But he is The Stig's Spartan cousin!

  

Report This Post to Admin Printer-friendly copy | Reply | Reply with quote

possible tire problem. [View all] , blak94gsx, Jul-21-10 07:48 AM
  RE: possible tire problem., Babbz413, Jul-21-10 12:49 PM, #1
RE: possible tire problem., RoninEclipse2G, Jul-21-10 03:37 PM #2
      RE: possible tire problem., Babbz413, Jul-21-10 03:50 PM, #3
           RE: possible tire problem., AdministratorCODE4, Jul-21-10 05:40 PM, #4
                RE: possible tire problem., Babbz413, Jul-21-10 05:51 PM, #5

Top 2GNT Technical Handling/Suspension topic #32916 Previous topic | Next topic
Powered by DCForum+ Version 1.2
Copyright 1997-2003 DCScripts.com

I generated this page in 0.02775502204895 seconds, executing 12 queries.