Jump to content
SAU Community

Recommended Posts

the block has been decked.

i will take some pics when i'm there at the mechanic sometime in couple days.

I have also attached CP piston SC7305 (mine- 86.5mm 9:1CR) and SC7307 (86mm bore ans 8.5:1CR) specification, the compression height is the same. :angry:

SC7305-1.pdf

SC7307.pdf

Have you determined the compression height fom the spec sheet or by measuring the actual pistons?

Ask your engine builder if you can solve the problem with a thicker head gasket and if he doesn't know for sure ask an engine builder who knows his RBs.

If the mechanic at your local workshop is building the engine he probably doesn't have enough relevant experience and/or knowledge.

measured the CP piston today and the compression height is exactly the same as my stock piston, about 31.5mm. putting next to each other and the height from the wrist pin to the top of piston is exactly the same.

seem like people are saying the r34 block and crank are the same as r33, if everything are the same, then the machiner took off too much meat from the block (by .8-1mm is crazy).

my tommei head gasket is 1.2mm, i assume that it won't be enough right?

Get on the phone to some Gasket makers/suppliers tell them your problem and see what they come up with. You can get thicker gaskets. And FFS find an engine builder who knows how to deal with this.There must be at least one probably more in a place the size of Sydney.

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

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