Jump to content
SAU Community

Recommended Posts

cheers for the extended response daniel :)

As a note the sump holes are at 10.8mm drill them to 12mm there is plenty enough meat there,with this done I am sure there will be wiggle room so they will all line up.

Is this 'slop' detremental to the holding ability of the bolts? Another way i can see it working, is bolt the plate to the sump, and drill out the holes in the plate through into the sump to take an M12 bolt. This way there won't be any 'slop' in the hole in the sump side. Although this may only work if the holes in the plate are currently M10.

I'm at work and home is a 45min train ride away, so cant confirm if this will work until i get home tonite.

yes this may work shane however if you go to m12 at least 3 of the bolts in the diff side will have ot be sacrificed as there is not enough meat on block to go all the way to a m12 bolt!!! the clamping pressure will be maintained as long a 40% of a bolt heads surface, and thats not meaning the hole bolt heads surface just the clamping area, is in contact with a the clamping surface... while the sump is heavy there is far beyond adequate bolting points the main reason for so many bolts is not to make it stronger but to prevent the sump leaking, its to pull the surface down evenly and prevent air or in this case liquid gaps. In theory and in accordance with Australian design standards you could easily hold that sump to the bottom of that motor with 4 bolts correctly positioned and pressured, you wouldnt, but there is adequate bolts there, the slop as you call it you may create will have no detramental effects on the strength or effectiveness of the sump bolting to the plate.

Cheers

Edited by Fitzpatrick Speed Works
yes this may work shane however if you go to m12 at least 3 of the bolts in the diff side will have ot be sacrificed as there is not enough meat on block to go all the way to a m12 bolt!!! the clamping pressure will be maintained as long a 40% of a bolt heads surface, and thats not meaning the hole bolt heads surface just the clamping area, is in contact with a the clamping surface... while the sump is heavy there is far beyond adequate bolting points the main reason for so many bolts is not to make it stronger but to prevent the sump leaking, its to pull the surface down evenly and prevent air or in this case liquid gaps. In theory and in accordance with Australian design standards you could easily hold that sump to the bottom of that motor with 4 bolts correctly positioned and pressured, you wouldnt, but there is adequate bolts there, the slop as you call it you may create will have no detramental effects on the strength or effectiveness of the sump bolting to the plate.

Cheers

The bolts on the diff side are fine, so they dont need to be changed to M12. I was referring to the 2 studs in the sump on the non-diff side. I've attached a pic and i've put a few details on. The measurements aren't 100% accurate, but are close, so i don't think there will be any problems changing the 2 M10 holes to M12 ones, will there?

adapterplateaye9.th.jpg

Oh, and before i forget again, in ur instruction book u say the tapped holes in the plate and the bolts u supply have a thread pitch of 1.50, but they actually are 1.25 thread pitch, just thought i'd let you know :(

Guys;

A number of posts on the very good GTROC UK RB30 thread refer to RB ignition scatter at >4500 rpm due to the CAS set up.

The last few pages describe a problem whereby there is significant ignition scatter due to cam belt flex affecting the CAS, and in particular the crank flex affecting the crank pulley and in turn the cam bet and CAS even more at high RPM + load.

A Datalog example to illustrate the problem is provided.

Theory seems to be that this can be alleviated by use of a crank trigger or ring gear trigger which makes sense, but the existence of the problem in the first place interests me. The thread is here;

http://www.gtr.co.uk/forum/upload/52458-rb...ight=r32+combat

I'm not viewing their findings either way as I haven't heard of it before, but there appears to be some evidence to support their argument.

Can anyone shed some light on this?

Cheers

Hey guys, about to start on an RB30 build & have got most of it sussed from reading this thread except when using the standard RB30E bottom end compression seems to be around 8.2:1 & was wondering if theres an easy way to bump this up a little? most people seem to be using an RB26 head gasket so would i be able to use an aftermarket metal gasket from tomei, hks or similar thats is slightly thinner to lift compression? does anyone know the thickness of a standard RB26 head gasket? ideally aiming for compression ratio between 8.5:1 - 9.0:1

Cheers in advance...

No can do.. Grab your self a set of aftermarket pistons that suit the comp ratio you are after.

Either that or be happy with a few more $$ in your pocket and an 8.2:1 comp ratio.

----------

McStocky... Very nice indeed. Does it drive? :rolleyes:

No can do.. Grab your self a set of aftermarket pistons that suit the comp ratio you are after.

Either that or be happy with a few more $$ in your pocket and an 8.2:1 comp ratio.

----------

Damn! is there any particular reason for this? i know there is varying thicknesses of aftermarket headgaskets.. is there a mechanical reason why this wont work? no budget for aftermarket pistons unfortunately this was my last hope.

Guys;

A number of posts on the very good GTROC UK RB30 thread refer to RB ignition scatter at >4500 rpm due to the CAS set up.

The last few pages describe a problem whereby there is significant ignition scatter due to cam belt flex affecting the CAS, and in particular the crank flex affecting the crank pulley and in turn the cam bet and CAS even more at high RPM + load.

A Datalog example to illustrate the problem is provided.

Theory seems to be that this can be alleviated by use of a crank trigger or ring gear trigger which makes sense, but the existence of the problem in the first place interests me. The thread is here;

http://www.gtr.co.uk/forum/upload/52458-rb...ight=r32+combat

I'm not viewing their findings either way as I haven't heard of it before, but there appears to be some evidence to support their argument.

Can anyone shed some light on this?

Cheers

I have seen lots of vibration/resonance with cam belts on various rb motors especially on rb30/26/25 with the additional cam belt length. We have even changed from using the standard CAS to a dedicated crank signal with the sync still on the cams with one motec system. I honestly felt there was no problem though with the timing control using both methods. I have however seen large timing variance (10-15deg) within the actual CAS spline/half moon key and I reckon this is what they are describing.

Damn! is there any particular reason for this? i know there is varying thicknesses of aftermarket headgaskets.. is there a mechanical reason why this wont work? no budget for aftermarket pistons unfortunately this was my last hope.

Try to find an aftermarket headgasket thats thinner than 0.040".

Then there's the issue of high rpm and the pistons kissing the head.

You might get away with a 0.010" thinner headgasket but its not going to raise the compression a great deal.

Try to find an aftermarket headgasket thats thinner than 0.040".

Then there's the issue of high rpm and the pistons kissing the head.

You might get away with a 0.010" thinner headgasket but its not going to raise the compression a great deal.

Cheers cubes :) from memory a 1.2mm metal head gasket gives no change in compression on an RB26 so hopefully goin to a 1.00mm headgasket will bump it slightly, havent seen any thinner than that yet for obvious reasons .

Does anyone know the formula for working out what the compression ratio will be with a standard 30e block & r32 RB25DE head with a 1.0mm metal head gasket??

Also is there any factory valve springs that interchange with R32 RB25DE that can withstand 300rwkw? have seen stock springs float badly at 260rwkw. would RB20DET Springs be an upgrade? or RB26 etc.

Cheers.

I have seen lots of vibration/resonance with cam belts on various rb motors especially on rb30/26/25 with the additional cam belt length. We have even changed from using the standard CAS to a dedicated crank signal with the sync still on the cams with one motec system. I honestly felt there was no problem though with the timing control using both methods. I have however seen large timing variance (10-15deg) within the actual CAS spline/half moon key and I reckon this is what they are describing.

They seem quite convinced it's to do with belt flex, but what you say re timing variance and the CAS spline is interesting and could well be the problem, as you suggest. Did you pursue a solution to eleiminate this?

The RB20DET valve springs are no upgrade, they are what you have now. Just the RB25de valves are larger so they need thougher valve springs.

1.2mm headgasket will lower compression.. 1mm headgasket is standard 0.040". To work out the comp ratio correctly you need to make measurements, i.e rip the motor apart.

They seem quite convinced it's to do with belt flex, but what you say re timing variance and the CAS spline is interesting and could well be the problem, as you suggest. Did you pursue a solution to eleiminate this?

Replace camshaft and CAS - good as new. I wish I had of taken a picture of it as I diagnosed a car the other day, it just looks like the spline wears along the side where it engages onto the cam as for reasons I'm not sure as the car didn't have that many k's on it if you can believe an import odometer reading.

The rb's have been around for ages and there has been alot of rb30/26's as well cant really see me not noticing a 10deg timing variance on a full throttle ramp let alone all the other tuners out there or anyone with a bit of an idea.

i got my heap of junk dynoed for a bit today, just a quick check to make sure it was OK. fixed the AFR's back to 12:1 and didn't play with timing much at all. total of 1.5 hours on the dyno, 225rwkw at 9psi. graph and stuff can be seen here --> http://www.skylinesaustralia.com/forums/in...howtopic=104332

Guys;

A number of posts on the very good GTROC UK RB30 thread refer to RB ignition scatter at >4500 rpm due to the CAS set up.

The last few pages describe a problem whereby there is significant ignition scatter due to cam belt flex affecting the CAS, and in particular the crank flex affecting the crank pulley and in turn the cam bet and CAS even more at high RPM + load.

A Datalog example to illustrate the problem is provided.

Theory seems to be that this can be alleviated by use of a crank trigger or ring gear trigger which makes sense, but the existence of the problem in the first place interests me. The thread is here;

http://www.gtr.co.uk/forum/upload/52458-rb...ight=r32+combat

I'm not viewing their findings either way as I haven't heard of it before, but there appears to be some evidence to support their argument.

Can anyone shed some light on this?

Cheers

There are in fact a number of problems that cause this sort of crap (suggested solutions in brackets);

1. Loose cambelt (re-tension the cambelt)

2. Poor relocation of the cambelt tensioner (mount them properly when you build the engine).

3. Worn camshaft/CAS interface (replace the worn components)

4. Poor choice of ECU, some ECU’s only use one of the trigger signals and therefore have no cross reference for “noise” elimination (if possible use the standard triggers with an ECU that has that capability).

5. Some ECU’s require the replacement of the standard trigger wheels, because they can’t interpret the standard CAS signals (select a more appropriate ECU in the first place.) (If you MUST use a high end ECU, then include the cost of separate crank and camshaft triggers).

6. Poor quality rewiring, insufficient “noise” insulation/suppression, low quality patch harnesses, ill fitting piggy back plugs, faulty wiring etc etc (use a plug and play ECU, like a Power FC or get a professional to do the engine wiring harness if using a high end ECU).

This is not all exclusive to RB30’s, I have seen all but #2 on other RB’s.

:( cheers :(

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

    • Any update on this one? did you manage to get it fixed?    i'm having the same issue with my r34 and i believe its to do with the smart entry (keyless) control module but cant be sure without forking out to get a replacement  
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if something was binding the shaft from rotating properly. I got absolutely no voltage reading out of the sensor no matter how fast I turned the shaft. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if shttps://imgur.com/6TQCG3xomething was binding the shaft from rotating properly. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • perhaps i should have mentioned, I plugged the unit in before i handed over to the electronics repair shop to see what damaged had been caused and the unit worked (ac controls, rear demister etc) bar the lights behind the lcd. i would assume that the diode was only to control lighting and didnt harm anything else i got the unit back from the electronics repair shop and all is well (to a point). The lights are back on and ac controls are working. im still paranoid as i beleive the repairer just put in any zener diode he could find and admitted asking chatgpt if its compatible   i do however have another issue... sometimes when i turn the ignition on, the climate control unit now goes through a diagnostics procedure which normally occurs when you disconnect and reconnect but this may be due to the below   to top everything off, and feel free to shoot me as im just about to do it myself anyway, while i was checking the newly repaired board by plugging in the climate control unit bare without the housing, i believe i may have shorted it on the headunit surround. Climate control unit still works but now the keyless entry doesnt work along with the dome light not turning on when you open the door. to add to this tricky situation, when you start the car and remove the key ( i have a turbo timer so car remains on) the keyless entry works. the dome light also works when you switch to the on position. fuses were checked and all ok ive deduced that the short somehow has messed with the smart entry control module as that is what controls the keyless entry and dome light on door opening   you guys wouldnt happen to have any experience with that topic lmao... im only laughing as its all i can do right now my self diagnosed adhd always gets me in a situation as i have no patience and want to get everything done in shortest amount of time as possible often ignoring crucial steps such as disconnecting battery when stuffing around with electronics or even placing a simple rag over the metallic headunit surround when placing a live pcb board on top of it   FML
    • Bit of a pity we don't have good images of the back/front of the PCB ~ that said, I found a YT vid of a teardown to replace dicky clock switches, and got enough of a glimpse to realize this PCB is the front-end to a connected to what I'll call PCBA, and as such this is all digital on this PCB..ergo, battery voltage probably doesn't make an appearance here ; that is, I'd expect them to do something on PCBA wrt power conditioning for the adjustment/display/switch PCB.... ....given what's transpired..ie; some permutation of 12vdc on a 5vdc with or without correct polarity...would explain why the zener said "no" and exploded. The transistor Q5 (M33) is likely to be a digital switching transistor...that is, package has builtin bias resistors to ensure it saturates as soon as base threshold voltage is reached (minimal rise/fall time)....and wrt the question 'what else could've fried?' ....well, I know there's an MCU on this board (display, I/O at a guess), and you hope they isolated it from this scenario...I got my crayons out, it looks a bit like this...   ...not a lot to see, or rather, everything you'd like to see disappears down a via to the other side...base drive for the transistor comes from somewhere else, what this transistor is switching is somewhere else...but the zener circuit is exclusive to all this ~ it's providing a set voltage (current limited by the 1K3 resistor R19)...and disappears somewhere else down the via I marked V out ; if the errant voltage 'jumped' the diode in the millisecond before it exploded, whatever that V out via feeds may have seen a spike... ....I'll just imagine that Q5 was switched off at the time, thus no damage should've been done....but whatever that zener feeds has to be checked... HTH
×
×
  • Create New...