Jump to content
SAU Community

Recommended Posts

vct affects your midrange torque and power more than peak (high rpm) power. not 100% sure on the rb series, but on the vg and vh engines it is only on until around 5000-6000rpm, then it switches off.

from what i understand, the idea is to increase valve overlap at low/medium rpm (not at idle though) to help suck in the in intake air/fuel mix and blow out the remaining exhaust gases. however at high rpm the pressure in the exhaust manifold may be high enough that some of the exhaust gas will actually be pushed back into the intake due to the bottleneck in the exhaust manifold... this would cause a decrease in power and increases your cylinder temps. so to avoid this they switch off vct at higher rpm's.

basically with vct disabled, there will be very little (if any) difference in your peak power compared to if you had working vct. your torque curve however will drop away after the peak torque, whereas with vct it will be abit flatter towards high rpm and your midrange power would be reduced.

i know the RB30 guys had a couple of dyno graphs in the forced induction thread with and without VCT. not a 100% sure exactly, but the difference was something like 10-15kw over a 1000-2000rpm range.

i don't know how applicable that would be over to an NA RB25, but i would say probably about the same taking compression into consideration????

my vct isnt working because I'm running a r32 loom and ecu.

I know the peak power is the same as vct is turned off in the higher rev range. was just wondering if anyone had some dyno plots so i could see the midrange difference.

why are you running a 32 loom and ecu? did u do a engine swap?

when did the vct's start getting used? what model onwards with the skylines?im not trying to hack the thread but my 33 is extremly gutless low and mid nothing starts happening until 5500 rpm?

its a s1 1993 r33 btw

Edited by LUME

VCT got bought in with the S1 R33s and from thereonwards was standard. easy way to tell whether or not it has VCT is whether it has a buldge on the lefthand side of your timing belt cover.

the only RB25DEs without VCT were the ones from the R32s, VL owners usually use them on RB30DE builds as they dont have to modify the block as much.

Luke, i had the same problem that your having. just launch it at about 4-5k RPM and you should be alright if youv got grippy tires, cos thats where the torque band is. i gained heaps of bottom end go when i turboed mine, cos of the high-comp motor.

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