Jump to content
SAU Community

Recommended Posts

Hi guys, so this week I installed the Nismo hard pipe intercooler kit on my R34 Gtr. After install took it for a drive and notice there is a boost leak and can't hold more than 0.4 bar of boost. So took the bumper off and re-tightened the clamps. The blue silicon hose that came with the kit was a bit thin so had to tighten extra hard and end up de-threading clamps.

I had no other option at the time but to put the stock hose back on and everything was working again. So my question is has anyone else installed the nismo or after market hard pipe kit with similar problem? I think because the cast alloy hard pipe is not perfectly round, with a thin silicon hose it wasn't sealing properly. So should I get a thicker silicon hose and maybe stronger clamps? Clamps that came with the kit was Murray gold seal worm drive, and the blue silicon hose is about 3mm thick.

Any help is much appreciated.

Did you buy a copy kit? If you aren't running extreme amounts of boost then good quality hose clamps and silicone is fine to use. You can use T bolt clamps and better quality silicon to aid with holding the pressure but if the kit is put together correctly then there shouldn't be any issues.

Its got to be perfectly round if using good clamps with a bead all the way around it to stop the hose slipping off.

Get rid of those worn drive clamps too and get some proper clamps.

Im surprised that nismo would produce a piping kit that's out of round, the casting looks pretty off center and average, the bead does not go all the way around.

Are you sure its genuine? Who did you buy it from?

Post up more pics of your pipes and hoses showing the nismo logos too. Your pipe doesnt have a lip all the way around which is strange because when you look at the photos from this for sale thread you can see all pipes have a lip all the way around.

http://www.sau.com.au/forums/topic/445298-nismo-intercooler-piping-kit-bnr34bcnr33-brand-new/

Edit: lol just read the for sale thread through to the end, looks like you bought the kit from that thread from nurvous?

Edited by Gts30t

Well im confused, googling more pics shows the shortest pipe, the one you have pictured does have a lip that doesnt run the whole way around. In any case i know other forum members are using this nismo kit without problems so it may just be an installation problem

Yeah, bought it from nurvous, not blaming him at all, just think I might have got a defective kit. Yeah it does have the lip, I think it's because the pipe is not true round and the silicon hose that came with the kit is a bit thin so it leaks air as it doesn't sealing properly..

It shouldn't matter if it's not perfectly round, as long as there are no dimples in it.

What's wrong with the stock piping? It is overkill for the stock power, and would probably support 600awkw at least.

It shouldn't matter if it's not perfectly round, as long as there are no dimples in it.

What's wrong with the stock piping? It is overkill for the stock power, and would probably support 600awkw at least.

Was trying to improve the response on the -5 turbos as tuner says stock rubber hose cause some lag, wasn't about power.

The whole Rubber hoses cause lag thing comes from some other other japanese cars, first that comes to mind is certain Mitsubishi, that have 1+m of rubber pipe on each end of the intercooler. GTR isn't that bad.

That being said I got a second hand Greddy kit for a good price and I can't complain. Can attach fittings to it for sensors too which is nice.

  • 4 weeks later...

Update:

Gave up and gave kit to mechanic to install, now running great with no leak, all he did was changed the broken clamps that I over tightened. Looks like it was my mechanical skills ( or lack of ) that was the issue. :rolleyes:

Then sends you the bill for something you could of fixed by paying no more than $30 for. Those style clamps are prone to breaking easily because of their shitty design. If over tightened or adjusted incorrectly, which most people tend to do, the mechanism tends to break.

  • Like 1

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