Jump to content
SAU Community

Whats the go with R31 drivers?


Recommended Posts

Guest Dragon

Driving to a clients place (Server problems) when I get stuck at a set of lights in Strathpine! (Hate that)

A R31 pulls up beside me, driver looks over (Dunno what he was looking at, tint is rather dark) lights go green and he spins the wheels taking off.

I keep pace, nudging a car length in front through first gear.

He hits second, spinning the wheels. I hit second a few seconds later (Ahh, rev limiters, what fun) I nudge another car length in front of him.

By third gear I am three car lengths in front.

Next set of lights, he 'tries' again. Again I take off nice and orderly, while he is madly wringing the poor R31's neck, spinning into each gear.

Again I get in front of him.

As his numberplate said ***-ESY He was easy to play with.

I just hope the soon to be R32 GTR goes a hell of alot better then that, otherwise I'll keep the little Q out of the wifes hands.

Stock Pulsar Q (Brand new) just has 4,000 km on the clock, not even run in yet (Working on it), eats R31's.

Shall I say 'owned' ? *Grin*

Anyways, watch out for a little white Q with a whale tail, it just might be me! (Or worse still, the hoon of a wife!) *Wink*

Link to comment
https://www.sau.com.au/forums/topic/12264-whats-the-go-with-r31-drivers/
Share on other sites

I think it's fairly naive of you to insinuate anything about a driver or model of car and all their drivers purely based on a single event.

Mabey the guy had a great night, just got head or something and was listening to some nice tracks. He was having some fun. Well done to you for having such a supreme stock and late model car. If it's such a beast then stop talkin' about it and run some quarters. You yourself infer you are a "Dragaholic". A superiority complex on the road is a dangerous thing.

And I'm sure you haven't exagerated any amount close to your level of patronisation either.

Let people have their fun (as long as it is safe naturally) and keep the self rightous crap to yourself.

/end_r31_owner_rant

yeh, would say that either his car was a peice of shit, he couldnt drive, or he wasnt trying.

Even tho all 31 drivers suck :D hehe, they are still quick cars. To give u an example, I had a squirt with Slip on our private test track in se qld, started at about 80km/h and by the time I hit 240km/h (in a 2002 wrx sti) was only just far enough in front to pull back into the right side of the 'track'.

I will admit that the R31 styling is either love it or hate it:D

Personally i love it.

And i know my car is a nightmare to get traction in with my standard rubber.

The higher models get wider rubber but 195's just dont cut it in an R31.

And i rekkon the great thing about r31's is they are cheap as and

lighter than new skylines(cheap car to start with and can pour money into when u have it)(just like my RB30DET plans)

But i dont blame R32+ drivers for lookin down on us ....cos R32+'s are a bit "nicer" after all.:D

Guest SVD001

Dear Dragon...... You wanna go on about driving abilty or how "SLOW" R31's are then just ask Slip or myself how us poor old R31 drivers went at Mt Cotton last year. Pretty much cleaned up the Turbo cars if I remember correctly. Yes the R32,s and R33,s are gorgeous cars and go hard but it's not always the car. Trust me when I say I'd be asking q's if I out dragged an R32 or R33. I do realise they are a quiker car than your average R31. The only reason I sold my R32 4 dr and bought an R31 was because I no longer pay $2000 for insurance and parts are far more available. So if this Mt Cotton thing goes ahead soon I guess we can all expect to see you there and show us just how good a driver you are. Slip and I will certainly look forward to it in our "SLOW" R31's.......

Love... SVD001

P.S. It's all good at least that we all like our Nissan's and that's all that really matters. No matter what the model...

I actually do belive this could have happened. These new little cars have some decent hp, and lightish weight, off the line they might go alright. In a highway roll on my 31 will take a Q down without a doubt.

Whats with 32 and 33 drivers? I beat them all in a time trial event at the last Mt Cotton skidpan event, you want to read into that single event that 32's and 33's are driven by uncos?

Congratulations, you beat a 6 cylinder (i think hearing that was the purpose of your post)

You enjoyed the race so don't even try to be condescending.

ps. I would like to have a couple of races with you on a 'closed road' if you like, just to see what a poor running r31 does VS a Q for myself.

Interesting to see that a Q can beat a skyline off the line though. If it was spinning into 2nd, it had crap tyres.

(not coming across defensive/angry)

some ppl (*cough* 31 owners *cough*) shouldnt get so upset. If i was driving a pulsar and beat a skyline , i reckon it would be pretty funny too. Dont forget that what you type on the net doesnt always come across as you intended it.

anyway - they both won, they drive nissans :D

Have had an R31 and now own an R33. Both the cars that have been bagged here light-heartedly.

Loved the R31 with heaps of old grunt and chirping into 2nd etc. Had to work at it, and that was part of the fun. Never showed the car an ounce of mercy and it respected me for that and never let me down.

Really enjoy the revving ease of the R33 now.

Both great ass-woopin cars

Pulsar sounds good too. All Nissans after all.

Enjoy !!!!!!!!

Laurie

hey slip, for arguments sake, if i can get my mum to let me drive her pulsar again, ill drag ya. its a 2000 Q and i know you will kick its ass....

its quick, but its not that quick.

and mum wont let me drive it cause i dragged an excel with a phat zaust tip and chirped second.

Guest Dragon

Oh my! I did ruffle some feathers, didn't I!

Let me assure you, all you R31 owners/drivers, I was not posting to gloat about some 'kill' story late one night.

I was just supprised that a stock R31 could not keep with a stock 2003 Pulsar from the line up to 100km/h

The little Pulsar's are very quick off the line, and have supprised many a larger car owner up to the legal speeds.

Yes, I do know that the R31 would pass me on a rolling start, or anything above 100km/h!

As for Mt Cotton, I have not been there, yet.

I would be 'very' interested in knowing just how well a large powerful turbo RWD car would go against a smaller, lighter FWD N/A car around such a small tight track!

SVD001, I did not say I was a good driver, I am just saying I was supprised that a new N/A Pulsar would get ahead of a N/A 6 cylinder R31.

As for going to Mt Cotton, I would like to go and have some fun. Who knows, maybe I can drive. ;)

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

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