Jump to content
SAU Community

Recommended Posts

2 minutes ago, r32-25t said:

You know how you all said the ultimate set up would be the 3.2 with the 6870 and vcam that Jez Tuned. That was reapers car and I’ll let him tell the rest of the story if he wants to

Rightly or wrongly, back when he had talked about that I was definitely pro VCam/6870 for what he said he wanted at the time.

 

7 minutes ago, r32-25t said:

Cylinder pressures cracking the deck of the block, head studs are to strong to stretch so the deck gives way instead 

Ahh I see.  And you think that the same cylinder pressures would not crack the block if there was a non-vcam head ?

The vcam makes more cylinder pressure lower down in the rev range as it’s coming onto boost and that’s what I believe is creating the problem. I’m not willing to experiment and find out on a $13,000 block 

1 minute ago, r32-25t said:

The vcam makes more cylinder pressure lower down in the rev range as it’s coming onto boost and that’s what I believe is creating the problem. I’m not willing to experiment and find out on a 13,000 block 

I'm bringing up  a couple points not to be a dick, or even defend the fact I've suggested that this kind of combo is good - just like to investigate things which have either turned out well or not... it kinda helps both understand what is working and why to help all of us get better results.  With the info you've presented so far I feel like blaming VCam is a mistake, especially if you have it and you're looking at spending money at moving away from it when its probably not the cause - at least all by itself. 

Peak cylinder pressures happen when the intake and exhaust valves are closed, some time after the spark event happens.  There is absolutely zero influence that valve timing has on this all by itself.   The cylinder pressures are going to be everything to do with the compression ratio, how much air/fuel combo has been forced into the cylinder, when the spark has been lit and how stable the combustion process is after that point.   It is VERY possible with a given static cam head setup to exceed the cylinder pressures achieved using a variable cam head setup.  

Not doubt Vcam (and the turbo setup used) could be making it easier to create a situation where cylinder pressures get to a point the block can't hold it - but blaming vcam for a cracked block is a bit like blaming a Porsche GT3 for being too fast if you don't brake for a corner and throw one off the road.   Things that improve torque naturally have the ability to put more stress on the parts which have to hold the associated forces, its up to the builder to ensure things are best setup to ensure the best chance of sustaining those forces and in this metaphor - the tuner/owner have to decide where to draw a line in terms of how far its pushed so they have less chance of overcooking the combination you have.

By all means remove vcam if it makes you feel better, but it won't necessarily lose you the ability of cracking the block due to excessive cylinder pressures if you were pushing things hard enough to achieve that.   There may be other reasons you are looking at changing as well, but realistically - if the only reason is due to cylinder pressures then perhaps it should be considered to hold back torque where you think it has caused a problem and keep the nice responsive drive that VCam provides while not compromising reliability.    Modern ECUs/control systems make it not particularly hard to target the torque you want, so instead of building the car to be inherently laggier in all situations it is possible to have your cake and eat it too.

  • Like 2

It’s the same theory as the barra and evo guys who keep the boost low through the bottom and mid range and ramp it in up high to save the rods from bending, just in an rb the rods aren’t the week point it’s the deck or the big ends that let go 

Just now, r32-25t said:

It’s the same theory as the barra and evo guys who keep the boost low through the bottom and mid range and ramp it in up high to save the rods from bending, just in an rb the rods aren’t the week point it’s the deck or the big ends that let go 

Snap, pretty much what I was getting at with my above post - just a bit confused about why you're blaming vcam instead of blaming the boost target/ignition timing which have far more direct influence on the kind of failure you're talking about

  • Like 1
2 minutes ago, Lithium said:

I'm bringing up  a couple points not to be a dick, or even defend the fact I've suggested that this kind of combo is good - just like to investigate things which have either turned out well or not... it kinda helps both understand what is working and why to help all of us get better results.  With the info you've presented so far I feel like blaming VCam is a mistake, especially if you have it and you're looking at spending money at moving away from it when its probably not the cause - at least all by itself. 

Peak cylinder pressures happen when the intake and exhaust valves are closed, some time after the spark event happens.  There is absolutely zero influence that valve timing has on this all by itself.   The cylinder pressures are going to be everything to do with the compression ratio, how much air/fuel combo has been forced into the cylinder, when the spark has been lit and how stable the combustion process is after that point.   It is VERY possible with a given static cam head setup to exceed the cylinder pressures achieved using a variable cam head setup.  

Not doubt Vcam (and the turbo setup used) could be making it easier to create a situation where cylinder pressures get to a point the block can't hold it - but blaming vcam for a cracked block is a bit like blaming a Porsche GT3 for being too fast if you don't brake for a corner and throw one off the road.   Things that improve torque naturally have the ability to put more stress on the parts which have to hold the associated forces, its up to the builder to ensure things are best setup to ensure the best chance of sustaining those forces and in this metaphor - the tuner/owner have to decide where to draw a line in terms of how far its pushed so they have less chance of overcooking the combination you have.

By all means remove vcam if it makes you feel better, but it won't necessarily lose you the ability of cracking the block due to excessive cylinder pressures if you were pushing things hard enough to achieve that.   There may be other reasons you are looking at changing as well, but realistically - if the only reason is due to cylinder pressures then perhaps it should be considered to hold back torque where you think it has caused a problem and keep the nice responsive drive that VCam provides while not compromising reliability.    Modern ECUs/control systems make it not particularly hard to target the torque you want, so instead of building the car to be inherently laggier in all situations it is possible to have your cake and eat it too.

By using vcam you are increasing power and torque which is filling the cylinder more and creating more pressure lower in the rev range which seems to where shit happens 

9 minutes ago, r32-25t said:

By using vcam you are increasing power and torque which is filling the cylinder more and creating more pressure lower in the rev range which seems to where shit happens 

The effect vcam has on power and torque is negligible compared to the boost targeting and ignition timing.  It may make it easier to hit the high torque levels earlier, but you are not obliged to make use of that.   There are MASSIVE amounts of setups running around which would be capable of doing this kind of thing with variable valve timing which are perfectly reliable.  I feel like going to laggier/less streetable setup to avoid cracking blocks when all you have to do is exercise some restraint where it could be a risk is very very strange, though I could be missing something.

Should be going back to 0 degree advance as soon as you're coming onto boost, keeping it on after that is what is causing the issue.

When I tunes SR20s, I do exactly that, use VCT to only get the turbo to come on, and turn it off quick smart.

I've seen plenty of tunes from "workshops" that keep VCT into 6 to 7k RPM, sure you're making much more torque, but can't imagine what cylinder pressures are like.

 

37 minutes ago, Dose Pipe Sutututu said:

I've seen plenty of tunes from "workshops" that keep VCT into 6 to 7k RPM, sure you're making much more torque, but can't imagine what cylinder pressures are like.

I'm not sure all the rationale or limits you are considering here, but just to pluck a random number out of the blue - what is the difference on the bottom end between making 500nm at 6500rpm with VCT on, or 500nm at 6500rpm with VCT off but running more boost?

Edited by Lithium
9 minutes ago, Lithium said:

I'm not sure all the rationale or limits you are considering here, but just to pluck a random number out of the blue - what is the difference on the bottom end between making 500nm at 6500rpm with VCT on, or 500nm at 6500rpm with VCT off but running more boost?

Sorry my response wasn't detailed enough - hence the confusion.

if both were to make 500nm at 6500 with VCT on of VCT off you would assume the motor making 500nm with VCT on would have much greater cylinder pressures.

If VCT were to be turned off for motor making 500nm with VCT on, you'll get a reduced amount of torque also a reduced amount of cylinder pressure.

Motor with VCT off making 500nm, if VCT were to be turned on, you would "assume" that motor would make even more torque, i.e. 500nm+ but now with added cylinder pressure.

5 minutes ago, Dose Pipe Sutututu said:

if both were to make 500nm at 6500 with VCT on of VCT off you would assume the motor making 500nm with VCT on would have much greater cylinder pressures.

Where does the extra cylinder pressure come from, and why are we seeing no more torque as a result of it?

4 minutes ago, Lithium said:

Where does the extra cylinder pressure come from, and why are we seeing no more torque as a result of it?

Motor 1 could be a S15 motor
Motor 2 could be a S13 motor

both might be the same, but in reality they're not

4 minutes ago, Dose Pipe Sutututu said:

Motor 1 could be a S15 motor
Motor 2 could be a S13 motor

both might be the same, but in reality they're not

Wut.

I'll try one last time, but I feel like I'm being trolled or something.

OK, so lets assume this.

A "workshop" has tuned an S15 which still has VCT on and with the current tune is making 500nm at 6500rpm at the given boost level.  Timing/fuelling is optimised, but because of silly old "workshop" using VCT it throws its insides out.

The engine is rebuilt to EXACTLY the same specs it was prior to throwing it's insides out.  Lets assume that its identical in every way, pretty much as though Dose Pipe went back in time and pushed "workshop" tuner out of the drivers seat and did the tune instead.

This time the engine is tuned with VCT off at 6500rpm, timing/fuelling is optimised for the conditions, but is running an appropriately different boost level to continue to make 500nm of torque at those rpm.

Are you saying the identical engine which is Dose Pipe tuned is more likely to survive?

 

  • Like 1

I would dare say motor with more boost thrown at it with the intake cam not advanced, i.e. VCT off at 6500rpm will survive vs. motor with less boost and VCT on at 6500rpm making the same 500nm at 6500rpm.

DYOR, this is not tuning advice.

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

    • Hi, is the HKS  Tower Bar still available ? negotiable ? 🤔
    • From there, it is really just test and assemble. Plug the adapter cables from the unit into the back of the screen, then the other side to the car harness. Don't forget all the other plugs too! Run the cables behind the unit and screw it back into place (4 screws) and you should now have 3 cables to run from the top screen to the android unit. I ran them along the DS of the other AV units in the gap between their backets and the console, and used some corrugated tubing on the sharp edges of the bracket so the wires were safe. Plug the centre console and lower screen in temporarily and turn the car to ACC, the AV should fire up as normal. Hold the back button for 3 sec and Android should appear on the top screen. You need to set the input to Aux for audio (more on that later). I put the unit under the AC duct in the centre console, with the wifi antenna on top of the AC duct near the shifter, the bluetooth antenna on the AC duct under the centre console The GPS unit on top of the DS to AC duct; they all seem to work OK there are are out of the way. Neat cable routing is a pain. For the drive recorder I mounted it near the rear view mirror and run the cable in the headlining, across the a pillar and then down the inside of the a pillar seal to the DS lower dash. From there it goes across and to one USB input for the unit. The second USB input is attached to the ECUtec OBD dongle and the 3rd goes to the USB bulkhead connected I added in the centre console. This is how the centre console looks "tidied" up Note I didn't install the provided speaker, didn't use the 2.5mm IPod in line or the piggyback loom for the Ipod or change any DIP switches; they seem to only be required if you need to use the Ipod input rather than the AUX input. That's it, install done, I'll follow up with a separate post on how the unit works, but in summary it retains all factory functions and inputs (so I still use my phone to the car for calls), reverse still works like factory etc.
    • Place the new daughterboard in the case and mount it using the 3 small black rivets provided, and reconnect the 3 factory ribbon cables to the new board Then, use the 3 piggyback cables from the daughterboard into the factory board on top (there are stand offs in the case to keep them apart. and remember to reconnect the antenna and rear cover fan wires. 1 screw to hold the motherboard in place. Before closing the case, make a hole in the sticker covering a hole in the case and run the cable for the android unit into the plug there. The video forgot this step, so did I, so will you probably. Then redo the 4 screws on back, 2 each top and bottom, 3 each side and put the 2 brackets back on.....all ready to go and not that tricky really.      
    • Onto the android unit. You need to remove the top screen because there is a daughterboard to put inside the case. Each side vent pops out from clips; start at the bottom and carefully remove upwards (use a trim remover tool to avoid breaking anything). Then the lower screen and controls come out, 4 screws, a couple of clips (including 3 flimsy ones at the top) and 3 plugs on the rear. Then the upper screen, 4 screws and a bunch of plugs and she is out. From there, remove the mounting brackets (2 screws each), 4 screws on the rear, 2 screws top and bottom and 3 screws holding in the small plates on each side. When you remove the back cover (tight fit), watch out for the power cable for the fan, I removed it so I could put the back aside. The mainboard is held in by 1 screw in the middle, 1 aerial at the top and 3 ribbon cables. If you've ever done any laptop stuff the ribbon cables are OK to work with, just pop up the retainer and they slide out. If you are not familiar just grab a 12 year old from an iphone factory, they will know how it works The case should now look like this:
    • Switching the console was tricky. First there were 6 screws to remove, and also the little adapter loom and its screws had to come out. Also don't forget to remove the 2 screws holding the central locking receiver. Then there are 4 clips on either side....these were very tight in this case and needed careful persuading with a long flat screw driver....some force required but not enough to break them...this was probably the fiddliest part of the whole job. In my case I needed both the wiring loom and the central locking receiver module to swap across to the new one. That was it for the console, so "assembly is the reverse of disassembly"
×
×
  • Create New...