Jump to content
SAU Community

Recommended Posts

From everything I read on the forums, the r32 gear box is the same as the r33, the r33 is just a newer version.

The R32 GTR can be run on rwd mode because there is no loading on the center shafts once the 4wd fuse is pulled out. This is not true for the r33 or r34 due to their upgraded 4wd system, sorry I don't know exact details here but it has been covered plenty of times before. Use the search function or google if you want more detail. Thus, people drop the center shafts for an r33 gtr to run in rwd mode during dyno applications.

because normally its the other way around, people's r32 boxes die and the cheapest option is to find the newest r33 gearbox possible to fit into their car.

try searching for r33 gtr in rwd mode or dyno

The power of google and wikipedia

"The R32 could be switched from AWD to RWD by removing the 4WD fuse, but R33 and R34 models had to have the front tailshaft removed, or the centre diff can be depressurised for 'towing mode' as specified in the owners manual."

The point is, it isn't the gearbox that is responsible for the awd to rwd ability for the r32

Edited by s2d4
  • 2 weeks later...

No I've put a r32 gtr box in my R33 that was rebuilt with os giken gears. You need to keep your R33 transfer case though or else you'll have no speedo using an R32 one (R32 cable speedo, R33 electronic speedo) other than that they are fully interchangeable.

Also R32s have no preload on transfer, R33 and 34 does so you need to drop hydraulic pressure to the back of the transfer to safely get rwd (modify line to back of transfer)

Edited by BK

You can use the r33 transfer case, just pull out the speed sensor and put in the cable drive unit in.

Also you may need to switch the front input snout cover to change from push type to pull type clutch as used in the R33GTRs.

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

    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...