Jump to content
SAU Community

Recommended Posts

That Bel garage Evo is quick :thumbsup: , with one of our race team drivers in it did a 1.44.572 at Eastern Creek yesterday IN THE RAIN. That was the fastest time at the Evo versus WRX Challenge, but not by much (0.05 sec). Driver's report was that it will do sub 40's in the dry with some minor sorting. Looks like my early guess that a 1.12 to 1.13 at Oran Park will be necessary to win this thing.

Cheers

Gary

I was just checking Natsoft site.

EVO V REX

Some of our customers where there racing and said he did this late in the day when it was dry.

  • Replies 1.9k
  • Created
  • Last Reply

Top Posters In This Topic

I was just checking Natsoft site.

EVO V REX

Some of our customers where there racing and said he did this late in the day when it was dry.

Not based on the drivers report, the track got oiled down when he was lined up for the last run. The time came from the earlier session when it was still wet.

Cheers

Gary

Gary so far the max amount of cars we are going to have on track at once is 12. I would profer 10 but it depends how many we have in each class etc and how long we run the sessions for.

As it stands at the moment we have almost DOUBLE the amount of EOI forms as we have entry spots as we have been limited to 70 odd entries as we want to maximize the track time we give you guys. I want to give Open Class an hour on the track and Clubsprint Class 45minutes. As it stands Open Class may very well end up being an invite only affair for this first event.

I was just checking Natsoft site.

EVO V REX

Some of our customers where there racing and said he did this late in the day when it was dry.

I was with BEL for the majority of yesterday and that time was set when the racing line was just starting to dry up. Also they were never running at full throttle that car has some very serious pace in it.

Not based on the drivers report, the track got oiled down when he was lined up for the last run. The time came from the earlier session when it was still wet.

Cheers

Gary

It should be this fast from what it has and with a race driver. Natsoft sort fo shows it was later session to?.

Individual times.

yes, and find a way to cheat! if 42s are the pace at EC I will be a long way behind!! and I thought low 50s was respectable. ;) time to admit I suck and get brisby to run back down the pit lane with my timing beacon while I lap to give me that extra few seconds a lap....

yes, and find a way to cheat! if 42s are the pace at EC I will be a long way behind!! and I thought low 50s was respectable. :D time to admit I suck and get brisby to run back down the pit lane with my timing beacon while I lap to give me that extra few seconds a lap....

bollocks, just go buy a car that does the driving for you....

Or have a serious go in the s13 ;)

yes, and find a way to cheat! if 42s are the pace at EC I will be a long way behind!! and I thought low 50s was respectable. :D time to admit I suck and get brisby to run back down the pit lane with my timing beacon while I lap to give me that extra few seconds a lap....

FARK MAN! Don't go giving away out trade secrets! ;)

Gary so far the max amount of cars we are going to have on track at once is 12. I would profer 10 but it depends how many we have in each class etc and how long we run the sessions for.

As it stands at the moment we have almost DOUBLE the amount of EOI forms as we have entry spots as we have been limited to 70 odd entries as we want to maximize the track time we give you guys. I want to give Open Class an hour on the track and Clubsprint Class 45minutes. As it stands Open Class may very well end up being an invite only affair for this first event.

Excellent, I think even a rusty nut like me can negotiate a time with 12 cars around a track the length of OP. Personally I would prefer more frequent, shorter sessions. Realistically around 3 to 5 laps is all my tyres are going to last, not to mention heat soak engine, gearbox, diff, brakes and driver. Around 10 cars and 20 to 30 minute sessions would be great. Plus the weather can play havoc at OP in July, I would hate to have the results skewed by one long session in the wet. Based on my recent master of rain attraction, that would be bad luck for the poor guys in my session.

Cheers

Gary

I was with BEL for the majority of yesterday and that time was set when the racing line was just starting to dry up. Also they were never running at full throttle that car has some very serious pace in it.

Especially considering it doesn't handle all that well, yet. :thumbsup:

Cheers

Gary

Excellent, I think even a rusty nut like me can negotiate a time with 12 cars around a track the length of OP. Personally I would prefer more frequent, shorter sessions. Realistically around 3 to 5 laps is all my tyres are going to last, not to mention heat soak engine, gearbox, diff, brakes and driver. Around 10 cars and 20 to 30 minute sessions would be great. Plus the weather can play havoc at OP in July, I would hate to have the results skewed by one long session in the wet. Based on my recent master of rain attraction, that would be bad luck for the poor guys in my session.

Cheers

Gary

Gary when I said I want to give you an hour of track time I didnt mean an hour straight. Open Class will be ( at this stage ) 3 20minute sessions which will equate to a total of 1 hour of track time.

Cheers

-Nathan

Gary when I said I want to give you an hour of track time I didnt mean an hour straight. Open Class will be ( at this stage ) 3 20minute sessions which will equate to a total of 1 hour of track time.

Cheers

-Nathan

Also excellent news. The reason for the requesting the specifics is that I have 4 or 5 guys pestering me to do set ups for them and I want to make sure I have the right format. Plus there is tyre selection criteria as well, which ultimately affects the suspension settings. The ground swell of interest I am seeing is impressive, maybe you should run 2 days, Open Class on one day and Clubsprint on the other.

Cheers

Gary

Somehow I think the BEL Garage EVO handles pretty well to do those times!!!!

I was with them the day Lofty and Dyno Dave had it at Wakey a month or so ago. Lofty was driving it and doing all of the suspension changes that the BEL boys had been mucking around with for some.

Lofty did a 1.04.2 at Wakey within 5 laps with some changes that he had made. Considering the cars previous fastest was a 1.06.0, I think the changes were in the right direction.

I was talking to both Lofty and Dyno Dave on the day and the boys said the car would do a high 1.02 :thumbsup:

Not sure if you are involved with this car at all Gary, but why do they get soooooooo many people giving input to the car. They have tried so many engineers, drivers etc......

The times that they did at the creek really don't relate to wakey. The lotus that I drive does a 5 at wakey and a 41 or 42 at the creek. I would expect the EVO to do a 40 at the creek.

Edited by Bozman1
Somehow I think the BEL Garage EVO handles pretty well to do those times!!!!

I was with them the day Lofty and Dyno Dave had it at Wakey a month or so ago. Lofty was driving it and doing all of the suspension changes that the BEL boys had been mucking around with for some.

Lofty did a 1.04.2 at Wakey within 5 laps with some changes that he had made. Considering the cars previous fastest was a 1.06.0, I think the changes were in the right direction.

I was talking to both Lofty and Dyno Dave on the day and the boys said the car would do a high 1.02 :thumbsup:

Not sure if you are involved with this car at all Gary, but why do they get soooooooo many people giving input to the car. They have tried so many engineers, drivers etc......

The times that they did at the creek really don't relate to wakey. The lotus that I drive does a 5 at wakey and a 41 or 42 at the creek. I would expect the EVO to do a 40 at the creek.

I hear you Boz. At WP the powerful cars don't get to stretch their legs as much as at OP and especially EC. I look for time comparisons between the 3 tracks often and it isn't always there. In simple terms, WP helps cars with handling and good brakes while EC punishes cars which lack horsepower. So I think the 40 at EC is a little conservative in this case.

The reports I got back were that it handled OK, not brilliant, but OK. Considering how much money it has had spent on it, it should be brilliant. It should have enough adjustabliity to be tuned for the circuit and the conditions on the day. The bottom line is it doesn't, going on the EC performance. But my expectations are high, I aim for perfection within the budget constraints.

I am not sure what the owner is looking for or even whether they have a structured plan for development or racing. From the outside it looks a little random, although I suspect the clash of dates last weekend may have altered the driver plans.

Cheers

Gary

Somehow I think the BEL Garage EVO handles pretty well to do those times!!!!

I was with them the day Lofty and Dyno Dave had it at Wakey a month or so ago. Lofty was driving it and doing all of the suspension changes that the BEL boys had been mucking around with for some.

Lofty did a 1.04.2 at Wakey within 5 laps with some changes that he had made. Considering the cars previous fastest was a 1.06.0, I think the changes were in the right direction.

I was talking to both Lofty and Dyno Dave on the day and the boys said the car would do a high 1.02 :thumbsup:

Not sure if you are involved with this car at all Gary, but why do they get soooooooo many people giving input to the car. They have tried so many engineers, drivers etc......

The times that they did at the creek really don't relate to wakey. The lotus that I drive does a 5 at wakey and a 41 or 42 at the creek. I would expect the EVO to do a 40 at the creek.

Yep another fast car then joining the pack. Will be great as long as not as quick as the Slot Car, all good. He he.

What power has it got and mods? I hear it is a rolling carbon fibre parts shop?

Edited by Boosted Zed
Guest
This topic is now closed to further replies.



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