Jump to content
SAU Community

Recommended Posts

Hi all,

We're building a new car for the Queensland Time Attack series. Starting with a pretty much stock 1999 R34, we are adding the following bits to get the output up to around 300-350HP ATW.

We started the build yesterday (08/04/10) and hope to get it all finished in the next few weeks.

Here is the shopping list;

HKS GT-RS Turbo kit

Apexi Power FC

HKS EVC Boost Control

Nismo 480cc injectors

Nismo Spark Plugs

Nismo High Pressure Fuel Pump

Nismo Fuel Pressure Regulator

Nismo Coppermix Clutch

Nismo GT LSD TT 2-way

and here is the progress so far.

08/04/10

Dropping the car off to Ivan at Hi Power Racing

resized_DSC_1283.jpg

resized_DSC_1292.jpg

resized_DSC_1295.jpg

resized_DSC_1296.jpg

resized_DSC_1302.jpg

resized_DSC_1304.jpg

resized_DSC_1322.jpg

On the dyno for the first run

DSC_1376_550p.jpg

Dyno Sheet

Dyno_Sheet_1_550p.jpg

Video of the run here

09/04/10

Clutch is in and Nismo LSD has been fitted. Turbo goes in early next week.

resized_DSC_1381.jpg

resized_DSC_1395.jpg

resized_DSC_1401.jpg

resized_DSC_1407.jpg

resized_DSC_1412.jpg

resized_DSC_1426.jpg

resized_DSC_1427.jpg

Link to comment
https://www.sau.com.au/forums/topic/315975-project-r34/
Share on other sites

  • Replies 92
  • Created
  • Last Reply

Top Posters In This Topic

Finished in a few Weeks!!!!!

Nice, gotta love a quick turnaround.

Some nice parts you have there, Looking forward to watching the progress.

Is it going to be a track only car?

What times are you hoping you will get out of her?

Link to comment
https://www.sau.com.au/forums/topic/315975-project-r34/#findComment-5173679
Share on other sites

nice work.. will be watching ur progress

isn't the turbo too big for the 350hp atw goal? also ur dyno run was 205hp stock??

edit: my bad, ur sig had r34 gtr so i assumed that was the car u were doing the mods to..

Edited by BWRGTR
Link to comment
https://www.sau.com.au/forums/topic/315975-project-r34/#findComment-5173714
Share on other sites

Thanks for the support guys! We are planning to get to the injectors and fit up the turbo this afternoon. Pics to follow!

Duncan1 - We will keep it road registered and we hope to break into the sub-one minute bracket at QR!

BWRGTR - Yeah, the Bayside Blue GT-R we are pretty happy with, no new mods to it at the moment. The 205HP ATW also seemed a bit low, but we did hit the speed cut.

Luke_ENR34 - You might have to put a bit more work into your proposal! :D

Link to comment
https://www.sau.com.au/forums/topic/315975-project-r34/#findComment-5175800
Share on other sites

Thanks for the support guys! We are planning to get to the injectors and fit up the turbo this afternoon. Pics to follow!

Duncan1 - We will keep it road registered and we hope to break into the sub-one minute bracket at QR!

BWRGTR - Yeah, the Bayside Blue GT-R we are pretty happy with, no new mods to it at the moment. The 205HP ATW also seemed a bit low, but we did hit the speed cut.

Luke_ENR34 - You might have to put a bit more work into your proposal! :action-smiley-069:

hmm yeh 205hp is very low i think, 206kw stock (not at the wheels given, but thats ~280hp) vs rb20 165kw(~220hp) and my old 32 gtst made 200hp atw with a 3inch exhaust, fMIC and a pod filter

does the car still have stock exhaust ?

otherwise great build ! good to see some people still go for a nice amount of power instead of chasing huge numbers :wub:

I much preffer a bit less power but more response, linear delivery

Link to comment
https://www.sau.com.au/forums/topic/315975-project-r34/#findComment-5176827
Share on other sites

Day 3 12/4/10

So while I was at the workshop yesterday, the CF card in my camera exploded. Luckily, my trusty camera phone

was there for backup.

LSD & gearbox are now bolted back in, factory turbo is out & HKS GT-RS is in!

resized_IMG00219-20100412-1640.jpg

Turbo out

resized_IMG00218-20100412-1640.jpg

Old & new side by side

resized_IMG00221-20100412-1641.jpg

resized_IMG00224-20100412-1644.jpg

Turbo fitted

Link to comment
https://www.sau.com.au/forums/topic/315975-project-r34/#findComment-5177565
Share on other sites

are you guys going to remove HICAS?

We're leaving the HICAS alone at the moment, we'll take it for a spin once it's all together and see how it it feels. We'll make a decision after that if it's going to go.

Link to comment
https://www.sau.com.au/forums/topic/315975-project-r34/#findComment-5177603
Share on other sites

Should be a nice car once its complete. but I am suprised at the choice on the Little GT-RS when QR is really all about straight line poke.

What suspension / tyres etc are you guys gonna run?

Zebra, we are going for strong and reliable, rather than going for the highest output. It doesn't have to be the quickest car out there, just enough to have some fun.

Leaving the suspension alone at the moment, it has a set of racing logic coilovers now and we will probably make a few changes, but nothing yet. The wheels will be LM GT4 18 x 10 all round and as far as tyre choice, we use either Nexen, Corsa or Achilles depending on the day.

Edited by Link Auto
Link to comment
https://www.sau.com.au/forums/topic/315975-project-r34/#findComment-5179928
Share on other sites

Zebra, we are going for strong and reliable, rather than going for the highest output. It doesn't have to be the quickest car out there, just enough to have some fun.

I like your thinking with that.

Are you not going to run proper semi-slicks for the track?

Its just that you said you wanted sub 60secs on the sprint track...which is pretty damn fast.

Link to comment
https://www.sau.com.au/forums/topic/315975-project-r34/#findComment-5179945
Share on other sites

I like your thinking with that.

Are you not going to run proper semi-slicks for the track?

Its just that you said you wanted sub 60secs on the sprint track...which is pretty damn fast.

Sorry mate, I didn't include Falken Azenis that we use at track days! On standard rubber in its previous form, we have managed a 1.06.03 from this car, so we are hoping that sub 60 is within reach. If everything falls into place, it will be ready for the next track day to find out!

Link to comment
https://www.sau.com.au/forums/topic/315975-project-r34/#findComment-5180039
Share on other sites

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

    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
×
×
  • Create New...