Jump to content
SAU Community

Recommended Posts

hey all, i currently own a r32 gts, i get of my ps in 6months time and am trying to decide on wether i should sell my car and buy a gtst or just put a rb20det or rb25det, i cant find any info on differances on a gts and a gtst, my car has a gtst diff and brakes so all i need to do is drop in a motor, iv seen many rb20 vs rb25 threads but just wondering is the rb25 worth the extra money

Link to comment
https://www.sau.com.au/forums/topic/369073-r32-gts-differances/
Share on other sites

rb25 is worth the money 1 million %. a rb20 with a mildly upgraded turbo and ecu will put out the same sort of power you can get from a stock rb25, but unlike the rb25, won't be able to make full boost at about 2500rpm. it will be closer to 4000rpm, by which time someone with a rb25 will be a pair of tail lights off in the distance.

my advice though, sell the natro and buy a turbo one. there are a few reasons for this, and price is one of them. another is to save you a heap of dicking around. a 3rd is because you can drive it before buying it to make sure the engine is decent.

i should mention that i'm not a huge fan of the r32. don't like it's looks, and certainly don't like the rb20, so personally i'd sell it and buy a 33, but that's just me.

rb25 is worth the money 1 million %. a rb20 with a mildly upgraded turbo and ecu will put out the same sort of power you can get from a stock rb25, but unlike the rb25, won't be able to make full boost at about 2500rpm. it will be closer to 4000rpm, by which time someone with a rb25 will be a pair of tail lights off in the distance.

my advice though, sell the natro and buy a turbo one. there are a few reasons for this, and price is one of them. another is to save you a heap of dicking around. a 3rd is because you can drive it before buying it to make sure the engine is decent.

i should mention that i'm not a huge fan of the r32. don't like it's looks, and certainly don't like the rb20, so personally i'd sell it and buy a 33, but that's just me.

thans the info on the engines mate much appreciated, i love the look of the r32 the r33 is to round and wide for me, i can do all the work myself but ofcorse with and engine swap theres always headaces wich is wat was pushing me to buying a gtst but my car is verry clean no rust and good paint and theres not many clean gtst around wich is wats making me stick to wat i have, are there any differances from the gts and gtst or just engine box diff brakes?

no they are pretty much all the major differences. does yours have 4 or 5 stud wheels?

as for the engine conversion, putting a rb20 in would be easier than a 25, but the 25 is a better option. it has a stonger gearbox as well as much more low end torque. but it means some wiring changes (for example you have to dick around with the speedo sender as it uses an electronic one and the r32 uses a mechanical one, but there is a fair bit of info around on how to get around this).

I have know a few people who quite easily blew their rb20 box on a 25 if your gonna convert it do it right the first time

I'm with you I love the look of r32's I've owned 2 and have had 1 r33 the torque low down on an rb25 is so much better the rb20 is a slug by comparison if I were you I'd sell the r32 na and buy a good condition sorted r32 gtst shell minus the gear box and engine and get the r33 engine and gearbox cause you gonna get shit all trying to sell and rb20 once you take it out

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...