Jump to content
SAU Community

Recommended Posts

Best flowing manifold is/was the HKS cast low mount, the only true low mount. But you'd likely not notice the advantage, I don't. A high flow makes it easier access for the turbo, but increases scrutiny from the porkers.

I'd save your $$$ and use the std manifold, get it extrude honed if you want.

BTW, to me a std manifold is a side mount.

it's either for looks or because there isn't enough space to fit it low mount.

from a performance point of view you want it low and as far back as possible (ie COG and weight distribution concerns) but for 99.9% of people it makes no difference.

I find twin low mounts more responsive. (Street / Track / Circut)

Then again twin high mounts will get you even further. (Track / Circut)

Big single high mount is more laggy but can achieve a ot higher in at the top end. (I suggest for Drag Racing).

OK now im loaded with enough info to make my desicion even harder, going low mount, single, just not sure which way to go in the material used, maybe mild steel steam pipe, maybe standard manifold.

What i need is some unobtanium.

Hmmm, Ive seen some pipes lying around that old government research facility. :P;)

You've neglected to mention desired power, drivabilty goals / turbo choice, thats where the answer is I'd say.

From what i can see/hear, theres not enough room for the low mount m.fold required if response from your larger framed turbo is needed.

If your needs are T3 hot side based, then you could save a lot of hassles, $ and time by using teh stocker.

OK now im loaded with enough info to make my desicion even harder, going low mount, single, just not sure which way to go in the material used, maybe mild steel steam pipe, maybe standard manifold.

What i need is some unobtanium.

Hmmm, Ive seen some pipes lying around that old government research facility. :happy:;)

All depends on what you want to use the car for, Daily, Street, Track (Circut / Drag)?

How much power you want to achieve?

Then work out whats the best set up.

High or low mount tends the be directly caused by the need to have more room.

i.e. a large turbo physically wont fit as a low mount.

Low mount = shorter exhaust manilfold pipes, shorter induction pipes, so better response (usualls also a smaller turbo)

High mount = longer exhaust manilfold pipes, longer/more induction piping, less response, but you can fit a much larger turbo

Basically decide on what the goals are for your engine, decide on what turbo (and manifold) and that will tell you if you need to go high mount, or if you can keep the low mount configuration.

you need to answer some questions:

1) what do you want to use the car for?

2) how much power do you want (will be partly answered by question 1)?

3) do you want the wank factor of a high mount (take into consideration that if you only want 250rwkw then a high flow is going to look dicky as a top mount)?

4) and most impotantly (for some) how much do you want to spend?

Answer these and you will have your decision made for you.

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