Jump to content
SAU Community

Recommended Posts

Hey Guys,

I bought an R32 GTS-T that has had a RB25 box put in it sometime in the past.

Now I have done some reading and know that you need to convert the electronic speedo to a mechanical one in order for it to work in the car. I'm assuming that this has been done in my car since the speedo is working, however the speedo is out by about 25kph at 100kph. I'm just wondering what you guys think is causing this?

My uneducated guesses are;

The Diff?

Maybe something to do with the mechanical speedo conversation?

Also the car has a GTR dash cluster (could this make a difference?).

Are any of my guesses close? where should I start? I would like to get the speedo as close as possible (doesn't have to be perfect).

Cheers in advanced,

Stuart

Here's the list of things that can affect it.

R32 GTSt diff ratio is 4.3:1. RB25 turbo diff ratios are 4.11:1. Difference of 4.5% which is not enough to explain your error.

R32 GTR diff ratio is 4.11:1, like the RB25 diffs, so that could/should get rid of the 4.5% error above anyway.

BUT....and here's the big but.....The GTR speedo expects to be turned at a particular speed by its speedo cable. That speed is dependent on the number of gears on the drive in the box and the end of the cable. The R32 GTSt works the same way, but it is entirely possible that there is a ~20-25% difference in the cable speed required to work the 2 different speedos, because the 2 different boxes (32GTSt and 32GTR) are not in any way related to each other.

So, I reckon that your easiest test (not that it's all that easy) is to try a GTSt cluster in the car and see if the speedo reads correct (or actually, maybe about 4.5% wrong rather than 25%).

I don't know anyone else who has transplanted a GTR cluster into a GTSt to know if there is that big a difference in the cable speed required for a given road speed, but I'd be willing to believe that there is and that many people who have done it either haven't realised or just live with it!

FWIW, if you do the Navara sender based mech speedo conversion (like I did in my R32) for the RB25 turbo box, then you can get nearly zero% speedo error. Mine is accurate to within 1km/h across the whole normal range (say up to about 130 km/h).

  • Like 1

BUT....and here's the big but.....The GTR speedo expects to be turned at a particular speed by its speedo cable. That speed is dependent on the number of gears on the drive in the box and the end of the cable. The R32 GTSt works the same way, but it is entirely possible that there is a ~20-25% difference in the cable speed required to work the 2 different speedos, because the 2 different boxes (32GTSt and 32GTR) are not in any way related to each other.

Awesome, this was basically my train of thought however I didn't know enough to make any real conclusions. It's good to know that I should be able to rule out the diff/box.

I will see if I can get my hand on a GTS-T cluster, I'd rather a GTS-T cluster anyway, while the red and silver dials are nice, the "Front Torque" dial is useless and just makes the car seem "ricey".

When I get my hands on one I will post the results up here and let you know.

Cheers!

You need to do more research.

I'd say the drive pinion has the wrong tooth count, something for you to check.

You can't just buy any GTSt instrument cluster as there's at least 2-variations through the years.

You'll need to verify your model car and buy the one that suits.

25kph wrong is a biggie.

Are you sure the previous owner didn't remove the needles and replace them incorrectly. (the white faced dial syndrome)

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

    • They need to get a grip. R32 GTRs got as low as AU$8-10K at one point here.
    • You have just offended every teenage boy in America
    • Structured text and other high level PLC programing languages are not allowable in Functional Safety. They are very difficult to audit. My PLC stuff is almost exclusively oriented towards Burner Management Systems which are a particularly pernicious form of Safety Instrumented System, when implemented in an SPLC. Even the part of the code written to work in the non-safety logic part of the PLC, like with a Siemens S7-1500 series, still needs to be treated as if it was safety code, with access restrictions, code fingreprints and the like. And Allen Bradley can go EABODs. They ae full of shit. They have this whole lie going on where they say if you use a ControlLogix controller and its IO, and then just duplicate the IOs (ie, run in series or parallel depending on type, to try to make it "fail safe") and "use these programming styles and place these restrictions on what you do" that you can achieve SIL2. What a load of crap. They just get away with it because no-one in the US seems to understand the first thing about Functional Safety and carries on as if all they have to do is buy only SIL2 rated equipment and hey presto, it's a SIL2 system. Idiots. /rant
    • If you're really considering leaving it, a great question to ask is, is the magnet going to stick to the sump? The answer to the above is the same answer towards if I'd have any level of comfort leaving it... Personally, based on the cost of a motor if the magnet were to cause damage, I'd be fishing it out either way. Use the methods in here. It fit in through the plug hole, it'll come out.   PS, get a small actuatable claw for a bore scope. OR if you know a vet, they have really cool controllable scopes with hooks on the end. Supposedly they're like playing a video game. Ask if they can acquire you one of their scopes... Engine oil after all is just a different type of lube right? Will only make it easier on the next dog or cat...
    • All other (Boolean) logic functions though, are just built on those blocks above. Which does give you a lot of functionality in logic. It is basing that on using thresholds with analogue signals like GTS alluded to.   Not having things like timers will make it less useful for some of the ramp up logic you'd want, and again, on Haltecs capacity specifically, I'm not across anymore what you can / can't do with different tables.   I'm assuming, with your logic you want to implement, not only do you want your timing safeties, you're wanting to be able to derive the duty cycle for your solenoid, to maintain I'm assuming 175PSi? Or are you using a standalone WMI controller to maintain the DC correct, and you just want the Haltech working out which fuelling maps you should be on?
×
×
  • Create New...