Jump to content
SAU Community

Recommended Posts

Had the oznats over the weekend...

The car wasnt finished but just bolted it together... need to finish the interior and the front end , side skirts etc etc

Have to sort out my traction issues. Even with slicks i cant keep the power down. If you listen to the video im constantly on and off throttle and constantly loosing traction. even on the well prepped drag strip. any ideas would be great

video-1477097823.mp4

  • 7 months later...
On 25/08/2015 at 11:21 AM, Adz2332 said:

Long time coming but i got the car tuned, again. This time by a different tuner and to say it was tuned badly seems an understatement.

Havent had a chance to take it out to the drags again but have a drift prac day coming up in 3 weeks i think, so will test it out then

attached the new dyno print out

post-33454-0-75076200-1440467476_thumb.jpg

post-33454-0-43456200-1440467490_thumb.jpg

 

Who did the good tune ?

On 28/04/2014 at 0:51 PM, Adz2332 said:

stripping down the engine at the moment. removing things i dont need and getting it ready for.....

20140425_132205_zps5265e3d5.jpg

This.....

20140425_095731_zps5d9d2432.jpg

HTA3076R

also have a trial waste gate, dump, 6boost mani and screamer

10307394_10154088892755215_2184393771918

 

I wanted an FP HTA turbo before i got mucked around and sent a wrong turbo.  Nice to see it made plenty of power

  • 4 weeks later...

Put on some AR1s  285s all round and went and did a track day at mallala on sat.

was a blast. car went really well and the tyres were excellent for the price

i now need to upgrade the brakes as it boiled its guts out and lost all braking by the end. and also get some coilovers to

But was a great day! 

19399721_10158955302765215_7190593453162086498_n.jpg

19400561_10155157369429550_3670939122459634837_o.jpg

  • 3 weeks later...

forgot to add.

had the VCT sorted working and tuned before the track day. You could see a bit of a difference on the dyno print out. but the butt dyno it made a hell of a difference. felt boost came on so much earlier and smoother. made the car so much easier to drive and so much quicker all round.

Funny how much it changed the whole feeling of the car

  • Like 1
  • 1 month later...

currently getting parts together for a rb25/30 build.

so far have a 30 block

my rb25 head, 6boost main, plazaman plenum, 1000cc injectors, computer etc etc

have to work out, pistons, bearings, rods etc

want to go big to hold 450kws ish...

 

any links or builds i should look at?

8 minutes ago, Adz2332 said:

any links or builds i should look at?

No, but we did one earlier this year so I've got a fairly good handle on what's needed. We used a stock bottom end (found an RB30 bottom end that had never been run). 

It's the little things that you'll need to sort out:

- the oil feed for the VCT (the machine shop we use has done quite a few 25/30's & knows what's needed),

-what you do with the cold start crap and associated hoses (we removed pretty much all of it, and don't regret it),

-coolant lines on the intake side (once again we got rid of some),

-the oil drain / breather on the front exhaust side (RB30 block doesn't have the port for this),

-engine mounts / raising the bonnet (we kept the mounts stock, and raised the rear of the bonnet with some spacers under the hinges - also had to ditch the strut tower brace. Didn't want to lower the mounts as we have an extended sump, and didn't want it to be the lowest part of the car),

-the dump pipe (had to cut & extend ours, as turbo was now 40mm higher),

-you'll probably need a new RB30 water pump (the RB25 one has a slotted hole, which doesn't quite cover the water channel in the block - ask me how I know),

-the intake piping (once again because the top of our engine was higher, we needed longer intake pipe silicone joiners on the intake pipes, just above the exhaust manifold. Had to buy a 1 metre length as we couldn't find the right size in smaller lengths),

-you will need to buy a second timing belt tensioner & a longer timing belt

-intake side wiring - we had to make up some extended loom mounts because the head was now higher.

 

I can't think of anything else at the moment. If you want the machine shop's contact details let me know - he's in Pooraka. We are loving the engine - the torque delivery is beautiful.

looking at some budget coils.

Monopro Type Coilovers- Street/Track

http://www.option1garage.com.au/HSD.htm

or

http://www.option1garage.com.au/BCRacing.htm

BR Series Street and Circuit Coilover

 

  • 1 month later...

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