Jump to content
SAU Community

Recommended Posts

Hi All,

Thinking of getting into the drift scene with an R31 however I have searched the forums and come to no definite conclusion about RB20DET/ET vs RB30ET. Would it be better to buy an RB20DET/ET skyline or turbo an RB30E? I understand at the end of the day not project car is ever cheap in the long run but I'm trying to go for the most budget friendly option. 

Cheers.

RB30/25  will be miles better. You can do it on the "cheap" stock everything except rings, bearings and small end bolts but it will still cost for the twin cam head, ecu and the other bits and pieces.

  • Like 1
6 hours ago, KiwiRS4T said:

RB30/25  will be miles better. You can do it on the "cheap" stock everything except rings, bearings and small end bolts but it will still cost for the twin cam head, ecu and the other bits and pieces.

Cheers man, what would you estimate the total cost for parts roughly? 

Edited by Anthony1016

Really hard to say as many parts will be second hand so may vary according to your luck. If you can pick up a going RB25DET for $1 500 that could be the way to go. Then you will need a FMIC, figure out a way to tune it (could cost 2k alone) better injectors and fuel pump, the aforementioned rings, bearings and small end bolts, better clutch...assuming no labour except for the tuning you are at $5k at least. Try not to spend any money on non essentials like FF Plenums or aftermarket exhaust manifolds etc

  • Like 1
3 hours ago, Griffin said:

Where are you located? I've got an rb25det neo engine, manifolds and bits and pieces at Newcastle if interested in having a look.

I'm in Sydney but willing to drive for parts, how much were you looking for? 

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