Jump to content
SAU Community

Recommended Posts

Hey guys I just purchased a 1993 model r33 GTS s1 manual skyline last week and the speedometer was not working at all however the odometer seemed to work fine. In an effort to get the speedo working I brought a second hand dash cluster and removed the section of the cluster where the speedo and odometer is located. Fitted it to my original cluster, reinstalled it and now the speedo actually works.

I took the car for a drive and my garmin gps was reading 90km/h (not 100% accurate but close) while at the same time my speedo was reading 170 km/h! Also the odometer has read I traveled aprox. 5 kms but I had intact only traveled 2.4 or so.

Any help would be muchly appreciated. Regards, Luke

Link to comment
https://www.sau.com.au/forums/topic/390867-r33-gts-big-speedo-odometer-dramas/
Share on other sites

He can't go faster than 90km/h because the the ecu thinks does doing 180km/h and hits the speed limiter. Also I think GPS don't take into account inclines and declines.

Edited by H4x

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • For fuelling the Haltechs have O2WB fuel controllers. Very useful for helping tuning VE and correcting for *small* mistakes. Of course if your injector/cam/trigger/sensor data is just wrong (or for a GTT which is not a GT) then you will get impossible reactions to things. I am sure you know this already but the reason people don't typically put haltechs (or any Aftermarket ECU) on GT's is because there's practically no real gains to be had - So this knowledge won't be commonplace.
    • Can someone tell me if the cracks seen in the rear sway bar bushings in these photo's is unacceptable from a roadworthy point of view?  
    • Shouldn't need a "base map" for anything other than guidance to ignition tuning. You just need the engine capacity right, the injector size right, and something, almost anything, for a VE map. On an NA engine, fuelling is almost completely a function of load signal & rpm. It should run and drive with a completely flat fuel map. It will be too lean under load, but that's easily fixed. We used to tune all ECUs without any base map. There were no such things (until someone had tuned a near stock engine on one, and then they had a "base map".
    • What did you actually buy/how much did it cost? When I got mine in like.. 2017...? 2019? the aim was to run Torque for gauges via ODB2 and things like Track Addict/Laptimers/Dashcam/Reversecam/Spotify etc. Mine never broke, but I wonder if you've got the same needs (it sounds like it). Cause I liked the idea of being able to do anything with it. That said, yours also cost 3x the cost of what I spent so... food for thought.  
    • For me there is a massive difference in manufacturer or big brand crippled android (Sony, Kenwood etc) vs the sort of thing I've installed here, which is basically just a tablet in DIN form factor with open Android, and the other model of course is mirroring - Android Auto/Carplay. I hate the locked down manufacturer and AA options where they decide what apps I'm allowed to install, including the Launcher but also importantly things like Ecutek (for this car) or Real Dash (Stagea) are not supported. Plus those crippled versions tend to be slower due to both overheads and lower spec hardware. On the other hand, when this breaks I'll likely be in trouble for support....but how is that different to owning an Infiniti anyway
×
×
  • Create New...