Jump to content
SAU Community

Recommended Posts

Dare i say 32 with a 25 in it?

It's the question i've been asking myself for a couple of months now my setup is great if it came on 1000rpm earlier it's jus tooooo DANM laggy when you try to make any reasonable kinda power..

So ithink its either smaller turbo or larger motor.

The only other way i can think of is maybe cams race fuel and a sit7 load of ignition advance??

SO CONFUSED..

anyway sorry for verbal dribble in your thread dude.

  • Replies 165
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

I had the same dilemma when i was looking for my skyline last year in November...

In the end i chose r33 1995 GTS T over the R32's...

Its a hard choice, and its really down to personal choice really... If you plan to extensivly mod the car, then all the talk about which as more power and what not, is not so relevant, as both are capable of making power if you have the cash.

Depending on how old you are (for insurance) i would personally go the R32 GTR... there only a bit more then the avg R33 GTS T... i would of chosen this road, if i was not only 20 yrs old with a students budget!

Anyway, R32 or R33.. its still a skyline! and all skylines are good in my books ^^

riiight....u think r33's look good??? haha yeh chek this beauty out...

1105_00.jpg

pffffft....

Whats wrong with it? I find it ok lookwise. It looks excatly like my GMG R33 minus the stock rims. And I'm not a fan of lowering my car coz I hit parking kerbs wayyy to easy.

Edited by Mayuri Krab
btw, y are u unhappy with ur xr6t?

Im not - it still puts a big smile on my face ;-) But the wife drives it 99% of the time and she wants a smaller auto.. :wub:

the majority of driving i do is in traffic with the occasional track day - thats while i was leaning towards the smaller rb20

Im not looking for a big HP car. done that. And while its fun - i just need something to have a bit of fun with.

LOL, come on br3ndan...the middle of the road is the most dangerous place :)

LOL!!!

In that case, i vote for R33 GTS T over the R32 GTS T.

But i really mean it when i say i like all skylines! :D

riiight....u think r33's look good??? haha yeh chek this beauty out...

1105_00.jpg

pffffft....

wat u want is one of these... :D

minor mods on an 32gtst get it moving fairly swiftly

32frontal.jpg

lol u r a funny kent

Edited by ztuned
sr20 in r32 is better than rb20 in r32.. lighter, more torque, more power potential

300rwkw with stock internals too easy hahah

HAve a hunt around for an SR2o with a TD06-20G with 8cm housing. An RB20 with the same turbo is as responsive and makes more power. Thats without the Step 1 cams that SR20s need. Im not convinced you are right :D

The differences aren't enormous. I reckon you need to drive them and make your mind up. Balance out what you want vs each car's good/bad points- but trust me, you need to drive them both to conclude your choice.

Roy,

Ever since the first DECA I went to, I fell in love with your car!!that is the ultimate 32! :D

Esp gate!!!!

3 years ago when I got my skyline - as much as I loved 32's more, the 33 I came across was just too nice to pass up. 32's were always my fav but now 33's are cause I have grown to love my 33!

But yeah, to keep on topic....man, if you do basic mods to both cars - they will be both great fun and can still do good battles/times on the track! Height wise, with a helmet - Id say 33...

I'd like to hear more on the oil starvation and prevention for 33's... :)

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